Month: April 2018

The web client was a god addition to Microsoft Dynamics GP and I do like the HTML 5 version introduced in Microsoft Dynamics GP 2016 RTM. While we have a few clients using it, and some only use the web client, we’ve not had any clients using both the web client and Account Level Security.

MVP Jen Kuntz is different; she’s currently looking at the web client for the company she works with and has come across an interesting problem.

The short version is printing the standard report version of the Trial Balance doesn’t work in the web client when Account Level Security is enabled:

Related to this problem, is another problem whereby user’s don’t have access to any accounts and so can’t do anything around transaction entry, enquiries or reports.

For full details of both of these issues, read Jen’s blog.

As Jen notes, both of these issues have written up as outstanding quality issues:

• Bug #1 is Trial Balance report does not work when signing into Web Client with Windows Authentication if Account Security is enabled.
• Bug #2 is Web Client users not able to post if Account Security is turned on. The user receives the error “Access denied/Account Missing”

The bad news is there is no timeline for fixing them, and from the sounds of it, it’ because there aren’t a lot of customers reporting this issue back to Microsoft. A “product suggestion” has been added to the new Ideas site for this which Jen encourages you to vote for:

Bug #1 aka product suggestion #1 link is here.

Bug #2 aka product suggestion #2 link is here.

One of the project managers was doing some testing for a development project recently and accidentally changed the security for the ‘sa’ account; they removed the ‘POWERUSER’ role (which gives global access to Microsoft Dynamics GP. In its place, they assigned the AP CLERK role.

What made this a major issue, was that the development system only had one company and this left the system with no users with access to the security windows.

They made the mistake by selecting the sa account instead of the sam account. Unfortunately, it was only after logging out as sa and back in as sam that they realised what they had done.

Fortunately, this isn’t actually too complext to fix, although it does require some SQL.

The sa account needed to be added back into the Security Assignment User Role (SY10500) table. I used a very simple script for fixing the development system, but have then tidied it up a little to post here.

This script adds POWERUSER back to the sa account for all companies and needs to be run against the system database (typically called DYNAMICS):

/*
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (https://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).
*/
INSERT INTO SY10500
	(USERID,CMPANYID,SECURITYROLEID)
--VALUES
	(
	SELECT
		'sa',CMPANYID,'POWERUSER'
	FROM
		SY01500 AS ['Company Master']
	WHERE
		(
		SELECT
			COUNT(*)
		FROM
			SY10500 AS ['Security Assignment User Role']
		WHERE
			['Security Assignment User Role'].CMPANYID = ['Company Master'].CMPANYID
		AND
			['Security Assignment User Role'].USERID = 'sa'
		) = 0
	)
GO

Before running, please make sure you are happy with what the script will do and have a good backup of your system database.

I’ve been doing some work with a US-based company as they implement Microsoft Dynamics GP in Europe for one of their subsidiaries (we do a fair bit of this type of work for expertise with VAT and Intrastat). One of the issues they asked for assistance with was a problem they had while importing transactions.

All of the transactions which were in the functional currency, imported without a problem, but all of those in other currencies failed.

The cause of the problem was actually quite a simple one, and one I have seen before with other clients. On the Multicurrency Exchange Rate Maintenance window, there is an Expiration date field:

Continue reading “Expiration Dates on Exchange Rates”

I’ve done a lot of work around the Microsoft Dynamics GP Workflow module and have configured Email Notifications to work with numerous different SMTP servers. One recent one we configured was Gmail.

This was not actually as straightforward as configuring other SMTP servers as the details Google publish are not accurate in that the port they list for SSL is not the correct one.

The settings required are below:

Continue reading “Configuring Workflow to use Gmail for Email Notifications”

I’ve seen this error at two different clients now when configuring Web Services for Microsoft Dynamics GP 2018:

A loader exception has occurred.
Loader Errors:
- System.Data.SqlClient.SqlException (0x80131904): There is already an object named 'taRequesterWSDynamicsOnlineConfiguration1' in the database.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Dynamics.InstallData.SqlObjectLoader.DoSqlFromResource(String resourceName)
   at Microsoft.Dynamics.GP.GPSystemWebServiceObjectLoader.PerformActionOnEConnectStoredProcedures(Action action)
   at Microsoft.Dynamics.InstallData.Loader.Process(String[] args)
ClientConnectionId:04c704d2-d12c-40f3-9ccc-1444c4b529d9
Error Number:2714,State:3,Class:16

Both clients have previously had the Web Services implemented so that they could use Email Actions for Workflow approval. The first client got the error while we were doing the initial installation and confguration of the Web Services for Microsoft Dynamics GP 2018 and the second got them when we did a redeploy of the Web Services on the test system after refreshing the databases, but hadn’t received the error during the initial installation and configuration.

Continue reading “Error Configuring Web Services for Microsoft Dynamics GP 2018”