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

callahan,

Thanks again for your response...

I think your exactly right. Now when I did use DBSVR\sharepoint as the
user, it would not work. I had to use only "sharepoint" to get the
configuration started. I assume that would mean it is local to WEBSVR.
What interest me though is that the database get created but fails after
that. Never makes it to task 3.

Now WEBSVR does see DBSVR. When I ping from WEBSVR it resolves the name.

I don't think this makes much difference, but the WEBSVR is running on a
Virtual Server (2003 Enterprise Server VHD i download off MSDN) with DBSVR
as the host.

I ended up loading SQL 2005 express on WEBSVR and keeping it all local.
Works awesome!

My only concern is security - having db and web apps on one server.

So... for production (server farm setup), looks like a domain is nessecary
which is probablly more secure.

"callahan" <cacallahan@xxxxxxxxxxxxxxxxxxx> wrote in message
news:e7T6x89IHHA.5104@xxxxxxxxxxxxxxxxxxxxxxx
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: 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)
  • I broke Sharepoint :(
    ... SBS was installed and the server was up and running including the default ... After 2 days I was looking at SQL backups I relaised that Sharepoint ... database and the other instances were not migrated accross. ...
    (microsoft.public.windows.server.sbs)
  • Re: Service Account Password Change
    ... app pools and changed the passwords, when I got to the sharepoint admin ... the sharepoint domain account didnt have the database admin ... Our dev environment is a domain member server running sharepoint portal ... > Detach from the config database in SharePoint Central Administration ...
    (microsoft.public.sharepoint.portalserver)
  • Steps for Migrating WSS 3.0 from Windows Internal Database to Microsoft SQL 2005
    ... done the stupid things I did when I started playing with Sharepoint ... when I first installed it and assuming that it would find the SQL 2005 ... Windows Internal Database). ... Reboot the server to finish up any uninstall scripts. ...
    (microsoft.public.sharepoint.windowsservices)
  • 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)