I broke Sharepoint :(



Hello everyone,

I have made some obvious silly mistakes and I am now stuck any help will be
greatly appreciated.

1. SBS was installed and the server was up and running including the default
Sharepoint which comes with it.
2. After a week a bespoke app had to be deployed which required SQL.
3. We had SBS premium edition hence I ran the install from the CD and it was
installed fine ( Note: the options we selected to install all of the
componenets. ( Default Instance)
4. Once this was done the engineer from the applications team came in and
compelted his work and got his application working on the server and left.
5. After 2 days I was looking at SQL backups I relaised that Sharepoint
database and the other instances were not migrated accross.

Actions performed:
Stopped the SharePoint timer service and than stopped the companyweb website
& I decided to backup the sharepoint databases. Than I uninstalled the
Sharepoint instance of sql and used the attach mechanisum to attach the
data.

When I went back to sharepoint it was broke. :(

Not to my surpirse I went in the Sharepoint administration and tried to
change the database and config settings to the sql server but it would not
work.

So I deleted the old datbases and started from sratch by playing with some
options by extending the virtual directory again and than it finally created
the new website again. Let me not forget it looks very different but it is
one of the defaults.

When I than accessed the companyweb site it asked me for a templte I
selected the first option "team site" and all seemed well.

BUT now I see the following errors in the application log + when I try to
upload documents and stuff soem pages are giving me errors.

****************************
I would like to get the Sharepoint working how it was out of the box when
SBS was installed but would like to have the database connected to SQL 2005
not another instance of MSDE
******************************


Event Type: Error
Event Source: Windows SharePoint Services 2.0
Event Category: None
Event ID: 1000
Date: 20/05/2007
Time: 20:06:10
User: N/A
Computer: SBS
Description:
#50070: Unable to connect to the database STS_Config on SBS. 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.


Event Type: Error
Event Source: Windows SharePoint Services 2.0
Event Category: None
Event ID: 1000
Date: 20/05/2007
Time: 20:06:10
User: N/A
Computer: SBS
Description:
#50070: Unable to connect to the database STS_Config on SBS. 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.

Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 18456
Date: 20/05/2007
Time: 20:06:10
User: NT AUTHORITY\SYSTEM
Computer: SBS
Description:
Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: 10.10.50.1]

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00 .H......
0008: 04 00 00 00 53 00 42 00 ....S.B.
0010: 53 00 00 00 07 00 00 00 S.......
0018: 6d 00 61 00 73 00 74 00 m.a.s.t.
0020: 65 00 72 00 00 00 e.r...

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 18056
Date: 20/05/2007
Time: 18:53:47
User: NT AUTHORITY\NETWORK SERVICE
Computer: SBS
Description:
The client was unable to reuse a session with SPID 69, which had been reset
for connection pooling. This error may have been caused by an earlier
operation failing. Check the error logs for failed operations immediately
before this error message.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 88 46 00 00 14 00 00 00 ?F......
0008: 04 00 00 00 53 00 42 00 ....S.B.
0010: 53 00 00 00 00 00 00 00 S.......


any help will be appreciated.

cheers
SBS Admin


.



Relevant Pages

  • RE: transfer companyweb config db
    ... configuration database for sharepoint services to a new location on the sql ... You may mistake SQL server conception. ... Move the Monitoring Database ... >project web access not working correctly is to use a config database on ...
    (microsoft.public.windows.server.sbs)
  • RE: Cisco801
    ... Routing Table on the SBS 2K3 server. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... You just need to add the database IP ...
    (microsoft.public.windows.server.sbs)
  • RE: Sharepoint and SBS2003 SP1
    ... If your companyweb can work well, this would be a known issue in SBS server ... To resolve the issue, please refer to the following knowledge based ... their SharePoint site could fail. ...
    (microsoft.public.windows.server.sbs)
  • Re: File transfers from LAN clients to Sharepoint get corrupted
    ... Transferring files to Sharepoint via the Companyweb browser interface is ... Is there anything on the server you'd suggest I checking regarding ... Les Connor [SBS MVP] ... I'll try replicating the problem from LAN clients that use different ...
    (microsoft.public.windows.server.sbs)
  • Re: sharepoint error
    ... If you are using SBS 2003 Premium Edition the easiest way is to follow ... to upgrade the SharePoint named instance. ... and search on "Migrating from WMSDE to SQL Server" ... Microsoft Small Business Server Support ...
    (microsoft.public.windows.server.sbs)