Troubleshooting

To troubleshoot the following start_primavera.bat error:

WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Access to domain '<domainName>' for user ‘<username>' denied.

Ensure that the userConfigFile and userKeyFile variables entered in the start_primavera.py file point to a valid path and file name for the primaveraConfig.secure and primaveraKeyfile.secure files.
Ensure that the node manager username and password are correct:
1. Start the AdminServer for the WebLogic Domain.
2. Launch the WebLogic Administrative Console.
3. In the Change Center pane of the Administration Console, click Lock & Edit.
4. Under the Domain Structure pane, select the link for your domain name.
5. Select the Security tab and then select the Advanced Options link.
6. Enter the valid credentials in the console for NodeManager username and NodeManager password.
7. Activate the changes.
8. Logout of the WebLogic Administrative Console.
9. Stop the AdminServer for the WebLogic Domain.
10. Retry executing the start_primavera.bat file.

For the following error, the managed server did not start using the Node Manager and you need to create a startup.properties file before you can start the managed server using WLST Scripting.

weblogic.management.ManagementException: Booting as administration server, but servername, <ManagedServerName>, does not match the administration server name, AdminServer.

To create a startup.properties file:

Start the AdminServer for the WebLogic Domain.
Launch the WebLogic Administrative Console.
Under the Domain Structure pane, select 'servers' link.
On the Servers page, select the Control tab.
Select Startup.
Once the server is in a running state, on the Servers page, select the Control tab.
Select Shutdown.
Verify the startup.properties file is in the weblogic_home\user_projects\domains\<domain>\servers\<managedServer>\data\nodemanager directory. You can now startup through the WebLogic scripting files.

Related Topics