web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Integrated Security is...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Integrated Security is required Error When using SQL Authentication in Connection String

(0) ShareShare
ReportReport
Posted on by Vaidh 60

I'm Getting the following error when creating transaction using eConnect in GP, with SQL Server Authentication in connection String.

Integrated Security is required. \r\n Please ensure that the ConnectionString input parameter is valid.\r\n Examples:SQLCLIENT Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=TWO;Data Source=MySQLServerName \r\n Examples:SQLOLEDB Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=TWO;Data Source=MySQLServerName

I'm using GP 2016, and eConnect 16.0

Categories:
Microsoft Dynamics GP
I have the same question (0)
  • Derek Albaugh Profile Picture
    Derek Albaugh on at

    An example of a connection string I've used with eConnect is here:

    "data source=SQLInstanceName;initial catalog=TWO;integrated security=SSPI;persist security info=False;packet size=4096"

    The data source would be the SQL Server instance name. If you have a named SQL instance, enter the entire name such as ServerName\SQLInstanceName.

    The TWO would be whatever company database for GP you're running against.

    See if this example doesn't work for you.

    Thanks

  • Vaidh Profile Picture
    Vaidh 60 on at

    I dont want to use : Integrated Security=SSPI

  • Suggested answer
    Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,058 Moderator on at

    Hi Vaidh,

    Why don't you want to use Integrated Security for the eConnect connection ? this is the most secure way of establishing a data connection to a SQL server..  Anything else is unsecure and could be just looked up by anyone who could access the application or the data connection..

    I typically mention as example the Excel workbook data connection to Dynamics GP data.. you can use a SQL user for the authentication string, but then anyone who has access to the Excel workbook would be able to lookup that SQL user (which can't be a GP user by the way, as the pwd is encrypted on the SQL side).

    Using SSPI allows for secured access control on the SQL server data side, since you can specify which user or group has access to which data.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 456 Super User 2025 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 429 Most Valuable Professional

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans