Unable to get printer context

[Luvsql]

Ever since we moved our Novel users to the new 2000 domain, all the users are now receiving the error "Unable to get printer context" when they try to print something within Great Plains. What they have to do is go to file > print setup (their printer is there) and click okay. However, as soon as they log out and log back in, they have to do the same thing. The only knowledge base article I can find has to do with Named Printers, but we do not use it and it's not a workstation specific error.

 

[35mph]

Hey, Luvsql... we just applied SP2 to Great Plains 8.0, AND moved the SQL database from one server to another. Now a remote terminal server user is getting this message... they're not using Named Printers either... any ideas?

 

[klewis10367]

LuvSQL, are you using citrix?

 

[Luvsql]

Yes, we are on citrix. The only workaround I could come up with is to add the printer setup window to their startup, so they are forced to choose a printer.

 

[winthropdc]

If you are using Named Printers you can set the default printer for the system.

This should be a network printer not a workstation printer. As workstation printers can change each time it is unwise to use them with Named Printers.

Note that Named Printers identifies machines using a setting in the Dex.ini. How you configure Named Printers does depending on if you are using a shared Dex.ini.

Please see the article below for more info.

http://www.microsoft.com/BusinessSolutions/Community/gp_using_named_printers.aspx

David Musgrave [MSFT]
Senior Development Consultant
Escalation Engineer
MBS Support - Asia Pacific

Microsoft Business Solutions

http://www.microsoft.com/BusinessSolutions

Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.

 

[klewis10367]

We sometimes run into the same issue but we have controlled it by loading the users default printer with there login script using a product called scriptlogic.

 

[Luvsql]

We do not use Named Printers...

 

[winthropdc]

Why not?