My client had an issue with their server dying on them and needed it replaced, this was prior to my taking over thier maintenance. Anyway the company that built it basically messed it up and then tried to cover thier tracks. I believe things went wrong when they installed a service pack. Basically, company web does not work, exchange does not work, connect computer wizard doesn't work. As the customer didn't use exchange or company web the previous IT company decided not to tell the customer and connected the computers to the domain the old way. I have now taken over maintaing the server and would like to set it up so the customer can use exchange and companyweb, it would also be nice to be able to use the connect computer wizard and not have all these sharepoint errors in the event log every few seconds. The customer doesn't really want the have the server rebuilt as they were without it long enough when this one was being built. Below is a list of issues and error logs, hope someone can talk me through some ideas to try and resolve this without a rebuild. Event Type: Error Event Source: Windows SharePoint Services 2.0 Event Category: None Event ID: 1000 Date: 28/02/2008 Time: 13:44:20 User: N/A Computer: MID-SERVER-1 Description: #50070: Unable to connect to the database STS_Config on MID-SERVER\SharePoint. Check the database connection information and make sure that the database server is running. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. ---------------------------------------------------------------- CompanyWeb: will not display and redirects to google search. ------------------------- Servers local IP: 192.168.16.2 displays 'Welcome to Windows Small Business Server 2003' Clicking on 'My Company's Internal Website' displays Internet Explorer cannot display the webpage -------------------- Exchange not working: Attempt to start information store results in error dependancy failed to start (dependancy is System attendant) Attempt to start Exchange System Attendant results in following event logs: Event Type: ErrorEvent Source: MSExchangeSAEvent Category: General Event ID: 1038Date: 28/02/2008Time: 14:05:22User: N/AComputer: MID-SERVER-1 Description:Microsoft Exchange System Attendant was unable to find the Exchange server object named 'MID-SERVER-1' in the Active Directory. All known Domain Controllers were checked for this object. ---------------------------------------- Event Type: ErrorEvent Source: MSExchangeSAEvent Category: General Event ID: 9149Date: 28/02/2008Time: 14:05:22User: N/AComputer: MID-SERVER-1 Description: Microsoft Exchange System Attendant failed to start Exchange server 'MID-SERVER-1'. Error code '0x80072030'. ------------------------------------ Event Type: ErrorEvent Source: MSExchangeSAEvent Category: General Event ID: 1005Date: 28/02/2008Time: 14:05:22User: N/AComputer: MID-SERVER-1 Description:Unexpected error There is no such object on the server. Facility: Win32 ID no: 80072030 Microsoft Exchange System Attendant occurred.