Hello,
I am having a problem connecting to SQL server 2000 through enterprise manager. Whenever i try to look at a table, view or DTS package I get the message...
"The query cannot be executed because some files are either missing or not registered. Run setup again to make sure the required files are registered."
I have tried to re-register, unregister and re-register.
I have tried to create a new instance of SQL server and attach the Data files to this.
I have tried to Re-install client tools.
The only option I am left with is totally removing SQL server and re-installing then restoring the Databases from a backup tape...
I just wanted to know if anyone has anyother ideas before i go ahead and do this.
Thanks in advance.
JF
One more thing...
I can access all of the tables through access and excel and other data analyzers as I normally would.hi
have you tried checking the error on microsoft tech net, they dont always mean what they say. have had lot of success in the past
all the best
Originally posted by josef fukano
Hello,
I am having a problem connecting to SQL server 2000 through enterprise manager. Whenever i try to look at a table, view or DTS package I get the message...
"The query cannot be executed because some files are either missing or not registered. Run setup again to make sure the required files are registered."
I have tried to re-register, unregister and re-register.
I have tried to create a new instance of SQL server and attach the Data files to this.
I have tried to Re-install client tools.
The only option I am left with is totally removing SQL server and re-installing then restoring the Databases from a backup tape...
I just wanted to know if anyone has anyother ideas before i go ahead and do this.
Thanks in advance.
JF
One more thing...
I can access all of the tables through access and excel and other data analyzers as I normally would.|||Originally posted by kpaynter
hi
have you tried checking the error on microsoft tech net, they dont always mean what they say. have had lot of success in the past
all the best
kpaynter
I found this article on microsoft tech net...
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b315868
On it has commands to be ran in command promt.
It did the trick, thank you very much for your reply...
You saved my 3 day weekend!!!!
Thanks again,
JF
Showing posts with label connecting. Show all posts
Showing posts with label connecting. Show all posts
Wednesday, March 21, 2012
Sunday, February 19, 2012
File in use error on connecting to database.
* Running SQL 2005 on XP Pro *
After running a ETL package to populate a sample DW which completed successfully, I attempted to open the SQL Server Management Studio. After login, an error was reported :
TITLE: Microsoft SQL Server Management Studio
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
ADDITIONAL INFORMATION:
Database 'msdb' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. (Microsoft SQL Server, Error: 945)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=945&LinkId=20476
In the server error log I see... (note, the problem persists after reboot)
2006-01-13 11:24:07.25 spid12s The Service Broker protocol transport is disabled or not configured.
2006-01-13 11:24:07.25 spid12s The Database Mirroring protocol transport is disabled or not configured.
2006-01-13 11:24:07.77 Logon Error: 17187, Severity: 16, State: 1.
2006-01-13 11:24:07.77 Logon SQL Server is not ready to accept new client connections; the connection has been closed. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: <local machine>]
2006-01-13 11:24:07.82 Logon Error: 17187, Severity: 16, State: 1.
2006-01-13 11:24:07.82 Logon SQL Server is not ready to accept new client connections; the connection has been closed. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: <local machine>]
2006-01-13 11:24:08.24 spid12s Service Broker manager has started.
2006-01-13 11:24:14.97 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2006-01-13 11:24:14.97 Server Dedicated admin connection support was established for listening locally on port 1434.
2006-01-13 11:24:14.97 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-01-13 11:24:17.28 Logon Error: 18456, Severity: 14, State: 16.
2006-01-13 11:24:17.28 Logon Login failed for user 'FUSION-NET\scottt'. [CLIENT: <local machine>]
2006-01-13 11:24:18.91 spid15s Starting up database 'ReportServer'.
2006-01-13 11:24:18.91 spid14s Starting up database 'msdb'.
2006-01-13 11:24:18.91 spid17s Starting up database 'Subscriptions'.
2006-01-13 11:24:18.91 spid16s Starting up database 'ReportServerTempDB'.
2006-01-13 11:24:19.23 spid14s Error: 17207, Severity: 16, State: 1.
2006-01-13 11:24:19.23 spid14s FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-13 11:24:19.23 spid14s Error: 17204, Severity: 16, State: 1.
2006-01-13 11:24:19.23 spid14s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
2006-01-13 11:24:19.25 spid14s Error: 5120, Severity: 16, State: 101.
2006-01-13 11:24:19.25 spid14s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
2006-01-13 11:24:19.37 spid16s Error: 17207, Severity: 16, State: 1.
2006-01-13 11:24:19.37 spid16s FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-13 11:24:19.37 spid17s Error: 17207, Severity: 16, State: 1.
2006-01-13 11:24:19.37 spid17s FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Subscriptions.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-13 11:24:19.37 spid17s Error: 17204, Severity: 16, State: 1.
2006-01-13 11:24:19.37 spid17s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Subscriptions.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
2006-01-13 11:24:19.37 spid17s Error: 5120, Severity: 16, State: 101.
2006-01-13 11:24:19.37 spid17s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Subscriptions.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
2006-01-13 11:24:19.38 spid16s Error: 17204, Severity: 16, State: 1.
2006-01-13 11:24:19.38 spid16s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
2006-01-13 11:24:19.38 spid16s Error: 5120, Severity: 16, State: 101.
2006-01-13 11:24:19.38 spid16s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
2006-01-13 11:24:19.91 spid14s Starting up database 'AdventureWorksDW'.
2006-01-13 11:24:19.91 spid17s Starting up database 'AdventureWorks'.
2006-01-13 11:24:19.91 spid16s Starting up database 'DnBSampleDW'.
2006-01-13 11:24:28.07 spid5s Error: 8355, Severity: 16, State: 1.
2006-01-13 11:24:28.07 spid5s Service Broker is disabled in MSDB or MSDB failed to start. Server level event notifications can not be delivered. Event notifications with FAN_IN in other databases could be affected as well.
2006-01-13 11:24:28.11 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-01-13 11:24:34.23 Logon Error: 18456, Severity: 14, State: 16.
2006-01-13 11:24:34.23 Logon Login failed for user 'FUSION-NET\scottt'. [CLIENT: <local machine>]
2006-01-13 11:24:34.90 Logon Error: 18456, Severity: 14, State: 16.
2006-01-13 11:24:34.90 Logon Login failed for user 'FUSION-NET\scottt'. [CLIENT: <local machine>]
2006-01-13 11:26:50.52 spid53 Using 'xpstar90.dll' version '2005.90.1399' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
Just a note here... I let the computer sit after a reboot while at lunch, I opened the Studio and tried the connection and it came up just fine...
|||I am getting a similar problem with my instance running on Windows 2003 Server. I have a database that is used by a .Net application. When somebody is using the .Net application I am unable to open the database in Management Studio. The same goes the other way, when I have the database open in Management Studio the application is unable to access the database. Why can I not have the database open and still have the application access the database?|||Turn your anti-virus scanner off or at least exclude the directory containing your SQL Server files from the scanning.|||I have a similar problem here but it occurs only when I attempt to use my other application's web service which needs to be connected to my db. The db's file is there.
System.Web.Services.Protocols.SoapException: Server was unable to process request. > System.Data.SqlClient.SqlException: Unable to open the physical file "c:\inetpub\wwwroot\WebSite1\App_Data\ASPNETDB.MDF". Operating system error 32: "32(error not found)".
An attempt to attach an auto-named database for file c:\inetpub\wwwroot\WebSite1\App_Data\ASPNETDB.MDF failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
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.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at ViewPropertyTableAdapters.AgentInfoTableAdapter.GetAgentInfo(String AgentUserName) in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\website1\353383d4\c7efb847\App_Code.ekppx9ry.1.vb:line 3229
at getDetails.getAgentInfo(String userName) in c:\inetpub\wwwroot\WebSite1\App_Code\getDetails.vb:line 11
at getAgentContact.getContact(String userName) in c:\inetpub\wwwroot\WebSite1\App_Code\getAgentContact.vb:line 17
File in use error on connecting to database.
* Running SQL 2005 on XP Pro *
After running a ETL package to populate a sample DW which completed successfully, I attempted to open the SQL Server Management Studio. After login, an error was reported :
TITLE: Microsoft SQL Server Management Studio
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
ADDITIONAL INFORMATION:
Database 'msdb' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. (Microsoft SQL Server, Error: 945)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=945&LinkId=20476
In the server error log I see... (note, the problem persists after reboot)
2006-01-13 11:24:07.25 spid12s The Service Broker protocol transport is disabled or not configured.
2006-01-13 11:24:07.25 spid12s The Database Mirroring protocol transport is disabled or not configured.
2006-01-13 11:24:07.77 Logon Error: 17187, Severity: 16, State: 1.
2006-01-13 11:24:07.77 Logon SQL Server is not ready to accept new client connections; the connection has been closed. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: <local machine>]
2006-01-13 11:24:07.82 Logon Error: 17187, Severity: 16, State: 1.
2006-01-13 11:24:07.82 Logon SQL Server is not ready to accept new client connections; the connection has been closed. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: <local machine>]
2006-01-13 11:24:08.24 spid12s Service Broker manager has started.
2006-01-13 11:24:14.97 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2006-01-13 11:24:14.97 Server Dedicated admin connection support was established for listening locally on port 1434.
2006-01-13 11:24:14.97 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-01-13 11:24:17.28 Logon Error: 18456, Severity: 14, State: 16.
2006-01-13 11:24:17.28 Logon Login failed for user 'FUSION-NET\scottt'. [CLIENT: <local machine>]
2006-01-13 11:24:18.91 spid15s Starting up database 'ReportServer'.
2006-01-13 11:24:18.91 spid14s Starting up database 'msdb'.
2006-01-13 11:24:18.91 spid17s Starting up database 'Subscriptions'.
2006-01-13 11:24:18.91 spid16s Starting up database 'ReportServerTempDB'.
2006-01-13 11:24:19.23 spid14s Error: 17207, Severity: 16, State: 1.
2006-01-13 11:24:19.23 spid14s FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-13 11:24:19.23 spid14s Error: 17204, Severity: 16, State: 1.
2006-01-13 11:24:19.23 spid14s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
2006-01-13 11:24:19.25 spid14s Error: 5120, Severity: 16, State: 101.
2006-01-13 11:24:19.25 spid14s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
2006-01-13 11:24:19.37 spid16s Error: 17207, Severity: 16, State: 1.
2006-01-13 11:24:19.37 spid16s FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-13 11:24:19.37 spid17s Error: 17207, Severity: 16, State: 1.
2006-01-13 11:24:19.37 spid17s FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Subscriptions.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-13 11:24:19.37 spid17s Error: 17204, Severity: 16, State: 1.
2006-01-13 11:24:19.37 spid17s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Subscriptions.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
2006-01-13 11:24:19.37 spid17s Error: 5120, Severity: 16, State: 101.
2006-01-13 11:24:19.37 spid17s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Subscriptions.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
2006-01-13 11:24:19.38 spid16s Error: 17204, Severity: 16, State: 1.
2006-01-13 11:24:19.38 spid16s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
2006-01-13 11:24:19.38 spid16s Error: 5120, Severity: 16, State: 101.
2006-01-13 11:24:19.38 spid16s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
2006-01-13 11:24:19.91 spid14s Starting up database 'AdventureWorksDW'.
2006-01-13 11:24:19.91 spid17s Starting up database 'AdventureWorks'.
2006-01-13 11:24:19.91 spid16s Starting up database 'DnBSampleDW'.
2006-01-13 11:24:28.07 spid5s Error: 8355, Severity: 16, State: 1.
2006-01-13 11:24:28.07 spid5s Service Broker is disabled in MSDB or MSDB failed to start. Server level event notifications can not be delivered. Event notifications with FAN_IN in other databases could be affected as well.
2006-01-13 11:24:28.11 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-01-13 11:24:34.23 Logon Error: 18456, Severity: 14, State: 16.
2006-01-13 11:24:34.23 Logon Login failed for user 'FUSION-NET\scottt'. [CLIENT: <local machine>]
2006-01-13 11:24:34.90 Logon Error: 18456, Severity: 14, State: 16.
2006-01-13 11:24:34.90 Logon Login failed for user 'FUSION-NET\scottt'. [CLIENT: <local machine>]
2006-01-13 11:26:50.52 spid53 Using 'xpstar90.dll' version '2005.90.1399' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
Just a note here... I let the computer sit after a reboot while at lunch, I opened the Studio and tried the connection and it came up just fine...
|||I am getting a similar problem with my instance running on Windows 2003 Server. I have a database that is used by a .Net application. When somebody is using the .Net application I am unable to open the database in Management Studio. The same goes the other way, when I have the database open in Management Studio the application is unable to access the database. Why can I not have the database open and still have the application access the database?|||Turn your anti-virus scanner off or at least exclude the directory containing your SQL Server files from the scanning.|||I have a similar problem here but it occurs only when I attempt to use my other application's web service which needs to be connected to my db. The db's file is there.
System.Web.Services.Protocols.SoapException: Server was unable to process request. > System.Data.SqlClient.SqlException: Unable to open the physical file "c:\inetpub\wwwroot\WebSite1\App_Data\ASPNETDB.MDF". Operating system error 32: "32(error not found)".
An attempt to attach an auto-named database for file c:\inetpub\wwwroot\WebSite1\App_Data\ASPNETDB.MDF failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
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.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at ViewPropertyTableAdapters.AgentInfoTableAdapter.GetAgentInfo(String AgentUserName) in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\website1\353383d4\c7efb847\App_Code.ekppx9ry.1.vb:line 3229
at getDetails.getAgentInfo(String userName) in c:\inetpub\wwwroot\WebSite1\App_Code\getDetails.vb:line 11
at getAgentContact.getContact(String userName) in c:\inetpub\wwwroot\WebSite1\App_Code\getAgentContact.vb:line 17
File in use error on connecting to database.
* Running SQL 2005 on XP Pro *
After running a ETL package to populate a sample DW which completed successfully, I attempted to open the SQL Server Management Studio. After login, an error was reported :
TITLE: Microsoft SQL Server Management Studio
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
ADDITIONAL INFORMATION:
Database 'msdb' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. (Microsoft SQL Server, Error: 945)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=945&LinkId=20476
In the server error log I see... (note, the problem persists after reboot)
2006-01-13 11:24:07.25 spid12s The Service Broker protocol transport is disabled or not configured.
2006-01-13 11:24:07.25 spid12s The Database Mirroring protocol transport is disabled or not configured.
2006-01-13 11:24:07.77 Logon Error: 17187, Severity: 16, State: 1.
2006-01-13 11:24:07.77 Logon SQL Server is not ready to accept new client connections; the connection has been closed. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: <local machine>]
2006-01-13 11:24:07.82 Logon Error: 17187, Severity: 16, State: 1.
2006-01-13 11:24:07.82 Logon SQL Server is not ready to accept new client connections; the connection has been closed. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: <local machine>]
2006-01-13 11:24:08.24 spid12s Service Broker manager has started.
2006-01-13 11:24:14.97 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2006-01-13 11:24:14.97 Server Dedicated admin connection support was established for listening locally on port 1434.
2006-01-13 11:24:14.97 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-01-13 11:24:17.28 Logon Error: 18456, Severity: 14, State: 16.
2006-01-13 11:24:17.28 Logon Login failed for user 'FUSION-NET\scottt'. [CLIENT: <local machine>]
2006-01-13 11:24:18.91 spid15s Starting up database 'ReportServer'.
2006-01-13 11:24:18.91 spid14s Starting up database 'msdb'.
2006-01-13 11:24:18.91 spid17s Starting up database 'Subscriptions'.
2006-01-13 11:24:18.91 spid16s Starting up database 'ReportServerTempDB'.
2006-01-13 11:24:19.23 spid14s Error: 17207, Severity: 16, State: 1.
2006-01-13 11:24:19.23 spid14s FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-13 11:24:19.23 spid14s Error: 17204, Severity: 16, State: 1.
2006-01-13 11:24:19.23 spid14s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
2006-01-13 11:24:19.25 spid14s Error: 5120, Severity: 16, State: 101.
2006-01-13 11:24:19.25 spid14s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
2006-01-13 11:24:19.37 spid16s Error: 17207, Severity: 16, State: 1.
2006-01-13 11:24:19.37 spid16s FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-13 11:24:19.37 spid17s Error: 17207, Severity: 16, State: 1.
2006-01-13 11:24:19.37 spid17s FCB::Open: Operating system error 32(The process cannot access the file because it is being used by another process.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Subscriptions.mdf'. Diagnose and correct the operating system error, and retry the operation.
2006-01-13 11:24:19.37 spid17s Error: 17204, Severity: 16, State: 1.
2006-01-13 11:24:19.37 spid17s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Subscriptions.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
2006-01-13 11:24:19.37 spid17s Error: 5120, Severity: 16, State: 101.
2006-01-13 11:24:19.37 spid17s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\Subscriptions.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
2006-01-13 11:24:19.38 spid16s Error: 17204, Severity: 16, State: 1.
2006-01-13 11:24:19.38 spid16s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf for file number 1. OS error: 32(The process cannot access the file because it is being used by another process.).
2006-01-13 11:24:19.38 spid16s Error: 5120, Severity: 16, State: 101.
2006-01-13 11:24:19.38 spid16s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
2006-01-13 11:24:19.91 spid14s Starting up database 'AdventureWorksDW'.
2006-01-13 11:24:19.91 spid17s Starting up database 'AdventureWorks'.
2006-01-13 11:24:19.91 spid16s Starting up database 'DnBSampleDW'.
2006-01-13 11:24:28.07 spid5s Error: 8355, Severity: 16, State: 1.
2006-01-13 11:24:28.07 spid5s Service Broker is disabled in MSDB or MSDB failed to start. Server level event notifications can not be delivered. Event notifications with FAN_IN in other databases could be affected as well.
2006-01-13 11:24:28.11 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-01-13 11:24:34.23 Logon Error: 18456, Severity: 14, State: 16.
2006-01-13 11:24:34.23 Logon Login failed for user 'FUSION-NET\scottt'. [CLIENT: <local machine>]
2006-01-13 11:24:34.90 Logon Error: 18456, Severity: 14, State: 16.
2006-01-13 11:24:34.90 Logon Login failed for user 'FUSION-NET\scottt'. [CLIENT: <local machine>]
2006-01-13 11:26:50.52 spid53 Using 'xpstar90.dll' version '2005.90.1399' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
Just a note here... I let the computer sit after a reboot while at lunch, I opened the Studio and tried the connection and it came up just fine...
|||I am getting a similar problem with my instance running on Windows 2003 Server. I have a database that is used by a .Net application. When somebody is using the .Net application I am unable to open the database in Management Studio. The same goes the other way, when I have the database open in Management Studio the application is unable to access the database. Why can I not have the database open and still have the application access the database?|||Turn your anti-virus scanner off or at least exclude the directory containing your SQL Server files from the scanning.|||I have a similar problem here but it occurs only when I attempt to use my other application's web service which needs to be connected to my db. The db's file is there.
System.Web.Services.Protocols.SoapException: Server was unable to process request. > System.Data.SqlClient.SqlException: Unable to open the physical file "c:\inetpub\wwwroot\WebSite1\App_Data\ASPNETDB.MDF". Operating system error 32: "32(error not found)".
An attempt to attach an auto-named database for file c:\inetpub\wwwroot\WebSite1\App_Data\ASPNETDB.MDF failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
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.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at ViewPropertyTableAdapters.AgentInfoTableAdapter.GetAgentInfo(String AgentUserName) in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\website1\353383d4\c7efb847\App_Code.ekppx9ry.1.vb:line 3229
at getDetails.getAgentInfo(String userName) in c:\inetpub\wwwroot\WebSite1\App_Code\getDetails.vb:line 11
at getAgentContact.getContact(String userName) in c:\inetpub\wwwroot\WebSite1\App_Code\getAgentContact.vb:line 17
Subscribe to:
Posts (Atom)