This is caused by a file within Service Manager not matching the Crystal Runtime file installed during the original setup. Open the Service Manager installation folder, usually at:
C:\Program Files (x86)\Access Applications\Service Manager
Open another File Explorer window and go to the Crystal Runtime installation folder, usually at:
C:\Program Files (x86)\Business Objects\Common\3.5\bin
Both folders contain a file called CRPE32.DLL. If the two files don't match, Service Manager won't be able to print. To fix this:
Make a copy of the CRPE32.DLL file in the Service Manager installation folder.
Copy CRPE32.DLL from the Business Objects folder.
Replace the file in the Service Manager folder with the copy from Business Objects.
If this doesn't work, check how you are logging in compared to how your username is saved. For example, if your username is saved as John Doe but you log in as JOHN DOE, this can cause the issue. Use exactly the same uppercase or lowercase characters as your saved username. If the issue persists, make sure you are logging in using the same ODBC data source as a working computer — using SQL Server Native Client instead of SQL Server is a common cause. Ask your IT team to check this.