Hi ALL,
I'd tried to install Visual Studio .NET 2005 Professional Edition on a Windows 2000 domain PC, and everything was fine except the last step (i.e. installing SQL Express). I got the error message "Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. ***EndOfSession***". Further investigation on the error in "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG" and found that "Product : SQL Server Database Services Error : SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot alter the login 'sa', because it does not exist or you do not have permission.. Refer to the server error logs and Setup logs for detailed error information." I used a domain account with local administrator privilege to install. I doubt whether my domain policy affect the installation. Could someone tell me what security policy I should set to allow the installation of the Visual Studio .NET 2005 Professional on a domain PC.
TIA.
M Chan
Try the workaround here:
http://blogs.msdn.com/quanto/archive/2005/12/16/504693.aspx
|||
We'd tried (Put the domain account into the local Users group as well) but still failed. As a domain account, how can we list it first in the local administrators group? PS. The domain account is already belonging to the local administrators group.
TIA.
M Chan
|||Moving thread to SQL setup forum.
|||
Hi ALL,
The domain PC is Windows XP Prof. with SP2 _ latest patches installed. The installation is run by a domain account which has local administrator privilege on the domain PC.
M Chan
|||Did you ever get this resolved. I'm having the same issue.|||Not yet. I just wonder why the setup cannot be done if the Windows XP Prof. SP2 had joined to the domain with McAfee v8.0 installed. The problem should be related to some security settings.|||
I looked through our bugs and came up with something.
Looks like if SQL Server 2005 RTM is installed in a Domain where a windows Group named 'sa', 'SA', 'Sa' or 'sA' exists, installation fails when Integrated Security is chosen. However, despite having the Windows group in the Domain, installation with Mixed Security work fine. After having installed successfully with Mixed Secuirty, the server properties can be changed to accept Integrated Security connections only. This should work.
Hope this helps.
-Jeffrey
|||Do you know if there are installation options in the Visual Studio .NET 2005 to specify the security mode for SQL Server 2005 RTM. If no, we need to separate out the SQL 2005 Express Edition from the Visual Studio .NET 2005 and install the SQL 2005 Express Edition individually.
TIA.
M Chan
|||No, there isn't an instgall option to specify the security mode separately. You should know, though, that with integrated security, the SA account is disabled.
No comments:
Post a Comment