Troubleshooting the Microsoft Dynamics GP 2013 Web Client - Part 2

Part 2 - Resolving Microsoft Dynamics GP 2013 Web Client Implementation Issues

---

Yesterday, in Part 1 of this series, I addressed the Microsoft Dynamics GP Support Team's posture when addressing Web Client support cases, by cataloging each reported issue as either implementation- or functional-related. In this opportunity, I will look at the major processes involved in driving your implementation-related support case to a rapid and successful closure.

In the process of troubleshooting your Web Client implementation issue, there are two categories of data that need to be compiled to close a support case: installation information and application related exceptions.


Compiling the installation information typically involves gathering the following information:

• Type of installation (Intranet/Extranet/both)
• Information about certificates
• Firewall and Ports information
• Number of servers supporting the installation (Web Servers/Session Hosts/SQL Servers)
• Information about load balancers (if exist)
• Domain security groups and user accounts
• Run the Web Client Diagnostic Tool available as an option when you open a support case.
• Provide the XML output file created by the Web Client Implementation Tool, if available

Compiling the Web Client application related exceptions involves gathering the following information:

• Dynamics application log events
• Session Service logs (if enabled)
• Session Central logs (if enabled)
• Internet Information Services (IIS) logs
• Web page exception messages
• Tenant exception information (if using Multi-tenant Services)
• Fiddler and Microsoft Network Monitor (Netmon) traces

Web Client implementation exceptions can usually be identified by an "Unexpected Error" message in the browser as shown below:

Web Client application exception

Traditionally a support case would be started with a screenshot of an issue. However, as it relates to Web Client, Microsoft Dynamics GP Support cannot determine what an exception really means other than the fact that you encountered an exception. As such, Web Client implementation cases will usually require running the Web Client Diagnostic Tool in addition to providing Event Viewer information related to the Correlation ID displayed in the browser.

Event Viewer: Dynamics application event log

In a future installment, I will be covering all the troubleshooting tools available at your disposal, including the Web Client Diagnostic Tool, Web Client Implementation Tool, Fiddler, and Netmon among others.

In Part 3 of this series, I will address functional exceptions and resolution of functional issues.

Until next post!

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

Read More

Troubleshooting the Microsoft Dynamics GP 2013 Web Client - Part 1

Part 1 - Microsoft Dynamics GP Support Team's Posture

---

With the introduction of the Microsoft Dynamics GP 2013 Web Client, system administrators now face additional challenges when troubleshooting errors produced while accessing the Web Client all the way to using the Microsoft Dynamics GP application itself over the browser.

To understand the troubleshooting process, it's best to explain the Microsoft Dynamics GP Support team's posture when addressing a support case: any error event that occur before the Microsoft Dynamics GP login window is presented to the end-user will be treated as a Web Client implementation support issue.

Issues in this category involve everything from the deployment planning of the Web Client up to the point where you obtain the Microsoft Dynamics GP Login window. Items such as issues during the installation of the Web Client, network configuration, certificates, routers, firewall configuration, DNS resolution issues, issues preventing access to the web client Sign In window are all considered issues that prevent an end user from using the Web Client and therefore access Microsoft Dynamics GP.

Web Client Sign In window (Windows Authentication)

Any error event that occurs after the Microsoft Dynamics GP application Login window is presented, and during the normal use of Microsoft Dynamics GP is considered a functional support issue.

Microsoft Dynamics GP Login Window (SQL authentication)

Functional support issues involve everything from issues accessing Microsoft Dynamics GP all the way through using all the application functions within the Web Client: data entry, printing problems, posting issues, Report Writer reporting, SSRS reports, Excel reports, and all issues that may happen within the Microsoft Dynamics GP application while using the Web Client.

Having a clear cut definition between problems will allow you to reach the right support engineer at Microsoft. In addition, implementation issues may require the use of specialized diagnostic tools to collect information about the Web Client installation environment that will allow the support engineer or escalation engineer to better understand how your environment is configured.

In contrast, functional issues would typically follow the standard support protocols you have come to know over the years.

There are some clear benefits to this posturing:

1. A reported problem can be routed to the right support team the first time around. After all, an issue with a certificate may require someone technical from within the support team to address the problem, as opposed to a problem printing a report.

2. Having the right team addressing the issue will allow Support to issue whitepapers, videos, or even training content on how to address the most frequent issues that come to them.

3. Diagnostic information can be served up to the right support engineer at the time a case is created. This is only possible if a problem is tagged as an implementation issue versus a functional issue.

4. It allows both technical and functional support teams at Microsoft to keep stats on product quality, which may result in targeted hotfix or service packs.

Tomorrow I will address the steps involved in resolving an implementation problem and how you can take advantage of some of the latest tools available from Microsoft to assist in the process.

Until next post!

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

Read More

How does Microsoft Dynamics GP determine which account to use when sending emails

One of the advantages of working with Microsoft Outlook is its ability to configure multiple email accounts.  Recently, a partner was working with a customer that supports multiple companies, so a such, each employee has an email account per company supported.

The partner was under the impression that Microsoft Dynamics GP "looked" at the mailbox for the email account opened at the time of sending an email, but came to the conclusion it wasn't the case as the customer could not get emails sent through a second email account.

So how does Microsoft Dynamics GP determine which email account to use when sending emails via Microsoft Outlook?

The mailbox information is determined based on the default email account configured in Microsoft Outlook. To check for the default email account in Microsoft Outlook, follow one of the following two procedures:

Method 1: Control Panel

1. Open the Control Panel
2. Double-click on User Account and Family Safety
3. Click on Mail to Open the Mail Setup - Outlook window
4. Click on the Email Accounts button to open the Account Settings window

Account Settings window

Method 2: Outlook

1. From inside Microsoft Outlook, click on the File menu
2. Click on the Account Settings drop-down button under the Account Information pane.

Account Settings button

3. Click on the Account Settings option in the drop-down and this should open the previously shown Account Settings window.

Now, the account marked with the checkmark next to it will be the default account used by Microsoft Dynamics GP when sending emails.

Until next post!

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

Read More

Microsoft Dexterity Training Roadshow - Next Stop: Boston

(C) Microsoft Corporation

The Microsoft Dexterity Training Roadshow rolls around the United States with its next and final stop in Boston, Massachusetts from July 15 - July 19, 2013. Our training will be hosted in the Regus Business Center, from 9:00 AM to 5:00 PM.



Regus Business Center
60 State Street, Suite 700
Boston, MA 02109

We still have some seats left, so if you want to learn some of the development techniques used by Microsoft Dynamics GP developers this is your chance. For registration information, click here.

Stay tuned as we will announce our second Roadshow coming up.

Until next post!

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

Read More

Microsoft Dynamics GP Technical Airlift 2013

The Microsoft Dynamics GP Technical Airlift 2013 hosted by GP Partner Connections is a little less than 3 months away, so if you are a Microsoft Dynamics GP partner please register now.

As is customary, I will be attending the Technical Airlift as a presenter this year and will really be rocking a cool new session:


Developing for the Web Client: a Microsoft Dexterity perspective
September 18 • 1:15pm - 2:15pm

In this session, I will be presenting some new (and not so new) techniques used by Microsoft Dexterity developers to render integrating applications on the Web Client. Come learn about user interface standards, ribbons, command forms, selective programming (Web Client vs Rich Client), techniques for converting your VBA customization to Web Client compatible customizations, and performance killers.

Lot's to cover in one hour, but trust me, you will walk out of this session with some good tips for your bag of tricks.

See you in beautiful Fargo, North Dakota.

Until next post!

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

Read More

How to do a "Save As" in SmartList Builder

Ever wish you could do a "Save As" in SmartList Builder? Have you been working on a very complex SmartList and got to a point where things are working and now you need to make additional changes and you don't want to mess up the work you have done so far?

Just recently, I came across a request for being able to save a SmartList Builder smartlist under a different name - hence the "Save As" title. However, as you know SmartList Builder does not offer the ability to perform such operation out of the box. So here are some steps for you to do a "Save As" with Smartlist Builder:

1. Open SLB's Export Lists window and click on the list you would like to duplicate.
MSDGP | Tools | SmartList Builder | Export

Export Lists window

Enter or identify a path and file name for the list to be exported. Click the Export button when finished.

2. Edit the exported XML file with a text editor, for example Notepad. Search and replace all occurrences of the list ID in your file with the new name.

XML file edited in Notepad

Save the file when finished and exit the editor.

3. Open the SLB's Import Lists window and choose the file you previously exported, now containing the changes you made in step 2.

Import Lists window

Click the Import button to perform the actual import.

4. Return to SmartList Builder to verify the imported record.

Duplicated List

It would be nice sometimes if some of these features were provided straight out of the box, but with some understanding of the functionality and little creativity almost anything can be accomplished.

Until next post!

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

Read More

Microsoft SQL Server security roles and Microsoft Dynamics GP SSRS reports

It's not uncommon to find system administrators and consultants alike struggling to deploy Microsoft Dynamics GP SRS reports in an environment, while trying to keep these reports secured. I find that the main issue revolves around understanding the different moving parts: domain accounts, GP user logins, the SQL Server database roles created for reporting, the reports web site security, the reports folder security and the list goes on.

So here is a list of resources that I believe will help with this:

The best place to start is the SQL Server Reporting Services Guide, which has all of the information for installing, deploying and setting up security for SRS reports to use with Dynamics GP. This guide is available for download from the Microsoft Download Center.

Microsoft Dynamics GP 2013 Guide: SQL Server Reporting Services

In order for users to access SRS reports (default) for Dynamics GP, they need to have the following permissions:

1. Access to the Reporting Services web site (native mode) or report library (SharePoint Integrated). I have found the following resources to be extremely useful when configuring Reporting Services security in native mode:

Granting Permissions on a Native Mode Report Server

If you are dealing with Reporting Services in SharePoint Integrated mode, the following is a good resource:

Security Overview for Reporting Services in SharePoint Integrated Mode


2. Permissions to the SRS report files themselves. The following TechNet video shows just that:


3. Database security roles (RPT_ ) under the DYNAMICS and/or company databases in order to pull data into the SRS reports. You will want to take a look at the following KB article 954242 - Frequently asked questions about the integration of SQL Server Reporting Services (SSRS) with Microsoft Dynamics GP 10.0 and Microsoft Dynamics GP 2010, which can be found at:

http://support.microsoft.com/kb/954242

I hope you find these resources useful.

Until next post!

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

Read More