Print Page | Close Window

connectivity - windows

Printed From: Crystal Reports Book
Category: Crystal Reports 9 through 2022
Forum Name: Data Connectivity
Forum Discription: How to connect to data sources and export reports
URL: http://www.crystalreportsbook.com/forum/forum_posts.asp?TID=224
Printed Date: 03 Apr 2025 at 1:15am


Topic: connectivity - windows
Posted By: jwhite2007
Subject: connectivity - windows
Date Posted: 20 Feb 2007 at 8:31am

I am having troubles getting a crystal report to run through my windows service.  It runs beautifully on my local development box, but when I load it to the server, I get an internal server error.

CrystalDecisions.CrystalReports.Engine.InternalException:

Error in File C:\WINNT\TEMP\ProOfficeInvoiceSummary {7B7E045C-427A-4874-B18D-1268B230D778}.rpt:

Operation not yet implemented.

When I remove the database call from the report - it will print (of course with no data) so the reports are being recognized on the server. Obviously I'm thinking it's got to do with the report itself which I am sad to say I have minimal experience with. But since it works on my local - what could be the issue? Same database calls, etc.

I am using CRXI, with VS2005, 2.0 .NET framework.
 
Thanks ahead of time for any input.


Replies:
Posted By: BrianBischof
Date Posted: 20 Feb 2007 at 9:04am
I would think it has something to do with permissions. A lot of times, when a report works in one place but not in another, then the permissions have changed and the report can access all the resources it needs. This could be related to database permissions or not having Write permission for saving the temporary files that get created during the report processing. If you are putting the report on a production box then there is probably tight securityon the production server and you need to figure out what aspect is getting hung up.

-------------
Please support the forum! Tell others by linking to it on your blog or website:<a href="http://www.crystalreportsbook.com/forum/">Crystal Reports Forum</a>

Posted By: jwhite2007
Date Posted: 20 Feb 2007 at 2:01pm
Surprisingly enough the 4 day debugging fest was all because of an outdated dll.  I loaded the latest and greatest MDAC and all works fine (well almost, but that is a different problem). Thank you Brian!


Print Page | Close Window