Error in File UNKNOWN.RPT

Crystal Report can be sometimes very tricky. When we faced the following bizarre  error message on a ASP.Net 2 web sites using Crystal 11, we learned that there are unknown undocumented secrets about distributing Crystal object.

Error in File UNKNOWN.RPT: The request could not be submitted for background processing.

We installed a web-application which was working fine on development environment on a Windows 2000 Server and we got following error message:

As far as we know there was no UNKNOWN.RPT in our project so we start searching the web for any hint about the source of the problem. There are number of posts on ASP.Net forum and other web sites about similar problems.

Finally after lots of research, following article turned to be helpful and fixed our problem. Interestingly the error message does not mach the actual addressed issue in the article, also we used Crystal 11, but this article is about Crystal 10.

BusinessObjects: https://boc.sdn.sap.com/node/231%23comment-2457/

Synopsis 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 to a computer that does not have a C drive, the following error message appears: “Load Report Failed” Why does this error message appear and how can it be resolved? It is common to not have a C drive on Terminal servers and Citrix servers. Solution 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. 1. On the ‘Start’ menu, click ‘Run’. 2. In the ‘Run’ dialog box, type “Regedit” then click ‘OK’. 3. In the Registry Editor browse to the following subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Crystal Decisions\10.0\Report Application Server\InprocServer\LocalConnectionMgr 4. Right-click the ‘ConnectionDirectoryPath’ string value, then click ‘Modify’. 5. 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’. 6. Right-click the ‘LocalConnectionMgr’ subkey, click ‘New’ then click ‘String Value’. 7. Name this String Value “ReportDirectoryPath”. 8. Right-click the ‘ReportDirectoryPath’ string value and click ‘Modify’. 9 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.

Well I will add this solution to my support notes and I guess this is one of those issues that I will face it again on different platforms of windows. The whole problem sounds like a bug and I do not know why BusinessObject hasn’t release any patch to fix it.

---

Possibly related posts: (automatically generated)

• InstallShield Build Error 5037
• AODC – error messages