SP09 upgrade fails

[Former Member]

Hello,

we were running BPC NW 7.5 SP07 Patch 1 (CMS mode) and tried to upgrade to SP09.

Both the ABAP addon upgrade and the .NET application server component upgrade were finished without any errors.

Unfortunately we have some errors now and cannot use the system anymore.

1. When we try to run the BPC Server Manager it is just not starting. We can see the initial start screen but thatu2019s it. Nothing else happens.

2. We cannot open the Launch page. We get an error message: u201CThe resource cannot be found.u201D

3. We cannot logon or get server information via Connection Wizard. But there is no error message.

We do not have any errors in Windows error logs or in ST22.

Our guess is that somehow the connection between the .NET application server and the CMS server is corrupt. On the other hand, we can logon to Business Objects CMC with the BPC_SYSADMIN and BPC_ADMIN user, so the connection between CMS and the ABAP server works fine.

Does anyone has an idea how to investigate this error in more detail? Anyone had this already?

Is there anything else we need to do after installed SP09? Something in the BW backend?

Thanks for your help.

Kind regards

Georg Renz

[Former Member]

Hi Georg

Could you list down your .NET framework version that are installed on your BPC server?

Halomoan

[Former Member]

Hello,

I've just found this SAP note, which looked like it could be my problem:

1571939 - Internet Information Services 7 Rapid Fail Protection feature locks Business Planning and Consolidation Application Pool

Unfortunately it did not solve my issue. Any idea?

Thanks.

Kind regards

Georg Renz

[valeriocicchiel]

Hello Georg,

did you restart IIS after patching the BPC Server? Try to reboot the server as a second option.

Does the Windows event viewer give more details about the error? Does the BPC log give more details?

I would suggest to redo all the BPC server post installation activities as the last option

Regards,

Valerio

[Former Member]

Hello Valerio,

yes we restarted IIS and we also rebooted the server. Unfortunately it didn't make any difference.

In the windows event viewer there was no log entry. Also no errors in ST22. Which BPC logs do you exactly mean?

Thanks.

Kind regards

Georg

[Former Member]

Hi Georg,

Before you did the upgrade did you backup the serverconfiguration.config file on the .NET server?

Can you change that file manually to remove the CMS configuration and see if that fixes the issue? Have you resolved this yet?

Cheers, Scott

[Former Member]

Hi Scott,

thanks for your answer. Unfortunately we did not backup the serverconfiguration.config file. But I will have a look and compare it to our working Q-System - which runs in CMS mode.

Is there somewhere a documentation on this serverconfiguration.config file?

Thanks a lot.

Kind regards

Georg

[Former Member]

Hi Georg,

There is unfortunately no documentation on the format of this file. This is the file that stores all of the settings that you configure inside of the Server Manager.

Do look at the configuration settings in the file on your Q Server... I bet by just eyeballing it you will be able to remove the setting.

Good luck.

Cheers, Scott

[Former Member]

Hi Scott,

I found the serverconfiguration.config and compared it to the one from our Q-system. Unfortunately it looks ok, besides a different IP and system name etc. everything looks the same. So I believe the file is not the problem.

You said I should try to remove the CMS mode authentication. Why would I like to do that? We used CMS mode before the upgrade and it worked fine. We still using it on the Q-system and there is no way we will switch back to AD.

So I need to find a solution with CMS mode enabled. Any other ideas?

Thanks.

Best regards

Georg

[Former Member]

Hi Georg,

The only other thing I can think of without seeing your system is that something got hosed during the actual .NET installation. Did you do a fresh installation or did you upgrade your existing system? I usually do a clean installation of the server meaning I do a full uninstall and new install instead of using the upgrade feature. The upgrade feature of the installer could work fine now but I have had so many problems with it in the past that I am now hesitant to even use it.

If you used the upgrade mechanism go ahead and uninstall and reinstall from a clean Windows Server.

Cheers, Scott