Showing posts with label install. Show all posts
Showing posts with label install. Show all posts

Tuesday, March 27, 2012

Failed to modify security permissions on WMI namespace

Hello everyone,
I am trying to install a SQL server 2005 on a cluster but It does not succeed.
At the end of the installation in Configuring components ... of SQL Server
database services step, I recive the following message :
"SQL Server Setup failed to modify security permissions on WMI namespace
\\.\root\Microsoft\SqlServer\ServerEvents\Instance Name. To proceed, verify
that the account and domain running SQL server Setup exist, that the account
running SQL Server Setup has administrator privileges, and that the WMI
namespace exists on the destination drive."
I verified the points mentioned in this message and everything is right but
I can not finish the installation.
Has anybody experienced something similar?
Thank you for your help.
Best regards,
Juanjo
Since you have provided no details, it would be very difficult for anyone to
provide anything but the most generic responses.
You might want to post the output of the setup logs to determine a more
precise failure issue.
Sincerely,
Anthony Thomas

"Juanjo" <Juanjo@.discussions.microsoft.com> wrote in message
news:F3ED7933-4BCE-4CE0-B35B-CC83AF479343@.microsoft.com...
> Hello everyone,
> I am trying to install a SQL server 2005 on a cluster but It does not
succeed.
> At the end of the installation in Configuring components ... of SQL Server
> database services step, I recive the following message :
> "SQL Server Setup failed to modify security permissions on WMI namespace
> \\.\root\Microsoft\SqlServer\ServerEvents\Instance Name. To proceed, verify
> that the account and domain running SQL server Setup exist, that the
account
> running SQL Server Setup has administrator privileges, and that the WMI
> namespace exists on the destination drive."
> I verified the points mentioned in this message and everything is right
but
> I can not finish the installation.
> Has anybody experienced something similar?
> Thank you for your help.
> Best regards,
> Juanjo
|||Anthony, thank you very much for your suggestion.
Here I enclosed a piece of my failed SQL 2005 installation. In this piece of
log appears the error I received (LEGATO is the instance name):
"Error Code: 29516
MSI (s) (20!70) [14:00:16:607]: Product: Microsoft SQL Server 2005 -- Error
29516. SQL Server Setup failed to modify security permissions on WMI
namespace \\.\root\Microsoft\SqlServer\ServerEvents\LEGATO. To proceed,
verify that the account and domain running SQL Server Setup exist, that the
account running SQL Server Setup has administrator privileges, and that the
WMI namespace exists on the destination drive.
Error 29516. SQL Server Setup failed to modify security permissions on WMI
namespace \\.\root\Microsoft\SqlServer\ServerEvents\LEGATO. To proceed,
verify that the account and domain running SQL Server Setup exist, that the
account running SQL Server Setup has administrator privileges, and that the
WMI namespace exists on the destination drive.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_WMISecurity
PerfTime Start: Do_WMISecurity : Mon Jan 22 14:00:16 2007
<Func Name='Do_WMISecurity'>
Configuring ACL for WMI namespace
\\.\root\Microsoft\SqlServer\ServerEvents\LEGATO
ACL:
(A;CI;CCDCLCSWRPWPRCWD;;;BA)(A;CI;CCDCRC;;;S-1-5-21-119559289-1840127793-336618761-622849)
<Func Name='SecureWMINamespace'>
CoSetProxyBlanket failed to switch security level to IMPERSONATE
Error value: 2147942487 (0x80070057)
Failed to connect to namespace
Error value: 2147942487 (0x80070057)
<EndFunc Name='SecureWMINamespace' Return='-2147024809' GetLastError='0'>
Error Code: 0x8007734c (29516)
Windows Error Text: Source File Name: sqlca\sqlwmisecurityca.cpp
Compiler Timestamp: Tue Aug 9 01:14:18 2005
Function Name: Do_WMISecurity
Source Line Number: 158"
Thank you.
Juanjo
"Anthony Thomas" wrote:

> Since you have provided no details, it would be very difficult for anyone to
> provide anything but the most generic responses.
> You might want to post the output of the setup logs to determine a more
> precise failure issue.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Juanjo" <Juanjo@.discussions.microsoft.com> wrote in message
> news:F3ED7933-4BCE-4CE0-B35B-CC83AF479343@.microsoft.com...
> succeed.
> account
> but
>
>
|||No, I have not yet seen this message.
Things I would check:
The account you logged in as has administrator privileges on both nodes.
That you typed in this account as the account with remote access.
That the default User Access Rights have not been overridden by Domain Level
GPOs.
Make sure you have sufficient free space on the system partition on all
nodes.
What version of the OS and SS2K5 are you installing?
Verify that the Local Domain Groups required by the setup program exist in
AD or the installation account has permission to create them during the
installation.
Take a look at this document:
http://support.microsoft.com/kb/910228/en-us
Sincerely,
Anthony Thomas

"Juanjo" <Juanjo@.discussions.microsoft.com> wrote in message
news:2F4A9A06-265A-4427-980E-64AEC5D1270B@.microsoft.com...
> Anthony, thank you very much for your suggestion.
> Here I enclosed a piece of my failed SQL 2005 installation. In this piece
of
> log appears the error I received (LEGATO is the instance name):
> "Error Code: 29516
> MSI (s) (20!70) [14:00:16:607]: Product: Microsoft SQL Server 2005 --
Error
> 29516. SQL Server Setup failed to modify security permissions on WMI
> namespace \\.\root\Microsoft\SqlServer\ServerEvents\LEGATO. To proceed,
> verify that the account and domain running SQL Server Setup exist, that
the
> account running SQL Server Setup has administrator privileges, and that
the
> WMI namespace exists on the destination drive.
> Error 29516. SQL Server Setup failed to modify security permissions on WMI
> namespace \\.\root\Microsoft\SqlServer\ServerEvents\LEGATO. To proceed,
> verify that the account and domain running SQL Server Setup exist, that
the
> account running SQL Server Setup has administrator privileges, and that
the
> WMI namespace exists on the destination drive.
> <Func Name='GetCAContext'>
> <EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
> Doing Action: Do_WMISecurity
> PerfTime Start: Do_WMISecurity : Mon Jan 22 14:00:16 2007
> <Func Name='Do_WMISecurity'>
> Configuring ACL for WMI namespace
> \\.\root\Microsoft\SqlServer\ServerEvents\LEGATO
> ACL:
>
(A;CI;CCDCLCSWRPWPRCWD;;;BA)(A;CI;CCDCRC;;;S-1-5-21-119559289-1840127793-336
618761-622849)[vbcol=seagreen]
> <Func Name='SecureWMINamespace'>
> CoSetProxyBlanket failed to switch security level to IMPERSONATE
> Error value: 2147942487 (0x80070057)
> Failed to connect to namespace
> Error value: 2147942487 (0x80070057)
> <EndFunc Name='SecureWMINamespace' Return='-2147024809' GetLastError='0'>
> Error Code: 0x8007734c (29516)
> Windows Error Text: Source File Name: sqlca\sqlwmisecurityca.cpp
> Compiler Timestamp: Tue Aug 9 01:14:18 2005
> Function Name: Do_WMISecurity
> Source Line Number: 158"
> Thank you.
> Juanjo
>
> "Anthony Thomas" wrote:
anyone to[vbcol=seagreen]
Server[vbcol=seagreen]
namespace[vbcol=seagreen]
verify[vbcol=seagreen]
WMI[vbcol=seagreen]
right[vbcol=seagreen]
|||I finally could have this SQL 2005 cluster installed. The cluster shared disk
from our SAN were not properly configured. These have been recreated.
Thank you very much for your help.
Best regards,
Juanjo
"Anthony Thomas" wrote:

> No, I have not yet seen this message.
> Things I would check:
> The account you logged in as has administrator privileges on both nodes.
> That you typed in this account as the account with remote access.
> That the default User Access Rights have not been overridden by Domain Level
> GPOs.
> Make sure you have sufficient free space on the system partition on all
> nodes.
> What version of the OS and SS2K5 are you installing?
> Verify that the Local Domain Groups required by the setup program exist in
> AD or the installation account has permission to create them during the
> installation.
> Take a look at this document:
> http://support.microsoft.com/kb/910228/en-us
> Sincerely,
>
> Anthony Thomas
>
> --
> "Juanjo" <Juanjo@.discussions.microsoft.com> wrote in message
> news:2F4A9A06-265A-4427-980E-64AEC5D1270B@.microsoft.com...
> of
> Error
> the
> the
> the
> the
> (A;CI;CCDCLCSWRPWPRCWD;;;BA)(A;CI;CCDCRC;;;S-1-5-21-119559289-1840127793-336
> 618761-622849)
> anyone to
> Server
> namespace
> verify
> WMI
> right
>
>

Failed to install: Cumulative hotfix package (build 2153) for SQL Server 2005 (KB918222)

Hi experts!

I try to update SQL Server 2005 SP1 with the Cumulative hotfix package (build 2153). I need to do this, because I get an error this hotfix is said to fix... and of course - the update completely crashes (sending an error report to microsoft).

Here is what the log looks like:

Failed ACL:
SetSecurityFileDescriptor is failed at the error code 5; Converted SDDL: '(A;OICI;FA;;;S-1-5-21-1276437202-3579633377-1796755180-1012)'
Error Code: 0x80077342 (29506)
Windows Error Text: Source File Name: sqlca\sqlsddlca.cpp
Compiler Timestamp: Tue Apr 11 11:45:24 2006
Function Name: ExceptionInSDDL
Source Line Number: 65

- Context --


Setting status of unmanaged components and removing unmanaged resources

MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
Error Code: 29506
MSI (s) (50!B4) [23:18:29:854]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:854]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Transforming table Error.

MSI (s) (50!B4) [23:18:29:870]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (50!B4) [23:18:29:870]: Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user SQL. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.

