Thursday, March 15, 2012

Dynamics GP Workflow Issues, Server Error in “/” Application


Yesterday I been through a wired issue with Dynamics GP Workflow, after activating Vendors Addition and Purchase Order workflows users were getting the below message when trying to open any workflow:

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.
Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".

<!-- Web.Config Configuration File -->



<customErrors mode="RemoteOnly"/>



Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->



<customErrors mode="On" defaultRedirect="mycustompage.htm"/>



I doubled check the web.config and been sure that the web.config in the inetpub folder has the <customErrors mode =”off”>, after doing many researches I found another web.config located in the below path:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS

Which has the <customErrors mode =”on”>, switching off this returned the actual error behind the workflow as shown below:

Server Error in '/' Application.

The application encountered an unhandled system exception. Contact your system administrator for details.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Services.Protocols.SoapException: The application encountered an unhandled system exception. Contact your system administrator for details.
Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
2) Add the following section to the configuration file of your application:
<compilation debug="true"/>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[SoapException: The application encountered an unhandled system exception. Contact your system administrator for details.]

System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) +413241

System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) +300

Microsoft.Dynamics.GP.Proxy.DynamicsGP.GetCurrencyList(CurrencyCriteria criteria, Context context) +98

Microsoft.Dynamics.GP.Formatter.GetCurrencyList(DynamicsGP service, Boolean useHttpUser) +505

Microsoft.Dynamics.GP.Formatter.CacheCurrencyFormatData(String webServiceURL, Boolean useHttpUser) +85

Microsoft.Dynamics.GP.Workflow.DocumentViewer..ctor() +159

ASP._layouts_dynamics_workflow_gp_vendorviewer_aspx..ctor() +18

__ASP.FastObjectFactory_app_web_dynamics_workflow_gp_vendorviewer_aspx_2a428413__lml_jl2.Create_ASP__layouts_dynamics_workflow_gp_vendorviewer_aspx() +31

System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +138

System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +50

System.Web.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +425

System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +263

Version Information: Microsoft .NET Framework Version:2.0.50727.5448; ASP.NET Version:2.0.50727.5456

That was a new challenge, trying to figure our the resolution behind the new error, doing more researches returned that such an issue are web-services related issues as the workflow was unable to read information from Dynamics GP, you will need the administrator user you are using to run the services to the BDC Administrator role in web-services administration console.

The issue will be resolved!!!

Mohammad R. Daoud MVP - MCT
+962 - 79 - 999 65 85

No comments:

Related Posts:

Related Posts with Thumbnails