SYMPTOM:
When attempting to connect to the Strategy Intelligence Server in 3-tier, the user is alerted that the login failed without further details.
On attempting to log in again, the Strategy Intelligence Server may be shown as not running. The DSSErrors.log on the server contains the following lines in different sections:
ConfigManager::GetServerDefSetting(): ServerDef not initialized: Long SettingId=75. PUManager::InitPUs: get_ProcessingUnits from ICDSSServerDef failed: 0x00000000 MsiSessionManager: NULL or Empty Authorization Server.
CAUSE:
The error indicates that the Server Definition has not been initialized correctly. The issue itself may not occur until the Strategy Intelligence Server is restarted.
ACTION:
This issue can be resolved by re-configuring the Strategy Intelligence Server to use the existing server definition.
This will force the server to re-load the correct server definition the next time the server is restarted. By setting the server to use the existing server definition, existing server level settings are also preserved.
- Launch the Strategy Configuration Wizard on the Strategy Intelligence Server machine.
- In the Configuration Wizard, select 'Set up Strategy Intelligence Server' and click on Next.
- In the next two screens, select your existing metadata DSN, and provide your Strategy Authentication.
- In the "Server Definitions" screen, select the "Use the selected Server definition as active".
- In the "Existing Server Definitions" box, select your current server definition.
- Click Next, and follow the steps in the Wizard to the final stage.
- The final stage will restart the Intelligence Server, forcing it to load the existing server definition again.