Reports Disappear from Print Que Without Printing

We just got two new machines for our customer service department which came with Windows XP installed.  

The problem is whenever the clerks try to print anything at all the report being printed flashes through the print que but then never prints.  The AP software they have uses Crystal 8.0, which we have learned does not support Windows XP, but I am hoping someone may have seen this little problem and solved it.  

When we stick their old machines back in place everything is fine, and there are not version differences in the software.  The only difference seems to be the operating system.
LVL 1
DreamingEagleAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mlmccCommented:
Can they print from other applications?

Can you install CR on an XP machine and print the reports from the designer?

Was the software installed by an administrator?

mlmcc
0
DreamingEagleAuthor Commented:
Sorry, yes, they can print from other applications.

I have not installed CR and tried to print from designer.

The software was installed by an administrator.  

We have learned Crystal is sending a 0 byte file to the print server.

0
DreamingEagleAuthor Commented:
The application I maintain also uses the old Crystal Report control.
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

DreamingEagleAuthor Commented:
CRYSTL32.OCX
0
mlmccCommented:
What if you try to print the report twice?  Do you get the report the second time?

mlmcc
0
DreamingEagleAuthor Commented:
No, you can print it over and over again with the same result nothing.  

We paused the printer from the print server and verified that the jobs being sent are 0 byte jobs.
0
DreamingEagleAuthor Commented:
This is to notify respondents that I've requested this question be deleted.  I suspect the CRYSTL32.OCX control is so old no one is keeping up with it any longer...thanks for your attention.
0
mlmccCommented:
That is true.  CR dropped the OCX from CR9 which was the first version tested on XP.

mlmcc
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DreamingEagleAuthor Commented:
Well, here's a twister.  Because of our need to get this machine into service we dropped back to Windows 2000 and encountered the same problem---even though we have a dozen machines running this application under 2000 with no problems...back to the drawing board.  Thanks for your efforts.
0
DreamingEagleAuthor Commented:
In fact, rather than post a Delete request I'm just giving you the points.  At least you took the time to try and help.
0
mlmccCommented:
I'll keep thinking and looking.  It is interesting you had trouble in Win2k.  We have an application we are getting ready to rollout that uses the OCX.  At this time it is too much work to update to the RDC.  

mlmcc
0
DreamingEagleAuthor Commented:
Well, gee, turns out the source of the error was human.

My install instructions to my network admin were incomplete.  The Crystal Reports use ODBC to connect to the SQL database.  However, I left the creation of the ODBCs out of the instructions, so they were not on the new machines.  

Instead of generating the usual "Cannot Open SQL Server" error message, however, Crystal rolled right along and generated the 0 byte file this time.  "Cannot Open SQL Server" would have pointed to the problem right way.  

Still kind of surprised CR didn't freak when it would not find the ODBC, but it did not issue any errors.

Once we created the ODBC connections, everything was fine---fine under Win 2000 and fine under Win XP.  

Life returns to normal for a while...
0
mlmccCommented:
Great to hear.

Thanks
mlmcc
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Crystal Reports

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.