cancel
Showing results for 
Search instead for 
Did you mean: 

Crystal Reports XI printOut Method fails...

Former Member
0 Kudos

I have a project built in VJ++ 6.0. For the most part, the Crystal Reports that print from it have no issues. However, one of our remote sites has been having issues lately. We installed a HP LJ P4015n printer. The application now fails sometimes when trying to print. It appears to fail on the printOut method, based on the debug log that I have. We use craxdrt.dll to call functions within the project. The printer is on a different subnet than the host PC, does this make a difference? Any help on this would be greatly appreciated.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hello,

Can that person use that printer with any other program, like Word Pad? If not thern you'll need to map the printer to that person PC. Possibly installing the HP driver on his local PC should fix it also, set the port to where the printer is actually located.

Thank you

Don

Former Member
0 Kudos

The HP driver is installed locally on the computer, as is the printer. They can print from anything else. Most of the time, the Crystal Report does print to this printer, but fails sometimes, causing their application to crash.

The printer is at a remote site connected over a ptp vpn on a different subnet. Could this be part of the problem? There is another remote site that does not have any issues but is also on a different subnet than the main application.

0 Kudos

Next step is to check with your IT people and network permissions, out of our support area. They should have tools that can monitor the network and see what's going on.

It may be that that printer is running our of memory, how busy is it when they fail to print?

You could always use Windows 2003 and configure it to be a Print Server, this may be able to manage the print jobs if it is memory related.

To fix the crash issue you could put in a TRY/CATCH in the print method so at least it captures the error in a message box which should handle the exception gracefully stop the app from crashing.

Former Member
0 Kudos

It is in a try/catch loop. The issue is that the error is in a throwable, which has no message to display, so I have no idea what the error actually is. When it fails, I set the report and application to null so as to end them and then do garbage cleanup. This still seems to cause a crash though, as I think it keeps a connection open or hung, not sure which though.

Former Member
0 Kudos

As an update to this - it appears this is due to a locking issue, as I get the following error in my log now.

Database Connector Error: ' [Database Vendor Code: -210015 ]'

This is apparently because SQL is not looking up by an index, causing a (temporary) lock on the entire table, causing it to fail. We have multiple different lookups on our tables that adding indexes may take some time. Is there anything I can do until such a time that I can research fully what indexes would be needed? It seems that these issues shouldn't occur. Is there a setting in XI that tells it to read with READ UNCOMMITTED, so as to eliminate any of these issues? Please let me know.

0 Kudos

Hello,

Curious how this went from a printing issue to a data read error? So the printer is not the issue correct?

I would search forums in the Report Design area and also search notes for setting Uncommited reads ( dirty reads ). We do have a Doc some where on how to do this. It's not recommended because of the issue with data that may be garbage but that's up to you.

You may want to discuss with your DBA and set indexing up so it doesn't lock the file. You should also download any patches, It's possible this was fixed in XI. I do recall tracking this against Access but not sure when it was fixed.

If this is not a printer issue then lets close this and post your question to the Report Design Forum. THey should have the Doc on how to set this in the registry.

Thanks agian

Don

Former Member
0 Kudos

OK - thank you.

The error I got today was the first time I had seen that, so that is why it switched.

Oh - and I am the DBA, so any indexing changes will be going through me as well, so fun for me either way.

Answers (0)