web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Unable to get printer ...
Microsoft Dynamics GP (Archived)

Unable to get printer context

(0) ShareShare
ReportReport
Posted on by Francisco Montano 130

I'm with windows server 2008 R2 64 bits and Dynamics GP 10.

we connect to GP via rdp. and for some user's when they post a document they get the message

Unable to get printer context for report ........

manually this user has to go to the configuration print and manually select the printer that the user has predifined locally.

The rdp is configurated to chose the local printer of the user.

To solve this problem i have to deleted the user profile from the server of GP. It work for some time, but for some Inexplicable event it stop working and the user began to have the same old problem.

*This post is locked for comments

I have the same question (0)
  • Francis Larocque Profile Picture
    Francis Larocque 1,921 on at

    Hi Francisco,

     We have exactly the same setup here and I'm facing the same problem.  We asked our partner for a solution and we're still waiting for it.  It is very annoying, indeed.  We've been waiting for three months now, but I've given up trying to find a solution.  I think to myself that someday some service pack will correct the problem.  We're facing a few INEXPLICABLE problems like this.  Anyways...

    I hope someone comes up with a solution soon... 

    Francis

  • MG-16101311-0 Profile Picture
    MG-16101311-0 26,225 on at

    Make sure you have default printer setup for Named Printers under MSDGP > Tools > Setup > System > Named Printers. You will also want to look at the article Using Named Printers with Terminal Server over at Developing for Dynamics GP.

  • Perry Smith - CRi Profile Picture
    Perry Smith - CRi 1,692 on at

    ditto on what Mario says.

     Also, Verify that the user has a default printer mapped prior to launching GP on the Terminal Server. 

     Perry

  • Francisco Montano Profile Picture
    Francisco Montano 130 on at

    The rdp file is configured to take the printers local device. and yes, all users has a local printer as default.

  • MG-16101311-0 Profile Picture
    MG-16101311-0 26,225 on at

    And what about the Named Printers configuration?

  • Francisco Montano Profile Picture
    Francisco Montano 130 on at
    Hi Mariano, I’m very glad that you answered my post; I had read some of yours solutions problems.We were using Windows server 2003 and Great Plains 7.5 and we weren’t using Named Printers. We connect to GP via an rdp file that was configured to take the local printer of the user, and we didn’t have any printer’s problem.Now, we migrated to windows server 2008 R2 64 bits and Dynamics GP10 SP4, and we have the above mentioned problem.Users have to manually configure the printers and the strangest situation is that the printer is there, but any way you have to choose the printer to take the default printer.I read that the windows server 2008 use the easy print functionality and all the clients (in my case Windows XP) has to have some specials considerations (Windows XP with Service Pack 3 includes RDC 6.1. However, you must install a supported version of .NET Framework separately. You can download Microsoft .NET Framework 3.5 (which includes .NET Framework 3.0 SP1)).This situations work fine for some time. We install Crystal reports on the server and the problem of default printer was back. For some reason that installation damage the user profile ( I supposed for the use of libraries of frame work 3.5). So we have to delete the user profiles, re-boot the server and the problem goes fore some time.Now, the problem is back but I haven’t identified what was caused it.

     So I was wonder if there is some Service pack or hot fix that fix this problem of the easy print with windows server 2008, rdp files and Dynamics GP10.

    there for, i'm going to test the named printers in my test enviroment.

    Thanks in advance.PD: sorry for my poor English, I’m from Santa Cruz-Bolivia in South America

     

  • MG-16101311-0 Profile Picture
    MG-16101311-0 26,225 on at

    Francisco,

    Your English is pretty darn good considering mine -- lol. 

    All I can say is there are way too many variables: Crystal Reports, XP and all its special requirements to run with Windows Server 2008 R2 Easy Print feature, etc. It sounds your best alternative would be to open a support case with Microsoft and have them walk through the issues with you.

    I also suggest you take a look at the following articles for more info:

    http://technet.microsoft.com/en-us/library/cc753853(WS.10).aspx (this is the article you are probably referencing)

    http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx (this is from the RDP Team Blog).

  • Verified answer
    Francisco Montano Profile Picture
    Francisco Montano 130 on at

    hi, i found a solution for this problem after reading a lot of articles, thanks to all

    If you are working with windows server 2008 R2 64 bits and Dynamics GP 10 and you connect to GP with remote app (windows server 2008) from windows XP (clients):

    1. you have to work with this article:

    technet.microsoft.com/.../cc753853(WS.10).aspx

    If the problem still continue is because you are using remote printers and have problems with your printers server. The printers are taking more time to become available, so when the remote app starts, launch GP, but the remote printers are not available at this moment. GP think there are no printers in the system …. Unable to get printer context

    2. You have to make a cmd file

    ---------------

    ---------------

    @echo off

    PING 1.1.1.1 -n 1 -w 3000 > NUL

    start "" "D:\Program Files\Microsoft Dynamics\GP\dynamics.exe" "D:\Program Files\Microsoft Dynamics\GP\dynamics.set"

    ---------------

    ---------------

    These cmd file delay for 3 seconds before launch GP, waiting the printers became available

    thanks to Carlos Peinado from AxxonIT for these cmd file ;)

    3. Save this cmd file in the GP folder, in my case D:\Program Files\Microsoft Dynamics\GP

    4. Create with remote app a new rdp file launching these cmd file

    thank's to all the replies to these post.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
mtabor Profile Picture

mtabor 1

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans