Re: Help with WSS 3.0 Server Farm Config - Backend SQL 2005

Well, to start, using the username WEBSVR\sharepoint is the wrong account to
use to try to do things on the DBSVR. When you specifically tell sharepoint
"use the account websvr\sharepoint" (specifically referring to an account
local to the WEBSVR) to create and access the SQL server, Sharepoint (the
program) tries to access DBSVR with an account that is explicitly local to
the WEBSVR.

I have never tried to do a simple farm install in a workgroup scenario, but
have you tried not specifying the machine name in the account username
field? Does it require the (machine or domain)\username format (if it fails
it usually won't leave the page you're messing up on)??

If you used DBSVR\username it would work trying to create the databases, but
then it would choke because the DBSVR\username account does not have local
access on the WEBSVR to work as the central administration's application
pool account.

But, maybe, just maybe, if you could do without the specification of
machine\username and use just the username, you might be able to pull it
off.

If not, then you will probably have to create a domain.

Please lemme know what happens, because I've never tried to do it the way
you are. And I think it would be a good thing to know.

-callahan
"Chris Green" <cgreen@xxxxxxxxxxxxx> wrote in message
news:On2hRM9IHHA.2056@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for your response...

Yes I tried that. Not being in an Active Directory Domain seems to make
this challenging.

I have DB server name DBSVR and the Web Server WEBSVR. I created an
account sharepoint on both machines with the same password. On DSBSVR,
that sharepoint user has the appropriate access. The setup indicates to
user a Domain\Username combo when setting up the wss database. I use
WEBSVR\sharepoint - the database Sharepoint_config and
Sharepoint_admincont_xxxxxx get created.

Should I setup and AD?

Thanks,
Chris

"callahan" <cacallahan@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uswykH6IHHA.1064@xxxxxxxxxxxxxxxxxxxxxxx
Hmmm, did you give the setup account (that sharepoint account you
created) the logins dbcreator, and securityadmins roles on the SQL
server. That setup account needs to be able to set up the configuration
database (which happens around step two of configuration if memory
serves), give that database to the databases account, and to give the
database account (the configuration database and central admin account)
the right to make the other sharepoint databases.

Not giving the setup account the right roles in SQL could definitely mess
things up in the way you described.

Lemme know if this helps.

"Chris Green" <cgreen@xxxxxxxxxxxxx> wrote in message
news:O0DM145IHHA.448@xxxxxxxxxxxxxxxxxxxxxxx
Has anyone one got WSS 3.0 working with a backend database?

I am getting a System.Security.Principal.IdentityNotMapped when trying
to configure the backend database.

I created the user "sharepoint" on both servers with the same password
and using NTLM to authenticate. When I go through the configuration,
the databases get created but something happens during step 2 and fails
with the above exception.

Any help will be greatly appreciated.

Thanks
Chris








.

Relevant Pages

  • Re: ADP/SQL Server 2000 Security Problem
    ... The server is running Windows 2003. ... I'll also test using a SQL Server account and see what happens. ... it worked in MSDE 2000. ... I have not created any new accounts for the production database. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: WSS MSDE DB Location Change Nightmare
    ... STS_servername_1 database. ... able to do your reinstall of MSDE and restore over top of the new Content DB ... Sharepoint Services was installed. ... Pool Is the Account That Has the Required Permissions to the SQL Server ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Restored Server but SharePoint refusing admin access
    ... > SID/BID or remove the user from the database and add it again. ... >, In SQL Configuration Manager go to SQL> Server ... > you had) you cannot access the database from that account. ... > newly added administrator account (for me, since I added a new admin ...
    (microsoft.public.windows.server.sbs)
  • Re: Restored Server but SharePoint refusing admin access
    ... I went ahead and forwarded my post to the SharePoint forums. ... SID/BID or remove the user from the database and add it again. ... you had) you cannot access the database from that account. ... newly added administrator account (for me, since I added a new admin account ...
    (microsoft.public.windows.server.sbs)
  • Re: Help with WSS 3.0 Server Farm Config - Backend SQL 2005
    ... It doesn't matter if the SQL server is virtual or physical, ... Did the account you were logged in as to install sharepoint have logins, ... if it managed to create the configuration database. ...
    (microsoft.public.sharepoint.windowsservices)