Upgrading from SP2 Patch 11 to SP3 Patch 4 fails

[TomNather]

I have tried a lot of different paths to try and upgrade my webserver from SP2 Patch 11 to SP3 Patch 4.

Everytime the install flashes up Warning: If this installation continues, fixes may be removed from the system. I have checked KB 3033384 and the upports list has SP3 Patch 5 (which has not been released) as the upport from SP2 Patch 11. So this doesn't seem like a solution.

I have been following the SP2 code line for 4.3 until the SP3 code stabilized enough that I could get my testing done without processes failing. We would like to get our training done on SP3 but with no upgrade path from SP2 guess we have no choice but to stick with SP2. Redoing webservers I don't feel is an option since SAP offers upgrades.

SAP put this out in April 2023 that the last patch for SP2 is Q2 2023 with Patch 13. So customers need an upgrade path, but I need some help in moving to SP3.

Support Pack End of Life Dates

Any suggestions? I have tried SP3 patch 3 which failed, should I go to SP 3 Patch 0?

[TomNather]

this question is for 4.3 and not 4.2.

[ayman_salem · Accepted solution]

So the problem with https was due to misconfiguration of https in server.xml and after fixing it it works

...

The error you see in the log file is related to the SAML configuration, has no impact on others and can simply be ignored.

14:03:04.316 [main] ERROR org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider - Error occurred while attempting to refresh metadata from '/WEB-INF/idp-meta-downloaded.xml'
org.opensaml.saml2.metadata.provider.MetadataProviderException: Metadata file '/WEB-INF/idp-meta-downloaded.xml' does not exist

[Luc_G · Accepted solution]

Hello

Upgrading from 4.3 SP2 to 4.3 SP4 patch 11 and I have the same issue.

https/http CMC is working

https/http BI LaunchPad is NOT working

I have performed all the steps to reconfigure SSL but still got the same issue.

I'm using WebSphere not the Tomcat embedded.

Can I have some details about the solution here ?

Many thanks

Luc

[CHickman72]

Hi Tom

If you deactivate SSL, does this work? How did you generate your SSL CSR? Did you include the SAN parameters in the command line?

I've seen that idp error in the logs before even without saml configured. It can likely be ignored at this point but looked at later.

I am happy to help look at this with you if you prefer.

Chris

https://www.linkedin.com/in/chickman

chris.hickman@bluelineinsights.com

[TomNather]

I don't have SAML configured at all. This is strictly Windows AD/Kerberos.

And this has worked 4 times in SP2 with no issues. If you have a SAML config KB article post it here and I can start checking.

I have HTTPS/8443 configured and that is what is broke.

[ayman_salem]

Contact me via LinkedIn and I can explain more to you. (You don't need to configure saml and can ignore the error in the log file.)

[TomNather]

14:03:04.316 [main] ERROR org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider - Error occurred while attempting to refresh metadata from '/WEB-INF/idp-meta-downloaded.xml'

org.opensaml.saml2.metadata.provider.MetadataProviderException: Metadata file '/WEB-INF/idp-meta-downloaded.xml' does not exist

If I can find out where this is coming from my https would work. 8080 works CMC non https works. Just this.

Are you running your webservers on windows or linux? But I am coming from 4.3 SP2 patch 11

[ayman_salem]

As I said earlier, the error you see in the log file is related to the SAML configuration, doesn't affect others and just ignore it.

I have many test environments. (Linux and Windows).

There is no difference if you come from SP2 P11 or from my SP2 P300 system.

If you want you can contact me via LinkedIn.

[TomNather]

We are currently running 4.3 SP2 patch 11. The problem is SP3 Patch 4 breaks my https connection.

I was working with SAP Support and found the the CMC works (Enterprise login) 8080 works but try https/8443 and that gets a 404 error.

[ayman_salem]

I am already update the system from 4.3 SP2-P300 to 4.3 SP3-P400 with no problems using https.

...

Did you have the error by logon?

[former_member595655]

Hello,

We have recently upgraded from BO 4.2 SP07 to BO 4.3 SP03 with no issues.

May be you can upgrade from BO 4.2 SP03 to BO 4.2 SP07 and then to BO 4.3 SP03 Patch 400 which is the latest.

Regards,

Ambarish.

[ayman_salem]

No, the update/upgrade can be carried out directly and without intermediate steps.

[TomNather]

And there lies the issue. I don't use SAML I use Windows AD/Kerberos.

I can't ignore them because Tomcat will not come up, big problem.

Never in my 25 years of working with Business Objects have I ever seen something like this.

[ayman_salem]

No, the Tomcat worked without any problems.

I already did the installation and it works. (If it doesn't work for you, there is another cause than this error)

[TomNather]

So what you saying is

1. SP2 patching is lagging SP3? Based on the screen shot SAP is not meeting this timeline of last SP2 patch Q2 2023, which drove me to move to SP3.
2. Because the toolbar changes in SP3 and based on SAPs timeline pushes me to move to SP3 for training to be developed

So why would I be getting these errors when I load SP3 patch 4?

14:03:04.316 [main] ERROR org.opensaml.saml2.metadata.provider.AbstractReloadingMetadataProvider - Error occurred while attempting to refresh metadata from '/WEB-INF/idp-meta-downloaded.xml'

org.opensaml.saml2.metadata.provider.MetadataProviderException: Metadata file '/WEB-INF/idp-meta-downloaded.xml' does not exist

[ayman_salem]

The errors shown in the log file are related to the configuration of SAML

If you are using SAML, complete the configuration. Otherwise you can ignore them.

[ayman_salem]

Tom, this is not an installation error but a warning that some fixes are not yet included in this patch.

In your case, some fixes made in 4.3 SP02-P1100 are not included in 4.3 SP03-P400.

You can read the 4.3 SP02 release notes and the list of fixes made in P1100 that are relevant to you and may have prevented you from completing your training properly. (Note that some issues do not affect SP03), and see if already fixed in SP03 Patch 100-400.

(e.g. the "Save As" issue in Web Intelligence (KBA 3294952) which was fixed in SP02-P1100 was already fixed in SP03 -P200 etc.)

Then you can decide whether you update your system to 4.3 SP03-P400 and do your training or wait for Patch 500 (week 29/2023).