Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Terminal Service Printing issue
Mauddib
Member Posts: 269
Hi all,
Has anyone else experienced this issue with 2015?
https://blogs.msdn.microsoft.com/nav/2013/02/25/nav-2013-reports-may-be-difficult-to-read-when-printing-over-terminal-services/
We had exactly this issue with Nav2015 Terminal Services on Windows Server 2008 R2. We installed the recommended patch https://support.microsoft.com/en-us/kb/3037639 and the problem fixed itself.
Now however we find that if the client has a few things to print and someone closes the Terminal Services Session...... the client is very often crashing. Not always. Maybe 50:50. Before the client would just keep running in the session and continue printing away happily.
In the Event Viewer of the server I see the following:
Type: System.Drawing.Printing.InvalidPrinterException
Message: Settings to access printer '\\printserver2\KUM-FS4300-02' are not valid.
StackTrace:
at System.Drawing.Printing.PrinterSettings.GetHdevmodeInternal(String printer)
at System.Drawing.Printing.PageSettings.get_ExtraBytes()
Application: Microsoft.Dynamics.Nav.Client.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Settings to access printer '\\printserver2\KUM-FS4300-02' are not valid.
Stack:
at System.Environment.FailFast(System.String)
at Microsoft.Dynamics.Nav.Client.WinClient.StartWinFormsClient.HandleGeneralException(System.Exception)
Has anyone else experienced this issue with 2015?
https://blogs.msdn.microsoft.com/nav/2013/02/25/nav-2013-reports-may-be-difficult-to-read-when-printing-over-terminal-services/
We had exactly this issue with Nav2015 Terminal Services on Windows Server 2008 R2. We installed the recommended patch https://support.microsoft.com/en-us/kb/3037639 and the problem fixed itself.
Now however we find that if the client has a few things to print and someone closes the Terminal Services Session...... the client is very often crashing. Not always. Maybe 50:50. Before the client would just keep running in the session and continue printing away happily.
In the Event Viewer of the server I see the following:
Type: System.Drawing.Printing.InvalidPrinterException
Message: Settings to access printer '\\printserver2\KUM-FS4300-02' are not valid.
StackTrace:
at System.Drawing.Printing.PrinterSettings.GetHdevmodeInternal(String printer)
at System.Drawing.Printing.PageSettings.get_ExtraBytes()
Application: Microsoft.Dynamics.Nav.Client.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Settings to access printer '\\printserver2\KUM-FS4300-02' are not valid.
Stack:
at System.Environment.FailFast(System.String)
at Microsoft.Dynamics.Nav.Client.WinClient.StartWinFormsClient.HandleGeneralException(System.Exception)
0
Answers
did you use the printer via RDP- Client?