|
Home > Archive > Commerce Server Setup > May 2004 > Install fails installing developer edition on 2 machines with Windows Authentication
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Install fails installing developer edition on 2 machines with Windows Authentication
|
|
|
| Any help would be appreciated with the problem described below:
I am a newbie, however, I have install Commerce Server 2002 Developer Edition successfully several times (Windows Server 2003 and XP Pro). With the exception 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 these for the most part when installing the "new" environment, except I first installed SQL Server 2000 an
d prereqs: MDAC 2.8, etc on one machine (no IIS on this box; and IIS, ASP.NET, MDAC 2.8, etc on the other box.
When installing Commerce Server 2002 (on the box with IIS, of course), I used Windows Authentication specifying the same domain account that I used to install SQL Server on the other box. The user was a member of the local Administrators 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 configurating 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 and be done with it, but those Microsoft warning popups.......scare me.
| |
| Maria Quian [MSFT] 2004-03-05, 9:34 pm |
| Thank you for using Microsoft Newsgroups.
Check that the default login database is master for the account or accounts
you are using when installing. The other thing to do is to take a profile
trace during the install or when you try to change the CSM connection
string from SQL to Windows Authentication. It might give you some ideas.
Maria Quian
Microsoft Technical Support
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
| |
|
| I checked and the default database is 'master' (I suspected so since I am using the same domain user that installed SQL Server).
Can you direct me to an article that describes the procedure for doing a profile trace during the install. I am not familiar with this procedure. Thanks.
| |
| Maria Quian [MSFT] 2004-05-30, 10:45 am |
| Thank you for using Microsoft Newsgroups.
To use integrated authentication, you are more secure using a domain
controller. If setting a domain controller is not an option then make sure
that you have the same users created in both machines.
Other than the SQL Books Online, I couldn't find a kb article that would
outline the steps. Once you open the Start > Programs > SQL > Profiler, on
the trace property windows go to events and select Errors and Warnings,
Security Audit, Stored Procedures and TSQL. From there you can add or take
out the different events you want to monitor.
Maria Quian
Microsoft Technical Support
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
|
|
|
|
|