Error 29506. SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user SQL. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
<Failure Type='Fatal' Error='29506'>
<EndFunc Name='LaunchFunction' Return='29506' GetLastError='0'>
MSI (s) (50:34) [23:18:29:886]: User policy value 'DisableRollback' is 0
MSI (s) (50:34) [23:18:29:886]: Machine policy value 'DisableRollback' is 0
Action ended 23:18:29: InstallFinalize. Return value 3.
MSI (s) (50:34) [23:18:29:964]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=910146116,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (50:34) [23:18:29:964]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (50:34) [23:18:29:964]: Executing op: DialogInfo(Type=1,Argument=Microsoft SQL Server 2005)
MSI (s) (50:34) [23:18:29:964]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (50:34) [23:18:29:964]: Executing op: RegisterBackupFile(File=C:\Config.Msi\643b07e2.rbf)
MSI (s) (50:34) [23:18:29:964]: Executing op: RegisterBackupFile(File=C:\Config.Msi\643b07e3.rbf)
MSI (s) (50:34) [23:18:29:979]: Executing op: RegisterBackupFile(File=C:\Config.Msi\643b07e4.rbf)
MSI (s) (50:34) [23:18:29:979]: Executing op: RegisterBackupFile(File=C:\Config.Msi\643b07e5.rbf)
MSI (s) (50:34) [23:18:29:979]: Executing op: RegisterBackupFile(File=C:\Config.Msi\643b07e6.rbf)
MSI (s) (50:34) [23:18:29:979]: Executing op: ActionStart(Name=Do_sqlFileSDDL.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Setting File Security,Template=File: [1])
MSI (s) (50:34) [23:18:29:979]: Executing op: ProductInfo(ProductKey={130A3BE1-85CC-4135-8EA7-5A724EE6CE2C},ProductName=Microsoft SQL Server 2005,PackageName=SqlRun_SQL.msi,Language=1033,Version=151062527,Assignment=1,ObsoleteArg=0,ProductIcon=ARPIcon.ico,PackageMediaPath=\Setup\,PackageCode={3185FC73-41E0-43F4-97DF-2254C4D7C667},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
MSI (s) (50:34) [23:18:29:979]: Executing op: ActionStart(Name=Do_sqlUserSecurity.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Setting User Security,Template=Account: [1])
MSI (s) (50:34) [23:18:29:979]: Executing op: ActionStart(Name=Do_sqlGroupMember.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Installing Local Groups,)
MSI (s) (50:34) [23:18:29:979]: Executing op: ActionStart(Name=Rollback_sqlGroupMember.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Installing Local Groups,)
MSI (s) (50:34) [23:18:29:979]: Executing op: CustomActionRollback(Action=Rollback_sqlGroupMember.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1345,Source=BinaryData,Target=Rollback_sqlGroupMember,CustomActionData=1 0 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$KMAUSQL01SRV$MSSQLSERVER NT AUTHORITY\LocalService )
MSI (s) (50:68) [23:18:29:995]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSICD9.tmp, Entrypoint: Rollback_sqlGroupMember
<Func Name='LaunchFunction'>

I would really be thankful for any hint regarding what to do to solve this problem.... As said - I have an error occuring, this hotfix is said to fix - to be exact, it's the one stating "not to be able to build the execution plan under some circumstances when using a SQL query inside a stored procedure"

Help greatly appreciated!!

Greetings, Wolfgang

Make sure the acct used to startup sqlserver service has read/write access to the folder listed. Also, be sure you login as admin to run setup.

|||

Thanks for your reply oj!

Actually I was logged in as member of the 'Administrators' group... That's what bugged me so much... But as I followed your hint and tried to modify the permissions of the folder manually I immediately got a Windows-Authentication Modal Popup - telling me that I have to authenticate to the domain...

So the problem was that I was local administrator but the hotfix-installation in fact needed mit to be also domain-administrator (don't really understand why though).

I just contacted the Domain-Admin and made him install the hotfix ;-) It worked... Thanks for the hint!

Regards,
Wolfgang

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 install SQL Server 2005 Enterprise (x86) on one server

Failed to install SQL Server 2005 Enterprise (x86) on one server

I am trying to install SQL Server 2005 Enterprise on one of my test server. I am sure I entered the correct domain user name and password and the account is admin. I’ve tried several times but I got this error instantly:

The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."

Some of the other component could be installed properly. The system was just rebuilt with only VSTS 2005 installed.

Here is the part of the log

MSI (s) (48:58) [06:04:54:365]: Executing op: ActionStart(Name=Do_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Configuring Microsoft SQL Server,Template=Starting SQL Service: [1])

MSI (s) (48:58) [06:04:54:365]: Executing op: CustomActionSchedule(Action=Do_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=9217,Source=BinaryData,Target=**********,CustomActionData=**********)

MSI (s) (48:CC) [06:04:54:365]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIE56.tmp, Entrypoint: Do_sqlScript

<Func Name='LaunchFunction'>

Function=Do_sqlScript

<Func Name='GetCAContext'>

<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>

Doing Action: Do_sqlScript

PerfTime Start: Do_sqlScript : Thu Jul 12 06:04:54 2007

Service MSSQLSERVER with parameters '-m SqlSetup -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Thu Jul 12 06:04:54 2007

Unable to start service (1069)

Error Code: 0x8007042d (1069)

Windows Error Text: The service did not start due to a logon failure.

Source File Name: sqlsetuplib\service.cpp

Compiler Timestamp: Fri Sep 16 13:20:12 2005

Function Name: sqls:ervice:tart

Source Line Number: 316

Thanks - Andy

Seems I have found the root cause. I changed starting the service using local system user and it works. I remember I installed SQL Server 2005 on another machine using the same way it works for me, very weird.

Failed to install MSDE 2000a

I have been tring to install the MSDE 200Aon my marchine that is using
the command prompt.
this is the command that i was using:
(setup INSTANCENAME="SA" SECURITYMODE=SQL SAPWD="SqlAdmin1"
TARGETDIR="C:\" )
but it gave me the following error message;
(Go to the control panel to install and configure system components)
now i really dont know what to do from here can you advice me?
hi Tino,
Tino wrote:
> I have been tring to install the MSDE 200Aon my marchine that is using
> the command prompt.
> this is the command that i was using:
> (setup INSTANCENAME="SA" SECURITYMODE=SQL SAPWD="SqlAdmin1"
> TARGETDIR="C:\" )
> but it gave me the following error message;
> (Go to the control panel to install and configure system components)
> now i really dont know what to do from here can you advice me?
did you navigate and posittioned your command prompt window in the folder
hosting the setup.exe boostrap installer of MSDE?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
-- remove DMO to reply
sql

Failed to install IDE using September CTP

While installation of September 2005 CTP, the installation failed to install IDE SQL projects .

Is this known issue or did I miss any thing.

Regards,
V

SQL Server 2005 does not ship Visual Studio 2005 SQL projects. You would need to install it separately.

Thanks,
-Vineet.

Monday, March 26, 2012

Failed to generate a user instance of SQL Server

Hello all,
I unisntall products as it are recommended (VS 2005 and SQL Server 2005
beta 2) in readme.txt of MSDN products subscription...
I install VS 2005 Pro and I have no problem during install. Now, if I want to open database, I have this error mesage :
"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."

In MBSA report, I see that the folders of SQL doesn't contain another
account than Administrator and VS2005 users. I delete other accounts but the
problem is the same.

If I create a new project with a new database the problem is the same.

Have you an idea to solve this problem ?
Thank you very mutch.
Regards.
Patrice.

This is because of a known problem in Windows. See http://support.microsoft.com/default.aspx?scid=kb;en-us;896613 for more details.

Thanks

|||Thanks Paul; Thank you very mutch because this problem is not solved. I called Msdn support last week without solution after two hours to solve that. We have controlled VS, IIS and others.
Then, I uninstalled VS2005 with all products. I cleaned the registry and then install again VS2005 and SQL Express.
The problem is exactly the same. It seem that the solution is in the account of the Window user.

Sorry for my lack of english.

Thank you for your help.
Patrice.|||Try deleting the directory SQLEXPRESS (Or better rename it say SQLEXPRESS_).

It solved my problem. This directory is at following location...

C:\Documents and Settings\[USERNAME]\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS

cheers!

Ref. http://forums.microsoft.com/msdn/showpost.aspx?postid=98346&siteid=1|||I was having the same problem and had tried the suggestions on this post with no results. I installed another instance of sql express and used the default instance name and that corrected the problem.
|||Hello,
Even your help and explanations I not solved my problem.
Now, I install SQL Server 2005.
I can attach the database : I use it, I create a new table; non problem here.
I create a connexion with the ODBC data source in Administrator tools in panel settings : Test connexion is OK.
But in VS 2005 I can't access to the database without this error with SQL Express or SQL Server !! :-((

I'm very hangry.

Thanks all.
Patrice.|||

Hello Pat84,
I got your problem yesterday, and I think I've solved it now.
You need to install the SQL Management Studio 2005 Express (CTD) first, create an account named "(YOUR)PC\ASPNET", subsitute (YOUR) with your PC's name. For me it's HENRYPC\ASPNET. Because VS Express will use this default account to access SQLEXPRESS's database.

Then create a database for the use of YOURPC\ASPNET with the help of Mgt Studio Express.
Then in your Visual Web Developer Express or Visual Studio, create a connection to the new database you just created. You need to select "SQL Server" as service provider, ".\SQLEXPRESS" as data source, and you will find your new database name as well as four system databases under the "select database". Then you test your connection. It will works!

Hope it helps! Good Luck,
Henry Li

|||

Thank you very mutch Henry !

I try that and I come back.

Regards.

Patrice.

|||You can get that error if your logging on using "Local Service". Try logging on using "Network Service", if you are not already.
Open the SQL Server Configuration Manager
Wtih the SQL Server 2005 Services node selected, right click SQL Server (SQLEXPRESS)
Select Properties
Make sure "Network Service" is selected
May need to reboot PC (not just restart the server).|||Sorry for that answer to be long. I was very ill...

Thank you all.

My problem is solved.

Patrice.

Failed to generate a user instance of SQL Server

Hello all,
I unisntall products as it are recommended (VS 2005 and SQL Server 2005
beta 2) in readme.txt of MSDN products subscription...
I install VS 2005 Pro and I have no problem during install. Now, if I want to open database, I have this error mesage :
"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."

In MBSA report, I see that the folders of SQL doesn't contain another
account than Administrator and VS2005 users. I delete other accounts but the
problem is the same.

If I create a new project with a new database the problem is the same.

Have you an idea to solve this problem ?
Thank you very mutch.
Regards.
Patrice.

This is because of a known problem in Windows. See http://support.microsoft.com/default.aspx?scid=kb;en-us;896613 for more details.

Thanks

|||Thanks Paul; Thank you very mutch because this problem is not solved. I called Msdn support last week without solution after two hours to solve that. We have controlled VS, IIS and others.
Then, I uninstalled VS2005 with all products. I cleaned the registry and then install again VS2005 and SQL Express.
The problem is exactly the same. It seem that the solution is in the account of the Window user.

Sorry for my lack of english.

Thank you for your help.
Patrice.|||Try deleting the directory SQLEXPRESS (Or better rename it say SQLEXPRESS_).

It solved my problem. This directory is at following location...

C:\Documents and Settings\[USERNAME]\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS

cheers!

Ref. http://forums.microsoft.com/msdn/showpost.aspx?postid=98346&siteid=1|||I was having the same problem and had tried the suggestions on this post with no results. I installed another instance of sql express and used the default instance name and that corrected the problem.|||Hello,
Even your help and explanations I not solved my problem.
Now, I install SQL Server 2005.
I can attach the database : I use it, I create a new table; non problem here.
I create a connexion with the ODBC data source in Administrator tools in panel settings : Test connexion is OK.
But in VS 2005 I can't access to the database without this error with SQL Express or SQL Server !! :-((

I'm very hangry.

Thanks all.
Patrice.|||

Hello Pat84,
I got your problem yesterday, and I think I've solved it now.
You need to install the SQL Management Studio 2005 Express (CTD) first, create an account named "(YOUR)PC\ASPNET", subsitute (YOUR) with your PC's name. For me it's HENRYPC\ASPNET. Because VS Express will use this default account to access SQLEXPRESS's database.

Then create a database for the use of YOURPC\ASPNET with the help of Mgt Studio Express.
Then in your Visual Web Developer Express or Visual Studio, create a connection to the new database you just created. You need to select "SQL Server" as service provider, ".\SQLEXPRESS" as data source, and you will find your new database name as well as four system databases under the "select database". Then you test your connection. It will works!

Hope it helps! Good Luck,
Henry Li

|||

Thank you very mutch Henry !

I try that and I come back.

Regards.

Patrice.

|||You can get that error if your logging on using "Local Service". Try logging on using "Network Service", if you are not already.
Open the SQL Server Configuration Manager
Wtih the SQL Server 2005 Services node selected, right click SQL Server (SQLEXPRESS)
Select Properties
Make sure "Network Service" is selected
May need to reboot PC (not just restart the server).|||Sorry for that answer to be long. I was very ill...

Thank you all.

My problem is solved.

Patrice.sql

Failed to generate a user instance of SQL Server

Hello all,
I unisntall products as it are recommended (VS 2005 and SQL Server 2005
beta 2) in readme.txt of MSDN products subscription...
I install VS 2005 Pro and I have no problem during install. Now, if I want to open database, I have this error mesage :
"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."

In MBSA report, I see that the folders of SQL doesn't contain another
account than Administrator and VS2005 users. I delete other accounts but the
problem is the same.

If I create a new project with a new database the problem is the same.

Have you an idea to solve this problem ?
Thank you very mutch.
Regards.
Patrice.

This is because of a known problem in Windows. See http://support.microsoft.com/default.aspx?scid=kb;en-us;896613 for more details.

Thanks

|||Thanks Paul; Thank you very mutch because this problem is not solved. I called Msdn support last week without solution after two hours to solve that. We have controlled VS, IIS and others.
Then, I uninstalled VS2005 with all products. I cleaned the registry and then install again VS2005 and SQL Express.
The problem is exactly the same. It seem that the solution is in the account of the Window user.

Sorry for my lack of english.

Thank you for your help.
Patrice.|||Try deleting the directory SQLEXPRESS (Or better rename it say SQLEXPRESS_).

It solved my problem. This directory is at following location...

C:\Documents and Settings\[USERNAME]\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\SQLEXPRESS

cheers!

Ref. http://forums.microsoft.com/msdn/showpost.aspx?postid=98346&siteid=1|||I was having the same problem and had tried the suggestions on this post with no results. I installed another instance of sql express and used the default instance name and that corrected the problem.
|||Hello,
Even your help and explanations I not solved my problem.
Now, I install SQL Server 2005.
I can attach the database : I use it, I create a new table; non problem here.
I create a connexion with the ODBC data source in Administrator tools in panel settings : Test connexion is OK.
But in VS 2005 I can't access to the database without this error with SQL Express or SQL Server !! :-((

I'm very hangry.

Thanks all.
Patrice.|||

Hello Pat84,
I got your problem yesterday, and I think I've solved it now.
You need to install the SQL Management Studio 2005 Express (CTD) first, create an account named "(YOUR)PC\ASPNET", subsitute (YOUR) with your PC's name. For me it's HENRYPC\ASPNET. Because VS Express will use this default account to access SQLEXPRESS's database.

Then create a database for the use of YOURPC\ASPNET with the help of Mgt Studio Express.
Then in your Visual Web Developer Express or Visual Studio, create a connection to the new database you just created. You need to select "SQL Server" as service provider, ".\SQLEXPRESS" as data source, and you will find your new database name as well as four system databases under the "select database". Then you test your connection. It will works!

Hope it helps! Good Luck,
Henry Li

|||

Thank you very mutch Henry !

I try that and I come back.

Regards.

Patrice.

|||You can get that error if your logging on using "Local Service". Try logging on using "Network Service", if you are not already.
Open the SQL Server Configuration Manager
Wtih the SQL Server 2005 Services node selected, right click SQL Server (SQLEXPRESS)
Select Properties
Make sure "Network Service" is selected
May need to reboot PC (not just restart the server).|||Sorry for that answer to be long. I was very ill...

Thank you all.

My problem is solved.

Patrice.

Friday, March 23, 2012

Failed to create Application Services Database for SQL Server

I have sql 2005 express installed with VS2005. I tried to install the service database using Aspnet_regsql.exe but always ended up with the same error:

Code Snippet

Setup failed.

Exception:
An error occurred during the execution of the SQL file 'InstallMembership.sql'. The SQL error number is -2 and the SqlException message is: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

-
Details of failure
-

SQL Server:
Database: [aspnetdb]
SQL file loaded:
InstallMembership.sql

Commands failed:

EXEC sp_addrolemember N'aspnet_Membership_BasicAccess', N'aspnet_Membership_FullAccess'
EXEC sp_addrolemember N'aspnet_Membership_ReportingAccess', N'aspnet_Membership_FullAccess'

SQL Exception:
System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at System.Web.Management.SqlServices.ExecuteFile(String file, String server, String database, String dbFileName, SqlConnection connection, Boolean sessionState, Boolean isInstall, SessionStateType sessionStatetype)


The database aspnetdb was always created with just 4 tables and 3 views.

Please can someone help me on this, thanks very much!

If the database still exists, the script might wait for the last database connection to close to be able to drop the database. Is there any DROp statement in the sql file ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

Wednesday, March 21, 2012

Failed to connect to sql server

Hi folks,

I′m brazilian and new in SQL Server.

Now i′m justing tryng to create a instance to use with WSUS.
I Already created but when i try to install the WSUS and its try to connect into my new instance, i received the message:
Failed to connect to sql server ... Class not registered.
Could you help me?

Regards,

Andre de CastroCan you copy-paste the complete text of the error message which you received? What is WSUS?

Thanks
Laurentiu

Failed to configure server install error

I've been looking into this all day and haven't gotten anywhere. I'm using
InstallShield to install a .Net application, the application uses MSDE as
its database. I've added InstallShield's MSDE object to the install, works
fine sometimes but most of the time I get the following error message when
the MSDE is almost installed.
"Setup failed to configure the server. Refer to the server error logs and
setup errors for more information."
I've scoured the internet looking into this error and nothing seems to
correct this issue. I've remove all files, registry keys and anything
related to MSDE and I still get the same error. I've generated an install
log (attached in an email to follow as "MSDELog.log").
Thanks in advance,
Dave
ERRORLOG
2004-11-16 14:01:09.51 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
2004-11-16 14:01:09.51 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-11-16 14:01:09.51 server All rights reserved.
2004-11-16 14:01:09.51 server Server Process ID is 4060.
2004-11-16 14:01:09.51 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$INSPPRO\LOG\ERRORLOG'.
2004-11-16 14:01:09.57 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-11-16 14:01:09.62 server SQL Server configured for thread mode
processing.
2004-11-16 14:01:09.62 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2004-11-16 14:01:09.63 spid3 Warning ******************
2004-11-16 14:01:09.63 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2004-11-16 14:01:09.68 spid3 Starting up database 'master'.
2004-11-16 14:01:10.13 server Using 'SSNETLIB.DLL' version '8.0.760'.
2004-11-16 14:01:10.13 spid5 Starting up database 'model'.
2004-11-16 14:01:10.20 server SQL server listening on 192.168.0.119:
1395.
2004-11-16 14:01:10.20 server SQL server listening on 127.0.0.1: 1395.
2004-11-16 14:01:10.20 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-11-16 14:01:10.20 server SQL Server is ready for client connections
2004-11-16 14:01:10.24 spid3 Server name is 'CHRISTABLET\INSPPRO'.
2004-11-16 14:01:10.24 spid3 Skipping startup of clean database id 5
2004-11-16 14:01:10.24 spid3 Skipping startup of clean database id 6
2004-11-16 14:01:10.24 spid3 Starting up database 'msdb'.
2004-11-16 14:01:10.84 spid5 Clearing tempdb database.
2004-11-16 14:01:11.78 spid5 Starting up database 'tempdb'.
2004-11-16 14:01:12.18 spid3 Recovery complete.
2004-11-16 14:01:12.18 spid3 SQL global counter collection task is
created.
2004-11-16 14:01:12.25 spid3 Warning: override, autoexec procedures
skipped.
2004-11-16 14:03:15.07 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
cnfgsvr.out
################################################## #############################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
An error occurred while attempting to start the service (1460)
SQL Server configuration failed.
################################################## #############################
Hi ,
net helpmsg 1460: This operation returned because the timeout period
expired.
This may occur due the following reasons:
1) You are using terminal services /RDP to install msde which opens a
different session and is NOT the same as being on the console.
Try to logon on locally to the machine and then run the installation with
the following command line
setup /L*v c:\msde.log disablerollback=1 disablenetworkprotocols=0
sapwd="some password"
Girish Sundaram
This posting is provided "AS IS" with no warranties, and confers no rights.
|||This is absolutely the solution.
I just solved the SAME problem described in the first message in this
way.
To Microsoft: please WRITE somewhere that you CAN NOT install SQL or
MSDE on Windows XP from Remote Desktop!!
Marco

> 1) You are using terminal services /RDP to install msde which opens a
> different session and is NOT the same as being on the console.
> Try to logon on locally to the machine and then run the installation with
> the following command line
> setup /L*v c:\msde.log disablerollback=1 disablenetworkprotocols=0
> sapwd="some password"
> Girish Sundaram
> This posting is provided "AS IS" with no warranties, and confers no rights.

Failed SQL Cluster Install Advice

A quick rant - After days of study, hours of install, and some killer
directions for Brad M McGehee I began to install a SQL Cluster on a Windows
2003 enterprise server cluster. If only i had found that one little article
that said that the install fails if you use two Cds.
So here I am for advice. My SQL 2005 cluster install failed when I
installed the second "tools" CD. Now I wonder what is the best resolution
for recovery. What I have read says that installing over a failed install is
not a good idea but in this case do i really have a failed install. The
installtion log shows no failures and everything that had installed up to
that point on both nodes had green "good" checks.
It states to install the installation files from both disks to a folder on
C: I assume that means the C: drive on the active node I used for the
installation would work right?
How should I proceed?
1. Try a standard unistall from control panel of all components on both
nodes.
2. Try to reinstall over the failed nut perhaps not failed install?
3. Complete the manual unistall as many artilces direct?
4. Any other proven ideas?
5. Send it to Bill and have him fix it. ha ha
Thanks for the advice ahead of time.
Regards, emagidson
The issue with installing from CD is that the remote node cannot direct the
local node to change the disk. By copying both CDs to a common location,
you eliminate the need to change disks. The exact location is not
necessarily important.
Don't do a reinstall on top of a broken install. Go to Control Panel |
Add/Remov programs and restart the existing install from there.
Note that some components such as client tools and SSIS do not install on
the remot enode during a cluster install. You have to install them on each
node locally. Personally, I prefer to do that install first, just to keep
things simple.
If the install restart fails, then you can try to do a manual remove and
re-install.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"EMagidson" <EMagidson@.discussions.microsoft.com> wrote in message
news:1695A1A1-CE3B-4B61-BA66-79BC6A9874E5@.microsoft.com...
>A quick rant - After days of study, hours of install, and some killer
> directions for Brad M McGehee I began to install a SQL Cluster on a
> Windows
> 2003 enterprise server cluster. If only i had found that one little
> article
> that said that the install fails if you use two Cds.
> So here I am for advice. My SQL 2005 cluster install failed when I
> installed the second "tools" CD. Now I wonder what is the best resolution
> for recovery. What I have read says that installing over a failed install
> is
> not a good idea but in this case do i really have a failed install. The
> installtion log shows no failures and everything that had installed up to
> that point on both nodes had green "good" checks.
> It states to install the installation files from both disks to a folder on
> C: I assume that means the C: drive on the active node I used for the
> installation would work right?
> How should I proceed?
> 1. Try a standard unistall from control panel of all components on both
> nodes.
> 2. Try to reinstall over the failed nut perhaps not failed install?
> 3. Complete the manual unistall as many artilces direct?
> 4. Any other proven ideas?
> 5. Send it to Bill and have him fix it. ha ha
> Thanks for the advice ahead of time.
> Regards, emagidson
|||Geoff:
Thanks for the advice I do have a couple of questions. According to what I
read and since the install takes place from the active node, can i create a
folder on the root of node 1 C: drive say c:\sqlinstall then a folder under
that for both disks or do I need to do this on one of the shared array drives?
Also you mention restarting the install from control panel / add/remove
programs. This is not something I have done before. Again, longer term net
admin but I am not a clustering guy. Can you elaborate a bit on how to do it
from there given that I am seeing four to five "programs" that installed
through the install. We are installing everything via the install Sql,
Analysis tools, reporting service etc.
Also you mention other items that do not get installed, according to what I
read everything does get installed to the second node later in the process
and it looked like that was the case.
thanks again for the advice and in advance for more advice.
Regards, emagidson
"Geoff N. Hiten" wrote:

> The issue with installing from CD is that the remote node cannot direct the
> local node to change the disk. By copying both CDs to a common location,
> you eliminate the need to change disks. The exact location is not
> necessarily important.
> Don't do a reinstall on top of a broken install. Go to Control Panel |
> Add/Remov programs and restart the existing install from there.
> Note that some components such as client tools and SSIS do not install on
> the remot enode during a cluster install. You have to install them on each
> node locally. Personally, I prefer to do that install first, just to keep
> things simple.
> If the install restart fails, then you can try to do a manual remove and
> re-install.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "EMagidson" <EMagidson@.discussions.microsoft.com> wrote in message
> news:1695A1A1-CE3B-4B61-BA66-79BC6A9874E5@.microsoft.com...
>
|||Local disk is best. Shared is NOT a good idea. You don't want the source
files going offline during the install or moving to another node.
The program you want to update is most likely called "Microsoft SQL Server".
That entry should have a "change" option. (I am working from memory here
since my Vista machine has very different labels for these functions.). The
installer will remember the earlier failure and try to correct it once you
have fixed the underlying issue.
Management Studio only gets installed to the local node during a cluster
install. Only items that have the "create failover cluster" option get
installed on the other node(s) in a cluster.
"EMagidson" <EMagidson@.discussions.microsoft.com> wrote in message
news:68B0121D-0FE1-434C-87FF-1C8B5A811676@.microsoft.com...
> Geoff:
> Thanks for the advice I do have a couple of questions. According to what
> I
> read and since the install takes place from the active node, can i create
> a
> folder on the root of node 1 C: drive say c:\sqlinstall then a folder
> under
> that for both disks or do
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
I need to do this on one of the shared array drives?[vbcol=seagreen]
> Also you mention restarting the install from control panel / add/remove
> programs. This is not something I have done before. Again, longer term
> net
> admin but I am not a clustering guy. Can you elaborate a bit on how to do
> it
> from there given that I am seeing four to five "programs" that installed
> through the install. We are installing everything via the install Sql,
> Analysis tools, reporting service etc.
> Also you mention other items that do not get installed, according to what
> I
> read everything does get installed to the second node later in the process
> and it looked like that was the case.
> thanks again for the advice and in advance for more advice.
> Regards, emagidson
> "Geoff N. Hiten" wrote:
|||Here is more information:
We completed a manual install as directed, changed the registry keys, even
killed the SQL registry entires. We have done this twice and both time get
the same message upon reinstall. "There is already a SQL instance with that
name". At this point I gues it is best to rebuild the whole thing as start
over. Unless someone else has a better idea.
We removed all of SQL from boht servers, everything on the shared array, the
folder that was still in Program files after the ininstall (come on uninstall
is uninstall get rid of everything) and the registry entires.
ALL OF THIS BECAUSE WE INSTALLED WITH TWO CDs WHICH DOES NOT WORK!!!!
Yes sorry I am very frustrated.
Thanks in advance, emagidson
"EMagidson" wrote:

> A quick rant - After days of study, hours of install, and some killer
> directions for Brad M McGehee I began to install a SQL Cluster on a Windows
> 2003 enterprise server cluster. If only i had found that one little article
> that said that the install fails if you use two Cds.
> So here I am for advice. My SQL 2005 cluster install failed when I
> installed the second "tools" CD. Now I wonder what is the best resolution
> for recovery. What I have read says that installing over a failed install is
> not a good idea but in this case do i really have a failed install. The
> installtion log shows no failures and everything that had installed up to
> that point on both nodes had green "good" checks.
> It states to install the installation files from both disks to a folder on
> C: I assume that means the C: drive on the active node I used for the
> installation would work right?
> How should I proceed?
> 1. Try a standard unistall from control panel of all components on both
> nodes.
> 2. Try to reinstall over the failed nut perhaps not failed install?
> 3. Complete the manual unistall as many artilces direct?
> 4. Any other proven ideas?
> 5. Send it to Bill and have him fix it. ha ha
> Thanks for the advice ahead of time.
> Regards, emagidson
|||Did you follow this KB article:
http://support.microsoft.com/kb/909967
(Perhaps the most complex KB article ever, but it should work. Just make
sure and perform the steps on both nodes.)
Also, remove any DNS and AD entries refering to the clustered instance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"EMagidson" <EMagidson@.discussions.microsoft.com> wrote in message
news:3763668C-691E-4DE0-871E-B450E36B7A68@.microsoft.com...[vbcol=seagreen]
> Here is more information:
> We completed a manual install as directed, changed the registry keys, even
> killed the SQL registry entires. We have done this twice and both time
> get
> the same message upon reinstall. "There is already a SQL instance with
> that
> name". At this point I gues it is best to rebuild the whole thing as start
> over. Unless someone else has a better idea.
> We removed all of SQL from boht servers, everything on the shared array,
> the
> folder that was still in Program files after the ininstall (come on
> uninstall
> is uninstall get rid of everything) and the registry entires.
> ALL OF THIS BECAUSE WE INSTALLED WITH TWO CDs WHICH DOES NOT WORK!!!!
> Yes sorry I am very frustrated.
> Thanks in advance, emagidson
> "EMagidson" wrote:
|||Geoff:
Thanks Geoff, We have deicded that we just don't feel we can trust the
systems with all the changes and have decided to install everything from
scratch. This way we know when out client begins to rely on the systems the
will be rock solid and ready to perform. Thanks for the link however I have
filed it into me personal knowledgebase.
Thanks again, emagidson
"Geoff N. Hiten" wrote:

> Did you follow this KB article:
> http://support.microsoft.com/kb/909967
> (Perhaps the most complex KB article ever, but it should work. Just make
> sure and perform the steps on both nodes.)
> Also, remove any DNS and AD entries refering to the clustered instance.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "EMagidson" <EMagidson@.discussions.microsoft.com> wrote in message
> news:3763668C-691E-4DE0-871E-B450E36B7A68@.microsoft.com...
>
|||Good call. I would recommend the same thing in the same situation. Clean
systems are generally the best, especially in a complex, clustered
environment.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"EMagidson" <EMagidson@.discussions.microsoft.com> wrote in message
news:C762EE7E-68A2-428C-8B2F-55F99BBE6555@.microsoft.com...[vbcol=seagreen]
> Geoff:
> Thanks Geoff, We have deicded that we just don't feel we can trust the
> systems with all the changes and have decided to install everything from
> scratch. This way we know when out client begins to rely on the systems
> the
> will be rock solid and ready to perform. Thanks for the link however I
> have
> filed it into me personal knowledgebase.
> Thanks again, emagidson
> "Geoff N. Hiten" wrote:
|||Geoff:
As you can most likely tell I am not a newby to IT and networks but I am
with Clustering. I wanted to thank you for all your help. We have now
reinstalled the whole shibang and have everything running. All of the
failover tests have been performed and the only thing left to do is create
backups of the servers.
I will be beginning a new thread to ask a few more basic questions "Basic
SQL cluster questions" that if you have time I would love to hear your
replies.
Again thank you. I always make a point to help out in newsgroups as much as
I can. It always seems to come back in spades.
Regards, emagidson
"Geoff N. Hiten" wrote:

> Good call. I would recommend the same thing in the same situation. Clean
> systems are generally the best, especially in a complex, clustered
> environment.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "EMagidson" <EMagidson@.discussions.microsoft.com> wrote in message
> news:C762EE7E-68A2-428C-8B2F-55F99BBE6555@.microsoft.com...
>
|||You are welcome.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"EMagidson" <EMagidson@.discussions.microsoft.com> wrote in message
news:96BC8AFB-F754-43FD-A412-137B8C3EE1F9@.microsoft.com...[vbcol=seagreen]
> Geoff:
> As you can most likely tell I am not a newby to IT and networks but I am
> with Clustering. I wanted to thank you for all your help. We have now
> reinstalled the whole shibang and have everything running. All of the
> failover tests have been performed and the only thing left to do is create
> backups of the servers.
> I will be beginning a new thread to ask a few more basic questions "Basic
> SQL cluster questions" that if you have time I would love to hear your
> replies.
> Again thank you. I always make a point to help out in newsgroups as much
> as
> I can. It always seems to come back in spades.
> Regards, emagidson
> "Geoff N. Hiten" wrote:
sql

Monday, March 19, 2012

Failed of install Microsoft SQL Server 2005 Express Edition Kb 921

Hi, do anyone know how to solve this failed install problem of microsoft SQL
server 2005.
Hi
"tazhy7" wrote:

> Hi, do anyone know how to solve this failed install problem of microsoft SQL
> server 2005.
Check the log files in the installation log directory (usually ...\90\Setup
Bootstrap\LOG ) start with the summary and find out what the error message
and information output.
John

Failed of install Microsoft SQL Server 2005 Express Edition Kb 921

Hi, do anyone know how to solve this failed install problem of microsoft SQL
server 2005.Hi
"tazhy7" wrote:
> Hi, do anyone know how to solve this failed install problem of microsoft SQL
> server 2005.
Check the log files in the installation log directory (usually ...\90\Setup
Bootstrap\LOG ) start with the summary and find out what the error message
and information output.
John

Failed of install Microsoft SQL Server 2005 Express Edition Kb 921

Hi, do anyone know how to solve this failed install problem of microsoft SQL
server 2005.Hi
"tazhy7" wrote:

> Hi, do anyone know how to solve this failed install problem of microsoft S
QL
> server 2005.
Check the log files in the installation log directory (usually ...\90\Setup
Bootstrap\LOG ) start with the summary and find out what the error message
and information output.
John

Failed installation to cluster

I have a 2 node cluster on which I am trying to install a
virtual SQL Server.
I am able to complete the setup process, but the
installation fails after checking the cluster resources.
In the application log I see that the ports have
automatically been disabled (as I'm installing SQL from a
CD without sp3a as yet) and the errors that follow show
that connections to the SQL Server were unable to be made.
Is there a switch for the install to stop the disabling of
ports? Has anyone else seen this issue?
Any help would be very much appreciated.
Kind regards,
Simon
Here is the workaround you need.
PRB: Installation of a Named Instance of SQL Server 2000 Virtual Server on a
Windows 2003-Based Cluster Fails
http://support.microsoft.com/default...&Product=sql2k
Once you install SP3a you can remove the alias.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Simon Call" <Simon@.eduserv.org.uk> wrote in message
news:138901c4265c$191f39a0$a101280a@.phx.gbl...
> I have a 2 node cluster on which I am trying to install a
> virtual SQL Server.
> I am able to complete the setup process, but the
> installation fails after checking the cluster resources.
> In the application log I see that the ports have
> automatically been disabled (as I'm installing SQL from a
> CD without sp3a as yet) and the errors that follow show
> that connections to the SQL Server were unable to be made.
> Is there a switch for the install to stop the disabling of
> ports? Has anyone else seen this issue?
> Any help would be very much appreciated.
> Kind regards,
> Simon
|||Geoff,
Many thanks for this.
Kind regards,
Simon

>--Original Message--
>Here is the workaround you need.
>PRB: Installation of a Named Instance of SQL Server 2000
Virtual Server on a
>Windows 2003-Based Cluster Fails
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;815431&Product=sql2k[vbcol=seagreen]
>Once you install SP3a you can remove the alias.
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Simon Call" <Simon@.eduserv.org.uk> wrote in message
>news:138901c4265c$191f39a0$a101280a@.phx.gbl...
a[vbcol=seagreen]
a[vbcol=seagreen]
made.[vbcol=seagreen]
of
>
>.
>
|||You probably noticed this but you cannot disable named pipes if you want to
install on Windows 2003, because setup needs named pipes to work.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Failed install of standard SQL 2005 server on XP

I have an issue with trying to install SQL 2005 standard on my XP machine.

I get an .hta file that is not readable and when I btpass that I get a pop-up message:

please go to the control panel to install and configure system components.

WTH?

PLease assist....

Gene

Is your XP on Service Pack 2?|||Yes, I am completely up to date with all of my SP's and patches.|||

I did not relize this but this was a simple fix.

All I had to do was go into the SQL disk was to open it up and execute the Setup.exe instead of opening it up from the .hta file.

Failed Install of SQL Server 2005 SP1 CTP

Hello,

We are attempting to install the CTP for SQL Server 2005 SP1 and receive the following error message in the log:

The following exception occurred: Unable to install Windows Installer MSP file Date: 03/24/2006 14:19:40.562 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856This is

then followed by this failure with the Database Services:

Product: Database Services Database Services (RTM 1399 ENU)- Failure Details: Unable to install Windows Installer MSP file

I also found the following entry in the SQL9_Hotfix_KB913090_sqlrun_sqlmsp.log file:

SqlUpgradeMessage = SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again.

Thanks in advance for any assistance, --John

This is puzzling. We found and fixed one bug generating the first error before releasing the CTP. Could you describe your installation and post a link to the setup log files? I think someone will need to pore over them to understand the problem.|||

Could you go ahead and log a bug using: http://lab.msdn.microsoft.com/ProductFeedback ?

|||I'm getting the same error with the final release.|||

Kevin, can you attach your msp log as well? The file is SQL9_Hotfix_KB913090_sqlrun_sql.msp.log. Are you applying SP1 to an RTM install or did you apply a previous SP1 build along the way?

Thanks,
Samuel Lester (MSFT)

|||Samuel, I just attempted to run the new SP1 and got the same problem as the original post (regarding "dm_exec_query_resource_semaphore"). I also found in the log file the same problem with the object named dm_exec_query_memory_grants.|||

Glenn, can you supply me with the log file I referenced above? This may help us determine why the object seems to be having permission issues.

Thanks,
Samuel Lester (MSFT)

|||I'm getting the same error, here's the tail of my log file (the whole thing is about 9MB, cant really post that :/)


Property(S): SqlUpgradeMessage = SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again.
Property(S): UpgradeInstruction = Connect to SQL instance SRVHAM14 as sysadmin
Launch SQL statement USE master
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\DbEngine_hotfix_install.sql
Launch script file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\repl_hotfix_install.sql
Stop service MSSQLSERVER
MSI (s) (20:A4) [13:56:22:544]: Product: Microsoft SQL Server 2005 (64-bit) - Update 'Service Pack 1 for SQL Server Database Services 2005 (64-bit) ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log.

MSI (s) (20:A4) [13:56:22:544]: Note: 1: 1729
MSI (s) (20:A4) [13:56:22:544]: Transforming table Error.

MSI (s) (20:A4) [13:56:22:544]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (20:A4) [13:56:22:544]: Transforming table Error.

MSI (s) (20:A4) [13:56:22:544]: Transforming table Error.

MSI (s) (20:A4) [13:56:22:544]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (20:A4) [13:56:22:544]: Transforming table Error.

MSI (s) (20:A4) [13:56:22:544]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (20:A4) [13:56:22:544]: Transforming table Error.

MSI (s) (20:A4) [13:56:22:544]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (20:A4) [13:56:22:544]: Transforming table Error.

MSI (s) (20:A4) [13:56:22:544]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (20:A4) [13:56:22:544]: Transforming table Error.

MSI (s) (20:A4) [13:56:22:544]: Transforming table Error.

MSI (s) (20:A4) [13:56:22:544]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (20:A4) [13:56:22:544]: Transforming table Error.

MSI (s) (20:A4) [13:56:22:544]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (20:A4) [13:56:22:544]: Transforming table Error.

MSI (s) (20:A4) [13:56:22:544]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (20:A4) [13:56:22:560]: Product: Microsoft SQL Server 2005 (64-bit) -- Configuration failed.

MSI (s) (20:A4) [13:56:22:560]: Attempting to delete file C:\WINDOWS\Installer\4aaf165.msp
MSI (s) (20:A4) [13:56:22:575]: Cleaning up uninstalled install packages, if any exist
MSI (s) (20:A4) [13:56:22:575]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\4aaf165.msp'
MSI (s) (20:A4) [13:56:22:575]: MainEngineThread is returning 1603
MSI (s) (20:98) [13:56:22:575]: Destroying RemoteAPI object.
MSI (s) (20:0C) [13:56:22:575]: Custom Action Manager thread ending.
=== Logging stopped: 21/04/2006 13:56:22 ===
MSI (c) (58:60) [13:56:22:606]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (58:60) [13:56:22:606]: MainEngineThread is returning 1603
=== Verbose logging stopped: 21/04/2006 13:56:22 ===


|||Little more, first time the error shows up in the logs:



SQL_SUCCESS_WITH_INFO (1) in OdbcConnection::connect
sqlstate=01000, level=-1, state=-1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'.
sqlstate=01000, level=-1, state=-1, native_error=5703, msg=[Microsoft][SQL Native Client][SQL Server]Changed language setting to us_english.

<Started SQL statement: Fri Apr 21 13:56:07 2006> USE master
SQL_SUCCESS_WITH_INFO (1) in OdbcStatement::execute_batch
sqlstate=01000, level=0, state=1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'.

<Finished SQL statement: Fri Apr 21 13:56:07 2006>
<Started SQL script: Fri Apr 21 13:56:07 2006> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql
Open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql in Unicode mode
SQL_SUCCESS_WITH_INFO (1) in OdbcStatement::execute_batch
sqlstate=01000, level=0, state=1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'.

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



|||Ok, some more digging into the upgrade scripts reveals this as the offending query (sysdbupg.sql):


-- Grant SELECT on Shiloh views to PUBLIC (only if they were not explicitely denied)
--
use master
go

set nocount on
set implicit_transactions off
set ansi_nulls on -- default for osql (consistent for suites)
set quoted_identifier on -- Force all ye devs to do this correctly!
go

-- temporary grant select to QE dmv
GRANT SELECT on sys.dm_exec_query_resource_semaphores TO PUBLIC
GRANT SELECT on sys.dm_exec_query_memory_grants TO PUBLIC



The error tells us that either these dont exist, or we dont have permission to them... And I believe they don't exist (certainly not post failed upgrade anyway). If there's another part of the upgrade that's supposed to create those table valued functions, it isn't doing so.
|||

Hey,

I also am getting this error on attempting to install Microsoft SQL Server 2005 Service Pack 1. :(

That is "Unable to install Windows Installer MSP file" .

I do not see any "SQL9_Hotfix_KB913090_sqlrun_sql.msp.log" file.

On my system it is "Redist9_Hotfix_KB913090_SqlSupport.msp.log". At least according to the event log:

"Product: Microsoft SQL Server Setup Support Files (English) - Update '{EE92F683-5F5C-4970-BB0B-9AC591B60268}' could not be installed. Error code 1642. Additional information is available in the log file C:\WINNT\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log."

So here is the log file:

=== Verbose logging started: 4/21/2006 12:23:36 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\WINNT\system32\msiexec.exe ===
MSI (c) (A4:58) [12:23:36:625]: Resetting cached policy values
MSI (c) (A4:58) [12:23:36:625]: Machine policy value 'Debug' is 0
MSI (c) (A4:58) [12:23:36:625]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (c) (A4:58) [12:23:36:625]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (A4:58) [12:23:36:625]: Grabbed execution mutex.
MSI (c) (A4:58) [12:23:36:640]: Cloaking enabled.
MSI (c) (A4:58) [12:23:36:640]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (A4:58) [12:23:36:640]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (4C:6C) [12:23:36:640]: Grabbed execution mutex.
MSI (s) (4C:EC) [12:23:36:640]: Resetting cached policy values
MSI (s) (4C:EC) [12:23:36:640]: Machine policy value 'Debug' is 0
MSI (s) (4C:EC) [12:23:36:640]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (s) (4C:EC) [12:23:36:640]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (4C:EC) [12:23:36:656]: End dialog not enabled
MSI (s) (4C:EC) [12:23:36:656]: Original package ==> C:\WINNT\Installer\1f5f617.msi
MSI (s) (4C:EC) [12:23:36:656]: Package we're running from ==> C:\WINNT\Installer\1f5f617.msi
MSI (s) (4C:EC) [12:23:36:656]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (4C:EC) [12:23:36:656]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (4C:EC) [12:23:36:656]: MSCOREE already loaded, using loaded copy
MSI (s) (4C:EC) [12:23:36:671]: File will have security applied from OpCode.
MSI (s) (4C:EC) [12:23:36:718]: Original patch ==> d:\857d69c78de19fc05980be8d2cc8\HotFixSqlSupport\Files\SqlSupport.msp
MSI (s) (4C:EC) [12:23:36:718]: Patch we're running from ==> C:\WINNT\Installer\1f5f686.msp
MSI (s) (4C:EC) [12:23:36:718]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'd:\857d69c78de19fc05980be8d2cc8\HotFixSqlSupport\Files\SqlSupport.msp' against software restriction policy
MSI (s) (4C:EC) [12:23:36:718]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (4C:EC) [12:23:36:718]: SOFTWARE RESTRICTION POLICY: d:\857d69c78de19fc05980be8d2cc8\HotFixSqlSupport\Files\SqlSupport.msp is not digitally signed
MSI (s) (4C:EC) [12:23:36:718]: SOFTWARE RESTRICTION POLICY: d:\857d69c78de19fc05980be8d2cc8\HotFixSqlSupport\Files\SqlSupport.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (4C:EC) [12:23:36:718]: SequencePatches starts. Product code: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}, Product version: 9.00.2047.00, Upgrade code: {3A91FA19-A197-467C-850F-0AFE90899371}, Product language 1033
MSI (s) (4C:EC) [12:23:36:718]: PATCH SEQUENCER WARNING: d:\857d69c78de19fc05980be8d2cc8\HotFixSqlSupport\Files\SqlSupport.msp patch will not be sequenced because it does not contain any transform that may apply to product!
MSI (s) (4C:EC) [12:23:36:718]: SequencePatches returns success.
MSI (s) (4C:EC) [12:23:36:718]: Final Patch Application Order:
MSI (s) (4C:EC) [12:23:36:718]: Other Patches:
MSI (s) (4C:EC) [12:23:36:718]: Unknown\Absent: {EE92F683-5F5C-4970-BB0B-9AC591B60268} - d:\857d69c78de19fc05980be8d2cc8\HotFixSqlSupport\Files\SqlSupport.msp
MSI (s) (4C:EC) [12:23:36:734]: Product: Microsoft SQL Server Setup Support Files (English) - Update '{EE92F683-5F5C-4970-BB0B-9AC591B60268}' could not be installed. Error code 1642. Additional information is available in the log file C:\WINNT\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log.

MSI (s) (4C:EC) [12:23:36:734]: Note: 1: 1708
MSI (s) (4C:EC) [12:23:36:734]: Note: 1: 2729
MSI (s) (4C:EC) [12:23:36:734]: Note: 1: 2729
MSI (s) (4C:EC) [12:23:36:734]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.

MSI (s) (4C:EC) [12:23:36:734]: Attempting to delete file C:\WINNT\Installer\1f5f686.msp
MSI (s) (4C:EC) [12:23:36:750]: MainEngineThread is returning 1642
The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer an
d that you have the correct upgrade patch.
C:\WINNT\Installer\1f5f617.msi
MSI (c) (A4:58) [12:23:36:750]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (A4:58) [12:23:36:750]: MainEngineThread is returning 1642
=== Verbose logging stopped: 4/21/2006 12:23:36 ===

Yes I am sure I am installing the right patch. Just downloaded from here:

http://www.microsoft.com/downloads/details.aspx?familyid=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC&displaylang=en

At the start of setup it even shows that it can update all the installed products to SP1.

So far I have tried everything. I even completely uninstalled Visual Studio 2005 professional, along with .net 2.0, etc. Everything on the uninstall page:

http://msdn.microsoft.com/vstudio/express/support/uninstall/

So I started all over again, and once again SP1 fails to install with the same error as everyone else. :(

Any help would be great.

Thanks a lot,

Will

|||

After you get the 'dm_exec_query_resource_semaphores' error and the installer cancels out, can you try to apply SP1 a second time? Does that attempt also fail with the same message?

Thanks,
Samuel Lester (MSFT)

|||

Samuel,

I too am getting the MSP error. I did sucessfully install SP1 to SQL 2005 Express prior to my attempt to update SQL 2005 Developer Edition. I have uninstalled SQL 2005 Express and tried to apply SP1 to SQL 2005 Server DE, but get the same error.

I have logs - where would you like me to mail them?

bill burrows

|||

Samuel, the site http://lab.msdn.microsoft.com/ProductFeedback would not allow me to post this issue. So, I have included the following lines from the log file SQLSetup0012_<mycomputername>_SQL.log:

<from line 28321>

SQL_ERROR (-1) in OdbcStatement::execute_batch

sqlstate=42000, level=16, state=1, native_error=15151, msg=[Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.

sqlstate=42000, level=16, state=1, native_error=15151, msg=[Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_memory_grants', 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: Wed Oct 26 16:37:41 2005

Function Name: OdbcStatement::execute_batch@.sysdbupg.sql@.2

Source Line Number: 91

<from line 28440>

Error Code: 15151

MSI (s) (B4!8C) [16:45:40:458]: Product: Microsoft SQL Server 2005 -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. Refer to the server error logs and Setup logs for detailed error information.

Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. Refer to the server error logs and Setup logs for detailed error information.

<Failure Type='Fatal' Error='15151'>

<EndFunc Name='LaunchFunction' Return='15151' GetLastError='203'>

I hope this helps!

Glenn

|||I have attempted to run SP1 (for SQL Express) 3 times; each time with the same error. Also, I initially installed SP1 for SQL Server 2005 with no problems.

Failed install of SQL Server 2005 Developer Edition on Win XP Pro

I've tried installing SQL Server 2005 Developer Edition 3 times now, from 2 different CDs. I keep failing with the same error message: "SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation."

This is the bottom of the SQLSetup0001_<machine name>_SQL.log

Doing Action: Do_sqlMofcomp

PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:33:07 2006

<Func Name='InstallMOF'>

Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.

An error occured while processing item 1 defined on lines 16 - 18

Error occured in phase 3, Error number: 0x80041001

Compiler returned error 0x80041001

<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>

Error Code: 0x80077349 (29513)

Windows Error Text:Source File Name: sqlca\sqlmofca.cpp

Compiler Timestamp: Tue Aug9 01:14:18 2005

Function Name: Do_sqlMofcomp

Source Line Number: 608

- Context --

Setting status of unmanaged components and removing unmanaged resources

Error Code: 29513

MSI (s) (40!00) [14:40:59:034]: Product: Microsoft SQL Server 2005 -- Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.

Error 29513. SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.

<Func Name='GetCAContext'>

<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>

Doing Action: Do_sqlMofcomp

PerfTime Start: Do_sqlMofcomp : Fri Jan 27 14:40:59 2006

<Func Name='InstallMOF'>

Failed to compile file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\etwcls.mof.

An error occured while processing item 1 defined on lines 16 - 18

Error occured in phase 3, Error number: 0x80041001

Compiler returned error 0x80041001

<EndFunc Name='InstallMOF' Return='-2147217407' GetLastError='183'>

Error Code: 0x80077349 (29513)

Windows Error Text:Source File Name: sqlca\sqlmofca.cpp

Compiler Timestamp: Tue Aug9 01:14:18 2005

Function Name: Do_sqlMofcomp

Source Line Number: 608

- Context --

Setting status of unmanaged components and removing unmanaged resources

Error Code: 29513

I'm at a complete loss, but I am sure the error is something about the configuration with this computer. I have fond a couple of posts on other web sites where people have similar errors, but no feedback on the error or even ideas on what to look at.

ANY recommendations would be helpful!!

Thank you,

Jay A. Moritz

I had the same error. Turns out my WMI repository is corrupted.

Run the following in a batch file to rebuild the repository and fix the problem:

net stop winmgmt
c:
cd %systemroot%\system32\wbem
rd /S /Q repository

regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll

mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
echo DONE reboot
pause

|||

Hello, I'm having hte same issue...

How do I run in a batch?....Does this mean something is wrong with my XP....If I installed a new version of XP, would this fix the problem?

|||

This is most likely caused by a corruption in WMI in your Windows Server. Try reinstalling WMI. There's information on how to do this at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp

Thanks,
Samuel Lester (MSFT)

|||

Strange, that page looks to be down now. Here is a WMI diagnosis tool you can also try:

http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en

Thanks,
Sam Lester (MSFT)

|||

I received the same error.

Thanks !!! this was useful for me !

Emil

|||

Would like to thank you. This solution worked for me.

Thanks

|||

The WMI Diagnostic utility provided only unhelpful information. The batch file provided above fixed the WMI problem and allowed the SQL Server 2005 installation to complete under Vista.

To run the text as a batch file, just copy and paste it into notepad, save it somewhere with a .bat extension, and then run it from a command (DOS) window