Technical FAQs

Ask a Question

Unable to start the Powerlogic Network Server Service due to Windows error 1053

Goals and Symptoms

The user is unable to start the Powerlogic Network Server Service due to Windows error 1053.

Causes and Fixes


The following list details the known causes for error 1053 in order of likelihood:

1. The Powerlogic Network Server service must be associated with an administrator account. Verify that the service is attempting to be started with an administrator account. If it is not run the SMS Admin Utility to resolve.
Note: If the administrator account associated with the service has a changed password, the admin utility will need to be run to resolve the issue as well.

2. A process associated with the Powerlogic Network Server Service is currently running. Open the Windows Task Manager > click on the Processes tab > click on Image Name to sort the processes alphabetically > and search for PLNsrvr.exe, PLCommsDBP.exe and, PLEvtsrv.exe. If they are running select the process and click end process. Once these processes are stopped attempt to start the Powerlogic Network Server service.

3. The SQL remote connections are set to local connections only. To resolve set to Local and remote connections, typically using TCP/IP only, however; this will vary depending upon the setup of the network:
NOTE: SQL 2005 only and all of the Powerlogic Services must be stopped BEFORE making changes. This error may also be detected via the SQL error log (default location = C:\MSSQL2005\MSSQL.1\MSSQL\LOG). Below is a screen shot of the errors encountered in the SQL error log:

To access the SQL surface area configuration screen navigate to Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration > Click on Surface Area Configuration for Services and Connections > Remote Connections.

Set to Local and remote connections:

4. The SQL Browser Service is disabled via the SQL Server Surface Area Configuration. Notice the screen shot above and the item labeled SQL Server Browser, expand this and set to Automatic then run the service. NOTE: The PowerLogic Services must be stopped BEFORE performing these changes.

Was this helpful?
What can we do to improve the information ?