Hello out there, I hope someone out there might have some pointers for me
...
I've recently installed SBS 2003 Premium on a P4 1.7GHz, 1GB RAM, 40GB HDD
(mirror set) box. Runs great except two issues: sharepoint doesn't work
(getting errors in the Event viewer) and I can't join client PCs to the
domain using the http://myhostname/connectcomputer browser based utility.

1. During the initial install, it appears that the MSDE was installed (for
Sharepoint and SBS Monitoring) for users that didn't end up purchasing
Premium (which comes with SQL 2000). The installation of the MSDE had an
instance name of Sharepoint. I went to install SQL 2000 and it detected
that MSDE was running and asked if I wanted to upgrade. I followed the
upgrade process... When I was done, SQL 2000 was installed but it still had
an instance name of Sharepoint ( \myhostname\sharepoint). The only thing
here was that for some reason, I couldn't get the SQL Service Manager app to
connect and start, the SQL Agent wouldn't start and the Enterprise Manager
acted erratic. I was able to back up the STS_Config and STS_Myhostname_1
databases. I uninstalled the "upgraded" SQL server and reinstalled fresh.
I restored the two databases and placed the appropriate security rights back
on them. Everything looks fine, but the sharepoint admin can't connect to
the database, "companyweb" doesn't work, and I have errors in the
Application event viewer which show up every 5 minutes saying "#50070:
Unable to connect to the database STS_Config on myhostname\SharePoint.
Check the database connection information and make sure that the database
server is running." Basically, the applications are still looking for an
database server with an instance name of Sharepoint. Where do I change the
settings for this so the apps will stop looking for this instance name?

2. Here's the other funky error I'm getting. I can manually join a client
Win2K PC to the domain but if I try to add domain users to security groups
on this local Win2K client PC, I get error messages that the domain doesn't
exist or can't be contacted. I did some research and found that I need to
go through the Server Management app and click Client Computers, then click
Set Up Client Computers. The wizard then says to go to the client PC and go
to http://myhostname/connectcomputer to finish the setup. If I do this, an
OCX control is loaded, and a wizard starts. If I enter a valid domain
username and password (using the admin account here ...) I get an error
message saying "The list of users and computers could not be found on the
server. Make sure that the Small Business Server network adapters are
configured correctly." What is the deal here? I'm at a total loss. There
is TCP connectivity, I can ping the server, I can browse the local network
and see the other computers (sitting in their default workgroup...). I know
physical connectivity is not an issue here. My only guess is that after the
installation of the SBS 2003 software, I removed the original NIC and added
two new ones. Was the first, primary NIC designated as a special network
adapter?

Thanks for any help you can provide, I'm so frustrated plus Microsoft wants
$245 for support (on a brand new product...)

-Brian

Problems w/ New SBS 2003 Premium install by anonymous

anonymous
Thu Feb 26 07:12:31 CST 2004

Whenever SQL is installed sharepoint doesn't work, I have
seen this on a number of platforms so it isn't hardware
related,





>-----Original Message-----
>Hello out there, I hope someone out there might have
some pointers for me
>....
>I've recently installed SBS 2003 Premium on a P4 1.7GHz,
1GB RAM, 40GB HDD
>(mirror set) box. Runs great except two issues:
sharepoint doesn't work
>(getting errors in the Event viewer) and I can't join
client PCs to the
>domain using the http://myhostname/connectcomputer
browser based utility.
>
>1. During the initial install, it appears that the MSDE
was installed (for
>Sharepoint and SBS Monitoring) for users that didn't end
up purchasing
>Premium (which comes with SQL 2000). The installation
of the MSDE had an
>instance name of Sharepoint. I went to install SQL 2000
and it detected
>that MSDE was running and asked if I wanted to upgrade.
I followed the
>upgrade process... When I was done, SQL 2000 was
installed but it still had
>an instance name of Sharepoint (
\myhostname\sharepoint). The only thing
>here was that for some reason, I couldn't get the SQL
Service Manager app to
>connect and start, the SQL Agent wouldn't start and the
Enterprise Manager
>acted erratic. I was able to back up the STS_Config and
STS_Myhostname_1
>databases. I uninstalled the "upgraded" SQL server and
reinstalled fresh.
>I restored the two databases and placed the appropriate
security rights back
>on them. Everything looks fine, but the sharepoint
admin can't connect to
>the database, "companyweb" doesn't work, and I have
errors in the
>Application event viewer which show up every 5 minutes
saying "#50070:
>Unable to connect to the database STS_Config on
myhostname\SharePoint.
>Check the database connection information and make sure
that the database
>server is running." Basically, the applications are
still looking for an
>database server with an instance name of Sharepoint.
Where do I change the
>settings for this so the apps will stop looking for this
instance name?
>
>2. Here's the other funky error I'm getting. I can
manually join a client
>Win2K PC to the domain but if I try to add domain users
to security groups
>on this local Win2K client PC, I get error messages that
the domain doesn't
>exist or can't be contacted. I did some research and
found that I need to
>go through the Server Management app and click Client
Computers, then click
>Set Up Client Computers. The wizard then says to go to
the client PC and go
>to http://myhostname/connectcomputer to finish the
setup. If I do this, an
>OCX control is loaded, and a wizard starts. If I enter
a valid domain
>username and password (using the admin account here ...)
I get an error
>message saying "The list of users and computers could
not be found on the
>server. Make sure that the Small Business Server
network adapters are
>configured correctly." What is the deal here? I'm at a
total loss. There
>is TCP connectivity, I can ping the server, I can browse
the local network
>and see the other computers (sitting in their default
workgroup...). I know
>physical connectivity is not an issue here. My only
guess is that after the
>installation of the SBS 2003 software, I removed the
original NIC and added
>two new ones. Was the first, primary NIC designated as
a special network
>adapter?
>
>Thanks for any help you can provide, I'm so frustrated
plus Microsoft wants
>$245 for support (on a brand new product...)
>
>-Brian
>
>
>
>
>.
>