suzannehealy
asked on
Xerces panic error when generating a crystal report from a terminal service session
I have an app installed on a server running 2003 standard r2 and msql 2005. this app runs reports using crystal .. but i'm not sure which
using rdp, my users log into a terminal services server with the same os. my ts server also has crystal reports 10 installed on it.
my problem: when a users without administrative rights attempts to run a report that was created with crystal v8 - they get a XERCES panic error. These same users can run any other crystal report contained in the app. this only happens when they are accessing the app through the terminal server. I can use the same user id to log directly into the msql server that contains the app, and run it without a problem.
i have increased the rights in the HKLM\software\microsoft\wi
as reccommended in a post found here, but that did not solve my problem.
any help would be greatly appreciated. this is something i need to fix asap as this is a vital report on a new system we have deployed.
using rdp, my users log into a terminal services server with the same os. my ts server also has crystal reports 10 installed on it.
my problem: when a users without administrative rights attempts to run a report that was created with crystal v8 - they get a XERCES panic error. These same users can run any other crystal report contained in the app. this only happens when they are accessing the app through the terminal server. I can use the same user id to log directly into the msql server that contains the app, and run it without a problem.
i have increased the rights in the HKLM\software\microsoft\wi
as reccommended in a post found here, but that did not solve my problem.
any help would be greatly appreciated. this is something i need to fix asap as this is a vital report on a new system we have deployed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Unfortunatly, I didn't have a chance yet today to download the files mentioned to my TS to test. However, they appear to be ones that will be very useful for troubleshooting not only this problem but future ones .. so thanks for that. As a new network admin, still working on finishing my BS, all those tips come in very handy.
I think we have narrowed the problem down to the crystal reports version. After much arguing, the light finally went on for my application vendor who suddenly realized that I am running their newest version which uses Crystal 10 as it's report generator --- and all of ther implementation specialists, that assist in designing custom reports are using Crystal 8 in the field. We are recreating the report in 10 tonight, and hopefully that will solve the problem
I think we have narrowed the problem down to the crystal reports version. After much arguing, the light finally went on for my application vendor who suddenly realized that I am running their newest version which uses Crystal 10 as it's report generator --- and all of ther implementation specialists, that assist in designing custom reports are using Crystal 8 in the field. We are recreating the report in 10 tonight, and hopefully that will solve the problem
ASKER
Using filemon/regmon i was able to send a log to the applications engineer. eventually we determined that the problem was due to conflicting versions of the xerces .dll file. deleting the older version solved the problem.
It might be better for you to convert the reports rather than let a user do it.
mlmcc