I'll assume that you are launching Crystal Reports via a Terminal Services session.
I think the problem is the report is using a jdbc driver as its datasource, and the path to the library file is not available to your login account. The crdb_jdbc.dll file is the JDBC library file.
Older versions of Crystal Reports put these files into a Windows\Crystal folder or Winnt\Crystal folder.
Search the drive where Crystal Reports is installed on the Terminal Server, locate where crdb_jdbc.dll is installed and copy it into the Windows\System or Windows\System32 folder.
Once it is there, any user should be able to access the file and Crystal Should work OK.