When the BillQuick application is deployed on a computer that does not have a C drive, an error occurs. A Microsoft Visual Studio .NET application uses Crystal Reports 10 for Visual Studio .NET SDK as the reporting development tool. When the application is deployed on a computer that does not have a C drive, the following appears:
"Load Report Failed"
It is common not to have a C drive on Terminal servers and Citrix servers.
This error message appears because the application sets registry values that point to the C drive. To resolve the error message, use the following steps to change these registry values in the Registry Editor.
WARNING: The following resolution involves editing the registry. Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall the Microsoft Windows operating system. Use the Registry Editor at your own risk.
For information on how to edit the registry key, view the 'Changing Keys and Values' online Help topic in the Registry Editor (Regedit.exe).
It is strongly recommended that you make a backup copy of the registry files (System.dat and User.dat on Win9x computers) before you edit the registry.
- Go to the 'Start' menu, Run.
- In the 'Run' dialog box, type "Regedit" then click 'OK'.
- In the Registry Editor, browse to the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Crystal Decisions\10.0 or 10.5 or Suite 12.0\Report Application Server\InprocServer\LocalConnectionMgr
- Right-click the 'ConnectionDirectoryPath' string value, then click 'Modify'.
- In the 'Value data' text box, change "c:\" to the drive letter where the following directory exists (You may need to search your computer to find where this directory exists):
\Program Files\Common Files\Crystal Decisions\2.5\bin
- Click 'OK'.
- Right-click the 'LocalConnectionMgr' subkey, click 'New' then click 'String Value'.
- Name this String Value "ReportDirectoryPath".
- Right-click the 'ReportDirectoryPath' string value and click 'Modify'.
- In the 'Value data' text box, type the same drive letter as you typed in step 5.
Note: After making changes to the registry, restart the affected service or application as required.
Now, when the application is run, the error message will not appear.