Search only in titles

---

Troubleshooting

Starting and Stopping Servers > Configuring the Node Manager to Start and Stop Servers > Using the WebLogic Scripting Tool on Windows

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.

1. 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.
2. Launch the WebLogic Remote Console.
3. Ensure that the password is correct for the WebLogic user:
   1. In the NavStrip, click Security Data Tree.
   2. In the Navigation Tree, expand Realms, expand myrealm, expand Authentication Providers, expand DefaultAuthenticator, then click Users.
   3. In the Content Pane, click the weblogic user.
   4. In the Use this page to change the description for the selected user area, click Password, then in the New Password field, enter the password for the WebLogic user.
   5. Click Save.
4. Ensure that the node manager username and password are correct:
   1. In the NavStrip, click Edit Tree.
   2. In the Navigation Tree, expand Environment and click Domain.
   3. In the Content Pane, click the Security tab, then click the General tab and select the Show Advanced Fields option.
   4. In the Node Manager Username field type the username for the WebLogic user.
   5. In the Node Manager Password field, type the password for the WebLogic user.
   6. Click Save.
5. Click Click to view shopping cart actions, and select Commit Changes.
6. Stop the AdminServer for the WebLogic Domain.
7. Retry executing the start_primavera.bat or start_primavera.sh 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:

1. Start the AdminServer for the WebLogic Domain.
2. Launch the WebLogic Remote Console.
3. In the NavStrip, click Monitoring Tree.
4. In the Navigation Tree, expand Environment then click Servers.
5. On the Servers page, select the server for which you want to create the startup.properties file.
6. Click Start.
7. Once the server is in a running state, on the Servers page, select the server again, then click Shutdown.
8. 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

Using the WebLogic Scripting Tool on Windows

Starting the Node Manager with WebLogic

Starting an Administration and Managed Servers Using WLST With Node Manager

Adding the start_primavera.bat to the Windows Task Scheduler

Executing the start_primavera.bat file

Using WebLogic Scripting to Stop the WebLogic Domain for P6 EPPM

---

Last Published Wednesday, February 25, 2026