Dynamics Blogger

Dynamics GP Workflow interface has been simplified ever since GP 2013 was launched. The functionality continued to improve on each version release. The ability to setup and configure workflows within native GP interface has reduced several steps in the process. I got a call this morning from my client who's a happy customer using Dynamics GP workflows extensively in his organization for more than an year ever since I implemented GP for him. The problem is none of the workflow notifications are popping up in users inbox. Strange. After taking control of his screen through a remote connection, I quickly went with the series of troubleshooting steps. 1. What is the mail server used by client? Office 365. 2. Did the workflow email sender account password change recently? Yes. they did change the password recently. So, I went to Workflow setup window through Microsoft Dynamics GP | Administration | Workflow Setup and have him update the password twice. 3. After saving the...

I covered about one error in workflows earlier. It is time for another troubleshoot. At this time, let us have a look at another error reproduced below Error “Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: General Event ID: 27745Date: 30/09/2008Time: 3:23:52 Amuser: N/A Computer: AUYXUAP310WBC32Description:The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: #50071: Unable to connect to the database SharePoint_Config on SharePointSQLServer_Dev. Check the database connection information and make sure that the database server is running..” Resolution A very small and quick resolution to this issue. Just run the fol...

Here is another article that talks about an error identified from the stack trace in Event Viewer. I have published a series of articles on Dynamics GP Workflows in recent times. After having installed Web Services, MOSS 2007 and Workflows successfully, I thought everything is perfect. I tried testing a dummy workflow for GL batch approval creating a one approver scenario. I was able to submit the batch for approval successfully. However, When i tried approving the said batch, it takes no action. To identify what’s happening in the back end, I opened Event Viewer. Remember that there would be a separate events series called Dynamics that would be available once you have workflows installed on the Web server running workflows. Under the Dynamics events, it was registering the following error every time I hit the Approval button.  Action: SubmitTaskAction Current User LogOnName: Domain\Admin Input parameters: Exception type: System.ArgumentException Exception message: logOnName St...

Recently while I was testing the workflows for Dynamics GP, I have had to uninstall the Workflows. Prior to uninstalling the workflows, it is always recommended to deactivate the active workflows. I forgot I was having GL Entry batch approval workflow active while doing this uninstall operation. The result was whenever I login to GP and try to open the General entry or GL batch entry window, I get a message saying Dynamics GP encountered an error and needs to close. Then it crashes immediately. I observed the GL batch entry window continue to show Workflow layer on top of it. In order to overcome this issue, I followed this troubleshooting method as below 1. Tried deactivating the workflows by going to Microsoft Dynamics GP | Tools | Setup | Workflow Setup. I could not unmark the Activate Workflow option there. 2. I went to SQL Server Management Studio (SSMS) and ran a statement on my company database SY00500 table to see the active batches for which workflow shows to be activated....

In one of my earlier articles, I covered a common issue that we encounter during installation of workflows. In this article, I’d cover another issue that we encounter during uninstallation and reinstallation of workflows. Background of this issue goes on like this before I present the troubleshooting route that I took to overcome the same. In one of my implementations, I have installed all the pre-requisites required for Workflows and configured them successfully. Same is the case with Workflows for which the installation went peacefully. Problems started only when I identified the workflows are not working properly with the Approvals during the initial testing. After several unsuccessful attempts, I decided to take the hard way to get out of this issue. I decided to uninstall the Workflows completely and reinstall the same. Even repairing workflows wasn’t working. To add to my already existing problems, the uninstallation also failed returning a fatal error. After several attempts ...

While trying to install Workflows for Dynamics GP, we might encounter the following errors. Microsoft.Dynamics.Workflow.InstallSystemSecurityMetadata has encountered a problem and needs to close. Microsoft.Dynamics.Workflow.InstallSystemSecurityMetadata returned –532459699   Resolution : This error comes primarily if we install MOSS 2007 Enterprise Edition as a basic installation instead of selecting Advanced installation. Only when we select the Advanced installation, the SharePoint 2007 would be installed as a “complete installation”. To verify if SharePoint was a complete installation, go to SharePoint 3.0 Central Administration site, Click Operations tab, then go to Topology and Services area, Click Services on server. Here we should be seeing web server for medium server farms should be marked. otherwise, it need to be treated as basic installation. If it is basic installation, we need to uninstall the MOSS and then install it again in Advanced mode to inst...