Showing posts with label MOSS. Show all posts
Showing posts with label MOSS. 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.

Tuesday, June 12, 2012

Publishing Cache Error, Event Id 5785

In one of my WFE event viewer, I received the following error continously

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Publishing Cache
Event ID: 5785
Date:  
Time:  9:30:46 AM
User:  N/A
Computer: xxxxx
Description:
Unable to connect publishing custom string handler for output caching. IIS Instance Id is '1851498615', Url is 'http://url/_layouts/images/*.GIF'.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

The reason for this error is that, the images inside the layouts folder was not able to be cached by sharepoint.

Following is the resolution for it.

Open the web.config file, look for <location path="_layouts/images">
just before the </System.Web> tag place the following code

<httpmodules>
<remove name="PublishingHttpModule">
</httpmodules>

 From now on, the error will not appear in the event viewer.
Thanks for the blog post which helped me in solving this issue.