Setting up Kingwaysoft / SSIS to connect - Connection String - Proxy user

(0) Share

Report

Posted on by Community Member

We have a series of SSIS packages that utilize Kingswaysoft to pull data from AX to send to other applications. I've deployed the packages to my SQL Server and have setup the various environment variables including my connection strings. During development we used our individual usernames/passwords, but I need to be able to use a proxy user and supply the password in my connection string in order to be able to run them through a SQL Job.

I am experiencing problems with my connection string. I've tried working in Visual Studio to setup by the string, test my connection, and copy the string from Properties. The test works fine, but as soon as I put the string into SQL Server, it fails with a message indicating "server is unavailable". We can log onto the AOS server as the proxy user without issue. I can ping the AOS server from the SQL Server as well.

UserName=ISProxy;UserDomain=MyDomain.Int;ProxyUserName=ISProxy;ProxyUserPassword=MyPassword;ProxyUserDomain=MyDomain.Int;ObjectServer=;Company=;Language=;ConfigurationName=;Tenant=;

The problem seems to be specifically with using the Proxy fields in the string. As soon as I put values into these fields I get this error. If I take values out of these fields and just use the UserName and UserDomain fields of the user I am logged into SQL with I can successfully run this package. I've also tried just using the proxy fields, but the UserName and UserDomain fields are required.

What am I missing?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

André Arnaud de Cal... 301,053 Super User 2025 Season 2 on at

Like (0)

Report

HI Lori,

However you want to retrieve data from an AX database, I would like to recommend using a SQL server forum for your question. In fact SSIS and, a for me unknown Kingwaysoft, is not related to Dynamics AX.

Your question is related to security on the SQL server.

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

Whatever software is using the connection string, make sure that you set the user context on that to be privileged for your SQL Server instance both as a login, and as a database reader for your target DB. Then in the connection string use integrated security. That way credentials are passed down from the execution user and your problem should be solved.

If that is something you cannot do, I would suggest to turn for help to the softwares' manufacturer or to the Microsoft SQL Server forums, since it is unrelated to the behavior of AX indeed.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you for your response. I will check there as well. I placed my question here because KingswaySoft utilizes the Dynamics Business Connector and the errors I am seeing were from Dynamics.

Probably oversimplifying, but just to share, KingswaySoft is a type of add-in for SSIS that provides a connection to Dynamics AX via the business logic.

Was this reply helpful? Yes No
Vilmos Kintera 46,149 on at

Like (0)

Report

Business Connector does not require connection to SQL Server defined as a connection string, because that feature is used to talk to Dynamics AX Application Object Server service directly, which runs the business login indeed.

Was this reply helpful? Yes No