Showing posts with label sql server. Show all posts
Showing posts with label sql server. Show all posts

Tuesday, June 19, 2012

Event ID : 3760, Database error, Sharepoint

The following error was repeatedly appearing since 2 days in one of my WFE continuosly every 5 mins.

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 3760
Date:
Time: 9:15:27 PM
User: N/A
Computer: XXXXXXX
Description:
SQL Database 'WSS_Content_XXXXX' on SQL Server instance 'DBSERVER' not found. Additional error information from SQL Server is included below.

Cannot open database "WSS_Content_XXXXX" requested by the login. The login failed.
Login failed for user 'Domain\adminuser'.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

The reason was, the Database seems to be not accessible.
The solution is to remove the content db to avoid errors.
For that, login to central admin site go to Application Management -> Content Databases. select the webapp having the content db and click on remove content db will solve the problem.

Friday, February 17, 2012

Unable to modify table, time out expired error

When I tried to modify a table structure in  with more than 20 million records. It gave me the time out expired error. This occurred in MS SQL Server 2005
The modifications were not saved.


When I initially tried to save the modifications for the table, a warning message appeared for me. 




Later I clicked yes and again waited for the result. It finally gave me an error saying that, 'time out expired' after 30 seconds.






The error was "Errors were encountered during the save process. Some database objects were not saved" and "Unable to modify table. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." The table structure was same as previous.


Reason for this is the time out setting in the designer option. It would be set to 30 seconds by default. If you changes take longer than that time then they would not be saved. We need to change the value of the setting.


For this, go to Tools -> Options -> Designers


There will be check box option of "Override connection time-out value for table designers updates:" and "Transaction time-out after:" change the default value of 30 secs to the a higher value. In my case I made it 1000 seconds. And then click on OK. Do remember that transaction time out setting value should be greater than 0 and it should be in the range between 1- 65535. 


Now after doing this change, I tried to modify the table and the changes got saved now. 
Note that while the table modifications are saved, the SQL Management studio would remain inaccessible till the changes to complete.