Re: Printing Issue

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Jeffrey,

I've told my client to reset all permissions on their printers and to try
again. I've also informed them about the default printer issue, which
they're taking steps to correct once they've reset the permissions. I found
that deleting and reinstalling the printer on *my* server actually sorted
out the issue, so long as it was made available as the default for any user
that logged on. As the client recently upgraded to W2K3 Server, I think
it's possible that some permissions haven't been "cascaded" through to the
existing users when logging on to the new server.

I'm hoping that this will fix the issue, and thankyou very much for your
time and patience on this.

However, is there any indication that MS will make this a bit easier to
diagnose in .NET 2.0? I'm still getting the regular question from my client
as to why they cannot at least do a print-preview, and I have to agree that
it shouldn't throw an exception at that stage. Surely a "No Default
Printer" exception would be more appropriate at the stage of actually trying
to print, along with some method in the printing namespace just to test "If
DefaultPrinter Is Nothing Then....(handle it)" ?

Thanks for all your help,
Alex Clark




""Jeffrey Tan[MSFT]"" <v-jetan@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:6rPCxeMvFHA.580@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Alex,
>
> Thanks for your defailed feedback.
>
> Sorry, I also have tested with this issue on more than 2 windows2003
> machines, all work well after setting a default printer, so I do not
> understand why you have different behavior. Because I can not reproduce
> this crash on my side, I can not give any useful comment to you. Also,
> based on the feedback from our product team, they should have the test
> result as me, that is: this is after logging with another account and
> setting a default printer under that account, the printing will not fail
> at
> all.
>
> So unless we can find a way to reproduce out your problem, the help I can
> provide is limited. Maybe, you may contact the Microsoft PSS for case
> support, then they may remote logging on to your machine to do some test
> on
> your problematic machines.
>
> Thanks for your understanding.
>
> Best regards,
> Jeffrey Tan
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
>


.

Quantcast