Error 1923 while installing SQL 2005 Express

This is from the event log

Product: Microsoft SQL Server 2005 Express Edition -- Error 1923. Service 'SQL Server ()' () could not be installed. Verify that you have sufficient privileges to install system services.

I've tried uninstalling through control panel and various cleanup tools and tried reinstalling with no luck.

I'm logged on with a user that has full admin rights.

1923 is an RPC error that translates to "The specified profile entry could not be added." You'll need to search through the SQL Server Setup log files for more detail on what went wrong. Start by looking here and in the subdirectory:

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Paul

|||I am having the same problem. Did you figure out a work around?

|||I have found NO answer to this question anywhere online. I got mine working last night here is what I did:
I was trying to install it on a VPS I only have licensing for one terminal server session and I noticed that earlier in the day my RDP connection had timed out and I was still logged in so I kicked the old connection uninstalled all instances of SQL and tried again. Guess what? it didn't work...lol So I uninstalled everything again and restarted the VPS and then it installed. I have no idea exactly what was wrong but that is how I solved it. Hope it helps someone else out.
sql

Error 1923 while installing SQL 2005 Express

This is from the event log

Product: Microsoft SQL Server 2005 Express Edition -- Error 1923. Service 'SQL Server ()' () could not be installed. Verify that you have sufficient privileges to install system services.

I've tried uninstalling through control panel and various cleanup tools and tried reinstalling with no luck.

I'm logged on with a user that has full admin rights.

1923 is an RPC error that translates to "The specified profile entry could not be added." You'll need to search through the SQL Server Setup log files for more detail on what went wrong. Start by looking here and in the subdirectory:

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Paul

|||I am having the same problem. Did you figure out a work around?

|||I have found NO answer to this question anywhere online. I got mine working last night here is what I did:
I was trying to install it on a VPS I only have licensing for one terminal server session and I noticed that earlier in the day my RDP connection had timed out and I was still logged in so I kicked the old connection uninstalled all instances of SQL and tried again. Guess what? it didn't work...lol So I uninstalled everything again and restarted the VPS and then it installed. I have no idea exactly what was wrong but that is how I solved it. Hope it helps someone else out.

error 18456 when trying to connect to 2005 using odbc

Hi all

I am using Windows XP SP2 with a Sql server 2005 Express installation. I created a test db with a user called test, schema also test. I gave the permission connect, db_datareader and db_datawriter. I can now connect into this user using WinSQL. But if I want to connect using a application which is using ODBC, then I get the error:

[SQLSTATE=28000 - [Microsoft][SQL Native][SQL Server]Login failed for user 'test'.[Native Error=18456]]

Because I connect using ODBC, I think there must be the problem. But I have to connect with ODBC. There is no other possibility.

any ideas ?

Regards, Waff

I found this out:

The server collation is defined to: Latin1_General_CI_AS

If I create a new login id in lowercase, then ODBC will change it to uppercase and then the server refuse the access. But why. CI means case insensitive, so doesn't matter if upper or lower case. should.

How do you use a id in lowercase and connecto via ODBC ?

You need to enable TCP in order for ODBC clients to connect. Check out http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx for information about doing this.

Mike

|||

Guess has something to do with the collation. I used Latin1_General_AI_CI.

If I create my login id in lowercase and try then to connect to the db using ODBC, then ODBC will switch my id to uppercase and so I can't logon.

Anyway, somehow, it must be possible to modify the server settings, so that it doesn't matter how I logon. lowercase or uppercase. I tryed with CI and CS but still them same.

ODBC is enabled but think has to do with the collation.

What are you using if you use id's as upper/lower case as Test ?

error 18456 when trying to connect to 2005 using odbc

Hi all

I am using Windows XP SP2 with a Sql server 2005 Express installation. I created a test db with a user called test, schema also test. I gave the permission connect, db_datareader and db_datawriter. I can now connect into this user using WinSQL. But if I want to connect using a application which is using ODBC, then I get the error:

[SQLSTATE=28000 - [Microsoft][SQL Native][SQL Server]Login failed for user 'test'.[Native Error=18456]]

Because I connect using ODBC, I think there must be the problem. But I have to connect with ODBC. There is no other possibility.

any ideas ?

Regards, Waff

I found this out:

The server collation is defined to: Latin1_General_CI_AS

If I create a new login id in lowercase, then ODBC will change it to uppercase and then the server refuse the access. But why. CI means case insensitive, so doesn't matter if upper or lower case. should.

How do you use a id in lowercase and connecto via ODBC ?

You need to enable TCP in order for ODBC clients to connect. Check out http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx for information about doing this.

Mike

|||

Guess has something to do with the collation. I used Latin1_General_AI_CI.

If I create my login id in lowercase and try then to connect to the db using ODBC, then ODBC will switch my id to uppercase and so I can't logon.

Anyway, somehow, it must be possible to modify the server settings, so that it doesn't matter how I logon. lowercase or uppercase. I tryed with CI and CS but still them same.

ODBC is enabled but think has to do with the collation.

What are you using if you use id's as upper/lower case as Test ?

Error 18452

Hi,
If I connect to SQLServer Express via Windows Authentication it works fine. But if I use SQL Server Authentication it doesn't work with a new created user and sa (with a new password) too. I turned mixed mode on, registry key HKLM\Software\Microsoft\Microsoft Sql Server\MSSQL.1\\MSSQLServer\login has the value 2 and all ports are set to 1433 but there is still error 18452. Any suggestions?

Did you restart the server service ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Yes, severeal times.
|||I guess the system you configured and the system you are connecting to are tw different ones then.|||No, it's the same system and I have only this one in the moment.
|||

What is the exact error message that you are getting back? Take a look at the errorlog as well to see what message is logged there.

How are you trying to connect? If you're connecting through an application, make sure that you don't specify integrated authentication in the connection string.

Thanks
Laurentiu

|||Restarting the server process was not enough. I had to restart windows and now it works.
Thank you.
sql

Error 17827 from SQL Server 2005 Express Edition

Hi,
I'm using SQL server 2005 Express Edition in my solution and I've run into a
problem that I can't find any information about.
The application was running OK (for several days) until this happend just
out of the blue.
The application is written in C++ and we are using ADO to access the
database.
The authentication used with sql server user names and passwords.
I have not changed the password for any user
In the SQL server error log I found the following lines.
2007-03-15 01:34:01.13 Server Server resumed execution after being idle
209 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2007-03-15 02:34:01.61 Server Server resumed execution after being idle
213 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2007-03-15 03:11:00.78 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:00.78 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:00.80 Server Error: 17054, Severity: 16, State: 1.
2007-03-15 03:11:00.80 Server The current event was not reported to the
Windows Events log. Operating system error = 5(error not found). You may nee
d
to clear the Windows Events log if it is full.
2007-03-15 03:11:02.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:02.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:05.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:05.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:11.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:11.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:23.45 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:23.45 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:48.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:48.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:12:38.31 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:12:38.31 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:14:16.67 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:14:16.67 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:15:55.91 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:15:55.91 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:17:35.19 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:17:35.19 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
Does anyone have any ideas why i get this behavior from SQL?
After we rebooted the system everything worked OK again.
Voja TadicVoja,
How many connections are being made to your SQL Express instance? Although
there is no hard limit to connections, there are resource limits on memory
and once those are used up, you will have problems.
Might you have many connections that should have closed during the several
successful days, but have not? If so, you many have many unused connections
still consuming resources.
The reason I ask is because the only instance of 17827 I see in technet is
SQL Server 2000 extended stored procedure related and means: The maximum
number of '%1!ld!' remote connections is currently in use.
Although that is not directly your error, it may be a hint as to the
underlying problem.
RLF
"vojat" <vojat@.discussions.microsoft.com> wrote in message
news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@.microsoft.com...
> Hi,
> I'm using SQL server 2005 Express Edition in my solution and I've run into
> a
> problem that I can't find any information about.
> The application was running OK (for several days) until this happend just
> out of the blue.
> The application is written in C++ and we are using ADO to access the
> database.
> The authentication used with sql server user names and passwords.
> I have not changed the password for any user
>
> In the SQL server error log I found the following lines.
>
> 2007-03-15 01:34:01.13 Server Server resumed execution after being
> idle
> 209 seconds: user activity awakened the server. This is an informational
> message only. No user action is required.
> 2007-03-15 02:34:01.61 Server Server resumed execution after being
> idle
> 213 seconds: user activity awakened the server. This is an informational
> message only. No user action is required.
> 2007-03-15 03:11:00.78 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:00.78 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:00.80 Server Error: 17054, Severity: 16, State: 1.
> 2007-03-15 03:11:00.80 Server The current event was not reported to
> the
> Windows Events log. Operating system error = 5(error not found). You may
> need
> to clear the Windows Events log if it is full.
> 2007-03-15 03:11:02.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:02.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:05.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:05.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:11.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:11.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:23.45 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:23.45 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:48.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:48.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:12:38.31 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:12:38.31 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:14:16.67 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:14:16.67 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:15:55.91 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:15:55.91 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:17:35.19 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:17:35.19 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
>
> Does anyone have any ideas why i get this behavior from SQL?
>
> After we rebooted the system everything worked OK again.
> Voja Tadic|||Hi,
I only use one connection for this application and I'm closing the
connection after each action to the database. I'm also using the connection
pooling functionality in ADO. This application uses the database alot.
I do have one additional application that uses ADO.DET and connects,
retrives data and dissconects and then terminats. This is done ~20-30 times
each day.
"Russell Fields" wrote:

> Voja,
> How many connections are being made to your SQL Express instance? Althoug
h
> there is no hard limit to connections, there are resource limits on memory
> and once those are used up, you will have problems.
> Might you have many connections that should have closed during the several
> successful days, but have not? If so, you many have many unused connectio
ns
> still consuming resources.
> The reason I ask is because the only instance of 17827 I see in technet i
s
> SQL Server 2000 extended stored procedure related and means: The maximum
> number of '%1!ld!' remote connections is currently in use.
> Although that is not directly your error, it may be a hint as to the
> underlying problem.
> RLF
> "vojat" <vojat@.discussions.microsoft.com> wrote in message
> news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@.microsoft.com...
>
>|||Voja,
I don't have any real good insight for you. You might look here for the
answer or someone to talk with:
http://blogs.msdn.com/sql_protocols.../23/558651.aspx
RLF
"vojat" <vojat@.discussions.microsoft.com> wrote in message
news:0ACE3553-246E-46EC-936D-5A57E1181A02@.microsoft.com...[vbcol=seagreen]
> Hi,
> I only use one connection for this application and I'm closing the
> connection after each action to the database. I'm also using the
> connection
> pooling functionality in ADO. This application uses the database alot.
> I do have one additional application that uses ADO.DET and connects,
> retrives data and dissconects and then terminats. This is done ~20-30
> times
> each day.
>
> "Russell Fields" wrote:
>

Error 17827 from SQL Server 2005 Express Edition

Hi,
I'm using SQL server 2005 Express Edition in my solution and I've run into a
problem that I can't find any information about.
The application was running OK (for several days) until this happend just
out of the blue.
The application is written in C++ and we are using ADO to access the
database.
The authentication used with sql server user names and passwords.
I have not changed the password for any user
In the SQL server error log I found the following lines.
2007-03-15 01:34:01.13 Server Server resumed execution after being idle
209 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2007-03-15 02:34:01.61 Server Server resumed execution after being idle
213 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2007-03-15 03:11:00.78 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:00.78 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:11:00.80 Server Error: 17054, Severity: 16, State: 1.
2007-03-15 03:11:00.80 Server The current event was not reported to the
Windows Events log. Operating system error = 5(error not found). You may need
to clear the Windows Events log if it is full.
2007-03-15 03:11:02.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:02.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:11:05.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:05.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:11:11.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:11.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:11:23.45 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:23.45 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:11:48.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:48.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:12:38.31 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:12:38.31 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:14:16.67 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:14:16.67 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:15:55.91 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:15:55.91 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:17:35.19 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:17:35.19 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
Does anyone have any ideas why i get this behavior from SQL?
After we rebooted the system everything worked OK again.
Voja Tadic
Voja,
How many connections are being made to your SQL Express instance? Although
there is no hard limit to connections, there are resource limits on memory
and once those are used up, you will have problems.
Might you have many connections that should have closed during the several
successful days, but have not? If so, you many have many unused connections
still consuming resources.
The reason I ask is because the only instance of 17827 I see in Technet is
SQL Server 2000 extended stored procedure related and means: The maximum
number of '%1!ld!' remote connections is currently in use.
Although that is not directly your error, it may be a hint as to the
underlying problem.
RLF
"vojat" <vojat@.discussions.microsoft.com> wrote in message
news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@.microsoft.com...
> Hi,
> I'm using SQL server 2005 Express Edition in my solution and I've run into
> a
> problem that I can't find any information about.
> The application was running OK (for several days) until this happend just
> out of the blue.
> The application is written in C++ and we are using ADO to access the
> database.
> The authentication used with sql server user names and passwords.
> I have not changed the password for any user
>
> In the SQL server error log I found the following lines.
>
> 2007-03-15 01:34:01.13 Server Server resumed execution after being
> idle
> 209 seconds: user activity awakened the server. This is an informational
> message only. No user action is required.
> 2007-03-15 02:34:01.61 Server Server resumed execution after being
> idle
> 213 seconds: user activity awakened the server. This is an informational
> message only. No user action is required.
> 2007-03-15 03:11:00.78 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:00.78 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:00.80 Server Error: 17054, Severity: 16, State: 1.
> 2007-03-15 03:11:00.80 Server The current event was not reported to
> the
> Windows Events log. Operating system error = 5(error not found). You may
> need
> to clear the Windows Events log if it is full.
> 2007-03-15 03:11:02.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:02.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:05.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:05.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:11.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:11.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:23.45 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:23.45 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:48.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:48.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:12:38.31 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:12:38.31 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:14:16.67 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:14:16.67 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:15:55.91 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:15:55.91 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:17:35.19 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:17:35.19 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
>
> Does anyone have any ideas why i get this behavior from SQL?
>
> After we rebooted the system everything worked OK again.
> Voja Tadic
|||Hi,
I only use one connection for this application and I'm closing the
connection after each action to the database. I'm also using the connection
pooling functionality in ADO. This application uses the database alot.
I do have one additional application that uses ADO.DET and connects,
retrives data and dissconects and then terminats. This is done ~20-30 times
each day.
"Russell Fields" wrote:

> Voja,
> How many connections are being made to your SQL Express instance? Although
> there is no hard limit to connections, there are resource limits on memory
> and once those are used up, you will have problems.
> Might you have many connections that should have closed during the several
> successful days, but have not? If so, you many have many unused connections
> still consuming resources.
> The reason I ask is because the only instance of 17827 I see in Technet is
> SQL Server 2000 extended stored procedure related and means: The maximum
> number of '%1!ld!' remote connections is currently in use.
> Although that is not directly your error, it may be a hint as to the
> underlying problem.
> RLF
> "vojat" <vojat@.discussions.microsoft.com> wrote in message
> news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@.microsoft.com...
>
>
|||Voja,
I don't have any real good insight for you. You might look here for the
answer or someone to talk with:
http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
RLF
"vojat" <vojat@.discussions.microsoft.com> wrote in message
news:0ACE3553-246E-46EC-936D-5A57E1181A02@.microsoft.com...[vbcol=seagreen]
> Hi,
> I only use one connection for this application and I'm closing the
> connection after each action to the database. I'm also using the
> connection
> pooling functionality in ADO. This application uses the database alot.
> I do have one additional application that uses ADO.DET and connects,
> retrives data and dissconects and then terminats. This is done ~20-30
> times
> each day.
>
> "Russell Fields" wrote:

Error 1612 - can't get Express installed

I have done all I can to resolve this on my own and would really appreciate any help anyone can give me. I have run uninstall utilities, followed a few MSDN reinstall methods, but all roads lead back to this vicious cycle:

The install hangs trying to install the prereq Microsoft SQL Server 2005 Setup Support Files with Error 1612. So I try to uninstall the Support files using Add/Remove..but the Windows Installer looks for "Microsoft SQL Server Native Client" disk, which of course I don't have because I install from downloads from Microsoft.

That's the very short version. I've got a ton of hours reading help groups, MSDN, trying everything.

I have posted the error log file below. Thanks in advance.

=== Verbose logging started: 1/25/2007 21:01:41 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: c:\6b4bf5519a6c349936f69599\setup.exe ===
MSI (c) (2C:64) [21:01:41:265]: Resetting cached policy values
MSI (c) (2C:64) [21:01:41:265]: Machine policy value 'Debug' is 0
MSI (c) (2C:64) [21:01:41:265]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (c) (2C:64) [21:01:41:265]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (2C:64) [21:01:41:265]: Grabbed execution mutex.
MSI (c) (2C:64) [21:01:41:281]: Cloaking enabled.
MSI (c) (2C:64) [21:01:41:281]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (2C:64) [21:01:41:281]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (98:90) [21:01:41:296]: Grabbed execution mutex.
MSI (s) (98:E4) [21:01:41:296]: Resetting cached policy values
MSI (s) (98:E4) [21:01:41:296]: Machine policy value 'Debug' is 0
MSI (s) (98:E4) [21:01:41:296]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (s) (98:E4) [21:01:41:296]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (98:E4) [21:01:41:296]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (98:E4) [21:01:41:296]: User policy value 'DisableMedia' is 0
MSI (s) (98:E4) [21:01:41:296]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Looking for sourcelist for product {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Adding {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Now checking product {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Media is enabled for product.
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Source with value name '1' is blank
MSI (s) (98:E4) [21:01:41:296]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msi
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Processing net source list.
MSI (s) (98:E4) [21:01:41:296]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msi
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Processing media source list.
MSI (s) (98:E4) [21:01:41:312]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (98:E4) [21:01:41:312]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (98:E4) [21:01:41:312]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msi
MSI (s) (98:E4) [21:01:41:312]: SOURCEMGMT: Processing URL source list.
MSI (s) (98:E4) [21:01:41:312]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (98:E4) [21:01:41:312]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msi
MSI (s) (98:E4) [21:01:41:312]: Note: 1: 1706 2: 3: SqlSupport.msi
MSI (s) (98:E4) [21:01:41:312]: SOURCEMGMT: Failed to resolve source
MSI (s) (98:E4) [21:01:41:312]: MainEngineThread is returning 1612
MSI (c) (2C:64) [21:01:41:312]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (2C:64) [21:01:41:312]: MainEngineThread is returning 1612
=== Verbose logging stopped: 1/25/2007 21:01:41 ===

hi,

jklegseth wrote:

I have done all I can to resolve this on my own and would really appreciate any help anyone can give me. I have run uninstall utilities, followed a few MSDN reinstall methods, but all roads lead back to this vicious cycle:

The install hangs trying to install the prereq Microsoft SQL Server 2005 Setup Support Files with Error 1612. So I try to uninstall the Support files using Add/Remove..but the Windows Installer looks for "Microsoft SQL Server Native Client" disk, which of course I don't have because I install from downloads from Microsoft.

try manually installing SQL Native Client before the SQLExpress installation by running the relative package (half the page down)

regards

|||

Hi Andrea,

I tried what you suggested. Here is what happens.

- I get a warning that "A lower version of this product has been detected on your stystem. Would you like to upgrade your existing installation?"

- I click Yes

- Install seems to go fine -- it shows me what will be installed, etc., until I get a window saying, "Insert the 'Microsoft SQL Native Client' disk and click OK.

|||

Update: Using Windows Install Cleanup I was able to get past the Native error. I think there was a registry entry for Native install that was no longer valid. I got through the SQL install only to have a new problem. Now, during the installation System Configuration Check I pass 14 of 15 tests. I get a warning for Com Plus Catalog Requirement.

The warning message is: "Com Plus Catalog Requirement (Warning), Messages: If SQL Server Setup fails, Setup will roll back....For more information, see How to: Work Around Com+ Check Failure in SQL Server Setup."

I followed the steps in that KB article but when I add Component Services in the Console and click on Com+ Applications, I get an error: "ERror Code 8004E00F - COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator.

So I looked that up and found various articles but none that seemed to apply directly to my problem.

If I continue the SQL Server setup and ignore the warning, I get a successful install of Setup Support Files, VSS WRiter, Backwards Compatability, but get failed warnings on all the of the SQL Express 2005 components. I'm once again stumped. Any ideas?

Thanks for your help.

|||

Update #2

I was to get past the above issue by following the steps at http://www.pcreview.co.uk/forums/thread-1596796.php. MSXML6 then failed during SQL Server install, so I removed it and reinstalled it. I am very close now. The error I now get is: "An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name" I have followed the steps at http://blogs.msdn.com/astebner/archive/2005/12/08/501885.aspx but this has not resolved the. I can't believe how much time I've spent on this, but maybe this error is one you have encountered? I will keep searching and posting here so others with this issue can find help. If you have any ideas I would appreciate it.

error 1603 installing microsoft sql native client

I am sql server 2005 installed, and I do not think I have sql server
express. I tried to install express but I keep getting.
Error 1603 installing Microsoft SQL Native Client.
This worked before when reinstalling SQL Server 2005 but uninstalling it,
but will this hurt SQL server 2005 if I do it again for SQL Express?Hi
You will need to remove all references to the SQL Server 2005 before you
start the instalation. Did you have any prior to RTM vesrions on your
computer?
"Microsoft News Group" <mflynn@.cvmediaonline.com> wrote in message
news:%23Ip$rjMlGHA.3512@.TK2MSFTNGP03.phx.gbl...
>I am sql server 2005 installed, and I do not think I have sql server
>express. I tried to install express but I keep getting.
> Error 1603 installing Microsoft SQL Native Client.
> This worked before when reinstalling SQL Server 2005 but uninstalling it,
> but will this hurt SQL server 2005 if I do it again for SQL Express?
>|||When you mean references, do you mean all of SQL Server 2005? I would like
both on the computer, is that not possible. What is RTM versions? If I
uninstall Native Client from Add/Remove Programs, and install Express, will
that mess up SQL server 2005 in anyway, because I have no idea what the
native client is.
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:evuRYJPlGHA.1340@.TK2MSFTNGP02.phx.gbl...
> Hi
> You will need to remove all references to the SQL Server 2005 before you
> start the instalation. Did you have any prior to RTM vesrions on your
> computer?
>
>
>
> "Microsoft News Group" <mflynn@.cvmediaonline.com> wrote in message
> news:%23Ip$rjMlGHA.3512@.TK2MSFTNGP03.phx.gbl...
>>I am sql server 2005 installed, and I do not think I have sql server
>>express. I tried to install express but I keep getting.
>> Error 1603 installing Microsoft SQL Native Client.
>> This worked before when reinstalling SQL Server 2005 but uninstalling it,
>> but will this hurt SQL server 2005 if I do it again for SQL Express?
>

error -1073741819.

hej!

i was installing sql client (sql server express edition), and i got error -1073741819.

how can i fiks this error.

Thank you

check this

http://support.microsoft.com/kb/306497

Madhu

error -1073741819.

hej!

i was installing sql client (sql server express edition), and i got error -1073741819.

how can i fiks this error.

Thank you

check this

http://support.microsoft.com/kb/306497

Madhu

error "MSDTC on server 'N\2984CABA-D249-43' is unavailable"

Could anybody help me with the following error
"MSDTC on server 'N\2984CABA-D249-43' is unavailable"
I am using Sql 2005 Express Edition
What does this error mean?
What should i do?

I had the same error - it's the Distributed Transaction Controller service that isn't running.

I found that if you go to Control Panel > Admin Tools > Component Services and then right click on My Computer, you'll see that there's an option to stop MSDTC - it seems that just getting this far automatically starts it. From here you can also view transaction info from the Distributed Transaction Coordinator folder.

If this doesn't work for you, then I'm afraid I can help no more!

Error

I already had SQL Server Express setup and had an application already running, but I installed SQL Server with Advanced Features to get Reporting Services.

I followed the directions step-by-step from the video tutorial on Getting Started with Reporting Services and when I tried to access the report server viahttp://localhost/Reports,

a page comes up giving me the following error.

The report server is not responding. Verify that the report server is running and can be accessed from this computer.

How do I resolve this error?

You can check couple of things.

1- go to start - all programs - Microsoft SQL Server 2005 - configuration tools - Reporting services configuration and make sure that the repoting services are configured properly.

2- check in the IIS and make sure, you have a virtual directory there, it might be different than you are typing.

If you still have a problems please let me know.

|||

What settings should I be looking for in Reporting Services?

The server is running and Server Status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity, Web Service Identity and Database Setup are configured and have green checks next to them.

I also opened up IIS and I saw the two virtual directories setup under Default Web Site where my current application resides.

|||

anybody?

|||

Ok, you can do one thing, go into IIS and select a reporting virtual directory, then right click and browse. This will open a site. If you get an error please let me know the exact error message.

|||

the same exact error as it gave me before when i went to localhost/reports

The report server is not responding. Verify that the report server is running and can be accessed from this computer.Home

|||

OK, i would recomend following, Please restart IIS and then Reporting service ( under windows service) as well.

|||

same thing. :(

|||

Is there a way I can send you the configuration so you guys can take a look at it? This is seriously very frustrating.

|||

Can you check the credentials of reporting service? and also make sure the serivce is started . I guess you can send me the snap shot of of your configuration and let me take a look.

Erroneous EOF's from Simple Queries

I am testing a VB.NET application using SQL Server Express (2005) and
ADODB.
Multiple instances of the application all access the database. In some
cases, they access and try to update the same row of a table. I am
opening this table with a single row query and
ADODB.LockTypeEnum.adLockPessimistic which I understand to be
equivalent to ROWLOCK.
Sample query:
SELECT Semaphores.* FROM Semaphores WHERE
(((Semaphores.SemaphoreName)='MySem'));
PROBLEM:
This query should always return the one record where this condition is
true. Most of the time it does this. However, sometimes it opens
without error, but the EOF condition is true (even though the query
should return the existing record).
My assumption was that the adLockPessimistic would fail the Open with
an exception if the the row could not be accessed with the lock. Is it
possible I am instead getting an EOF in this case? If not, any ideas
what may cause an EOF on a query that works almost every other time?
Other settings:
m_Connection.CommandTimeout = 5
m_Connection.ConnectionTimeout = 15
SET LOCK_TIMEOUT 0
Note:
Since I know the record is there, I could technically loop on the
erroneous EOF to get around the problem. But I believe I am seeing it
occur in other places where I cannot guarantee the EOF is not valid.
Gary Geniesse"GaryGen" <gary@.garygen.com> wrote in message
news:1146582362.350598.240750@.j73g2000cwa.googlegroups.com...
>I am testing a VB.NET application using SQL Server Express (2005) and
> ADODB.
Why are you using ADODB instead of System.Data.SqlClient?

> Multiple instances of the application all access the database. In some
> cases, they access and try to update the same row of a table. I am
> opening this table with a single row query and
> ADODB.LockTypeEnum.adLockPessimistic which I understand to be
> equivalent to ROWLOCK.
>
Ditch ADODB, use SqlClient, and read the BOL for lock hints and OUTPUT
clause.
No one remembers details of exactly ADO works, and no one wants to figure it
out. But plenty of people here can help with pure SQL solutions.
So what are you trying to acomplish? What are the table structures (DDL
please), and desired results?
David

ERREUR to open a data base with SSMSEE

I installed Visual Studio 2005 Standard Edition which contains SQL Server Express.

I downloaded and installed SQL Server Management Studio Express. It run !

I established a connection server BellFixe\SQLEXPRESS (BellFixe is the name of my computer). Ok.

The command " add " of the function " attach " of SSMSE allows to navigate on the disk and to attach diverse data bases but it refuses to open the directory D:\Documents and Settings\Alain (this path is the base of all my directories of data). This directory appears empty. I cannot thus attach the data bases which are under this directory !

I can open a data base only if it is elsewhere localised.

Why this limitation of access and how to resolve this problem? There is certainly a relation with the management of the users of the PC.

I am only user and administrator of my PC under XP. All my directories of data are under D:\Documents and Settings\Alain. The explorer Windows allows to navigate everywhere the disk.

Tanks.

hi,

the position you specfied is not a good one for such a kind of data as it is meant as "private" storage for the current (aka Alain) logged user... you should modify the path to something available to all users, even if SQLExpress always is run under the credential of the account you specified at install time or later, via the Surface Area Configuration or SQL Server Configuration Manager..

regards

|||

But SSMSEE should be able to cross all the disk, in mode administrator. He is not right for such a limitaion there is not it ?

This is only an MSDN exercise "Coatch ASP.NET". But it is blocking for me.

Regards

|||

hi,

AchLog wrote:

But SSMSEE should be able to cross all the disk, in mode administrator. He is not right for such a limitaion there is not it ?

is your SQL Server engine service running under Network Service or Local Service account?

please verify via SQL Server Configuration Manager..

regards

|||

Thank You for your answer Andrea.

SQL Server is local on my machine of development.

I have not yet understood how to verify the connexion mode with SQL Server Configuration Manager. I am a little bit novice with SQL Server and his tools.
Can you tell me how to verify it?

Here method indicated by coach ASP.NET to attach a local data base with SSMSEE. On my computer it is the step 4 which does not function.

===========================================

A simple solution is to attach your data base to your waiter SQL Express. It is now very easy with the console of administration “SQL Server Management Studio Express train” of the final version of SQL Server Express:

1 - to launch the console of administration since the menu To start/All the programs/Microsoft SQL Server 2005/SQL Server Management Studio Express train CTP.

2 - connect to the waiter of name”. \ SQLExpress " via the Windows authentification.

3 - in the explorer of object, made a right click on the file “Databases” then the order “attach”.

4 - find on the disc your file .mdf and add it. Your data base is now attached to SQL Server. You must see it in the list of the data bases of the console.

============================================
Thank you

|||

AchLog wrote:

Thank You for your answer Andrea.

SQL Server is local on my machine of development.

I have not yet understood how to verify the connexion mode with SQL Server Configuration Manager. I am a little bit novice with SQL Server and his tools.
Can you tell me how to verify it?

execute the SQL Server Configuration Manager.. in the SQL Server services locate the SQL Server engine you are dealing with.. right click on it and access it's properties.. you can there see (and set) the account running the services... if you modify it you have to restart the service..

AchLog wrote:

Here method indicated by coach ASP.NET to attach a local data base with SSMSEE. On my computer it is the step 4 which does not function.

===========================================

A simple solution is to attach your data base to your waiter SQL Express. It is now very easy with the console of administration “SQL Server Management Studio Express train” of the final version of SQL Server Express:

1 - to launch the console of administration since the menu To start/All the programs/Microsoft SQL Server 2005/SQL Server Management Studio Express train CTP.

2 - connect to the waiter of name”. \ SQLExpress " via the Windows authentification.

3 - in the explorer of object, made a right click on the file “Databases” then the order “attach”.

4 - find on the disc your file .mdf and add it. Your data base is now attached to SQL Server. You must see it in the list of the data bases of the console.

============================================
Thank you

the "explanation" is correct... this is the "traditional" way to attach a database to a SQL Server instance via SSMS (and SSMSE), but not to "user instances" as the perform differently...

regards

|||

Tank You Andrea,

The parameters are the following ones :

Name : bellfixe\sqlexpress

ERREUR to open a data base with SSMSEE

I installed Visual Studio 2005 Standard Edition which contains SQL Server Express.

I downloaded and installed SQL Server Management Studio Express. It run !

I established a connection server BellFixe\SQLEXPRESS (BellFixe is the name of my computer). Ok.

The command " add " of the function " attach " of SSMSE allows to navigate on the disk and to attach diverse data bases but it refuses to open the directory D:\Documents and Settings\Alain (this path is the base of all my directories of data). This directory appears empty. I cannot thus attach the data bases which are under this directory !

I can open a data base only if it is elsewhere localised.

Why this limitation of access and how to resolve this problem? There is certainly a relation with the management of the users of the PC.

I am only user and administrator of my PC under XP. All my directories of data are under D:\Documents and Settings\Alain. The explorer Windows allows to navigate everywhere the disk.

Tanks.

hi,

the position you specfied is not a good one for such a kind of data as it is meant as "private" storage for the current (aka Alain) logged user... you should modify the path to something available to all users, even if SQLExpress always is run under the credential of the account you specified at install time or later, via the Surface Area Configuration or SQL Server Configuration Manager..

regards

|||

But SSMSEE should be able to cross all the disk, in mode administrator. He is not right for such a limitaion there is not it ?

This is only an MSDN exercise "Coatch ASP.NET". But it is blocking for me.

Regards

|||

hi,

AchLog wrote:

But SSMSEE should be able to cross all the disk, in mode administrator. He is not right for such a limitaion there is not it ?

is your SQL Server engine service running under Network Service or Local Service account?

please verify via SQL Server Configuration Manager..

regards

|||

Thank You for your answer Andrea.

SQL Server is local on my machine of development.

I have not yet understood how to verify the connexion mode with SQL Server Configuration Manager. I am a little bit novice with SQL Server and his tools.
Can you tell me how to verify it?

Here method indicated by coach ASP.NET to attach a local data base with SSMSEE. On my computer it is the step 4 which does not function.

===========================================

A simple solution is to attach your data base to your waiter SQL Express. It is now very easy with the console of administration “SQL Server Management Studio Express train” of the final version of SQL Server Express:

1 - to launch the console of administration since the menu To start/All the programs/Microsoft SQL Server 2005/SQL Server Management Studio Express train CTP.

2 - connect to the waiter of name”. \ SQLExpress " via the Windows authentification.

3 - in the explorer of object, made a right click on the file “Databases” then the order “attach”.

4 - find on the disc your file .mdf and add it. Your data base is now attached to SQL Server. You must see it in the list of the data bases of the console.

============================================
Thank you

|||

AchLog wrote:

Thank You for your answer Andrea.

SQL Server is local on my machine of development.

I have not yet understood how to verify the connexion mode with SQL Server Configuration Manager. I am a little bit novice with SQL Server and his tools.
Can you tell me how to verify it?

execute the SQL Server Configuration Manager.. in the SQL Server services locate the SQL Server engine you are dealing with.. right click on it and access it's properties.. you can there see (and set) the account running the services... if you modify it you have to restart the service..

AchLog wrote:

Here method indicated by coach ASP.NET to attach a local data base with SSMSEE. On my computer it is the step 4 which does not function.

===========================================

A simple solution is to attach your data base to your waiter SQL Express. It is now very easy with the console of administration “SQL Server Management Studio Express train” of the final version of SQL Server Express:

1 - to launch the console of administration since the menu To start/All the programs/Microsoft SQL Server 2005/SQL Server Management Studio Express train CTP.

2 - connect to the waiter of name”. \ SQLExpress " via the Windows authentification.

3 - in the explorer of object, made a right click on the file “Databases” then the order “attach”.

4 - find on the disc your file .mdf and add it. Your data base is now attached to SQL Server. You must see it in the list of the data bases of the console.

============================================
Thank you

the "explanation" is correct... this is the "traditional" way to attach a database to a SQL Server instance via SSMS (and SSMSE), but not to "user instances" as the perform differently...

regards

|||

Tank You Andrea,

The parameters are the following ones :

Name : bellfixe\sqlexpress