Print Audit Service not starting when Server boots
Copy Audit Communicator or Database Communicator service doesn't start when the server is rebooted.
If the database back end for the Print Audit service is MS-SQL, it's possible that the Print Audit service may fail to start because the MS-SQL services haven't fully started.
You can make Windows services dependent on other services to start first.
- Open the registry editor. Go to Start and type regedit in the search field.
- Locate the Registry Key for the Print Audit Service(s) that you want to delay. They should be under one of the following keys:
- Right click on the entry and select "New --> String Value".
- Name the value "DependOnService".
- Give it the name of the MS-SQL service (usually MSSQLSERVER).
- Exit the Registry.
- Go to Administrative Tools --> Services.
- Locate the Print Audit Service and double click on it.
- Click on the "Dependencies" tab.
- You should see "SQL Server (MSSQLSERVER) in the dependencies window.
Note: Some of the values may differ depending on the version of Windows, Print Audit and MS-SQL.
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. Use Registry Editor at your own risk. You should back up the registry before making any changes to it.
To backup a selected key in the registry, use these steps:
- Click Start, and then click Run.
- In the Open box, type regedit.exe, and then click OK
- Locate and then click the key that contains the value that you want to edit
- Right-click on the key and choose Export.
- In the Save in box, select a location where you want to save the Registration Entries (.reg)
- In the File name box, type a file name, and then click Save.
How did we do with this article?