[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4708
  • Last Modified:

SBS 2008 web site only displaying 'HTTP/1.1 200 OK Server: Microsoft-IIS/7.0 Date: Wed, 29 Apr 2009 06:56:07 GMT Connection: close ' ?

When I start the default Small Business Server web site http://companyweb, I get the following message : 'HTTP/1.1 200 OK Server: Microsoft-IIS/7.0 Date: Wed, 29 Apr 2009 06:56:07 GMT Connection: close ' There is a web page and the site is local. Can any body advise as to why I am not seeing the website. The website sits on SharePoint
0
CaussyR
Asked:
CaussyR
  • 2
1 Solution
 
CaussyRAuthor Commented:
The event log has the following error:

Log Name:      Application
Source:        Windows SharePoint Services 3
Date:          29/04/2009 09:15:07
Event ID:      5586
Task Category: Database
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CWOSBS3001.cwideonline.local
Description:
Unknown SQL Exception 33002 occured. Additional error information from SQL Server is included below.

Access to module dbo.proc_MSS_Cleanup is blocked because the signature is not valid.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows SharePoint Services 3" />
    <EventID Qualifiers="0">5586</EventID>
    <Level>2</Level>
    <Task>484</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-04-29T08:15:07.000Z" />
    <EventRecordID>446757</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CWOSBS3001.cwideonline.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>33002</Data>
    <Data>Access to module dbo.proc_MSS_Cleanup is blocked because the signature is not valid.</Data>
  </EventData>
</Event>
0
 
CaussyRAuthor Commented:
This was resolved by restoring all of SharePoint databases, 9 in total, from VSS backup.  The restored databases were placed in a new folder. The live SQL databases were detached and the restored databases attached. Replaced them on the Windows Internal Database instance.  Then the SharePoint Job cache using the following procedure had to be cleared:

- Backup and delete all of the *.xml files in c:\programdata\Microsoft\SharePoint\Config\<GUID>
- Edit the Cache.ini and replace the value with 1.
- Restart the Windows SharePoint Timer service
0
 
ITnavigatorsCommented:
Similar behavior.  In my case I was able to quickly resolve the problem by restarting the MSSQL$MICROSOFT##SSEE service from the services tab in Task Manager.  The service  doesn't appear in services.msc.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now