We hope you had a restful Labor Day weekend! To start the week off we have a Tech Tuesday article from our SmartList Builder guru, Jared Dux, who is addressing an error that some users have been experiencing when upgrading SmartList Builder.
Management Reporter 2012 Process Service Not being Started – The time zone ID ‘Jerusalem Standard Time’ was not found on the local computer.
Few days back I got a very wired case from one of my customers, the reports they are generating are not being processed and locked in the “Queued” state, which normally caused due to the fact that Management Reporter Services are not running, moving to the services I have noticed that the “Management Reporter 2012 Process Service” is not running and unable to be started. I moved to the Event Viewer trying to find the cause of the issue and found the following wired error: Service cannot be started.
This week’s Tech Tuesday is from our Senior Technical Consultant, Chris Hanson, who will show us the easiest method to tracking the Source Company in a Real-Time Map. One of our features in SmartConnect is a real-time data source that allows maps to automatically execute when a certain event is triggered. When using a GP real-time source you can setup that source once to be used across every
This morning I been thinking about the new security structure for Dynamics GP web-client user who does not have SQL Users, and how these users will interact with SQL Server, I had to go through this as I have a client who’s running a very strict policy in granting SQL permissions for domain users. Getting through this, I have created few users with multiple scenarios as below: The first user linked to domain account called that “TEST1”, but didn’t check “Web Client user only (no SQL Server Account)” The second user linked to domain account called that “TEST2”, and checked the “Web Client user only (no SQL Server Account)” option. I have noticed that the first case created an “SQL User Account” called “TEST1” and didn’t granted the domain user any access to the database, and the second didn’t create any users which been a mystery to me understanding which user will be used to access the SQL Server! To test this I have modified the GL00100 table and added a new column called “UserName” –this is for testing only, you cannot do this on GP tables!- and set the default value for this column to be “SUSER_SNAME()” function which returns the user who’s currently logged in and started my testing by creating new accounts! Logged in by TEST1 to the web client and created a new account, the result was somehow wired, the user who was recorded was “DYNSA” Logged in by TEST2 to the web client and created a new account, the result was the same, the user who was recorded was “DYNSA” as well
Dynamics GP 2013 R2 upgrade: The following SQL statement produced an error: exec wfDeployClrAssemblies
During the upgrade process to Dynamics GP 2013 R2 with one of my customers we got the error in the subject, the issue is with dropping one of the SQL level Assemblies called “System.DirectoryServices” that been used by “Microsoft.Dynamics.GP.WorkflowGP.WorkflowEngine”. The “System.DirectoryServices” assembly is being used by the Workflow module in Dynamics GP, if you have workflow installed you will not be able to drop this reference as you will be having another assembly depending on this and the other assembly is being used by 7 functions and stored procedures.