December 2, 2009 at 7:51 am
Hi Everyone,
Since moving to SQL Server 2008, we have experienced intermitted connection problems while using sqlcmd to execute stored procedures in a .cmd script. The error that occurs is "Microsoft SQL Server Native Client 10.0 : Unable to complete login process due to delay in opening server connection". The .cmd script is stored locally on the database server and the sqlcmd command uses the -E option to connect to the instance. I believe sqlcmd uses the OLE DB provider when run from the command line...Could the provider be the issue? Is there anyway to have sqlcmd use a different provider? Maybe use the SQL Server provider instead of SQL Server Native Client 10.0 provider?
Any help would be appreciated.
Thanks
December 22, 2009 at 12:28 pm
We are having the same problem with SQL 2005. IF we use the -U -P switches instead of -E, the command connects instantly. Unfortunately, our process requires Windows Authentication. Any ideas, beside DC communication issues, that might be causing this error?
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy