Excel Report Error: “The SELECT permission was denied on the object ‘accounts’, database ‘MLC’, schema ‘dbo.’”

post2-1

With Microsoft Dynamics GP permissions come from two different types of accounts.  There are local accounts and GP accounts.  Local accounts are setup on a domain in Active Directory.  GP accounts are setup within the GP programs.

The permissions for excel reports pulls from Active Directory and not Microsoft Dynamics GP.  Specifically, it is an active directory account setup in SQL and set DYNGRP and rpt_power_user for it to access the account.

First login to SQL and expand security.  Under the security right click on login and select ‘new login…’.  After you select new login you will be able to see the option to search for a login.  This search will allow you to search in Active Directory.  After you add the new user under the general tab, then select the user mapping.  Under the user mapping, select all the databases that the user should be able to run excel reports in and add the permissions DYNGRP and rpt_power_user.  If you do not want to provide them the rpt_power_user role, then you would be able to select the rpt_%rolename% that best fits your company’s security policy.  This can also be matched to their GP logins permissions.

post2-2

Advertisements

Script error when opening Microsoft Dynamic GP: “An error has occurred in the script on this page”

script-error-when-opening-gp

For the error, “An error has occurred in the script on this page” URL: “https://online.dynamics.com/us/WebResource.axd?d=2eiL_4UDyPKUYbDwJbaFejBYJ44y52hSWZGz5-A7NDC2pVxbl2HB1Ni-” the solution is not within the GP software.  The first time I came across this error and attempted to resolve it, I followed https://support.microsoft.com/en-us/kb/2702223.  None of these solutions fixed the error. Steps I had taken was to proceed to clear the temp folder from the user directory and then verified the permissions for GP.   Most directions that I find online refer to these steps.

In the end, the solution was within Internet Explorer.  The error was typically occurring for our hosted Terminal Servers.  This is because security is typically stronger on the server due to group policies and security.  One of the resources I had referenced clearing cookies.  This prompted me to look at compatibility settings and trusted sites.

Compatibility Settings:
In Internet Explorer, Go to Tools- Compatibility View Settings
Add microsoft.com
Add dynamics.com

Trusted Sites:
In Internet Explorer, Go to Tools-Internet options
Select the security tab
Select Trusted Sites
Then select Sites
Uncheck “Require server verification (https:) for all sites in this zone
Add *.microsoft.com
Add *.dynamics.com
Select Close
Select ok
Restart Internet explorer