COMMUNITY FORUM

A security issue has occurred at a GP 2010 client of ours who uses SmartConnect 2012.  All of the GP and SmartConnect users access those apps via Terminal Server.
 
Up until now, two of their GP users had Admin access to SmartConnect.  Then, for whatever reason, their DBA ran the script below.  Now, these two users get the error "Login failed for user", upon trying to run a map.

Specifically, when one of these two users tries running the map, the error message references the other user–not her.  And, the error message doesn't even reference the domain name as part of the user name.
 
The client did try to fix this by deleting these users from SmartConnect, re-adding them, and granting SmartConnect Admin access once again.  But, no luck.
 
The AD logins of these users, in SQL Management Studio, show that indeed they have DYNGRP and Public access to the GP databases as well as sysadmin access.  And, this issue is only occurring for these two users.
 
Would running SmartConnect System Maintenance fix this?  If not, then what is the remedy?
 
Thanks!  Much appreciated!

Here is that script:

To add Windows AD users to the GP databases use the script below.
Replace domainusername with the login details for each user
IF NOT EXISTS (SELECT loginname FROM master.dbo.syslogins WHERE name = 'domainusername')
BEGIN
CREATE LOGIN [domainusername] FROM WINDOWS
WITH DEFAULT_DATABASE=master,
DEFAULT_LANGUAGE=[us_english]
USE DYNAMICS;
CREATE USER [domainusername] FOR LOGIN [domainusername] WITH DEFAULT_SCHEMA=[dbo]
EXEC sys.sp_addrolemember 'DYNGRP',[domainusername]
USE TWO
CREATE USER [domainusername] FOR LOGIN [domainusername] WITH DEFAULT_SCHEMA=[dbo]
EXEC sys.sp_addrolemember 'DYNGRP',[domainusername]
END
GO
duplicate the lines below for each GP company database the user should be able to access.
USE TWO
CREATE USER [domainusername] FOR LOGIN [domainusername] WITH DEFAULT_SCHEMA=[dbo]
EXEC sys.sp_addrolemember 'DYNGRP',[domainusername]
where TWO is the Company ID
Alternatively an AD user group may be added to MSSQL, the appropriate permissions added, then the AD users added to the AD user group.
From SmartConnect 2011 SP2 administrators will be able to define a single MSSQL user which SmartConnect should use to connect to the Dynamics GP Company databases.