Unable to complete login process due to delay in opening server connection

  • SQLSERVER 2008 R2

    Hi, I'm getting the error

    "Unable to complete login process due to delay in opening server connection"

    when running a very simply one line dos batch script on my laptop that then calls a batch script on the sql server.

    The sql script runs ok on the server but when called remotely from my dos batch script I get the above error.

    Reason:

    I have a database error with a security value not being cleared out during the night and its stopping users in the morning. Until I have time to properly look at the database performance etc I thought I'd allow the bog std user to run a script which will clear the value so came up with idea of a batch script they can't edit etc, simply run.

    My server script reads:

    @echo off

    PATH=\\MYSERVER\allied;\\MYSERVER\Program Files\Microsoft SQL Server\80\Tools\Binn;%path%

    set dbase=demo

    set sqlcmd="\\MYSERVER\program files\microsoft sql server\80\tools\binn\sqlcmd"

    sqlcmd -S MYSERVER -h-1 -U scheme -P passthru -d %dbase% -Q"set nocount on;update security set release =''' where id =''nathaniel' and secvalue =''beth"

    I have tried mapping a local drive to the Directory where the server batch script sits and have tried both domain name and IP addressing formats, both with same result.

    Anyone please advise?

  • Do you still get the timeout if you run a simple select as the query? If you force a failure on login (like a bad password) do you see anything in the error log?

  • Hi, using a select instead of an update produces same result. I know the batch script is being called as my manual log is being updated on the server side witht he echo statement in te script.

    Which error log are you referring to, I assume an sql log?

    Thanks for your earlier reply, much appreciated & Happy New Year.

  • The SQL Server error log, I am curious if you are 'getting' to SQL Server at all.

  • I'm wondering that too but am thinking is it due to my having the '\\MYSERVER" mapping in the command when I don't have a reconnected mapped name to the shared directory its pointed at. I thought as long as the directory was shared I wouldn't have to map it as well, but only a thought which I can try later when back at work. The batch file is definately called so the access will be either due to remote calling of command or as you intimate, the access of sql server itself.

    Thanks

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply