December 4, 2007 at 8:58 am
Hello,
I'm getting an error when attempting to do an upgrade (from 2000 SP3) install of SQL 2005 on my W2K3 server.
The error is as follows:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
SQL Server Setup was unable add user WTBHOME\Administrator to local group SQLServer2005SQLAgentUser$XXXXXX$MSSQLSERVER.
I Googled the error and tried the suggestion to manually add the account to the group, but when I run the setup again, I still have the same problem.
Any and all help is greatly appreciated!
December 4, 2007 at 2:52 pm
Here's a bit more information:
My W2K3 server is an AD controller.
I have seen some stuff around that this was a problem with the preview version, but that it would be fixed in the RTM.
Side note / rant: I've tried to post in the MS forums, but on any machine with IE7 the forums never load and on my lone remaining IE6 machine, when I click on "New post" it takes me to a "You have successfully logged out" page!!!!!!!! :crazy:
December 5, 2007 at 6:19 am
I've had install problems when the user account I was trying to run SQL Server under had too weak a password to be accepted under the security policy added in SQL Server 2005, though I would have expected messages to this affect. Silly question but are you logged in as an administrator on the server?
December 5, 2007 at 6:32 am
I'm logged in as an administrator on the server (but not THE Administrator account) and the password I have should meet the complexity standards for SQL.
Thanks for the reply!
December 6, 2007 at 9:04 am
We've had some password complexity issues during an upgrade from SQL2000 to 2005. From what I understand, SQL 2005 by default inherits the Windows security/password policy. First we made sure that our SQL logins complied with our Windows password policy, but were still running into some issues. We finally found a resultion at the below link:
- http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=451474&SiteID=1
Microsoft hard-coded a password ‘Yukon90_’ in one of it's install scripts, which does not meet our Windows password policy. We had to go in and manually update that password to one that passes our requirements. The password is for a temporary object that is dropped at the end of the script, so it shouldn't affect anything else. The script file was in the below location:
- C:\Program Files\Microsoft SQL Server\MSSQL.1MSSQL\Upgrade\sqlagent90_msdb_upgrade.sql
December 7, 2007 at 2:29 am
If you are installing SQL Server on a Domain Controller, you must do the job with domain Admin rights. This is in BOL somewhere...
If you install on any server that is not a DC, the groups that get created during the install are machine local groups, and you only need local Administrator rights to do this.
On a DC, the groups get created as domain groups, so you need domain Administrator rights. The only work-round is to instal SQL on a different machine that is not a DC.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
December 7, 2007 at 6:18 am
Thanks for the suggestion.
I double checked, and as I thought the account I'm installing under is a mamber of Domain Admins.
October 22, 2008 at 12:42 pm
Boy oh boy ... I wish someone would answer this issue in a thread somewhere. We have the same issue and I've found many posts high and low, but no answer. Anyone know how to get SQL Server 2005 installed successfully on a Domain Controller (Server 2003)?
October 22, 2008 at 1:28 pm
Hi All,
Quick question the service account you have SQL server running under is a domain account and not local service?
If you check BOL one of the requirements is that it runs under a domain account and not local service or network service accounts.
Regards
Richard...
http://www.linkedin.com/in/gbd77rc
October 22, 2008 at 2:23 pm
We have tried both the Local Service (as seen working on another client machine with a similar setup) and a domain account (for which we gave rights to the kingdom) ... and nothing. A few minutes ago I added some of the domain user groups manually and assigned the SQL domain user ID that we plan to run it under and re-attempted the installation. It went further, then failed. Now I have a partially installed instance that doesn't work (but I can see traces of it being there) and when I reattempt the install it says to pick another instance name as the one is already in use. We are now going to reboot the machine and try to uninstall again.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply