03-05-04 10:35 PM
Any help would be appreciated with the problem described below:
I am a newbie, however, I have install Commerce Server 2002 Developer Editio
n successfully several times (Windows Server 2003 and XP Pro). With the exce
ption of the XP Pro installation, I have always installed everything on one
machine (including the doma
in controller).
This week, we tried to setup the "real" development/test environment. I had
documented procedure tested in a single computer environment. I followed the
se for the most part when installing the "new" environment, except I first i
nstalled SQL Server 2000 an
d prereqs: MDAC 2.8, etc on one machine (no IIS on this box; and IIS, ASP.NE
T, MDAC 2.8, etc on the other box.
When installing Commerce Server 2002 (on the box with IIS, of course), I use
d Windows Authentication specifying the same domain account that I used to i
nstall SQL Server on the other box. The user was a member of the local Admin
istrators group on both mac
hines. SQL Server was setup with Mixed Mode.
The install proceeded as usually right up to the point where it starts confi
gurating the database (running scripts). I get the a message saying that the
user "" could not update database 'master'. I had to backout the installed.
I tried this several times
, tried using differenct windows user accounts, added accounts to SQL Server
, etc, etc, etc. No luck. Several others tried the same, even burnt down the
boxes and tried again (same freakin thing!).
Just for grins, I tried the SQL Login using sa. It worked fine. Then (again
for grins), I tried setting it to SQL login typed a user name then switched
it back to Windows Authentication (the 'sa' remained in the grayed text box)
. This time the message sai
d user "sa" could not update database 'master'. Tried a couple of other IDs
and passwords, whatever was in the SQL Login text box always shows up in the
message, the login never succeeds, though (well, unless I don't use Windows
Authentication).
I guess if I weren't so bullheaded, I would just use the SQL Server login an
d be done with it, but those Microsoft warning popups.......scare me.
[ Post a follow-up to this message ]
|