Troubleshooting the Microsoft Dynamics GP 2013 Web Client - Part 3

Part 3 - Resolving Microsoft Dynamics GP 2013 Web Client Functional Issues

Last week, Part 2 of this series dealt with resolving Web Client implementation issues. The key to remember is any exception condition prior to the Microsoft Dynamics GP login window is treated as an implementation issue and as noted back in Part 2, there are two major processes - steps, if you will - in compiling information that will lead to resolving Web Client exceptions.

Just like with the implementation issues, you must compile information related to all application exceptions. Let's see what type of information can be compiled:

  • If the problem involves product functionality, it's always a good idea to record the steps to reproduce the problem.
  • It's also possible that the issues are UI related, i.e., a window does not display correctly (though these issues are less frequent, but certainly possible).
  • Printing and data export issues. In this case, you will want to determine whether the Silverlight application is being trusted.
  • Silverlight exceptions, i.e., those displayed in a window with a stop sign
  • Third party application customization vs. standard Microsoft Dynamics GP functionality. In a multi-dictionary setting, this will play a role whether using Web Client or the Rich Client (traditional Dexterity application).
  • Enable all available Web Client logs (session management and multi-tenant logs)
  • Capture all user-machine related information with MSINFO32.EXE
  • Can you reproduce the problem in the standard Microsoft Dynamics GP rich client application
  • Can the problem be reproduced by more than one user
  • Can the problem be reproduced in more than one company


The following are sample application exceptions:

Silverlight exception

App stuck on "Initializing" upon login

As you can tell, some of the information that must be compiled is standard. What must be taken into account here is, the Session Service is a real GP client running in the background supporting the Web Client session.

With that said, the following are some key success factors for the resolution of Web Client functional issues:

  • First, all issues must be treated jointly as Microsoft Dynamics GP issues and not something isolated to the Web Client.
  • You must keep in mind that Web Client will display the same exception messages displayed by the standard Microsoft Dynamics GP rich client.
  • Breakdown the problem and make sure it's focused on the Web Client.

Finally, summarizing:

  • The Web Client functionality "resembles" that of the Microsoft Dynamics GP rich client - we use the word "resemble" here, because we know certain things like navigation are slightly different in Web Client.
  • The rich client is installed on the Session Host server(s), therefore files like DYNAMICS.SET, DEX.INI, and forms and reports dictionaries are still in the mix
  • All exceptions experienced by the rich client are submitted to the Web Client, whether handled or unhandled.
  • All Dexterity third party applications are supported in the Web Client.
  • The Web Client uses a proprietary messaging system.

In part 4 of this series, I will look into some tools available for troubleshooting both implementation and functional issues.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Comments

Bharti said…
Excellent blog very nice and unique information related to Beclovent. Thanks for sharing this information.Microsoft Dynamics Implementation
December 21, 2016 at 3:12 AM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics
Read more

Cannot insert the value NULL into column 'CONTACT' error when clicking on Items List in Navigation Pane

Image
Moving on from my previous article on a similar subject - see Cannot insert the value NULL into column 'BASEUOFM' error when clicking on Items List in Navigation Pane , I recently came across this error,  Cannot insert the value NULL into column 'CONTACT' when clicking on the All Purchasing Transactions list under the Purchasing Navigation Pane option, after performing an upgrade from Microsoft Dynamics GP 9.0 to Microsoft Dynamics GP 2010 R2. All Purchasing Transactions list error - Purchasing Navigation List The name of the global temp table - in this case, tempdb.dbo.##2093338- varies in almost all cases, but the end result of the error is the same. The issue has been identified running Microsoft Dynamics GP 2010 RTM, SP1 or SP2. Upon further review, the issue is due to bad data in the Vendor ID (VENDORID) column in the Purchasing Receipt History table (POP30300). In summary, if you have a purchasing receipt with a blank vendor ID or a vendor ID that doe
Read more

How to uninstall Microsoft Dynamics GP 10.0 if you cannot uninstall it by using the "Add or Remove Programs" feature

INTRODUCTION This article describes how to uninstall an existing Microsoft Dynamics GP v10 system if you cannot uninstall it by using the Add or Remove Programs feature (or Programs and Features in Windows Vista) in Control Panel. It is recommended that you verify that you cannot uninstall by using Add or Remove Programs first. MORE INFORMATION First, verify that you cannot uninstall Microsoft Dynamics GP by using Add or Remove Programs (or Programs and Features) To verify that you cannot uninstall Microsoft Dynamics GP by using Add or Remove Programs (or Programs and Features in Windows Vista), follow these steps. For Windows XP or Windows Server 2003: 1. Click Start, click Run, type control appwiz.cpl in the Open box, and then press ENTER. 2. Click to select Microsoft Dynamics GP 10.0 product from the application list, and then click Remove. For Windows Vista: 1. Click Start, type Programs and Features in the Search box, and then press ENTER. 2. Click to select the product to be un
Read more