melwong
asked on
Timeout Expired , The timeout period elapsed prior to completion of the operation or the server is not responding
Hi there,
I using KenicoCMS software to manage website , installed MS SQL Server 2005 and restored all the files from bak db . Firstly it can works but afterward i facing the following errors : -
[DataConnection.ExecuteQue ry]: Query: Proc_CMS_QueryProvider_Sel ectAll: caused exception: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
And i checking the db log file viewer it show this error : -
[Login failed for 'sa']
[error 18456 severity 14 state 16]
I sent to the support and reply as this but not works :-
Following error occurs when application is trying to access your database:
Error: 18456, Severity: 14, State: 16.
It indicates that the session database could not be determined which may mean that the database is offline or the user does not have permissions to access the database. You can verify the name and location of the mdf file and make sure that the user has permissions to read and write the file (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ MusuemInve ntory.mdf) .
Hope can help for this .
MS Sql Server 2005 Info :
Microsoft SQL Server Management Studio - 9.00.1399.00
Microsoft Analysis Services Client Tools - 2005.090.1399.00
Microsoft Data Access Components (MDAC) - 2000.086.3959.00 (srv03_sp2_rtm.070216-1710 )
Microsoft MSXML - 2.6 3.0 6.0
Microsoft Internet Explorer - 7.0.5730.13
Microsoft .NET Framework - 2.0.50727.42
Operating System - 5.2.3790
Window Server 2003 Info :
Microsoft Windows Server 2003 R2 Enterprise x64 Edition Service Pack 2
Cannot-open-database.JPG
I using KenicoCMS software to manage website , installed MS SQL Server 2005 and restored all the files from bak db . Firstly it can works but afterward i facing the following errors : -
[DataConnection.ExecuteQue
And i checking the db log file viewer it show this error : -
[Login failed for 'sa']
[error 18456 severity 14 state 16]
I sent to the support and reply as this but not works :-
Following error occurs when application is trying to access your database:
Error: 18456, Severity: 14, State: 16.
It indicates that the session database could not be determined which may mean that the database is offline or the user does not have permissions to access the database. You can verify the name and location of the mdf file and make sure that the user has permissions to read and write the file (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\
Hope can help for this .
MS Sql Server 2005 Info :
Microsoft SQL Server Management Studio - 9.00.1399.00
Microsoft Analysis Services Client Tools - 2005.090.1399.00
Microsoft Data Access Components (MDAC) - 2000.086.3959.00 (srv03_sp2_rtm.070216-1710
Microsoft MSXML - 2.6 3.0 6.0
Microsoft Internet Explorer - 7.0.5730.13
Microsoft .NET Framework - 2.0.50727.42
Operating System - 5.2.3790
Window Server 2003 Info :
Microsoft Windows Server 2003 R2 Enterprise x64 Edition Service Pack 2
[DataConnection.ExecuteQuery]: Query: Proc_CMS_QueryProvider_SelectAll: caused exception: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
timout-expired.JPGCannot-open-database.JPG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I just read through the link that u provided : -
Matt Neerincx [MSFT] said:
State=16 means that the incoming user does not have permissions to log into the target database. So for example say you create a user FOO and set FOO's default database to master, but FOO does not have permissions to log into master.
This can also happen if for example the default database for user FOO is not online (for example the database is marked suspect).
So to check on this theory, try logging the user into some other database and then try using the USE DATABASE command to switch to the target database, you will get a better error message as to the root cause of the failure.
The question is how to "USE DATABASE" command work to switch to target database ?
can you explain more for that ?
Matt Neerincx [MSFT] said:
State=16 means that the incoming user does not have permissions to log into the target database. So for example say you create a user FOO and set FOO's default database to master, but FOO does not have permissions to log into master.
This can also happen if for example the default database for user FOO is not online (for example the database is marked suspect).
So to check on this theory, try logging the user into some other database and then try using the USE DATABASE command to switch to the target database, you will get a better error message as to the root cause of the failure.
The question is how to "USE DATABASE" command work to switch to target database ?
can you explain more for that ?
ASKER
I am running Ms Sql Server 2005 (32bit) in the OS (64bit), is that rise any incompatibility ?
SQL Server 2005 SP2 should help.
"...
The question is how to "USE DATABASE" command work to switch to target database ?
can you explain more for that ?
..."
just run it using sa., replace word "DATABASE" with name of the database we are troubleshooting.
"I am running Ms Sql Server 2005 (32bit) in the OS (64bit), is that rise any incompatibility ?"
with SP2 applied Ms Sql Server 2005 (32bit) in the OS (64bit) runs free of issues.
-- cheers
"...
The question is how to "USE DATABASE" command work to switch to target database ?
can you explain more for that ?
..."
just run it using sa., replace word "DATABASE" with name of the database we are troubleshooting.
"I am running Ms Sql Server 2005 (32bit) in the OS (64bit), is that rise any incompatibility ?"
with SP2 applied Ms Sql Server 2005 (32bit) in the OS (64bit) runs free of issues.
-- cheers
Can you poste here the code for stored procedure Proc_CMS_QueryProvider_Sel ectAll?
any progress?
-- cheers
-- cheers
Did you try to connect to server and see if you can reach database GUA using administrative account. I wonder if the issue is sa account or database itself. Though SQL Server 2005 has a number of security features that need to be kept in mind when similar errors occur. See this link for more info.
-- cheers