Hello,
Thank you for your post in MSDN newsgroup!
I understand that you encountered issue when prview/print a specific report
on different machines. If I'm off-base, please let me know.
Based on my research, I was not able to find any known issue on this error.
To troubleshoot the issue we may need to analyze memory dumps or use live
debug, this work has to be done by contacting Microsoft Product Support
Services. Therefore, we probably will not be able to resolve the issue
through the newsgroups. If the issue is urgent, I recommend that you open a
Support incident with Microsoft Product Support Services so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.
For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp If you'd still like to continue working via the newsgroup, please
understand the issue might take a long time to narrow down. During the
course of troubleshooting, we may redirect you to PSS if required. For now,
please try the following and let me know how it goes:
1. Get the sample RS project, and backend database with necessary tables
behind, and send them to me at petery@microsoft.com. Please also let's know
the detailed reproduce steps
2. Does the issue occurs in report designer? Does the issue occur if you
configure default printer to "Microsoft Office Document Image Writer"?
3. Does the issue only occur with report with large number rows? If you
limit the rows/pages, can you reproduce the issue?
If you have other related information, please also let's know.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications
<
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<
http://msdn.microsoft.com/subscriptions/support/default.aspx>. ==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.