failed to install sql server express due to Cannot alter the login 'sa'

Hi,

I am using dell precision m60 laptop with xp professional sp2. I had trouble to install sql server due to "Cannot alter the login 'sa'". I am part of administrators for this machine. Below is the log. Any idea? thanks. -dale

SQL_SUCCESS_WITH_INFO (1) in OdbcStatement::execute_batch
sqlstate=01000, level=0, state=1, native_error=15457, msg=[Microsoft][SQL Native Client][SQL Server]Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.

SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=42000, level=16, state=1, native_error=15151, msg=[Microsoft][SQL Native Client][SQL Server]Cannot alter the login 'sa', because it does not exist or you do not have permission.

Error Code: 0x80073b2f (15151)
Windows Error Text:Source File Name: lib\odbc_statement.h
Compiler Timestamp: Mon Jun 13 14:30:24 2005
Function Name: OdbcStatement::execute_batch@.CnfgSQL@.120
Source Line Number: 91

- Context --

Connecting to SQL Server
ExecuteSqlCommands
USE [master]
<Started SQL statement: Tue Feb 28 15:10:40 2006>declare @.ServerName nvarchar(255) if not exists (select * from sysservers) begin select @.ServerName = Convert(nvarchar(255), SERVERPROPERTY(N'ServerName')) execute sys.sp_addserver @.ServerName, local end
<Finished SQL statement: Tue Feb 28 15:10:41 2006>
<Started SQL statement: Tue Feb 28 15:10:41 2006>ALTER DATABASE model SET RECOVERY SIMPLE
<Finished SQL statement: Tue Feb 28 15:10:41 2006>
<Started SQL statement: Tue Feb 28 15:10:41 2006>EXEC sp_configure N'show advanced options', 1 RECONFIGURE WITH OVERRIDE
<Finished SQL statement: Tue Feb 28 15:10:41 2006>
<Started SQL statement: Tue Feb 28 15:10:41 2006>DECLARE @.Name AS nvarchar(128), @.LangID AS smallint SELECT @.Name=name, @.LangID=langid FROM syslanguages WHERE lcid=1033 EXEC sp_defaultlanguage N'sa', @.Name EXEC sp_configure N'default language', @.LangID EXEC sp_configure N'default full-text language', 1033 RECONFIGURE WITH OVERRIDE
<Finished SQL statement: Tue Feb 28 15:10:41 2006>
<Started SQL statement: Tue Feb 28 15:10:41 2006>EXEC sp_configure N'show advanced options', 0 RECONFIGURE WITH OVERRIDE
<Finished SQL statement: Tue Feb 28 15:10:41 2006>

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.|||thanks, Jeff. It is working now.

Failed to generate user instance and Cached Domain Login....

I am having trouble with the "Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. " message however I believe my circumstances are different that what I have found in any posts about this subject.
I use a laptop computer for development on my domain at work (I am in admin group on that domain). I have worked for several hours today on a project and logged off my network and then hooked my computer up at home. I log onto the machine again when I get home and log on normally, with a cached domain logon and I am unable access the database. This happened to me yesterday as well and after several hours of reading posts and troubleshooting I decided to reinstall SQL and that fixed the problem.
I don't want to have to reinstall each time I log on my computer at different locations. Most of the posts I read have to do with working on different computers or posting an application and accessing it remotely. I am working on the same machine all the time withouht making any changes to my configuration and am at a loss about how further to troubleshoot this problem.
Any suggestions would be greatly appreciated!

Just wanted to post and update on how I resolved this problem.

It would appear that resinstalling would fix the problem for short time but it would surface again after a few sessions.

I ended up un-installing SQL and then logging on the computers local admin account and installed SQL that way. I am not sure why being logged with an account that was in the admin group for my computer was any different, but at least that took care of the problem.

I will post an update again if this problem starts back up again, otherwise give that a shot if you are having the same problem I was.

|||

Well after a few days of successful use, I started having trouble again. I downloaded the SSEUTil.exe from http://www.microsoft.com/downloads/details.aspx?FamilyID=FA87E828-173F-472E-A85C-27ED01CF6B02&displaylang=en.

When I ran this utility I got the same error message "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed".

I started poking around with the SQL Configuration Manager and went to the properties for the instance of SQL that was running and changed the "log on as option" from "Network Service" to "Local System" and everything seemed to work again.

I hope this thread is helpfule to some besides me :)

|||

Setting it to log on as "Local System" worked for me as well, once I told it to not open the database using a "User Instance".

Thanks, this has been bothering me for days.

|||How do you tell your system not to open the database using a "User Instance"?|||To tell it not to generate user instance, go to the advanst property on the login window, a new window should appear. Move down the window untill you find the "User Instance" property, set that to false. I do not know how to do it on websites I would appresiate any help.

Failed to generate user instance and Cached Domain Login....

I am having trouble with the "Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed. " message however I believe my circumstances are different that what I have found in any posts about this subject.
I use a laptop computer for development on my domain at work (I am in admin group on that domain). I have worked for several hours today on a project and logged off my network and then hooked my computer up at home. I log onto the machine again when I get home and log on normally, with a cached domain logon and I am unable access the database. This happened to me yesterday as well and after several hours of reading posts and troubleshooting I decided to reinstall SQL and that fixed the problem.
I don't want to have to reinstall each time I log on my computer at different locations. Most of the posts I read have to do with working on different computers or posting an application and accessing it remotely. I am working on the same machine all the time withouht making any changes to my configuration and am at a loss about how further to troubleshoot this problem.
Any suggestions would be greatly appreciated!

Just wanted to post and update on how I resolved this problem.

It would appear that resinstalling would fix the problem for short time but it would surface again after a few sessions.

I ended up un-installing SQL and then logging on the computers local admin account and installed SQL that way. I am not sure why being logged with an account that was in the admin group for my computer was any different, but at least that took care of the problem.

I will post an update again if this problem starts back up again, otherwise give that a shot if you are having the same problem I was.

|||

Well after a few days of successful use, I started having trouble again. I downloaded the SSEUTil.exe from http://www.microsoft.com/downloads/details.aspx?FamilyID=FA87E828-173F-472E-A85C-27ED01CF6B02&displaylang=en.

When I ran this utility I got the same error message "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed".

I started poking around with the SQL Configuration Manager and went to the properties for the instance of SQL that was running and changed the "log on as option" from "Network Service" to "Local System" and everything seemed to work again.

I hope this thread is helpfule to some besides me :)

|||

Setting it to log on as "Local System" worked for me as well, once I told it to not open the database using a "User Instance".

Thanks, this has been bothering me for days.

|||How do you tell your system not to open the database using a "User Instance"?|||To tell it not to generate user instance, go to the advanst property on the login window, a new window should appear. Move down the window untill you find the "User Instance" property, set that to false. I do not know how to do it on websites I would appresiate any help.

Failed to generate user instance and Cached Domain Login....

I am having trouble with the "Failed to generate a

user instance of SQL Server due to a failure in starting the process for the

user instance. The connection will be closed. " message however I

believe my circumstances are different that what I have found in any posts

about this subject.

I use a laptop computer for development on my domain at work (I am in admin

group on that domain). I have worked for several hours today on a project and

logged off my network and then hooked my computer up at home. I log onto the

machine again when I get home and log on normally, with a cached domain logon

and I am unable access the database. This happened to me yesterday as

well and after several hours of reading posts and troubleshooting I decided to

reinstall SQL and that fixed the problem.

I don't want to have to reinstall each time I log on my computer at different

locations. Most of the posts I read have to do with working on different

computers or posting an application and accessing it remotely. I am working on

the same machine all the time withouht making any changes to my configuration and am at a loss about how further to

troubleshoot this problem.

Any suggestions would be greatly appreciated!

Just wanted to post and update on how I resolved this problem.

It would appear that resinstalling would fix the problem for short time but it would surface again after a few sessions.

I ended up un-installing SQL and then logging on the computers local admin account and installed SQL that way. I am not sure why being logged with an account that was in the admin group for my computer was any different, but at least that took care of the problem.

I will post an update again if this problem starts back up again, otherwise give that a shot if you are having the same problem I was.

|||

Well after a few days of successful use, I started having trouble again. I downloaded the SSEUTil.exe from http://www.microsoft.com/downloads/details.aspx?FamilyID=FA87E828-173F-472E-A85C-27ED01CF6B02&displaylang=en.

When I ran this utility I got the same error message "Failed to generate user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed".

I started poking around with the SQL Configuration Manager and went to the properties for the instance of SQL that was running and changed the "log on as option" from "Network Service" to "Local System" and everything seemed to work again.

I hope this thread is helpfule to some besides me :)

|||

Setting it to log on as "Local System" worked for me as well, once I told it to not open the database using a "User Instance".

Thanks, this has been bothering me for days.

|||How do you tell your system not to open the database using a "User Instance"?|||To tell it not to generate user instance, go to the advanst property on the login window, a new window should appear. Move down the window untill you find the "User Instance" property, set that to false. I do not know how to do it on websites I would appresiate any help.

Failed during recovery

I have been having a lot of trouble trying to reattach a database. The
latest issue is that after 9% of recovery I get a primary key violation and
it stops.
Is there anything I can do to get around this'
Thanks
RichardWhat SQL Server version are you using?
If you are using 2000, have you installed service pack 4?
thanks,
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>|||You most likely dettached the database without using the checkpoint command
to commit the data on memory to disk. This caused your identities to become
of synch to fix run dbcc checkident( sysrestorehistory ) in the msdb
database.
do you still have the old database?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>|||Richard
Do you have last FULL BACKUP of the database? If you do , perform just
RESTORE command
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>

Failed during recovery

I have been having a lot of trouble trying to reattach a database. The
latest issue is that after 9% of recovery I get a primary key violation and
it stops.
Is there anything I can do to get around this?
Thanks
Richard
What SQL Server version are you using?
If you are using 2000, have you installed service pack 4?
thanks,
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this?
> Thanks
> Richard
>
|||You most likely dettached the database without using the checkpoint command
to commit the data on memory to disk. This caused your identities to become
of synch to fix run dbcc checkident( sysrestorehistory ) in the msdb
database.
do you still have the old database?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this?
> Thanks
> Richard
>
|||Richard
Do you have last FULL BACKUP of the database? If you do , perform just
RESTORE command
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this?
> Thanks
> Richard
>

Failed during recovery

I have been having a lot of trouble trying to reattach a database. The
latest issue is that after 9% of recovery I get a primary key violation and
it stops.
Is there anything I can do to get around this'
Thanks
RichardWhat SQL Server version are you using?
If you are using 2000, have you installed service pack 4?
thanks,
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>|||You most likely dettached the database without using the checkpoint command
to commit the data on memory to disk. This caused your identities to become
of synch to fix run dbcc checkident( sysrestorehistory ) in the msdb
database.
do you still have the old database?
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>|||Richard
Do you have last FULL BACKUP of the database? If you do , perform just
RESTORE command
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>