2,469
When I try to install the eConnect Runtime on a client machine so I can use the eConnect adapters for Integration Manager, it fails with 'Unable to Add user to SQL'.
The eConnect Service User domain & ID I entered is the same one I used when I installed eConnect on the server.
Any ideas?
*This post is locked for comments
Dear all,
I was try to install econnect 8 sp5 on Window7(32bit) i was having error while installation it said Error Number=-2147217601 Error Description =[Microsoft][ODBC SQL Server Driver][SQL Server] The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION. Error Source= Microsoft SQL-DMO(ODBC SQL State 25000)Line Number=330.
after I click Ok then i was encounter another window which ask me to enter the User Domain/Login and user password for loggin into the Incoming Services,Outgoing Services, and COM +econect 8 for GP package.
i have tried with sa and the user id that i installed for, unfortunately both were failed. I have already checked that, user already inside DYNGRP in the sql server.
Did anyone have enconter same problem and how did you solve it?
Your Earliest Reponse is very much appreicated.
Best Regards.
Dear all,
I just deleted user ID from SQL Server-->Security-->Logins and reinstall eConnect 2010 and it did install sucessfully.
Please keep notes of user rights and other details before deleting.
Thanks
Sandip
Mariano was on the right track....per Microsoft, this is a known issue. I had to define a brand-new Windows user (that wasn't already set up in SQL Server), then run the install with that ID. Strangely, though, now that it's been set up in SQL Server by the eConnect install process, I can re-use the ID for subsequent workstation installs. Go figure.
If you are provided with a resolution, could you please update this thread?
Have a great weekend.
Bob,
At this point I would advise you open a support request as clearly we are not getting any closer to a resolution.
[quote user="bcool"]Well, I didn't set up a new user - I used an administrative ID that we use for all our software installations (and the same one I used when I installed eConnect on the server).
I'm curious - why would I get the message about trying to add a new user to SQL, when it already exists?
The GP server is a new box, so I'm wondering if there is something missing that allows communication from my desktop to the server (although I can log on to GP on the new box OK from my PC)?
[/quote]I have had some insight on this matter with some MS folks and apparently this is a known issue. I don't think it has to do with you having a communication problem. Now, is your administrative user a member of the SQL Server sysadmin security role? I have to assume it is, but thought I would ask.
Well, I didn't set up a new user - I used an administrative ID that we use for all our software installations (and the same one I used when I installed eConnect on the server).
I'm curious - why would I get the message about trying to add a new user to SQL, when it already exists?
The GP server is a new box, so I'm wondering if there is something missing that allows communication from my desktop to the server (although I can log on to GP on the new box OK from my PC)?
Did you setup a new domain user and added that user to the Domain Admins group? Furthermore, did you run the eConnect installation under that new user?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (