Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

Printing causes GP v10.0.1301 to Crash

(0) ShareShare
ReportReport
Posted on by

We have a number of named printer configurations for different User and Company combinations that all seem to be working for most of the users, but, one company configuration is having a strange result.  When they print a document that has a specific named printer it may or may not crash them out of GP.   THis is all being run on Terminal Services and has been a stable Terminal environment for almost 2 years.

When it crashes them, the GP application simply drops off the screen like it was minimized and it is gone.  When the user logs back into GP they are confronted with the 'still logged in - delete' message and therefore we know the system is in fact tracking the crash correcly.

The issue really seems to be (1) what is causing the crash and (2) it is not consistant, in that today of the 6 users in the office using this comapny database, only two have experienced the crash, one of the two times, the other only once.  And since the crash both users have been able to re-enter the system and continue to work with no other apparent side issues.

 THere have been no changes to the server, network or computers.  Only change in the system in the past 3 months is the replacement of the printer that appears to be the cause of the crashes.  This is an HP 4015 tn printer with 3 trays.

Bill C.

*This post is locked for comments

  • Re: Re: Re: Re: Re: Re: Printing causes GP v10.0.1301 to Crash

    [quote user="Ruel"]I forgot to add that the client computers themselves may be a factor [/quote]

    That would be a factor if the users were infact using traditional 'workstations' however, each user is running from a thin client designed for Terminal Service access - these machines have no native desktop - they simply provide a way to RDP to the terminal machine.

     All users (27 of them) use the same type of device - but, only 6 in the one office location are experiencing the problem - the problem we believe now is the printer and the driver for that printer - so that printer is getting the boot and a new one will be installed in a couple of days.

    Thanks for all the great comments and suggestions, this is a great way to get ideas out to the working consultants.  Keep up the great work.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: Re: Re: Re: Re: Printing causes GP v10.0.1301 to Crash

    I forgot to add that the client computers themselves may be a factor as well:

    Are the users logging in from the same client computers each time?

    If so, what if you try to have one user experiencing the error to RDP from another client computer where the error had never occurred?

    Also, are there any client computers that have their own printers connected? They might be sharing drivers that may conflict with the one on the server when they connect.

    On the Local Resources tab on the RDP client, do they have the "Printers" marked? If so, try having the problematic users log on with this option unmarked.

     

     

  • Re: Re: Re: Re: Printing causes GP v10.0.1301 to Crash

    I will discuss this with the hardware tech on site - they are also considering changing out the printer.  In the past I have found most printers either work full time or not at all - I have a hard time figuring out how it works some time and not all the time.

     Just a pain in the ass on this one.  Thanks for the suggestions and comments - have assisted in getting me in the right direction.

    Bill C

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    Re: Re: Re: Re: Printing causes GP v10.0.1301 to Crash

    If you say it only happens on 6 out of 27 users then the problem may be profile specific. 

    Perhaps, if possible, can you try re-creating their accounts? 

    And try isolating the issue by letting them...

    1) log into a re-created TS account and their usual GP account

    2) log into their usual TS account and a re-created GP account

    3) log into re-created accounts on both

    Also, this may not be related but in some cases I found setting "Use temporary folders per session" to No in the TS Configuration panel fixed some of my TS problems.

     

  • Re: Re: Printing causes GP v10.0.1301 to Crash

    I thougth about this as well, howver, only 6 of the 27 users are having any - I mean any - issues with GP failing.  All users are in the same office and all users are using the same printer - so, the commonality seems to be the HP4041 tn printer that was just installed in this branch office at the beginning of last week - when the GP crash / fails all started.

  • Rashid Farooq Profile Picture
    Rashid Farooq 1,000 on at
    Re: Re: Printing causes GP v10.0.1301 to Crash

    "GP application simply drops off the screen like it was minimized"

    Also look like a system problem. (if the printer is a HP, it would confirmed that a system problem according to MS KB related to this issue) 

     

  • Dencio Profile Picture
    Dencio 2,172 on at
    Re: Re: Printing causes GP v10.0.1301 to Crash

    Hi Bill,

    In addition to Rashid guidelines, I will recommend the test on TS user session:

    Seemed TS is involved and user session in TS will create printer configurations for active sessions and destroy the printer configuration when the session is properly exited.  The named printer and the printer created for each TS user session should match.

    Recreate named printers in GP for the replacement printer you mentioned earlier.

    I am pretty sure it is in one of these areas as we have been using named printer in few of our sites and there are minimal interruptions so far even when replacing an old printer device with a new printer device.

    Cheers,

    Dencio

  • Rashid Farooq Profile Picture
    Rashid Farooq 1,000 on at
    Re: Printing causes GP v10.0.1301 to Crash

    HERE IS MS KB MAY BE RESOLVE YOUR PROBLEM.

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

    How the named printers feature selects a printer in Microsoft Dynamics GP

    This article describes how the named printers feature selects a printer in Microsoft Dynamics GP.
     
    MORE INFORMATION
    The named printers feature is a workstation-based feature. Each workstation has a machine ID that is stored in the Dex.ini file. This machine ID is typically based on the network ID of the workstation.

    When a printer task is assigned to a printer class, you can select one of the following printer classes in the Assign Named Printers window:
    • System
    • User
    • Company
    • User & Company
    • Any Printer ID
    • Manual Selection
    • None
    For more information about these printer classes, see the following descriptions.
     

    System

    If you select System in the Printer Class field, the named printers feature uses the selected printer ID for all users and for all companies.
     

    User

    If you select User in the Printer Class field, you must select a printer ID that is assigned to the User printer class for each user in the Assign Named Printers window.
     

    Company

    If you select Company in the Printer Class field, you must select a printer ID that is assigned to the Company printer class for each company in the Assign Named Printers window.
     

    User & Company

    If you select User & Company in the Printer Class field, you must select a printer ID that is assigned to the "User & Company" printer class. You must select this printer ID for each user in the Assign Named Printers window and for each company combination in the Assign Named Printers window.

    Note If you select one of the following four options, and you do not select a printer ID, the named printers feature prompts you to define a printer ID that is assigned to the same printer class:
    • System
    • User
    • Company
    • User & Company
    You are prompted for this printer ID when you print a document.
     

    Any Printer ID

    If you select Any Printer ID in the Printer Class field, you are prompted for the printer ID when you print a document. You can select the printer ID from any printer class.
     

    Manual Selection

    If you select Manual Selection in the Printer Class field, the Printer Selection window opens when you print a document. This is the same window that opens when you click Print Setup on the File menu.

    Note If no valid printer selection can be made for the current user, and if the current user is mapped to a template user ID, the named printers feature repeats the selection process. However, the named printers feature uses the template user ID to find a valid printer selection. Template users can be configured in the "Setup Named Printers - Advanced" window. To open the "Setup Named Printers - Advanced" window, follow these steps:
    1. On the Tools menu, point to Setup, point to System, and then click Named Printers.
    2. In the Assign Named Printers window, click Setup.
    3. In the Setup Named Printers window, click Advanced.
    If a printer task is assigned to the User printer class, the Machine ID window prompts you for a printer ID for all users on a workstation. For an example of why you are prompted for a printer ID, consider the following scenario:
    1. A workstation has a machine ID. A printer ID that is assigned to the User printer class is created for User A. When User A is selected in the User ID field in the Assign Named Printers window, the printer class for a printer task is changed to User. The printer ID that was previously created is selected.
    2. User B logs on to the workstation. User B prints this printer task. The named printers feature sees that the printer task is assigned to the User printer class. But there is no printer ID selected for User B.
    3. The named printers feature checks whether the current user is associated with a template user. If the current user is associated with a template user, the named printers feature looks for a valid printer ID selection for the template user ID.
    4. If no printer ID can be selected, the Named Printers window prompts the user to enter a printer ID that is assigned to the User printer class.
    Note To prevent the Machine ID window from appearing, use one of the following methods:
    • Define a printer ID for each user of the workstation.
    • Use a template user, and then assign other users to the template user.
    We recommend that you set up a template user when you set up a system on which Terminal Server is installed. In this situation, you can group users who need the same printer configuration. Additionally, you can set up a template user by using a single user ID.

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

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,711 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,458 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans