These forums are read-only and considered to be an archive. Please use the new Community for future interaction and posts.

Timeout Error During Logout

FileVista was not functioning yesterday. The error I received was:

Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 7/30/2009 3:16:47 PM 
Event time (UTC): 7/30/2009 7:16:47 PM 
Event ID: 37f7b54ecff6497fbca810aca267ec45 
Event sequence: 40 
Event occurrence: 13 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/529271765/Root/FileVista-1-128934539408201834 
    Trust level: Full 
    Application Virtual Path: /FileVista 
    Application Path: C:\Inetpub\wwwroot\FileVista\ 
    
Process information: 
    Process ID: 780 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\NETWORK SERVICE 
 
Exception information: 
    Exception type: OleDbException 
    Exception message: Timeout expired 
 
Request information: 
    Request URL: https://10.96.71.114:443/filevista/administration.asmx/LogoutUser 
    Request path: /filevista/administration.asmx/LogoutUser 

Stack Trace:

Stack trace:    at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
   at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.OleDb.OleDbConnection.Open()
   at GleamTech.FileVista.OleDbDataManager.GetNumberOfEvents()
   at GleamTech.FileVista.OleDbDataManager..ctor(String connectionString)
   at GleamTech.FileVista.FileVistaApplication..cctor()

I just restarted IIS and everything was fine. What caused this error?

Thanks!
Ken 7/31/2009 11:22 AM
It seems your network was down at that moment so the connection to the SQL server was interrupted.
Cem Alacayir 8/10/2009 1:52 PM