Normal
0
false
false
false
EN-US
X-NONE
X-NONE
MicrosoftInternetExplorer4
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
Colleagues;
I am pleased to report to you that I have apparently resolved this
troublesome issue. The steps I took are as follows:
SQL Server steps:
1: A new login was created in SQL Server with no domain specification
using SQL Server authentication
2: A password was used, but password policy and expiration were disabled
3: User mappings were set on the target dbase (“production” in this case). User
is the new login, default schema was the login id. Role memberships were set to
public, db_datareader
4: Status settings are: Permission to connect to dbase engine = “Grant”, Login=”Enabled”
Navision security steps:
1: A new database login was created for the new login id
2: A single role “SUPER (DATA) “ was assigned to the login
Testing:
Multiple (at least 5) resynchs did not alter the dbase mappings. An external
ODBC system data source was tested using the new login against SQL and it ran
fine. Our shared production data source used by our SQL RS reports was updated,
tested, and re-deployed to the report server, all reports ran fine.
Thanks for everyone’s help, I think that we can (hopefully) put this issue
to rest.
Cheers! RDS