Setting Security in SQL for eConnect users

Today a client reported this error

Error processing document: \\<sql box>\<folders>\test\CM1700039_20170609150741.XML db: <dbname> Cannot open database "<dbname>" requested by the login. The login failed. Login failed for user '<domain name>\<user name>'. Complete Document: 7CM17/0003909766
 

eConnect uses SSPI security, meaning that it uses the credentials of the logged on user

Restated: The user that is logged on has to have security assigned to them in SQL

Screen shots below will walk you through it. 

This permission error can be fixed two ways:
• Create an AD group and add users to the group, then add the group to SQL. Better for large installs, lots of people
• Add the user directly to SQL. Trouble for more than a few users, emp turnover is a pain. Better for small stable installs.

In the images below we show the latter, but the process is the same for a group. 

Add a new login

 

Search for the AD user. Change the Locations to be the domain, enter in the user name and hit Check Names. 

Add the user to the DYNGRP role. 

All set


RealWorldCode gives developers practical, real‑world solutions with clean, working code — no fluff, no theory, just answers.
Links
Home
Knowledge Areas
Sitemap
Contact
Et cetera
Privacy Policy
Terms and Conditions
Cookie Preferences