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:
|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.
- 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!
Mariano Gomez, MVP