D
DCraig
I'm having problems printing to a line printer from both Crystal Reports and
SQL Server reporting services using dotnet. When I try and print a report
from an application with Crystal I get the error message "the data area
passed to a system call is too small", and nothing else. With SSRS when I
try to print the report from the IDE I get the same error, I can load the
report up to the report server and view it with IE, then print it from there
but there are some formatting issues.
So far I've found that this appears to be an error that can be generated by
different processes, I found one that seemed to be almost exactly my
problem:
http://support.microsoft.com/default.aspx?scid=kb;en-us;822779
The common elements are dotnet printing - I'm assuming that printdocument
class is used by both Crystal and SSRS, and the plain text printer driver.
The problem is that it's the wrong operating system, my client is XP and the
print server is Windows 2003 server.
I'm using Visual Studio 2003, everything is up to date.
Has anyone seen this with XP/2003 and if so, have any tips on finding the
cause?
Thanks in advance;
David Craig.
ABC-CLIO
SQL Server reporting services using dotnet. When I try and print a report
from an application with Crystal I get the error message "the data area
passed to a system call is too small", and nothing else. With SSRS when I
try to print the report from the IDE I get the same error, I can load the
report up to the report server and view it with IE, then print it from there
but there are some formatting issues.
So far I've found that this appears to be an error that can be generated by
different processes, I found one that seemed to be almost exactly my
problem:
http://support.microsoft.com/default.aspx?scid=kb;en-us;822779
The common elements are dotnet printing - I'm assuming that printdocument
class is used by both Crystal and SSRS, and the plain text printer driver.
The problem is that it's the wrong operating system, my client is XP and the
print server is Windows 2003 server.
I'm using Visual Studio 2003, everything is up to date.
Has anyone seen this with XP/2003 and if so, have any tips on finding the
cause?
Thanks in advance;
David Craig.
ABC-CLIO