Hello,
I have detected a problem with the stored procedure xp_MSADEnabled. I am using Windows 2000 (workstation, 5.00.2195, SP4) and SQLServer 2000 Developer (Product version 8.00.858 SP3). Calling xp_MSADEnabled results in an unspecified error (-2147467259).
If I call the same procedure on a Windows 2003 Server machine, it works fine.
This procedure is called in several other system procedures like sp_addmergepublication and sp_dropmergepublication.
I am developing the replication functionality of a database application. I discovered the problem when I wanted to call sp_addmergepublication from my ADO.NET application. This resulted in the SqlException "A severe error occurred on the current command.
The results, if any, should be discarded". Calling this procedure from the SQL Query Analyzer did not result in the error.
greeting, Marco
Hi
Looking at other people having problems with this xp_MSADEnabled tend to
point to service account problems such as duplicate account entries in the
AD or insufficient permissions to access it.
John
"Marco Broenink" <marco.broenink@.ict.nl> wrote in message
news:0EB1A879-F364-4646-AE5B-28C3754194AD@.microsoft.com...
> Hello,
> I have detected a problem with the stored procedure xp_MSADEnabled. I am
using Windows 2000 (workstation, 5.00.2195, SP4) and SQLServer 2000
Developer (Product version 8.00.858 SP3). Calling xp_MSADEnabled results in
an unspecified error (-2147467259).
> If I call the same procedure on a Windows 2003 Server machine, it works
fine.
> This procedure is called in several other system procedures like
sp_addmergepublication and sp_dropmergepublication.
> I am developing the replication functionality of a database application. I
discovered the problem when I wanted to call sp_addmergepublication from my
ADO.NET application. This resulted in the SqlException "A severe error
occurred on the current command. The results, if any, should be discarded".
Calling this procedure from the SQL Query Analyzer did not result in the
error.
> greeting, Marco
Showing posts with label detected. Show all posts
Showing posts with label detected. Show all posts
Wednesday, March 28, 2012
Problem report xp_MSADEnabled
Hello
I have detected a problem with the stored procedure xp_MSADEnabled. I am using Windows 2000 (workstation, 5.00.2195, SP4) and SQLServer 2000 Developer (Product version 8.00.858 SP3). Calling xp_MSADEnabled results in an unspecified error (-2147467259)
If I call the same procedure on a Windows 2003 Server machine, it works fine
This procedure is called in several other system procedures like sp_addmergepublication and sp_dropmergepublication.
I am developing the replication functionality of a database application. I discovered the problem when I wanted to call sp_addmergepublication from my ADO.NET application. This resulted in the SqlException "A severe error occurred on the current command. The results, if any, should be discarded". Calling this procedure from the SQL Query Analyzer did not result in the error
greeting, MarcoHi
Looking at other people having problems with this xp_MSADEnabled tend to
point to service account problems such as duplicate account entries in the
AD or insufficient permissions to access it.
John
"Marco Broenink" <marco.broenink@.ict.nl> wrote in message
news:0EB1A879-F364-4646-AE5B-28C3754194AD@.microsoft.com...
> Hello,
> I have detected a problem with the stored procedure xp_MSADEnabled. I am
using Windows 2000 (workstation, 5.00.2195, SP4) and SQLServer 2000
Developer (Product version 8.00.858 SP3). Calling xp_MSADEnabled results in
an unspecified error (-2147467259).
> If I call the same procedure on a Windows 2003 Server machine, it works
fine.
> This procedure is called in several other system procedures like
sp_addmergepublication and sp_dropmergepublication.
> I am developing the replication functionality of a database application. I
discovered the problem when I wanted to call sp_addmergepublication from my
ADO.NET application. This resulted in the SqlException "A severe error
occurred on the current command. The results, if any, should be discarded".
Calling this procedure from the SQL Query Analyzer did not result in the
error.
> greeting, Marcosql
I have detected a problem with the stored procedure xp_MSADEnabled. I am using Windows 2000 (workstation, 5.00.2195, SP4) and SQLServer 2000 Developer (Product version 8.00.858 SP3). Calling xp_MSADEnabled results in an unspecified error (-2147467259)
If I call the same procedure on a Windows 2003 Server machine, it works fine
This procedure is called in several other system procedures like sp_addmergepublication and sp_dropmergepublication.
I am developing the replication functionality of a database application. I discovered the problem when I wanted to call sp_addmergepublication from my ADO.NET application. This resulted in the SqlException "A severe error occurred on the current command. The results, if any, should be discarded". Calling this procedure from the SQL Query Analyzer did not result in the error
greeting, MarcoHi
Looking at other people having problems with this xp_MSADEnabled tend to
point to service account problems such as duplicate account entries in the
AD or insufficient permissions to access it.
John
"Marco Broenink" <marco.broenink@.ict.nl> wrote in message
news:0EB1A879-F364-4646-AE5B-28C3754194AD@.microsoft.com...
> Hello,
> I have detected a problem with the stored procedure xp_MSADEnabled. I am
using Windows 2000 (workstation, 5.00.2195, SP4) and SQLServer 2000
Developer (Product version 8.00.858 SP3). Calling xp_MSADEnabled results in
an unspecified error (-2147467259).
> If I call the same procedure on a Windows 2003 Server machine, it works
fine.
> This procedure is called in several other system procedures like
sp_addmergepublication and sp_dropmergepublication.
> I am developing the replication functionality of a database application. I
discovered the problem when I wanted to call sp_addmergepublication from my
ADO.NET application. This resulted in the SqlException "A severe error
occurred on the current command. The results, if any, should be discarded".
Calling this procedure from the SQL Query Analyzer did not result in the
error.
> greeting, Marcosql
Problem report xp_MSADEnabled
Hello,
I have detected a problem with the stored procedure xp_MSADEnabled. I am using Windows 2000 (workstation, 5.00.2195, SP4) and SQLServer 2000 Developer (Product version 8.00.858 SP3). Calling xp_MSADEnabled results in an unspecified error (-2147467259).
If I call the same procedure on a Windows 2003 Server machine, it works fine.
This procedure is called in several other system procedures like sp_addmergepublication and sp_dropmergepublication.
I am developing the replication functionality of a database application. I discovered the problem when I wanted to call sp_addmergepublication from my ADO.NET application. This resulted in the SqlException "A severe error occurred on the current command.
The results, if any, should be discarded". Calling this procedure from the SQL Query Analyzer did not result in the error.
greeting, Marco
This procedure test to see if the particular SQL Server is Active Directory enabled.
In your code are you publishing your publication to Active Directory? IE in the proc sp_addpublication are you setting
@.add_to_active_directory to true?
Do you need this functionality?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||Thanks for reply.
I don't need active directory functionality. I set the @.add_to_active_directory to false but the sp_addmergepublication still calls xp_MSADEnabled.
-- Hilary Cotter wrote: --
This procedure test to see if the particular SQL Server is Active Directory enabled.
In your code are you publishing your publication to Active Directory? IE in the proc sp_addpublication are you setting
@.add_to_active_directory to true?
Do you need this functionality?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||Hi
Looking at other people having problems with this xp_MSADEnabled tend to
point to service account problems such as duplicate account entries in the
AD or insufficient permissions to access it.
John
"Marco Broenink" <marco.broenink@.ict.nl> wrote in message
news:0EB1A879-F364-4646-AE5B-28C3754194AD@.microsoft.com...
> Hello,
> I have detected a problem with the stored procedure xp_MSADEnabled. I am
using Windows 2000 (workstation, 5.00.2195, SP4) and SQLServer 2000
Developer (Product version 8.00.858 SP3). Calling xp_MSADEnabled results in
an unspecified error (-2147467259).
> If I call the same procedure on a Windows 2003 Server machine, it works
fine.
> This procedure is called in several other system procedures like
sp_addmergepublication and sp_dropmergepublication.
> I am developing the replication functionality of a database application. I
discovered the problem when I wanted to call sp_addmergepublication from my
ADO.NET application. This resulted in the SqlException "A severe error
occurred on the current command. The results, if any, should be discarded".
Calling this procedure from the SQL Query Analyzer did not result in the
error.
> greeting, Marco
I have detected a problem with the stored procedure xp_MSADEnabled. I am using Windows 2000 (workstation, 5.00.2195, SP4) and SQLServer 2000 Developer (Product version 8.00.858 SP3). Calling xp_MSADEnabled results in an unspecified error (-2147467259).
If I call the same procedure on a Windows 2003 Server machine, it works fine.
This procedure is called in several other system procedures like sp_addmergepublication and sp_dropmergepublication.
I am developing the replication functionality of a database application. I discovered the problem when I wanted to call sp_addmergepublication from my ADO.NET application. This resulted in the SqlException "A severe error occurred on the current command.
The results, if any, should be discarded". Calling this procedure from the SQL Query Analyzer did not result in the error.
greeting, Marco
This procedure test to see if the particular SQL Server is Active Directory enabled.
In your code are you publishing your publication to Active Directory? IE in the proc sp_addpublication are you setting
@.add_to_active_directory to true?
Do you need this functionality?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||Thanks for reply.
I don't need active directory functionality. I set the @.add_to_active_directory to false but the sp_addmergepublication still calls xp_MSADEnabled.
-- Hilary Cotter wrote: --
This procedure test to see if the particular SQL Server is Active Directory enabled.
In your code are you publishing your publication to Active Directory? IE in the proc sp_addpublication are you setting
@.add_to_active_directory to true?
Do you need this functionality?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||Hi
Looking at other people having problems with this xp_MSADEnabled tend to
point to service account problems such as duplicate account entries in the
AD or insufficient permissions to access it.
John
"Marco Broenink" <marco.broenink@.ict.nl> wrote in message
news:0EB1A879-F364-4646-AE5B-28C3754194AD@.microsoft.com...
> Hello,
> I have detected a problem with the stored procedure xp_MSADEnabled. I am
using Windows 2000 (workstation, 5.00.2195, SP4) and SQLServer 2000
Developer (Product version 8.00.858 SP3). Calling xp_MSADEnabled results in
an unspecified error (-2147467259).
> If I call the same procedure on a Windows 2003 Server machine, it works
fine.
> This procedure is called in several other system procedures like
sp_addmergepublication and sp_dropmergepublication.
> I am developing the replication functionality of a database application. I
discovered the problem when I wanted to call sp_addmergepublication from my
ADO.NET application. This resulted in the SqlException "A severe error
occurred on the current command. The results, if any, should be discarded".
Calling this procedure from the SQL Query Analyzer did not result in the
error.
> greeting, Marco
Friday, March 9, 2012
Problem joining 2 Views
Hi guys,
I detected a strange behaviour when doing an inner join of two views.
There is table_Objects, table_Contracts and view_Objects, View_Contracts.
Table_Objects: ID, Price
View_Objects: Select * from Table_Objects Where Price > 10
Table_Contracts: ID, Year
View_Contracts: Select c.ID, c.Year
From Table_Contracts c Join View_Objects o on c.id=o.id
Quiete simple so far, but it doesn't work. Imagine Object with id 3 that is shown in View_Objects and Table_Contracts but not shown in View_Contracts. How is that possible?
EDIT: Sometimes its shown, sometimes not
Thx for your reply!Is Table_Contracts.ID a primary key or a foreign key to Table_Objects?|||Table_Contract's PK is (ID,Year)
Table_Object's PK is (ID)
There is a FK from Table_Contract(ID) to Table_Objects(ID)|||Oh, just realized that I'm joining a view and a table and not 2 views.
I detected a strange behaviour when doing an inner join of two views.
There is table_Objects, table_Contracts and view_Objects, View_Contracts.
Table_Objects: ID, Price
View_Objects: Select * from Table_Objects Where Price > 10
Table_Contracts: ID, Year
View_Contracts: Select c.ID, c.Year
From Table_Contracts c Join View_Objects o on c.id=o.id
Quiete simple so far, but it doesn't work. Imagine Object with id 3 that is shown in View_Objects and Table_Contracts but not shown in View_Contracts. How is that possible?
EDIT: Sometimes its shown, sometimes not
Thx for your reply!Is Table_Contracts.ID a primary key or a foreign key to Table_Objects?|||Table_Contract's PK is (ID,Year)
Table_Object's PK is (ID)
There is a FK from Table_Contract(ID) to Table_Objects(ID)|||Oh, just realized that I'm joining a view and a table and not 2 views.
Wednesday, March 7, 2012
Problem installing SQL Express
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and the run SQL Server 2005 Setup again.
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to remove all beta versions of VB, SQL, .NET and etc. Nothing is listed. I do have VB6 PRO. I have looked for directories and removed all. I have searched for SQLexpress in the registry and eliminated all I could find. I reinstalled .Net 2.0 and I'm still finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032
turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to remove all beta versions of VB, SQL, .NET and etc. Nothing is listed. I do have VB6 PRO. I have looked for directories and removed all. I have searched for SQLexpress in the registry and eliminated all I could find. I reinstalled .Net 2.0 and I'm still finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032
Thank you for your assistance.
Hi Gary,
If you can't find the product listed in the Add/Remove Program listing (they would be listed under Microsoft SQL Server 2005), then you can try manually removing the offending products using the Product ID. The two problem commonents are identified as
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
You can manually remove them by typing the following into the Run dialog:
msiexec /x <product id>
Where <product id> is the GUID referenced from your log file.
Regards,
Mike Wachal
SQL Express team
-
Mark the best posts as Answers!
I am having a similar problem.
Microsoft SQL Server 2005 Setup beginning at Thu Aug 10 14:33:57 2006
Process ID : 1604
d:\51b5dbc1449baa0bbd43\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/7/10 14:33:57
Complete: LoadResourcesAction at: 2006/7/10 14:33:57, returned true
Running: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57
Loaded DLL:d:\51b5dbc1449baa0bbd43\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57, returned true
Running: ValidateWinNTAction at: 2006/7/10 14:33:57
Complete: ValidateWinNTAction at: 2006/7/10 14:33:57, returned true
Running: ValidateMinOSAction at: 2006/7/10 14:33:57
Complete: ValidateMinOSAction at: 2006/7/10 14:33:57, returned true
Running: PerformSCCAction at: 2006/7/10 14:33:57
Complete: PerformSCCAction at: 2006/7/10 14:33:57, returned true
Running: ActivateLoggingAction at: 2006/7/10 14:33:57
Complete: ActivateLoggingAction at: 2006/7/10 14:33:57, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1604" returned false.
Running: PerformSCCAction2 at: 2006/7/10 14:33:58
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
there are no items in add/remove programs.
when i attempt to run
msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD
i recieve an error message
"this instilation package could not be opened. verify
that the package exists and that you can access it, or
contact the application vendoe to verify that this is a
valid windows installer package"
any one help me?
thanks
Drance
|||lost my post can not be bothered to re type it 
Me too.
We had the CTP version installed. Now it finds various CTP "Products" even though I removed the CTP versions using Add-Remove Programs.
Of course, if these things were vital to my operation, the slightest breeze would erase them forever.
Good Luck,
Mike
|||Drance wrote:
I am having a similar problem.
...
Class not registered.
there are no items in add/remove programs.
when i attempt to run
msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD
i recieve an error message
"any one help me?
thanks
Drance
Try:
msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"
|||I have a problem that when I try to uninstall the offending package I get this Error Message:
The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The Error is
:Failed to read property "InstallIds" {"MachineConfiguration".""."SAM"} from Cache
Unable to write poperty into cache: IsClustered
Unable to write poperty into cache: "IsClustered"
XmlRWError: failure loading xmlrw.dll
CheckAllProcedures() returned: 2
|||omg!!! this issue has been such a pain since im planning to use sql server express to advance my DB and programming skills (from access+vba to sql+c++,#).turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb
Problem Installing SQl express
hi, Im trying to install SQL express 2005 on my Desktop Computer and I keep running into the error "Setup has detected a problem with Microsoft .Net Framework installation and cannot proceed .Net Framework 2.0 is either not installed on this system or is corrupt"
when infact it is installed.. any sugestions?
when infact it is installed.. any sugestions?
By the way im Running Windows X64 Pro with a AMD athlon X2 3800+ CPU and 2GB of Corsair DDr2 ram
I would try removing and then re-installing .NET Framework 2.0, the error would seem to suggest that there is a problem with your installation. I would assume that the .NET Framework 2.0 installer would tell you if you tried to install the 32-bit version on your x64 computer, but just the same, make sure you're installing the right bit level version of the framework. 
Mike
|||Thanks for oyur Reply mike, I have solved the problem :] It turns out i was using the Beta 2 build of the .net framework.. after Some searching i found the Final build of the framework and the installation succeded|||That would do it.
Mike
Problem installing SQL Express
SQL Server 2005 Setup has detected incompatible components from beta
turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb
versions of Visual Studio, .NET Framework, or SQL Server 2005.
Use Add or Remove Programs to remove these components, and the run SQL
Server 2005 Setup again.
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07
is not compatible with current builds of SQL Server.Expected at least
version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to
remove all beta versions of VB, SQL, .NET and etc. Nothing is
listed. I do have VB6 PRO. I have looked for directories
and removed all. I have searched for SQLexpress in the registry
and eliminated all I could find. I reinstalled .Net 2.0 and I'm still
finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07
is not compatible with current builds of SQL Server.Expected at least
version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07
is not compatible with current builds of SQL Server.Expected at least
version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible
components from beta versions of Visual Studio, .NET Framework, or SQL
Server 2005. Use Add or Remove Programs to remove these components, and
then run SQL Server 2005 Setup again. For detailed instructions on
uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032
Thank you for your assistance.
Hi Gary,
If you can't find the product listed in the Add/Remove Program listing (they would be listed under Microsoft SQL Server 2005), then you can try manually removing the offending products using the Product ID. The two problem commonents are identified as
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
You can manually remove them by typing the following into the Run dialog:
msiexec /x <product id>
Where <product id> is the GUID referenced from your log file.
Regards,
Mike Wachal
SQL Express team
-
Mark the best posts as Answers!
I am having a similar problem.
Microsoft SQL Server 2005 Setup beginning at Thu Aug 10 14:33:57 2006
Process ID : 1604
d:\51b5dbc1449baa0bbd43\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/7/10 14:33:57
Complete: LoadResourcesAction at: 2006/7/10 14:33:57, returned true
Running: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57
Loaded DLL:d:\51b5dbc1449baa0bbd43\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57, returned true
Running: ValidateWinNTAction at: 2006/7/10 14:33:57
Complete: ValidateWinNTAction at: 2006/7/10 14:33:57, returned true
Running: ValidateMinOSAction at: 2006/7/10 14:33:57
Complete: ValidateMinOSAction at: 2006/7/10 14:33:57, returned true
Running: PerformSCCAction at: 2006/7/10 14:33:57
Complete: PerformSCCAction at: 2006/7/10 14:33:57, returned true
Running: ActivateLoggingAction at: 2006/7/10 14:33:57
Complete: ActivateLoggingAction at: 2006/7/10 14:33:57, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1604" returned false.
Running: PerformSCCAction2 at: 2006/7/10 14:33:58
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
there are no items in add/remove programs.
when i attempt to run
msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD
i recieve an error message
"this instilation package could not be opened. verify
that the package exists and that you can access it, or
contact the application vendoe to verify that this is a
valid windows installer package"
any one help me?
thanks
Drance
|||lost my post can not be bothered to re type it
Me too.
We had the CTP version installed. Now it finds various CTP "Products" even though I removed the CTP versions using Add-Remove Programs.
Of course, if these things were vital to my operation, the slightest breeze would erase them forever.
Good Luck,
Mike
|||Drance wrote:
I am having a similar problem.
...
Class not registered.
there are no items in add/remove programs.
when i attempt to run
msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD
i recieve an error message
"any one help me?
thanks
Drance
Try:
msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"
|||I have a problem that when I try to uninstall the offending package I get this Error Message:
The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The Error is
:Failed to read property "InstallIds" {"MachineConfiguration".""."SAM"} from Cache
Unable to write poperty into cache: IsClustered
Unable to write poperty into cache: "IsClustered"
XmlRWError: failure loading xmlrw.dll
CheckAllProcedures() returned: 2
|||omg!!! this issue has been such a pain since im planning to use sql server express to advance my DB and programming skills (from access+vba to sql+c++,#).turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb
Problem installing SQL Express
SQL Server 2005 Setup has detected incompatible components from beta
turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb
versions of Visual Studio, .NET Framework, or SQL Server 2005.
Use Add or Remove Programs to remove these components, and the run SQL
Server 2005 Setup again.
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07
is not compatible with current builds of SQL Server.Expected at least
version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to
remove all beta versions of VB, SQL, .NET and etc. Nothing is
listed. I do have VB6 PRO. I have looked for directories
and removed all. I have searched for SQLexpress in the registry
and eliminated all I could find. I reinstalled .Net 2.0 and I'm still
finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07
is not compatible with current builds of SQL Server.Expected at least
version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07
is not compatible with current builds of SQL Server.Expected at least
version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible
components from beta versions of Visual Studio, .NET Framework, or SQL
Server 2005. Use Add or Remove Programs to remove these components, and
then run SQL Server 2005 Setup again. For detailed instructions on
uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032
Thank you for your assistance.
Hi Gary,
If you can't find the product listed in the Add/Remove Program listing (they would be listed under Microsoft SQL Server 2005), then you can try manually removing the offending products using the Product ID. The two problem commonents are identified as
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
You can manually remove them by typing the following into the Run dialog:
msiexec /x <product id>
Where <product id> is the GUID referenced from your log file.
Regards,
Mike Wachal
SQL Express team
-
Mark the best posts as Answers!
I am having a similar problem.
Microsoft SQL Server 2005 Setup beginning at Thu Aug 10 14:33:57 2006
Process ID : 1604
d:\51b5dbc1449baa0bbd43\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/7/10 14:33:57
Complete: LoadResourcesAction at: 2006/7/10 14:33:57, returned true
Running: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57
Loaded DLL:d:\51b5dbc1449baa0bbd43\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57, returned true
Running: ValidateWinNTAction at: 2006/7/10 14:33:57
Complete: ValidateWinNTAction at: 2006/7/10 14:33:57, returned true
Running: ValidateMinOSAction at: 2006/7/10 14:33:57
Complete: ValidateMinOSAction at: 2006/7/10 14:33:57, returned true
Running: PerformSCCAction at: 2006/7/10 14:33:57
Complete: PerformSCCAction at: 2006/7/10 14:33:57, returned true
Running: ActivateLoggingAction at: 2006/7/10 14:33:57
Complete: ActivateLoggingAction at: 2006/7/10 14:33:57, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1604" returned false.
Running: PerformSCCAction2 at: 2006/7/10 14:33:58
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
there are no items in add/remove programs.
when i attempt to run
msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD
i recieve an error message
"this instilation package could not be opened. verify
that the package exists and that you can access it, or
contact the application vendoe to verify that this is a
valid windows installer package"
any one help me?
thanks
Drance
|||lost my post can not be bothered to re type it
Me too.
We had the CTP version installed. Now it finds various CTP "Products" even though I removed the CTP versions using Add-Remove Programs.
Of course, if these things were vital to my operation, the slightest breeze would erase them forever.
Good Luck,
Mike
|||I am having a similar problem.
...
Class not registered.
there are no items in add/remove programs.
when i attempt to run
msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD
i recieve an error message
"any one help me?
thanks
Drance
Try:
msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"
|||I have a problem that when I try to uninstall the offending package I get this Error Message:
The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The Error is
:Failed to read property "InstallIds" {"MachineConfiguration".""."SAM"} from Cache
Unable to write poperty into cache: IsClustered
Unable to write poperty into cache: "IsClustered"
XmlRWError: failure loading xmlrw.dll
CheckAllProcedures() returned: 2
|||omg!!! this issue has been such a pain since im planning to use sql server express to advance my DB and programming skills (from access+vba to sql+c++,#).turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb
Problem installing SQL Express
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and the run SQL Server 2005 Setup again.
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to remove all beta versions of VB, SQL, .NET and etc. Nothing is listed. I do have VB6 PRO. I have looked for directories and removed all. I have searched for SQLexpress in the registry and eliminated all I could find. I reinstalled .Net 2.0 and I'm still finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032
turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to remove all beta versions of VB, SQL, .NET and etc. Nothing is listed. I do have VB6 PRO. I have looked for directories and removed all. I have searched for SQLexpress in the registry and eliminated all I could find. I reinstalled .Net 2.0 and I'm still finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032
Thank you for your assistance.
Hi Gary,
If you can't find the product listed in the Add/Remove Program listing (they would be listed under Microsoft SQL Server 2005), then you can try manually removing the offending products using the Product ID. The two problem commonents are identified as
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
You can manually remove them by typing the following into the Run dialog:
msiexec /x <product id>
Where <product id> is the GUID referenced from your log file.
Regards,
Mike Wachal
SQL Express team
-
Mark the best posts as Answers!
I am having a similar problem.
Microsoft SQL Server 2005 Setup beginning at Thu Aug 10 14:33:57 2006
Process ID : 1604
d:\51b5dbc1449baa0bbd43\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/7/10 14:33:57
Complete: LoadResourcesAction at: 2006/7/10 14:33:57, returned true
Running: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57
Loaded DLL:d:\51b5dbc1449baa0bbd43\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57, returned true
Running: ValidateWinNTAction at: 2006/7/10 14:33:57
Complete: ValidateWinNTAction at: 2006/7/10 14:33:57, returned true
Running: ValidateMinOSAction at: 2006/7/10 14:33:57
Complete: ValidateMinOSAction at: 2006/7/10 14:33:57, returned true
Running: PerformSCCAction at: 2006/7/10 14:33:57
Complete: PerformSCCAction at: 2006/7/10 14:33:57, returned true
Running: ActivateLoggingAction at: 2006/7/10 14:33:57
Complete: ActivateLoggingAction at: 2006/7/10 14:33:57, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1604" returned false.
Running: PerformSCCAction2 at: 2006/7/10 14:33:58
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
there are no items in add/remove programs.
when i attempt to run
msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD
i recieve an error message
"this instilation package could not be opened. verify
that the package exists and that you can access it, or
contact the application vendoe to verify that this is a
valid windows installer package"
any one help me?
thanks
Drance
|||lost my post can not be bothered to re type it
Me too.
We had the CTP version installed. Now it finds various CTP "Products" even though I removed the CTP versions using Add-Remove Programs.
Of course, if these things were vital to my operation, the slightest breeze would erase them forever.
Good Luck,
Mike
|||I am having a similar problem.
...
Class not registered.
there are no items in add/remove programs.
when i attempt to run
msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD
i recieve an error message
"any one help me?
thanks
Drance
Try:
msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"
|||I have a problem that when I try to uninstall the offending package I get this Error Message:
The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The Error is
:Failed to read property "InstallIds" {"MachineConfiguration".""."SAM"} from Cache
Unable to write poperty into cache: IsClustered
Unable to write poperty into cache: "IsClustered"
XmlRWError: failure loading xmlrw.dll
CheckAllProcedures() returned: 2
|||omg!!! this issue has been such a pain since im planning to use sql server express to advance my DB and programming skills (from access+vba to sql+c++,#).turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb
Problem installing SQL Express
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and the run SQL Server 2005 Setup again.
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to remove all beta versions of VB, SQL, .NET and etc. Nothing is listed. I do have VB6 PRO. I have looked for directories and removed all. I have searched for SQLexpress in the registry and eliminated all I could find. I reinstalled .Net 2.0 and I'm still finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032
turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
I used Add/Remove Progs and used the list in the order suggested to remove all beta versions of VB, SQL, .NET and etc. Nothing is listed. I do have VB6 PRO. I have looked for directories and removed all. I have searched for SQLexpress in the registry and eliminated all I could find. I reinstalled .Net 2.0 and I'm still finding this problem.
Microsoft SQL Server 2005 Setup beginning at Thu Jun 08 17:37:43 2006
Process ID : 164
c:\90b92fd6a1de42b9ee\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/8 17:37:43
Complete: LoadResourcesAction at: 2006/5/8 17:37:43, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43
Loaded DLL:c:\90b92fd6a1de42b9ee\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/8 17:37:43, returned true
Running: ValidateWinNTAction at: 2006/5/8 17:37:43
Complete: ValidateWinNTAction at: 2006/5/8 17:37:43, returned true
Running: ValidateMinOSAction at: 2006/5/8 17:37:43
Complete: ValidateMinOSAction at: 2006/5/8 17:37:43, returned true
Running: PerformSCCAction at: 2006/5/8 17:37:43
Complete: PerformSCCAction at: 2006/5/8 17:37:43, returned true
Running: ActivateLoggingAction at: 2006/5/8 17:37:43
Complete: ActivateLoggingAction at: 2006/5/8 17:37:43, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__164" returned false.
Running: PerformSCCAction2 at: 2006/5/8 17:37:43
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.
Message pump returning: 70032
Thank you for your assistance.
Hi Gary,
If you can't find the product listed in the Add/Remove Program listing (they would be listed under Microsoft SQL Server 2005), then you can try manually removing the offending products using the Product ID. The two problem commonents are identified as
Product "{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Express Edition CTP (SQLEXPRESS)"
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1187.07 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
You can manually remove them by typing the following into the Run dialog:
msiexec /x <product id>
Where <product id> is the GUID referenced from your log file.
Regards,
Mike Wachal
SQL Express team
-
Mark the best posts as Answers!
I am having a similar problem.
Microsoft SQL Server 2005 Setup beginning at Thu Aug 10 14:33:57 2006
Process ID : 1604
d:\51b5dbc1449baa0bbd43\setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/7/10 14:33:57
Complete: LoadResourcesAction at: 2006/7/10 14:33:57, returned true
Running: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57
Loaded DLL:d:\51b5dbc1449baa0bbd43\xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/7/10 14:33:57, returned true
Running: ValidateWinNTAction at: 2006/7/10 14:33:57
Complete: ValidateWinNTAction at: 2006/7/10 14:33:57, returned true
Running: ValidateMinOSAction at: 2006/7/10 14:33:57
Complete: ValidateMinOSAction at: 2006/7/10 14:33:57, returned true
Running: PerformSCCAction at: 2006/7/10 14:33:57
Complete: PerformSCCAction at: 2006/7/10 14:33:57, returned true
Running: ActivateLoggingAction at: 2006/7/10 14:33:57
Complete: ActivateLoggingAction at: 2006/7/10 14:33:57, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1604" returned false.
Running: PerformSCCAction2 at: 2006/7/10 14:33:58
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.1116 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00
The Product Name is "Microsoft SQL Server 2005 Tools Express Edition CTP"
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Error: Action "PerformSCCAction2" threw an exception during execution.
Return Code: 70032
Message displayed to user
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
Class not registered.
there are no items in add/remove programs.
when i attempt to run
msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD
i recieve an error message
"this instilation package could not be opened. verify
that the package exists and that you can access it, or
contact the application vendoe to verify that this is a
valid windows installer package"
any one help me?
thanks
Drance
|||lost my post can not be bothered to re type it
Me too.
We had the CTP version installed. Now it finds various CTP "Products" even though I removed the CTP versions using Add-Remove Programs.
Of course, if these things were vital to my operation, the slightest breeze would erase them forever.
Good Luck,
Mike
|||I am having a similar problem.
...
Class not registered.
there are no items in add/remove programs.
when i attempt to run
msiexec /x 2750B389-A2D2-4953-99CA-27C1F2A8E6FD
i recieve an error message
"any one help me?
thanks
Drance
Try:
msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}"
|||I have a problem that when I try to uninstall the offending package I get this Error Message:
The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The Error is
:Failed to read property "InstallIds" {"MachineConfiguration".""."SAM"} from Cache
Unable to write poperty into cache: IsClustered
Unable to write poperty into cache: "IsClustered"
XmlRWError: failure loading xmlrw.dll
CheckAllProcedures() returned: 2
|||omg!!! this issue has been such a pain since im planning to use sql server express to advance my DB and programming skills (from access+vba to sql+c++,#).turns out that I had a beta version of sql server (ctp-community technology preview) that couldn't be taken out using the above instructions. that doesnt really bother me - what does is the fact that the add/remove program doesn't "see" the ctp version. I had to install the Windows Installer Cleanup Utility. 'Lo and Behold the CTP version pops up on the item list - i select -I remove - et voila! it's gone. I was able to run the sql express install without a hitch. I hope that helps some folks out there. My gripe is with Microsoft really - but being a newb im hoping someone can straighten me out: why can't I see the sql ctp version in the add/remove utility? why do I have to install yet another add/remove utility to see it? why doesn't Microsoft incoporate or update the add/remove utility? don't be mean =) like I said - im a newb
Saturday, February 25, 2012
Problem installing SP4
Hi, when attempting to apply SP4 to a SQL cluster, we are getting the
following message.
Buffer Overrun detected!
A buffer overrun has been detected which has corrupted the programs internal
state. The program cannot safely continue execution and must now be
terminated.
This happens just after entering the account required to update both cluster
notes. The account is a domain admin account.
Any help greatly appreciated.
BB
Hello Bruce,
Verify that there are no dependencies other than those created by the SQL Server setup on any SQL Server cluster resources. Resources such as file shares, FTP servers, and Microsoft Internet Information
Services (IIS) servers must always have a unique network name and an IP address resource. You must remove any such non-default dependencies before you install SQL Server 2000 SP4. No dependencies other
than those supplied by the SQL Server setup must be used, except to validate whether SQL Server is online and available for the client application.
For example, if you have MSDTC resource in the SQL group and if MSDTC is dependent on SQL Server Network Name and SQL IP Address then you may have this issue. If this is the case then you will need to
remove the dependencies and then re-run the setup.
Also, make sure that you have followed the SP4 pre-installation checklist (see link below).
If you still have the same problem, then the next step will be to review the logs. I would start with the sqlsp.log (created on the node where you ran the SP4 setup). You can also cut and paste the log for us to review.
Recommended Reading
======================
SQL Server 2000 Service Pack 3, Service Pack 3a, or Service Pack 4 pre-installation checklist for SQL Server 2000 virtual server for failover clustering
http://support.microsoft.com/?kbid=811168
Clustered SQL Server do's, don'ts, and basic warnings
http://support.microsoft.com/default...B;EN-US;254321
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Hi,
I checked the dependencies. It doesn't look like anything is dependent on
SQL Server other than SQLAgent which I believe is correct. The only thing
that I think is weird in this setup is that MSDTC is in the cluster quorum
resource group...
Anyway, here is the content of sqlsp.log.
21:41:52 Begin Setup
21:41:52 Version on Media: 8.00.2039
21:41:52 Mode = Normal
21:41:52 ModeType = NORMAL
21:41:52 Loading library - sqlsut.dll (#L1)
21:41:52 Begin: SetupInitialize()
21:41:52 End: SetupInitialize()
21:41:52 Begin: CheckFixedRequirements()
21:41:52 Platform ID: 0xf00000
21:41:52 Version: 5.2.3790
21:41:52 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.327
21:41:52 End: CheckFixedRequirements()
21:41:53 Processor Architecture: x86 (Pentium)
21:41:53 ComputerName: OMF-DBCLUSTER-A
21:41:53 User Name: datacom
21:41:53 IsAllAccessAllowed returned: 1
21:41:53 OS Language: 0x409
21:41:53 Begin: SetupInstall()
21:41:53 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
21:41:53 CommonFilesDir=C:\Program Files\Common Files
21:41:53 Windows Directory=C:\WINDOWS\
21:41:53 Program Files=C:\Program Files\
21:41:53 TEMPDIR=C:\DOCUME~1\datacom\LOCALS~1\Temp\1\
21:41:53 End: SetupInstall()
21:41:53 Begin: ShowDialogs()
21:41:53 Initial Dialog Mask: 0x8300037, Disable Back=0x1
21:41:53 Begin Action ShowDialogsHlpr: 0x1
21:41:53 Begin Action: DialogShowSdWelcome
21:41:56 End Action DialogShowSdWelcome
21:41:56 Dialog 0x1 returned: 1
21:41:56 End Action ShowDialogsHlpr
21:41:56 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
21:41:56 Begin Action ShowDialogsHlpr: 0x2
21:41:56 Begin Action: DialogShowSdMachineName
21:42:02 ShowDlgMachine returned: 1
21:42:02 Name = OMF-DBCLUSTER, Type = 0x20000008
21:42:02 End Action DialogShowSdMachineName
21:42:02 begin ShowDialogsUpdateMask
21:42:02 nFullMask = 0x8300037, nCurrent = 0x2, nDirection = 1
21:42:02 Updated Dialog Mask: 0xb73c037, Disable Back = 0x1
21:42:02 Dialog 0x2 returned: 1
21:42:02 End Action ShowDialogsHlpr
21:42:02 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
21:42:02 Begin Action ShowDialogsHlpr: 0x4
21:42:02 Begin Action: DialogShowSdInstallMode
21:42:02 ShowDlgInstallMode returned: 1
21:42:02 InstallMode : 0x2
21:42:02 End Action DialogShowSdInstallMode
21:42:02 begin ShowDialogsUpdateMask
21:42:02 nFullMask = 0xb73c037, nCurrent = 0x4, nDirection = 1
21:42:02 Updated Dialog Mask: 0xb034607, Disable Back = 0x1
21:42:02 Dialog 0x4 returned: 1
21:42:02 End Action ShowDialogsHlpr
21:42:02 ShowDialogsGetDialog returned: nCurrent=0x200,index=9
21:42:02 Begin Action ShowDialogsHlpr: 0x200
21:42:02 Begin Action: DialogShowSdInstanceName
21:42:02 Begin Action: ShowDlgInstanceName
21:42:02 SKU is : Enterprise Edition
21:42:02 End Action: ShowDlgInstanceName
21:42:02 ShowDlgInstanceName returned : 0
21:42:02 InstanceName : MSSQLSERVER
21:42:02 End Action DialogShowSdInstanceName
21:42:02 begin ShowDialogsUpdateMask
21:42:02 nFullMask = 0xb034607, nCurrent = 0x200, nDirection = 0
21:42:02 Updated Dialog Mask: 0xb034603, Disable Back = 0x1
21:42:02 Dialog 0x200 returned: 0
21:42:02 End Action ShowDialogsHlpr
21:42:02 ShowDialogsGetDialog returned: nCurrent=0x400,index=10
21:42:02 Begin Action ShowDialogsHlpr: 0x400
21:42:02 Begin Action: DialogShowSdMaintain
21:42:02 ShowDlgMaintainInstall returned : 1
21:42:02 Type : 0xc
21:42:02 CreateSetupTopology(OMF-DBCLUSTER-A), Handle : 0x12648e0, returned
: 0
21:42:02 CreateSetupTopology returned : 0, Handle : 0x12648e0
21:42:02 Topology Type : 1, Return Value : 0
21:42:02 ST_GetPhysicalNode returned : 0, PNHandle : 0x1264928
21:42:02 PN_EnumerateEx returned : 0
21:42:02 PN_GetSQLStates returned : 0, SqlStates : 0x88008221
21:42:02 PN_GetInstance for MSSQLSERVER [0x1264928] returned : 0
21:42:02 SQLI_GetPackageId [0x1264ec0] returned : 0, PackageId = 0x3
21:42:02 SQLI_GetVersion [0x1264ec0] returned : 0, Version = 8.00.194
21:42:02 SQLI_GetSQLStates for MSSQLSERVER [0x1264ec0] returned : 0,
SQLStates: 0x400209
21:42:02 SQLI_GetInstallPath [0x1264ec0] returned : 0, Path = C:\Program
Files\Microsoft SQL Server\MSSQL
21:42:02 SQLI_GetDataPath [0x1264ec0] returned : 0, DataPath = F:\Program
Files\Microsoft SQL Server\MSSQL
21:42:02 SQLI_GetVersion [0x1264ec0] returned : 0, Version = 8.00.194
21:42:02 SQLI_GetRegKeyRoot [0x1264ec0] returned : 0, RegKeyRoot =
Software\Microsoft\MSSQLServer
21:42:02 SQLI_GetPackageName [0x1264ec0] returned : 0, szPackage =
Enterprise Edition
21:42:02 SQLI_GetPackageId [0x1264ec0] returned : 0, PackageId = 0x3
21:42:02 Previous Install Path: C:\Program Files\Microsoft SQL Server\MSSQL
21:42:02 Previous Install Data: F:\Program Files\Microsoft SQL Server\MSSQL
21:42:02 Previous Install Version: 8.00.194
21:42:02 ReleaseSetupTopology
21:42:02 End Action DialogShowSdMaintain
21:42:02 begin ShowDialogsUpdateMask
21:42:02 nFullMask = 0xb034603, nCurrent = 0x400, nDirection = 1
21:42:02 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1
21:42:02 Dialog 0x400 returned: 1
21:42:02 End Action ShowDialogsHlpr
21:42:02 ShowDialogsGetDialog returned: nCurrent=0x2000,index=13
21:42:02 Begin Action ShowDialogsHlpr: 0x2000
21:42:02 Begin Action: DialogShowSdUpgrade
21:42:02 ShowDlgUpgrade returned : 1
21:42:02 Checking databases on instance 'MSSQLSERVER'
21:42:02 Begin Action: Check for VS Node
21:42:02 Begin Action: Check for VS Node
21:42:02 Begin Action: Cluster Resources Offline
21:42:06 End Action: Cluster Resources Offline
21:42:06 Authenticate access
21:42:06 Begin SDPassword Dialog
21:42:09 End SDPassword Dialog
21:42:09 C:\DOCUME~1\datacom\LOCALS~1\Temp\1\SqlSetup\Bin\s cm.exe -Silent 1
-Action 6 -Service MSSQLSERVER
21:42:09 Process Exit Code: (0)
21:42:09 C:\DOCUME~1\datacom\LOCALS~1\Temp\1\SqlSetup\Bin\s cm.exe -Silent 1
-Action 1 -Service MSSQLSERVER -StartupOptions \-T4022
21:42:30 Process Exit Code: (0)
21:42:30 C:\SQL2KSP4\x86\BINN\osql.exe -Slpc:OMF-DBCLUSTER -n -d master -Q
"exit" -o "C:\DOCUME~1\datacom\LOCALS~1\Temp\1\sqlsp.out " -E
21:42:30 Process Exit Code: (0)
21:42:30 Begin: CheckSAPassword
21:42:30 Begin: LogOnUsingBlankSA
21:42:30 C:\SQL2KSP4\x86\BINN\osql.exe -Slpc:OMF-DBCLUSTER -n -d master -o
"C:\DOCUME~1\datacom\LOCALS~1\Temp\1\sqlsp.out " -Q"Exit(declare @.ret int if
(select count(*) from master..syslogins where name='sa' AND ( (1 = pwd
21:42:30 Process Exit Code: (0)
21:42:30 End: LogOnUsingBlankSA
21:42:30 Begin: SdBlankPwd
21:42:30 End: SdBlankPwd
21:42:30 End: CheckSAPassword
21:42:30 Begin : SdErrorReportingDlg
21:45:02 End: SdErrorReportingDlg
21:45:02 Access authenticated
21:45:02 C:\SQL2KSP4\x86\BINN\osql.exe -Slpc:OMF-DBCLUSTER -n -b -d master
-o "C:\DOCUME~1\datacom\LOCALS~1\Temp\1\~sqldb0.t xt" -i
"C:\DOCUME~1\datacom\LOCALS~1\Temp\1\SqlSetup\Bin\ dbverify.sql" -E
21:45:02 Process Exit Code: (0)
21:45:02 C:\DOCUME~1\datacom\LOCALS~1\Temp\1\SqlSetup\Bin\s cm.exe -Silent 1
-Action 6 -Service MSSQLSERVER
21:45:17 Process Exit Code: (0)
21:45:18 Setup Type: Custom (303)
21:45:18 Processing: SQLProg
21:45:18 Processing: SQLProg\SQLServr
21:45:18 Processing: SQLProg\UpgTools
21:45:18 Processing: SQLProg\ReplSupp
21:45:18 Processing: SQLProg\Install
21:45:18 Processing: SQLProg\System
21:45:18 Processing: SQLProg\SvrExt
21:45:18 Processing: SQLProg\Dat
21:45:18 Processing: SQLProg\DatSmpl
21:45:18 Processing: SQLProg\BaseSys
21:45:18 Processing: SQLProg\BaseBinn
21:45:18 Processing: SQLProg\MSSearch
21:45:18 Processing: SQLProg\BaseInst
21:45:18 Processing: SQLProg\UI
21:45:18 Processing: SQLProg\Symbols
21:45:18 Processing: SQLProg\Perfmon
21:45:18 Processing: SQLProg\Root
21:45:18 Processing: SQLProg\EXE
21:45:18 Processing: SQLProg\DLL
21:45:18 Processing: MgtTool
21:45:18 Processing: MgtTool\SEM
21:45:18 Processing: MgtTool\Profiler
21:45:18 Processing: MgtTool\Qryanlz
21:45:18 Processing: MgtTool\DTCCLi
21:45:18 Processing: MgtTool\Wzcnflct
21:45:18 Processing: MgtTool\UtilSys
21:45:18 Processing: MgtTool\UtilBinn
21:45:18 Processing: Connect
21:45:18 Processing: Connect\ConnSys
21:45:18 Processing: Books
21:45:18 Processing: Books\Bookso
21:45:18 Processing: DevTools
21:45:18 Processing: DevTools\Headers and Libraries
21:45:18 Processing: DevTools\MDAC SDKs
21:45:18 Processing: DevTools\VDI
21:45:18 Processing: DevTools\Dbg Int
21:45:18 Processing: Samples
21:45:18 Processing: Samples\ADO
21:45:18 Processing: Samples\DBLIB
21:45:18 Processing: Samples\Desktop
21:45:18 Processing: Samples\DTS
21:45:18 Processing: Samples\ESQLC
21:45:18 Processing: Samples\Misc
21:45:18 Processing: Samples\MSDTC
21:45:18 Processing: Samples\ODBC
21:45:18 Processing: Samples\ODS
21:45:18 Processing: Samples\OLEAut
21:45:18 Processing: Samples\Repl
21:45:18 Processing: Samples\SilverstoneDB
21:45:18 Processing: Samples\SQLDMO
21:45:18 Processing: Samples\SQLNS
21:45:18 Processing: Samples\Utils
21:45:18 Processing: Samples\XML
21:45:18 Processing: CoreRepl
21:45:18 Processing: CoreRepl\Res1033
21:45:18 Processing: CoreRepl\ResIntl
21:45:18 Processing: Core
21:45:18 Processing: Core\Res1033
21:45:18 Processing: Core\ResOther
21:45:18 Processing: Repostry
21:45:18 Processing: Repostry\RepstSys
21:45:18 Processing: Repostry\Res1033
21:45:18 Processing: Repostry\ResIntl
21:45:18 Processing: CoreMisc
21:45:18 Processing: CoreMisc\ActiveX
21:45:18 Processing: CoreMisc\Res1033
21:45:18 Processing: Monarch
21:45:18 Processing: Monarch\Monr1033
21:45:18 Processing: Monarch\MonrIntl
21:45:18 Processing: Jet
21:45:18 Processing: CoreInst
21:45:18 Processing: CoreCOM
21:45:18 Processing: CoreCOM\Res1033
21:45:18 Processing: CoreCOM\ResIntl
21:45:18 Processing: CoreTool
21:45:18 Processing: CoreTool\Res1033
21:45:18 Processing: CoreTool\ResOther
21:45:18 Processing: DBLibCli
21:45:18 Processing: SFExt
21:45:18 Processing: SFExt\ActiveX
21:45:18 Processing: SFExt\Res1033
21:45:18 Processing: SFExt\ResIntl
21:45:18 Processing: Trace
21:45:18 Processing: Trace\Res1033
21:45:18 Processing: Trace\ResOther
21:45:18 Processing: CnctBinn
21:45:18 Processing: MiscCore
21:45:18 Processing: MC
21:45:18 Processing: MC\MC1033
21:45:18 Processing: MC\MCIntl
21:45:18 Processing: MC\Help
21:45:18 Processing: UI
21:45:18 Processing: UI\UIHlp
21:45:18 Processing: UI\UI1033
21:45:18 Processing: UI\UIIntl
21:45:18 Processing: ClstSys
21:45:18 Processing: SQLMgr
21:45:18 Processing: SQLMgr\Res1033
21:45:18 Processing: SQLMgr\ResIntl
21:45:18 Processing: SvrTool
21:45:18 Processing: SvrTool\Res1033
21:45:18 Processing: SvrTool\ResIntl
21:45:18 Processing: DTSUI
21:45:18 Processing: DTSUI\Res1033
21:45:18 Processing: DTSUI\ResIntl
21:45:18 Processing: ClFTSys
21:45:18 Processing: ClFtdata
21:45:18 Processing: MSOlap
21:45:18 Processing: MSOlap\Res1033
21:45:18 Processing: MSOlap\ResIntl
21:45:18 Processing: ATL
21:45:18 Processing: ATL\winnt
21:45:18 Processing: ATL\win9x
21:45:18 Processing: MFC42U
21:45:18 Processing: VC
21:45:18 Processing: VB
21:45:18 Processing: OCX1
21:45:18 Processing: SQLAdHlp
21:45:18 Processing: SQLAdHlp\Res1033
21:45:18 Processing: SQLAdHlp\ResOther
21:45:18 Setup type: Custom
21:45:18 End Action DialogShowSdUpgrade
21:45:18 begin ShowDialogsUpdateMask
21:45:18 nFullMask = 0xb03e607, nCurrent = 0x2000, nDirection = 1
21:45:18 Updated Dialog Mask: 0xb03e003, Disable Back = 0x1
21:45:18 Dialog 0x2000 returned: 1
21:45:18 End Action ShowDialogsHlpr
21:45:18 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14
21:45:18 Begin Action ShowDialogsHlpr: 0x4000
21:45:18 Skipping DialogShowSdVirtualServer
21:45:18 begin ShowDialogsUpdateMask
21:45:18 nFullMask = 0xb03e003, nCurrent = 0x4000, nDirection = 1
21:45:18 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1
21:45:18 Dialog 0x4000 returned: 1
21:45:18 End Action ShowDialogsHlpr
21:45:18 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15
21:45:18 Begin Action ShowDialogsHlpr: 0x8000
21:45:18 Begin Action : DialogShowSdDiskGroups
21:45:18 ShowDlgDiskGroups returned: 1
21:45:18 Disk Group = SQL Group
21:45:18 End Action : DialogShowSdDiskGroups
21:45:18 begin ShowDialogsUpdateMask
21:45:18 nFullMask = 0xb03e607, nCurrent = 0x8000, nDirection = 1
21:45:18 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1
21:45:18 Dialog 0x8000 returned: 1
21:45:18 End Action ShowDialogsHlpr
21:45:18 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16
21:45:18 Begin Action ShowDialogsHlpr: 0x10000
21:45:18 Begin Action: DialogShowSdClusterDef
21:45:18 Before !! The Prefowner list is : . g_szSpNeededNodelst is : .
g_nNumnodes :0 g_szOwners :, g_szDiskGroup SQL Group
21:45:18 ShowDlgClusterDef returned: 1
21:45:18 PrefOwners = OMF-DBCLUSTER-A,OMF-DBCLUSTER-B, NumIp = 2
21:45:18 Begin Action : ValidateNodeActions
21:45:18 Begin Action : EnumerateInstancesForVirtualServer
21:45:18 End Action : EnumerateInstancesForVirtualServer
21:45:18 Begin Action : ValidateNodeActions
21:45:18 End Action : ValidateNodeActions
21:45:18 End Action : ValidateNodeActions
21:45:18 End Action DialogShowSdClusterDef
21:45:18 begin ShowDialogsUpdateMask
21:45:18 nFullMask = 0xb03e607, nCurrent = 0x10000, nDirection = 1
21:45:18 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1
21:45:18 Dialog 0x10000 returned: 1
21:45:18 End Action ShowDialogsHlpr
21:45:18 ShowDialogsGetDialog returned: nCurrent=0x20000,index=17
21:45:18 Begin Action ShowDialogsHlpr: 0x20000
21:45:18 Begin Action : Cluster Security - DlgAcct
following message.
Buffer Overrun detected!
A buffer overrun has been detected which has corrupted the programs internal
state. The program cannot safely continue execution and must now be
terminated.
This happens just after entering the account required to update both cluster
notes. The account is a domain admin account.
Any help greatly appreciated.
BB
Hello Bruce,
Verify that there are no dependencies other than those created by the SQL Server setup on any SQL Server cluster resources. Resources such as file shares, FTP servers, and Microsoft Internet Information
Services (IIS) servers must always have a unique network name and an IP address resource. You must remove any such non-default dependencies before you install SQL Server 2000 SP4. No dependencies other
than those supplied by the SQL Server setup must be used, except to validate whether SQL Server is online and available for the client application.
For example, if you have MSDTC resource in the SQL group and if MSDTC is dependent on SQL Server Network Name and SQL IP Address then you may have this issue. If this is the case then you will need to
remove the dependencies and then re-run the setup.
Also, make sure that you have followed the SP4 pre-installation checklist (see link below).
If you still have the same problem, then the next step will be to review the logs. I would start with the sqlsp.log (created on the node where you ran the SP4 setup). You can also cut and paste the log for us to review.
Recommended Reading
======================
SQL Server 2000 Service Pack 3, Service Pack 3a, or Service Pack 4 pre-installation checklist for SQL Server 2000 virtual server for failover clustering
http://support.microsoft.com/?kbid=811168
Clustered SQL Server do's, don'ts, and basic warnings
http://support.microsoft.com/default...B;EN-US;254321
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Hi,
I checked the dependencies. It doesn't look like anything is dependent on
SQL Server other than SQLAgent which I believe is correct. The only thing
that I think is weird in this setup is that MSDTC is in the cluster quorum
resource group...
Anyway, here is the content of sqlsp.log.
21:41:52 Begin Setup
21:41:52 Version on Media: 8.00.2039
21:41:52 Mode = Normal
21:41:52 ModeType = NORMAL
21:41:52 Loading library - sqlsut.dll (#L1)
21:41:52 Begin: SetupInitialize()
21:41:52 End: SetupInitialize()
21:41:52 Begin: CheckFixedRequirements()
21:41:52 Platform ID: 0xf00000
21:41:52 Version: 5.2.3790
21:41:52 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.327
21:41:52 End: CheckFixedRequirements()
21:41:53 Processor Architecture: x86 (Pentium)
21:41:53 ComputerName: OMF-DBCLUSTER-A
21:41:53 User Name: datacom
21:41:53 IsAllAccessAllowed returned: 1
21:41:53 OS Language: 0x409
21:41:53 Begin: SetupInstall()
21:41:53 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
21:41:53 CommonFilesDir=C:\Program Files\Common Files
21:41:53 Windows Directory=C:\WINDOWS\
21:41:53 Program Files=C:\Program Files\
21:41:53 TEMPDIR=C:\DOCUME~1\datacom\LOCALS~1\Temp\1\
21:41:53 End: SetupInstall()
21:41:53 Begin: ShowDialogs()
21:41:53 Initial Dialog Mask: 0x8300037, Disable Back=0x1
21:41:53 Begin Action ShowDialogsHlpr: 0x1
21:41:53 Begin Action: DialogShowSdWelcome
21:41:56 End Action DialogShowSdWelcome
21:41:56 Dialog 0x1 returned: 1
21:41:56 End Action ShowDialogsHlpr
21:41:56 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
21:41:56 Begin Action ShowDialogsHlpr: 0x2
21:41:56 Begin Action: DialogShowSdMachineName
21:42:02 ShowDlgMachine returned: 1
21:42:02 Name = OMF-DBCLUSTER, Type = 0x20000008
21:42:02 End Action DialogShowSdMachineName
21:42:02 begin ShowDialogsUpdateMask
21:42:02 nFullMask = 0x8300037, nCurrent = 0x2, nDirection = 1
21:42:02 Updated Dialog Mask: 0xb73c037, Disable Back = 0x1
21:42:02 Dialog 0x2 returned: 1
21:42:02 End Action ShowDialogsHlpr
21:42:02 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
21:42:02 Begin Action ShowDialogsHlpr: 0x4
21:42:02 Begin Action: DialogShowSdInstallMode
21:42:02 ShowDlgInstallMode returned: 1
21:42:02 InstallMode : 0x2
21:42:02 End Action DialogShowSdInstallMode
21:42:02 begin ShowDialogsUpdateMask
21:42:02 nFullMask = 0xb73c037, nCurrent = 0x4, nDirection = 1
21:42:02 Updated Dialog Mask: 0xb034607, Disable Back = 0x1
21:42:02 Dialog 0x4 returned: 1
21:42:02 End Action ShowDialogsHlpr
21:42:02 ShowDialogsGetDialog returned: nCurrent=0x200,index=9
21:42:02 Begin Action ShowDialogsHlpr: 0x200
21:42:02 Begin Action: DialogShowSdInstanceName
21:42:02 Begin Action: ShowDlgInstanceName
21:42:02 SKU is : Enterprise Edition
21:42:02 End Action: ShowDlgInstanceName
21:42:02 ShowDlgInstanceName returned : 0
21:42:02 InstanceName : MSSQLSERVER
21:42:02 End Action DialogShowSdInstanceName
21:42:02 begin ShowDialogsUpdateMask
21:42:02 nFullMask = 0xb034607, nCurrent = 0x200, nDirection = 0
21:42:02 Updated Dialog Mask: 0xb034603, Disable Back = 0x1
21:42:02 Dialog 0x200 returned: 0
21:42:02 End Action ShowDialogsHlpr
21:42:02 ShowDialogsGetDialog returned: nCurrent=0x400,index=10
21:42:02 Begin Action ShowDialogsHlpr: 0x400
21:42:02 Begin Action: DialogShowSdMaintain
21:42:02 ShowDlgMaintainInstall returned : 1
21:42:02 Type : 0xc
21:42:02 CreateSetupTopology(OMF-DBCLUSTER-A), Handle : 0x12648e0, returned
: 0
21:42:02 CreateSetupTopology returned : 0, Handle : 0x12648e0
21:42:02 Topology Type : 1, Return Value : 0
21:42:02 ST_GetPhysicalNode returned : 0, PNHandle : 0x1264928
21:42:02 PN_EnumerateEx returned : 0
21:42:02 PN_GetSQLStates returned : 0, SqlStates : 0x88008221
21:42:02 PN_GetInstance for MSSQLSERVER [0x1264928] returned : 0
21:42:02 SQLI_GetPackageId [0x1264ec0] returned : 0, PackageId = 0x3
21:42:02 SQLI_GetVersion [0x1264ec0] returned : 0, Version = 8.00.194
21:42:02 SQLI_GetSQLStates for MSSQLSERVER [0x1264ec0] returned : 0,
SQLStates: 0x400209
21:42:02 SQLI_GetInstallPath [0x1264ec0] returned : 0, Path = C:\Program
Files\Microsoft SQL Server\MSSQL
21:42:02 SQLI_GetDataPath [0x1264ec0] returned : 0, DataPath = F:\Program
Files\Microsoft SQL Server\MSSQL
21:42:02 SQLI_GetVersion [0x1264ec0] returned : 0, Version = 8.00.194
21:42:02 SQLI_GetRegKeyRoot [0x1264ec0] returned : 0, RegKeyRoot =
Software\Microsoft\MSSQLServer
21:42:02 SQLI_GetPackageName [0x1264ec0] returned : 0, szPackage =
Enterprise Edition
21:42:02 SQLI_GetPackageId [0x1264ec0] returned : 0, PackageId = 0x3
21:42:02 Previous Install Path: C:\Program Files\Microsoft SQL Server\MSSQL
21:42:02 Previous Install Data: F:\Program Files\Microsoft SQL Server\MSSQL
21:42:02 Previous Install Version: 8.00.194
21:42:02 ReleaseSetupTopology
21:42:02 End Action DialogShowSdMaintain
21:42:02 begin ShowDialogsUpdateMask
21:42:02 nFullMask = 0xb034603, nCurrent = 0x400, nDirection = 1
21:42:02 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1
21:42:02 Dialog 0x400 returned: 1
21:42:02 End Action ShowDialogsHlpr
21:42:02 ShowDialogsGetDialog returned: nCurrent=0x2000,index=13
21:42:02 Begin Action ShowDialogsHlpr: 0x2000
21:42:02 Begin Action: DialogShowSdUpgrade
21:42:02 ShowDlgUpgrade returned : 1
21:42:02 Checking databases on instance 'MSSQLSERVER'
21:42:02 Begin Action: Check for VS Node
21:42:02 Begin Action: Check for VS Node
21:42:02 Begin Action: Cluster Resources Offline
21:42:06 End Action: Cluster Resources Offline
21:42:06 Authenticate access
21:42:06 Begin SDPassword Dialog
21:42:09 End SDPassword Dialog
21:42:09 C:\DOCUME~1\datacom\LOCALS~1\Temp\1\SqlSetup\Bin\s cm.exe -Silent 1
-Action 6 -Service MSSQLSERVER
21:42:09 Process Exit Code: (0)
21:42:09 C:\DOCUME~1\datacom\LOCALS~1\Temp\1\SqlSetup\Bin\s cm.exe -Silent 1
-Action 1 -Service MSSQLSERVER -StartupOptions \-T4022
21:42:30 Process Exit Code: (0)
21:42:30 C:\SQL2KSP4\x86\BINN\osql.exe -Slpc:OMF-DBCLUSTER -n -d master -Q
"exit" -o "C:\DOCUME~1\datacom\LOCALS~1\Temp\1\sqlsp.out " -E
21:42:30 Process Exit Code: (0)
21:42:30 Begin: CheckSAPassword
21:42:30 Begin: LogOnUsingBlankSA
21:42:30 C:\SQL2KSP4\x86\BINN\osql.exe -Slpc:OMF-DBCLUSTER -n -d master -o
"C:\DOCUME~1\datacom\LOCALS~1\Temp\1\sqlsp.out " -Q"Exit(declare @.ret int if
(select count(*) from master..syslogins where name='sa' AND ( (1 = pwd
21:42:30 Process Exit Code: (0)
21:42:30 End: LogOnUsingBlankSA
21:42:30 Begin: SdBlankPwd
21:42:30 End: SdBlankPwd
21:42:30 End: CheckSAPassword
21:42:30 Begin : SdErrorReportingDlg
21:45:02 End: SdErrorReportingDlg
21:45:02 Access authenticated
21:45:02 C:\SQL2KSP4\x86\BINN\osql.exe -Slpc:OMF-DBCLUSTER -n -b -d master
-o "C:\DOCUME~1\datacom\LOCALS~1\Temp\1\~sqldb0.t xt" -i
"C:\DOCUME~1\datacom\LOCALS~1\Temp\1\SqlSetup\Bin\ dbverify.sql" -E
21:45:02 Process Exit Code: (0)
21:45:02 C:\DOCUME~1\datacom\LOCALS~1\Temp\1\SqlSetup\Bin\s cm.exe -Silent 1
-Action 6 -Service MSSQLSERVER
21:45:17 Process Exit Code: (0)
21:45:18 Setup Type: Custom (303)
21:45:18 Processing: SQLProg
21:45:18 Processing: SQLProg\SQLServr
21:45:18 Processing: SQLProg\UpgTools
21:45:18 Processing: SQLProg\ReplSupp
21:45:18 Processing: SQLProg\Install
21:45:18 Processing: SQLProg\System
21:45:18 Processing: SQLProg\SvrExt
21:45:18 Processing: SQLProg\Dat
21:45:18 Processing: SQLProg\DatSmpl
21:45:18 Processing: SQLProg\BaseSys
21:45:18 Processing: SQLProg\BaseBinn
21:45:18 Processing: SQLProg\MSSearch
21:45:18 Processing: SQLProg\BaseInst
21:45:18 Processing: SQLProg\UI
21:45:18 Processing: SQLProg\Symbols
21:45:18 Processing: SQLProg\Perfmon
21:45:18 Processing: SQLProg\Root
21:45:18 Processing: SQLProg\EXE
21:45:18 Processing: SQLProg\DLL
21:45:18 Processing: MgtTool
21:45:18 Processing: MgtTool\SEM
21:45:18 Processing: MgtTool\Profiler
21:45:18 Processing: MgtTool\Qryanlz
21:45:18 Processing: MgtTool\DTCCLi
21:45:18 Processing: MgtTool\Wzcnflct
21:45:18 Processing: MgtTool\UtilSys
21:45:18 Processing: MgtTool\UtilBinn
21:45:18 Processing: Connect
21:45:18 Processing: Connect\ConnSys
21:45:18 Processing: Books
21:45:18 Processing: Books\Bookso
21:45:18 Processing: DevTools
21:45:18 Processing: DevTools\Headers and Libraries
21:45:18 Processing: DevTools\MDAC SDKs
21:45:18 Processing: DevTools\VDI
21:45:18 Processing: DevTools\Dbg Int
21:45:18 Processing: Samples
21:45:18 Processing: Samples\ADO
21:45:18 Processing: Samples\DBLIB
21:45:18 Processing: Samples\Desktop
21:45:18 Processing: Samples\DTS
21:45:18 Processing: Samples\ESQLC
21:45:18 Processing: Samples\Misc
21:45:18 Processing: Samples\MSDTC
21:45:18 Processing: Samples\ODBC
21:45:18 Processing: Samples\ODS
21:45:18 Processing: Samples\OLEAut
21:45:18 Processing: Samples\Repl
21:45:18 Processing: Samples\SilverstoneDB
21:45:18 Processing: Samples\SQLDMO
21:45:18 Processing: Samples\SQLNS
21:45:18 Processing: Samples\Utils
21:45:18 Processing: Samples\XML
21:45:18 Processing: CoreRepl
21:45:18 Processing: CoreRepl\Res1033
21:45:18 Processing: CoreRepl\ResIntl
21:45:18 Processing: Core
21:45:18 Processing: Core\Res1033
21:45:18 Processing: Core\ResOther
21:45:18 Processing: Repostry
21:45:18 Processing: Repostry\RepstSys
21:45:18 Processing: Repostry\Res1033
21:45:18 Processing: Repostry\ResIntl
21:45:18 Processing: CoreMisc
21:45:18 Processing: CoreMisc\ActiveX
21:45:18 Processing: CoreMisc\Res1033
21:45:18 Processing: Monarch
21:45:18 Processing: Monarch\Monr1033
21:45:18 Processing: Monarch\MonrIntl
21:45:18 Processing: Jet
21:45:18 Processing: CoreInst
21:45:18 Processing: CoreCOM
21:45:18 Processing: CoreCOM\Res1033
21:45:18 Processing: CoreCOM\ResIntl
21:45:18 Processing: CoreTool
21:45:18 Processing: CoreTool\Res1033
21:45:18 Processing: CoreTool\ResOther
21:45:18 Processing: DBLibCli
21:45:18 Processing: SFExt
21:45:18 Processing: SFExt\ActiveX
21:45:18 Processing: SFExt\Res1033
21:45:18 Processing: SFExt\ResIntl
21:45:18 Processing: Trace
21:45:18 Processing: Trace\Res1033
21:45:18 Processing: Trace\ResOther
21:45:18 Processing: CnctBinn
21:45:18 Processing: MiscCore
21:45:18 Processing: MC
21:45:18 Processing: MC\MC1033
21:45:18 Processing: MC\MCIntl
21:45:18 Processing: MC\Help
21:45:18 Processing: UI
21:45:18 Processing: UI\UIHlp
21:45:18 Processing: UI\UI1033
21:45:18 Processing: UI\UIIntl
21:45:18 Processing: ClstSys
21:45:18 Processing: SQLMgr
21:45:18 Processing: SQLMgr\Res1033
21:45:18 Processing: SQLMgr\ResIntl
21:45:18 Processing: SvrTool
21:45:18 Processing: SvrTool\Res1033
21:45:18 Processing: SvrTool\ResIntl
21:45:18 Processing: DTSUI
21:45:18 Processing: DTSUI\Res1033
21:45:18 Processing: DTSUI\ResIntl
21:45:18 Processing: ClFTSys
21:45:18 Processing: ClFtdata
21:45:18 Processing: MSOlap
21:45:18 Processing: MSOlap\Res1033
21:45:18 Processing: MSOlap\ResIntl
21:45:18 Processing: ATL
21:45:18 Processing: ATL\winnt
21:45:18 Processing: ATL\win9x
21:45:18 Processing: MFC42U
21:45:18 Processing: VC
21:45:18 Processing: VB
21:45:18 Processing: OCX1
21:45:18 Processing: SQLAdHlp
21:45:18 Processing: SQLAdHlp\Res1033
21:45:18 Processing: SQLAdHlp\ResOther
21:45:18 Setup type: Custom
21:45:18 End Action DialogShowSdUpgrade
21:45:18 begin ShowDialogsUpdateMask
21:45:18 nFullMask = 0xb03e607, nCurrent = 0x2000, nDirection = 1
21:45:18 Updated Dialog Mask: 0xb03e003, Disable Back = 0x1
21:45:18 Dialog 0x2000 returned: 1
21:45:18 End Action ShowDialogsHlpr
21:45:18 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14
21:45:18 Begin Action ShowDialogsHlpr: 0x4000
21:45:18 Skipping DialogShowSdVirtualServer
21:45:18 begin ShowDialogsUpdateMask
21:45:18 nFullMask = 0xb03e003, nCurrent = 0x4000, nDirection = 1
21:45:18 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1
21:45:18 Dialog 0x4000 returned: 1
21:45:18 End Action ShowDialogsHlpr
21:45:18 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15
21:45:18 Begin Action ShowDialogsHlpr: 0x8000
21:45:18 Begin Action : DialogShowSdDiskGroups
21:45:18 ShowDlgDiskGroups returned: 1
21:45:18 Disk Group = SQL Group
21:45:18 End Action : DialogShowSdDiskGroups
21:45:18 begin ShowDialogsUpdateMask
21:45:18 nFullMask = 0xb03e607, nCurrent = 0x8000, nDirection = 1
21:45:18 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1
21:45:18 Dialog 0x8000 returned: 1
21:45:18 End Action ShowDialogsHlpr
21:45:18 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16
21:45:18 Begin Action ShowDialogsHlpr: 0x10000
21:45:18 Begin Action: DialogShowSdClusterDef
21:45:18 Before !! The Prefowner list is : . g_szSpNeededNodelst is : .
g_nNumnodes :0 g_szOwners :, g_szDiskGroup SQL Group
21:45:18 ShowDlgClusterDef returned: 1
21:45:18 PrefOwners = OMF-DBCLUSTER-A,OMF-DBCLUSTER-B, NumIp = 2
21:45:18 Begin Action : ValidateNodeActions
21:45:18 Begin Action : EnumerateInstancesForVirtualServer
21:45:18 End Action : EnumerateInstancesForVirtualServer
21:45:18 Begin Action : ValidateNodeActions
21:45:18 End Action : ValidateNodeActions
21:45:18 End Action : ValidateNodeActions
21:45:18 End Action DialogShowSdClusterDef
21:45:18 begin ShowDialogsUpdateMask
21:45:18 nFullMask = 0xb03e607, nCurrent = 0x10000, nDirection = 1
21:45:18 Updated Dialog Mask: 0xb03e607, Disable Back = 0x1
21:45:18 Dialog 0x10000 returned: 1
21:45:18 End Action ShowDialogsHlpr
21:45:18 ShowDialogsGetDialog returned: nCurrent=0x20000,index=17
21:45:18 Begin Action ShowDialogsHlpr: 0x20000
21:45:18 Begin Action : Cluster Security - DlgAcct
Subscribe to:
Posts (Atom)