Hi!
I have installed MSDE 2000 in "Mixed Windows and SQL mode authentication with network access" .following is the command:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="password" INSTANCENAME="TempInstance" SECURITYMODE=SQL
Then I created the database TempDB in it.
When I try to connect this database from my program running on my machine , it works fine. But when i try to connect to it from the same program running on a different machine on the same domain.It gives error:
"SQL Server does not exist or access denied ."
Even when i run the same program in my machine to access the same TempDB database on a remote machine that is not in my domain, it works fine.
this is my connection string:
Data Source={Database server's IP Address}\TempInstance;Initial Catalog=TempDB;User ID=sa;PWD=password;
Please help.
KT.What's the operating system for the client from which you are unsuccessfully attempting to connect? What version of MDAC is running on it?
Also, be aware that a named instance install of MSDE will set up to run on a non-default port (ie, not 1433). You can verify your connectivity by determining what port the SQL listener is running on and then using telnet {ip address} {port} from your client machine. You may need to account for the alternate port on your client machine. You can set up an alias for it by running cliconfg at a command prompt on your client machine.
Regards,
hmscott|||Thanks hmscott!
Actually my problem was caused by windows firewall.
regards.
Kuldeep.
Showing posts with label domain. Show all posts
Showing posts with label domain. Show all posts
Monday, March 26, 2012
Wednesday, March 21, 2012
Problem getting SQL and SQL agent to start automatically
Hi folks,
Can anyone help me out with this strange problem I'm having. I have a
new server (Win 2003 standard) that is part of a domain and it is
running SQL 2000. I have changed the services to run as a domain
account. The password for this account is correct and the account is
also local admin and domain admin.
I am able to manually start the SQL server and SQL agent service
manually but when i restart the box or try to restart the services
they do not start up. I get the following error message in in the
event log:
Event Type:Error
Event Source:Service Control Manager
Event Category:None
Event ID:7000
Date:10/05/2007
Time:09:58:45
User:N/A
Computer:xxxxx
Description:
The MSSQLSERVER service failed to start due to the following error:
The account name is invalid or does not exist, or the password is
invalid for the account name specified.
I checked the account details and they are working as I am able to log
into the server using the account.
Does anyone know why this happens and how i can get SQL and SQL agent
to start up automatically as I don't want to be caught out in the
event of the server rebooting.
Anyone any tips or suggestions?
Thanks in advance
Fox1977
The Windows Account for the MSSQLServer service and the SQLServerAgent
service has a bad password, or could not be validated through your Active
Directory or because network services were unavailable.
Do you have any other service that starts under the same account? If so do
you have the same problem with that service also? Also please check the
event logs to check if there are any error messages or warning messages
related to this account. Also one other thing you can try is to use a
different account as a startup for SQL server and see if you can repro the
behavior.
"Fox1977" <foxj77@.gmail.com> wrote in message
news:1178789826.884648.294580@.w5g2000hsg.googlegro ups.com...
> Hi folks,
> Can anyone help me out with this strange problem I'm having. I have a
> new server (Win 2003 standard) that is part of a domain and it is
> running SQL 2000. I have changed the services to run as a domain
> account. The password for this account is correct and the account is
> also local admin and domain admin.
> I am able to manually start the SQL server and SQL agent service
> manually but when i restart the box or try to restart the services
> they do not start up. I get the following error message in in the
> event log:
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7000
> Date: 10/05/2007
> Time: 09:58:45
> User: N/A
> Computer: xxxxx
> Description:
> The MSSQLSERVER service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is
> invalid for the account name specified.
> I checked the account details and they are working as I am able to log
> into the server using the account.
> Does anyone know why this happens and how i can get SQL and SQL agent
> to start up automatically as I don't want to be caught out in the
> event of the server rebooting.
> Anyone any tips or suggestions?
> Thanks in advance
>
|||I was getting a netlogon error in the event log saying could not
contact PDC. After doing a bit of searching on the net I came across
this site:
[url]http://www.eventid.net/display.asp?eventid=5719&eventno=104&source=NETLOG ON&phase=1[/url]
About half way down there is an entry about lmhosts/wins. I compare
the LMHOSTS setting on the server against some of the other database
servers in the domain. I changed the LMHOSTS/NETBIOS setting to
Default from Disable NETBIOS over TCP/IP.
I rebooted the server and then the PDC error disappeared and the
services started automatically. Brilliant
Thanks for your help, much appreciated
Can anyone help me out with this strange problem I'm having. I have a
new server (Win 2003 standard) that is part of a domain and it is
running SQL 2000. I have changed the services to run as a domain
account. The password for this account is correct and the account is
also local admin and domain admin.
I am able to manually start the SQL server and SQL agent service
manually but when i restart the box or try to restart the services
they do not start up. I get the following error message in in the
event log:
Event Type:Error
Event Source:Service Control Manager
Event Category:None
Event ID:7000
Date:10/05/2007
Time:09:58:45
User:N/A
Computer:xxxxx
Description:
The MSSQLSERVER service failed to start due to the following error:
The account name is invalid or does not exist, or the password is
invalid for the account name specified.
I checked the account details and they are working as I am able to log
into the server using the account.
Does anyone know why this happens and how i can get SQL and SQL agent
to start up automatically as I don't want to be caught out in the
event of the server rebooting.
Anyone any tips or suggestions?
Thanks in advance
Fox1977
The Windows Account for the MSSQLServer service and the SQLServerAgent
service has a bad password, or could not be validated through your Active
Directory or because network services were unavailable.
Do you have any other service that starts under the same account? If so do
you have the same problem with that service also? Also please check the
event logs to check if there are any error messages or warning messages
related to this account. Also one other thing you can try is to use a
different account as a startup for SQL server and see if you can repro the
behavior.
"Fox1977" <foxj77@.gmail.com> wrote in message
news:1178789826.884648.294580@.w5g2000hsg.googlegro ups.com...
> Hi folks,
> Can anyone help me out with this strange problem I'm having. I have a
> new server (Win 2003 standard) that is part of a domain and it is
> running SQL 2000. I have changed the services to run as a domain
> account. The password for this account is correct and the account is
> also local admin and domain admin.
> I am able to manually start the SQL server and SQL agent service
> manually but when i restart the box or try to restart the services
> they do not start up. I get the following error message in in the
> event log:
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7000
> Date: 10/05/2007
> Time: 09:58:45
> User: N/A
> Computer: xxxxx
> Description:
> The MSSQLSERVER service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is
> invalid for the account name specified.
> I checked the account details and they are working as I am able to log
> into the server using the account.
> Does anyone know why this happens and how i can get SQL and SQL agent
> to start up automatically as I don't want to be caught out in the
> event of the server rebooting.
> Anyone any tips or suggestions?
> Thanks in advance
>
|||I was getting a netlogon error in the event log saying could not
contact PDC. After doing a bit of searching on the net I came across
this site:
[url]http://www.eventid.net/display.asp?eventid=5719&eventno=104&source=NETLOG ON&phase=1[/url]
About half way down there is an entry about lmhosts/wins. I compare
the LMHOSTS setting on the server against some of the other database
servers in the domain. I changed the LMHOSTS/NETBIOS setting to
Default from Disable NETBIOS over TCP/IP.
I rebooted the server and then the PDC error disappeared and the
services started automatically. Brilliant
Thanks for your help, much appreciated
Problem getting SQL and SQL agent to start automatically
Hi folks,
Can anyone help me out with this strange problem I'm having. I have a
new server (Win 2003 standard) that is part of a domain and it is
running SQL 2000. I have changed the services to run as a domain
account. The password for this account is correct and the account is
also local admin and domain admin.
I am able to manually start the SQL server and SQL agent service
manually but when i restart the box or try to restart the services
they do not start up. I get the following error message in in the
event log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 10/05/2007
Time: 09:58:45
User: N/A
Computer: xxxxx
Description:
The MSSQLSERVER service failed to start due to the following error:
The account name is invalid or does not exist, or the password is
invalid for the account name specified.
I checked the account details and they are working as I am able to log
into the server using the account.
Does anyone know why this happens and how i can get SQL and SQL agent
to start up automatically as I don't want to be caught out in the
event of the server rebooting.
Anyone any tips or suggestions?
Thanks in advanceFox1977
The Windows Account for the MSSQLServer service and the SQLServerAgent
service has a bad password, or could not be validated through your Active
Directory or because network services were unavailable.
Do you have any other service that starts under the same account? If so do
you have the same problem with that service also? Also please check the
event logs to check if there are any error messages or warning messages
related to this account. Also one other thing you can try is to use a
different account as a startup for SQL server and see if you can repro the
behavior.
"Fox1977" <foxj77@.gmail.com> wrote in message
news:1178789826.884648.294580@.w5g2000hsg.googlegroups.com...
> Hi folks,
> Can anyone help me out with this strange problem I'm having. I have a
> new server (Win 2003 standard) that is part of a domain and it is
> running SQL 2000. I have changed the services to run as a domain
> account. The password for this account is correct and the account is
> also local admin and domain admin.
> I am able to manually start the SQL server and SQL agent service
> manually but when i restart the box or try to restart the services
> they do not start up. I get the following error message in in the
> event log:
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7000
> Date: 10/05/2007
> Time: 09:58:45
> User: N/A
> Computer: xxxxx
> Description:
> The MSSQLSERVER service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is
> invalid for the account name specified.
> I checked the account details and they are working as I am able to log
> into the server using the account.
> Does anyone know why this happens and how i can get SQL and SQL agent
> to start up automatically as I don't want to be caught out in the
> event of the server rebooting.
> Anyone any tips or suggestions?
> Thanks in advance
>|||I was getting a netlogon error in the event log saying could not
contact PDC. After doing a bit of searching on the net I came across
this site:
http://www.eventid.net/display.asp?eventid=5719&eventno=104&source=NETLOGON&phase=1
About half way down there is an entry about lmhosts/wins. I compare
the LMHOSTS setting on the server against some of the other database
servers in the domain. I changed the LMHOSTS/NETBIOS setting to
Default from Disable NETBIOS over TCP/IP.
I rebooted the server and then the PDC error disappeared and the
services started automatically. Brilliant
Thanks for your help, much appreciated
Can anyone help me out with this strange problem I'm having. I have a
new server (Win 2003 standard) that is part of a domain and it is
running SQL 2000. I have changed the services to run as a domain
account. The password for this account is correct and the account is
also local admin and domain admin.
I am able to manually start the SQL server and SQL agent service
manually but when i restart the box or try to restart the services
they do not start up. I get the following error message in in the
event log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 10/05/2007
Time: 09:58:45
User: N/A
Computer: xxxxx
Description:
The MSSQLSERVER service failed to start due to the following error:
The account name is invalid or does not exist, or the password is
invalid for the account name specified.
I checked the account details and they are working as I am able to log
into the server using the account.
Does anyone know why this happens and how i can get SQL and SQL agent
to start up automatically as I don't want to be caught out in the
event of the server rebooting.
Anyone any tips or suggestions?
Thanks in advanceFox1977
The Windows Account for the MSSQLServer service and the SQLServerAgent
service has a bad password, or could not be validated through your Active
Directory or because network services were unavailable.
Do you have any other service that starts under the same account? If so do
you have the same problem with that service also? Also please check the
event logs to check if there are any error messages or warning messages
related to this account. Also one other thing you can try is to use a
different account as a startup for SQL server and see if you can repro the
behavior.
"Fox1977" <foxj77@.gmail.com> wrote in message
news:1178789826.884648.294580@.w5g2000hsg.googlegroups.com...
> Hi folks,
> Can anyone help me out with this strange problem I'm having. I have a
> new server (Win 2003 standard) that is part of a domain and it is
> running SQL 2000. I have changed the services to run as a domain
> account. The password for this account is correct and the account is
> also local admin and domain admin.
> I am able to manually start the SQL server and SQL agent service
> manually but when i restart the box or try to restart the services
> they do not start up. I get the following error message in in the
> event log:
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7000
> Date: 10/05/2007
> Time: 09:58:45
> User: N/A
> Computer: xxxxx
> Description:
> The MSSQLSERVER service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is
> invalid for the account name specified.
> I checked the account details and they are working as I am able to log
> into the server using the account.
> Does anyone know why this happens and how i can get SQL and SQL agent
> to start up automatically as I don't want to be caught out in the
> event of the server rebooting.
> Anyone any tips or suggestions?
> Thanks in advance
>|||I was getting a netlogon error in the event log saying could not
contact PDC. After doing a bit of searching on the net I came across
this site:
http://www.eventid.net/display.asp?eventid=5719&eventno=104&source=NETLOGON&phase=1
About half way down there is an entry about lmhosts/wins. I compare
the LMHOSTS setting on the server against some of the other database
servers in the domain. I changed the LMHOSTS/NETBIOS setting to
Default from Disable NETBIOS over TCP/IP.
I rebooted the server and then the PDC error disappeared and the
services started automatically. Brilliant
Thanks for your help, much appreciated
Problem getting SQL and SQL agent to start automatically
Hi folks,
Can anyone help me out with this strange problem I'm having. I have a
new server (Win 2003 standard) that is part of a domain and it is
running SQL 2000. I have changed the services to run as a domain
account. The password for this account is correct and the account is
also local admin and domain admin.
I am able to manually start the SQL server and SQL agent service
manually but when i restart the box or try to restart the services
they do not start up. I get the following error message in in the
event log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 10/05/2007
Time: 09:58:45
User: N/A
Computer: xxxxx
Description:
The MSSQLSERVER service failed to start due to the following error:
The account name is invalid or does not exist, or the password is
invalid for the account name specified.
I checked the account details and they are working as I am able to log
into the server using the account.
Does anyone know why this happens and how i can get SQL and SQL agent
to start up automatically as I don't want to be caught out in the
event of the server rebooting.
Anyone any tips or suggestions?
Thanks in advanceFox1977
The Windows Account for the MSSQLServer service and the SQLServerAgent
service has a bad password, or could not be validated through your Active
Directory or because network services were unavailable.
Do you have any other service that starts under the same account? If so do
you have the same problem with that service also? Also please check the
event logs to check if there are any error messages or warning messages
related to this account. Also one other thing you can try is to use a
different account as a startup for SQL server and see if you can repro the
behavior.
"Fox1977" <foxj77@.gmail.com> wrote in message
news:1178789826.884648.294580@.w5g2000hsg.googlegroups.com...
> Hi folks,
> Can anyone help me out with this strange problem I'm having. I have a
> new server (Win 2003 standard) that is part of a domain and it is
> running SQL 2000. I have changed the services to run as a domain
> account. The password for this account is correct and the account is
> also local admin and domain admin.
> I am able to manually start the SQL server and SQL agent service
> manually but when i restart the box or try to restart the services
> they do not start up. I get the following error message in in the
> event log:
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7000
> Date: 10/05/2007
> Time: 09:58:45
> User: N/A
> Computer: xxxxx
> Description:
> The MSSQLSERVER service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is
> invalid for the account name specified.
> I checked the account details and they are working as I am able to log
> into the server using the account.
> Does anyone know why this happens and how i can get SQL and SQL agent
> to start up automatically as I don't want to be caught out in the
> event of the server rebooting.
> Anyone any tips or suggestions?
> Thanks in advance
>|||I was getting a netlogon error in the event log saying could not
contact PDC. After doing a bit of searching on the net I came across
this site:
http://www.eventid.net/display.asp?...phase=
1
About half way down there is an entry about lmhosts/wins. I compare
the LMHOSTS setting on the server against some of the other database
servers in the domain. I changed the LMHOSTS/NETBIOS setting to
Default from Disable NETBIOS over TCP/IP.
I rebooted the server and then the PDC error disappeared and the
services started automatically. Brilliant
Thanks for your help, much appreciated
Can anyone help me out with this strange problem I'm having. I have a
new server (Win 2003 standard) that is part of a domain and it is
running SQL 2000. I have changed the services to run as a domain
account. The password for this account is correct and the account is
also local admin and domain admin.
I am able to manually start the SQL server and SQL agent service
manually but when i restart the box or try to restart the services
they do not start up. I get the following error message in in the
event log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 10/05/2007
Time: 09:58:45
User: N/A
Computer: xxxxx
Description:
The MSSQLSERVER service failed to start due to the following error:
The account name is invalid or does not exist, or the password is
invalid for the account name specified.
I checked the account details and they are working as I am able to log
into the server using the account.
Does anyone know why this happens and how i can get SQL and SQL agent
to start up automatically as I don't want to be caught out in the
event of the server rebooting.
Anyone any tips or suggestions?
Thanks in advanceFox1977
The Windows Account for the MSSQLServer service and the SQLServerAgent
service has a bad password, or could not be validated through your Active
Directory or because network services were unavailable.
Do you have any other service that starts under the same account? If so do
you have the same problem with that service also? Also please check the
event logs to check if there are any error messages or warning messages
related to this account. Also one other thing you can try is to use a
different account as a startup for SQL server and see if you can repro the
behavior.
"Fox1977" <foxj77@.gmail.com> wrote in message
news:1178789826.884648.294580@.w5g2000hsg.googlegroups.com...
> Hi folks,
> Can anyone help me out with this strange problem I'm having. I have a
> new server (Win 2003 standard) that is part of a domain and it is
> running SQL 2000. I have changed the services to run as a domain
> account. The password for this account is correct and the account is
> also local admin and domain admin.
> I am able to manually start the SQL server and SQL agent service
> manually but when i restart the box or try to restart the services
> they do not start up. I get the following error message in in the
> event log:
> Event Type: Error
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7000
> Date: 10/05/2007
> Time: 09:58:45
> User: N/A
> Computer: xxxxx
> Description:
> The MSSQLSERVER service failed to start due to the following error:
> The account name is invalid or does not exist, or the password is
> invalid for the account name specified.
> I checked the account details and they are working as I am able to log
> into the server using the account.
> Does anyone know why this happens and how i can get SQL and SQL agent
> to start up automatically as I don't want to be caught out in the
> event of the server rebooting.
> Anyone any tips or suggestions?
> Thanks in advance
>|||I was getting a netlogon error in the event log saying could not
contact PDC. After doing a bit of searching on the net I came across
this site:
http://www.eventid.net/display.asp?...phase=
1
About half way down there is an entry about lmhosts/wins. I compare
the LMHOSTS setting on the server against some of the other database
servers in the domain. I changed the LMHOSTS/NETBIOS setting to
Default from Disable NETBIOS over TCP/IP.
I rebooted the server and then the PDC error disappeared and the
services started automatically. Brilliant
Thanks for your help, much appreciated
Monday, March 12, 2012
Problem encountered during the installation of Visual Studio .NET 2005 Professional on a windows
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.Problem encountered during the installation of Visual Studio .NET 2005 Professional on a windows
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.Problem encountered during the installation of Visual Studio .NET 2005 Professional on a windows
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.
Subscribe to:
Posts (Atom)