Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "The EXECUTE permission was denied on the object..." error when logging into Microsoft Dynamics PDK 2013

"The EXECUTE permission was denied on the object..." error when logging into Microsoft Dynamics PDK 2013

View products that this article applies to.

Symptoms

You may get the on or more of following errors after the password is changed on MS Dynamics PDK 2013 when the user tries to log in:


[Microsoft][SQL Server Native Client 10.0][SQL Server] The EXECUTE permission was denied on the object 'zDP_SY02100SS_1', database 'master', schema 'dbo'.

A get/change on operation table 'SY_Pathnames' failed accessing SQL data.

Your'e attempting to log in from a data source using a trusted connection.  Update the SQL Server settings for this data source to disable trusted connections and try logging in again.


↑ Back to the top

Cause

The PDK ODBC gets set to a default database name of 'Master', instead of 'Dynamics', since Microsoft Dynamics GP 2013 allows you to name this (Dynamics)database whatever you want. This happens when the ODBC is created by PDK.

↑ Back to the top

Resolution

To resolve this issue, you will need to set the Default Database for the PDK ODBC to 'Dynamics' (or whatever you named this database). Please follow these steps:


1. Exit PDK.

2. Navigate to Start, click on Control Panel, click on Administrative Tools, click on Data Sources (ODBC), and click on the System DSN tab.

3. Click to select the ODBC for PDK, and click on Configure. (If you don't know the name of the ODBC, log into PDK and see what you selected for the Data Server name.) 

4. Click Next to get to the In the Microsoft SQL Server DSN Configuration window.

5.  Change the name of the database from 'Master' to 'DYNAMICS' in the field for Change the default database to:

Note: Both of the checkboxes for the "Use ANSI..." settings should not be marked.

6. Click Next and Finish.

7. Log into PDK and the error should now be gone. 



↑ Back to the top

More Information

Another reason may also be that the user in not in the role of DYNGRP. In SQL Server Management Studio, under the SQL instance, expand Databases, expand the company database, expand Security and expand Users. Right-click on the user having issues and select Properties. Under General, verify the user is in the DYNGRP role. Re-launch PDK and verify the error no longer happens.


↑ Back to the top

Keywords: kbmbspartner, kbmbsmigrate, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2870546
Revision : 1
Created on : 1/7/2017
Published on : 8/19/2013
Exists online : False
Views : 218