This is caused by a file within the Service Manager install not matching the same file that has been installed by crystal runtime when Service Manager was initially installed.
Navigate to where Service Manager has been installed, this is usually:
C:\Program Files (x86)\Access Applications\Service Manager
And in another file explorer window, navigate to the folder where Crystal Runtime has been installed, this is usually:
C:\Program Files (x86)\Business Objects\Common\3.5\bin
In these folder, there is a file, CRPE32.DLL
If the 2 files in these 2 folder do not match, then Service Manager won't be able to print.
To rectify:
Make a copy of the file that is in the Service Manager install folder
Copy crpe32.dll from the Business Objects folder
Replace the file that is in the Service Manager folder
If the above does not work, then review how you are logging in to SME compared to how your username is saved. For example, if your user name is John Doe, logging in by typing your username as JOHN DOE can cause this issue.
If none of the above solutions work for you, please make sure you are logging in using the same ODBC data source as a working PC. A common issue is using a driver called SQL Server Native Client rather than using SQL Server. Please ask your IT team to check this