Sharepoint 3.0 Sites Not Working

Hello,

SBS2003, SQL 2000, ISA2004

I have installed WSS 3.0 on my SBS and am having some problems. While I am
able to see and work in the Central Administration console and am able to
create a Web Application and see it on the list, I am unable to go to the
application using the link http://[sbsserver]:[portnumber]. I beleive the
problem lies with the databases. First of all, I cant find them in the same
folder as the SharePoint_AdminContent, SharePoint_Config, and WSS_Search
databases (which I have moved from the default location for space reasons).
Also, I get the following two events in my logs every night:

Source: Windows SharePoint Services
Category: Database
EventID: 3760
Description:
SQL Database 'SharePoint_Config_f76b131a-35b0-4e8e-8863-1edddea8dca5' on SQL
Server instance 'HI-SERVER\Microsoft##SSEE' not found. Additional error
information from SQL Server is included below.
Cannot open database
"SharePoint_Config_f76b131a-35b0-4e8e-8863-1edddea8dca5" requested by the
login. The login failed.

Source: Windows SharePoint Services
Category: MSSQL$MICROSOFT##SSEE
EventID: 18456
Description:
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named pipe>]

I have tried giving the Network Service user full access to the folder where
I store the databases and restarting the MSSQL$MICROSOFT##SSEE service using
net stop/net start (because it's not in the services menu), but have had no
luck.

I also have SharePoint 2.0 on the server and it is running well. I don't
think this is a conflict because I did not select upgrade when installing
3.0, but thought I would mention it.

All of that said, I am not sure where to go from here. Any help would be
most appreciated.

Finally, is it possible to move the Sharepoint 2 and 3 databases to SQL
Server 2000? I think it should speed up response times. Should I even move
2.0 databases to SQL Server considering I will no longer use 2 (never used
it to begin with)?

I appreciate the help. Thanks in advance.

Chris

First I'm GLAD you didn't do a Upgrade on you WSS 2.0
(You just saved yourself a BIG headache)

Did you Publish the Port in ISA?
http://technet.microsoft.com/en-us/l.../cc713327.aspx

Assuming port is published

Next If the WSS 3.0 Console comes up and
everything looks fine in IIS?
I'd delete your WSS 3.0 Site you just created and Create a New one
(This assumes there is no data there.)

Also did you use the Instructions for the Creation of WSS 3.0 Website?
(I know you may know how to do it without instructions but sometimes you
miss a step)

Installing Windows SharePoint Services 3.0 on a Server Running Windows Small
Business Server 2003
http://www.microsoft.com/downloads/d...displaylang=en

Assuming you can delete your Existing site with out any loss
I'd delete it in your WSS 3.0 control panel and create a new site.

I hope this gives you some ideas to try.

Also


Russ

--
Russell Grover - SBITS.Biz
Microsoft Gold Certified Partner
Microsoft Small Business Specialist
World Wide Remote SBS2003 Support - http://www.SBITS.Biz
Get Help Now! http://www.crossloop.com/SBITSdotBiz


"Chris Guimbellot" <cguimbellotnospam@hifranchise.com> wrote in message
news:epacuJO8IHA.3696@TK2MSFTNGP04.phx.gbl...
> Hello,
>
> SBS2003, SQL 2000, ISA2004
>
> I have installed WSS 3.0 on my SBS and am having some problems. While I am
> able to see and work in the Central Administration console and am able to
> create a Web Application and see it on the list, I am unable to go to the
> application using the link http://[sbsserver]:[portnumber]. I beleive the
> problem lies with the databases. First of all, I cant find them in the
> same folder as the SharePoint_AdminContent, SharePoint_Config, and
> WSS_Search databases (which I have moved from the default location for
> space reasons). Also, I get the following two events in my logs every
> night:
>
> Source: Windows SharePoint Services
> Category: Database
> EventID: 3760
> Description:
> SQL Database 'SharePoint_Config_f76b131a-35b0-4e8e-8863-1edddea8dca5' on
> SQL Server instance 'HI-SERVER\Microsoft##SSEE' not found. Additional
> error information from SQL Server is included below.
> Cannot open database
> "SharePoint_Config_f76b131a-35b0-4e8e-8863-1edddea8dca5" requested by the
> login. The login failed.
>
> Source: Windows SharePoint Services
> Category: MSSQL$MICROSOFT##SSEE
> EventID: 18456
> Description:
> Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named
> pipe>]
>
> I have tried giving the Network Service user full access to the folder
> where I store the databases and restarting the MSSQL$MICROSOFT##SSEE
> service using net stop/net start (because it's not in the services menu),
> but have had no luck.
>
> I also have SharePoint 2.0 on the server and it is running well. I don't
> think this is a conflict because I did not select upgrade when installing
> 3.0, but thought I would mention it.
>
> All of that said, I am not sure where to go from here. Any help would be
> most appreciated.
>
> Finally, is it possible to move the Sharepoint 2 and 3 databases to SQL
> Server 2000? I think it should speed up response times. Should I even move
> 2.0 databases to SQL Server considering I will no longer use 2 (never used
> it to begin with)?
>
> I appreciate the help. Thanks in advance.
>
> Chris
>

I'm having a similar problem with Sharepoint on SBS.


Using Sharepoint 3, installed separately...in fact, sharepoint 2 still
seems to be running. I can get to the administration page for that.
The rest of sharepoint is wrecked though...companyweb, a couple of
workgroup sites we set up. This seemed to come from an attack of
somesort. Unfortunately another "computer guy" got to it before I did
and undid some of the damage. We're getting alot of this in the event
viewer:


SQL Database 'STS_Config' on SQL Server instance 'np:\\.\pipe\MSSQL
$Microsoft##SSEE\sql\query' not found...


The outward facing SBS web page is gone, but OWA and remote access
still work. Is there any way to fix this are am I looking at
reinstalling SQL and sharepoint 3?

Russ,

I appreciate the help. I skimmed over the Publishing with ISA article you
mentioned, but it looks like this is to set up access from outside of the
network. At this point, I am only setting up a test site to work with from
within the network. I will worry about publishing it outward later.

That said, all looks well with IIS. I also followed the steps in the
Installing Windows SharePoint Services 3.0 on a Server Running Windows Small
Business Server 2003 whitepaper, but am still having trouble. Basically, the
same problem is there. I was able to create both the application pool and
the team site, but when it gives me the link to click on, I still get the
404 error. The Companyweb from WSS2 is still working, but for some reason,
the new one is not. I think it still has to do with the database. I can see
both the mdf and ldf files in the
C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data and have provided the Network
Service account with full access, so I can't think of what the problem may
be. Any other ideas?

Again, I appreciate the help.

Chris

"Russ (www.SBITS.Biz)" <support@REMOVETHIS.sbits.biz> wrote in message
news:enzUsvO8IHA.1080@TK2MSFTNGP06.phx.gbl...
> First I'm GLAD you didn't do a Upgrade on you WSS 2.0
> (You just saved yourself a BIG headache)
>
> Did you Publish the Port in ISA?
> http://technet.microsoft.com/en-us/l.../cc713327.aspx
>
> Assuming port is published
>
> Next If the WSS 3.0 Console comes up and
> everything looks fine in IIS?
> I'd delete your WSS 3.0 Site you just created and Create a New one
> (This assumes there is no data there.)
>
> Also did you use the Instructions for the Creation of WSS 3.0 Website?
> (I know you may know how to do it without instructions but sometimes you
> miss a step)
>
> Installing Windows SharePoint Services 3.0 on a Server Running Windows
> Small Business Server 2003
> http://www.microsoft.com/downloads/d...displaylang=en
>
> Assuming you can delete your Existing site with out any loss
> I'd delete it in your WSS 3.0 control panel and create a new site.
>
> I hope this gives you some ideas to try.
>
> Also
>
>
> Russ
>
> --
> Russell Grover - SBITS.Biz
> Microsoft Gold Certified Partner
> Microsoft Small Business Specialist
> World Wide Remote SBS2003 Support - http://www.SBITS.Biz
> Get Help Now! http://www.crossloop.com/SBITSdotBiz
>
>
> "Chris Guimbellot" <cguimbellotnospam@hifranchise.com> wrote in message
> news:epacuJO8IHA.3696@TK2MSFTNGP04.phx.gbl...
>> Hello,
>>
>> SBS2003, SQL 2000, ISA2004
>>
>> I have installed WSS 3.0 on my SBS and am having some problems. While I
>> am able to see and work in the Central Administration console and am able
>> to create a Web Application and see it on the list, I am unable to go to
>> the application using the link http://[sbsserver]:[portnumber]. I beleive
>> the problem lies with the databases. First of all, I cant find them in
>> the same folder as the SharePoint_AdminContent, SharePoint_Config, and
>> WSS_Search databases (which I have moved from the default location for
>> space reasons). Also, I get the following two events in my logs every
>> night:
>>
>> Source: Windows SharePoint Services
>> Category: Database
>> EventID: 3760
>> Description:
>> SQL Database 'SharePoint_Config_f76b131a-35b0-4e8e-8863-1edddea8dca5' on
>> SQL Server instance 'HI-SERVER\Microsoft##SSEE' not found. Additional
>> error information from SQL Server is included below.
>> Cannot open database
>> "SharePoint_Config_f76b131a-35b0-4e8e-8863-1edddea8dca5" requested by the
>> login. The login failed.
>>
>> Source: Windows SharePoint Services
>> Category: MSSQL$MICROSOFT##SSEE
>> EventID: 18456
>> Description:
>> Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named
>> pipe>]
>>
>> I have tried giving the Network Service user full access to the folder
>> where I store the databases and restarting the MSSQL$MICROSOFT##SSEE
>> service using net stop/net start (because it's not in the services menu),
>> but have had no luck.
>>
>> I also have SharePoint 2.0 on the server and it is running well. I don't
>> think this is a conflict because I did not select upgrade when installing
>> 3.0, but thought I would mention it.
>>
>> All of that said, I am not sure where to go from here. Any help would be
>> most appreciated.
>>
>> Finally, is it possible to move the Sharepoint 2 and 3 databases to SQL
>> Server 2000? I think it should speed up response times. Should I even
>> move 2.0 databases to SQL Server considering I will no longer use 2
>> (never used it to begin with)?
>>
>> I appreciate the help. Thanks in advance.
>>
>> Chris
>>
>
>