Connection time out issue

  • Here is the below sql server Version that we have in our organisation.

    Microsoft SQL Server 2005 - 9.00.2047.00 (X64) Microsoft Corporation Developer Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)

    There is an issue causing Time out & below is the Error message for info.

    Is this something to related "Application "or "Database".

    There was an error adding/updating the Creative<br>System.Exception: Execute SQL Failed, Err=System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

    at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

    at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

    at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()

    at System.Data.SqlClient.SqlDataReader.get_MetaData()

    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

    at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

    at System.Data.SqlClient.SqlCommand.ExecuteScalar()

    at IDS.Classes.clsSQLDB.Execute(String SQL) in C:\Documents and Settings\Hansifer\My Documents\Files\Career\Origin Digital\code\Common\IDSClasses\clsSQLDB.vb:line 177, SQL=INSERT INTO Creative(AddedContactID, Copyright, ClickThruURL, UPC, ISRC, TrackNumber, TrackLabel, TrackGenre, AlbumTitle, AlbumLabel, AlbumTrackCount, ExplicitLyrics, ReleaseDate, CustomerID, ForeignID, ForeignField2, CreativeTypeID, Creativename, Description, Author, Keywords, Width, Height, CategoryID, Status, ThumbNailURL) VALUES (10015, '', '', '', '', NULL, '', '', '', '', NULL, 0, NULL, 185, '8e8ead350d', '', 7, '8e8ead350d', '', '', '', 0, 0, 1, 0, 'http://www.odaptor.com/ALPCreatives/noimage.gif')

    at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)

    at IDS.Classes.clsSQLDB.Execute(String SQL) in C:\Documents and Settings\Hansifer\My Documents\Files\Career\Origin Digital\code\Common\IDSClasses\clsSQLDB.vb:line 184

    at IDS.Classes.clsSQLDB.AddSQLString_Execute(String Tbl, String Where) in C:\Documents and Settings\Hansifer\My Documents\Files\Career\Origin Digital\code\Common\IDSClasses\clsSQLDB.vb:line 543

    at IDS.ALPClasses.clsSimpleAsset.Save(clsSQLDB AL, Int32 ContactID) in C:\Documents and Settings\Hansifer\My Documents\Files\Career\Origin Digital\code\Odaptor\ALPClasses\clsSimpleAsset.vb:line 813; RERUN on 8/5/2008 3:45:17 PM by OD Encoders.

    [highlight=#ffff11]please any one reply me back it's very urgent.[/highlight]

  • Set the commandTimeout property in the Connection object to 0 (= no timeout).

    -- Gianluca Sartori

  • To specifically address the question, start by looking at the connection object created by the application within the application code itself. The connection string probably does not have the timeout value specified. If you're using ADO.NET, I believe by not specifying the TIMEOUT value for the connection string, you accept the default which I believe is 30 seconds.

    If you specify a timeout of 0, you tell the connection object to never time out.

    Usually, SQL Server isn't configured to timeout connections at the server side. Not by default in any case.

    If that doesn't help, make sure there's not a weird network-related issue occurring. A simple ping to the SQL Server should be able to at least tell you if the server connection can be established in the first place, and what kind of latency you may have.

Viewing 3 posts - 1 through 2 (of 2 total)

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