on 06-24-2016 3:13 PM
Hello experts,
After a V2V move of a BPC MS 10.0 SP17 server and its SQL server, I am having issues connecting to the new SQL server. After the old SQL server is taken offline, BPC Server Manager throws this error message and fails to launch:
And the OsoftSendGovernor service is stuck on starting and never actually starts:
The new server parameters (SQL Server: SVCSQLAPPCLUS02 port: 51436, OLAP Server: SVCSQLAPPCLUS02 port: 2383) have been updated in Server Manager, and I have checked the registry values as well as updated OutLookSoft.config and Web.config with the new value: SVCSQLAPPCLUS02:51436
However, the connection still fails. If I bring the old SQL server online, BPC Server manager and the services start without issue.
What am I missing?
BR,
Andreas
These two services are using a preconfigured domain user id.
Most likely that user ID has no rights in the new SQL server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Stefan,
I've disabled Shared Memory and Named Pipes on both the the 32 and 64-bit connections and updated the default port to 51436 (the SQL Server instance port) for TCP/IP. The problem still persists, however, although the error message when launching Server Manager has changed slightly:
/Andreas
User | Count |
---|---|
16 | |
4 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.