Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts

Tuesday, March 27, 2012

Error installing SQL 2005 on a cluster

I am installing SQL 2005 on a two node 2003 SP1 cluster and get an error
after selecting components and I have narrowed it down to Shared Tools. The
error is:
"The drive specified cannot be used for program location. Program files
must be installed on a valid local disk available on all cluster nodes. The
valid values are"
The help icon gives a LinkID of 20467, but I can't find any info on that.
I'm installing to C:\Program Files\Microsoft SQL Server, which the Data
Files feature seems happy to install to. If only Shared Tools wasn't a
required component!
Anyone run into this or know what can cause it?
Which drive letters do you have on each node? Which ones are local disks
and which are in the shared array? Which disks are configured in the
cluster group you are specifying for the failover cluster instance?
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"CShane" <CShane@.discussions.microsoft.com> wrote in message
news:9314C7CC-067B-4732-9274-DC6BA28AC092@.microsoft.com...
>I am installing SQL 2005 on a two node 2003 SP1 cluster and get an error
> after selecting components and I have narrowed it down to Shared Tools.
> The
> error is:
> "The drive specified cannot be used for program location. Program files
> must be installed on a valid local disk available on all cluster nodes.
> The
> valid values are"
> The help icon gives a LinkID of 20467, but I can't find any info on that.
> I'm installing to C:\Program Files\Microsoft SQL Server, which the Data
> Files feature seems happy to install to. If only Shared Tools wasn't a
> required component!
> Anyone run into this or know what can cause it?
|||C drives are local for both nodes. The S drive will eventually be the SQL
drive, although I am not able to get to that point in the installation to
specify the resource group yet, although it is online and functioning. Q is
the quorum and it's working fine.
"Michael Hotek" wrote:

> Which drive letters do you have on each node? Which ones are local disks
> and which are in the shared array? Which disks are configured in the
> cluster group you are specifying for the failover cluster instance?
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "CShane" <CShane@.discussions.microsoft.com> wrote in message
> news:9314C7CC-067B-4732-9274-DC6BA28AC092@.microsoft.com...
>
>
|||You need the S now to install the SQL data, C for the bits.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"CShane" <CShane@.discussions.microsoft.com> wrote in message
news:69BC9FF1-38C1-490A-BC6B-704D22B1A607@.microsoft.com...[vbcol=seagreen]
>C drives are local for both nodes. The S drive will eventually be the SQL
> drive, although I am not able to get to that point in the installation to
> specify the resource group yet, although it is online and functioning. Q
> is
> the quorum and it's working fine.
>
> "Michael Hotek" wrote:
|||I'm not quite sure I understand your suggestion. The C:\Program Files\
folder is where I'm trying to install the software. If I can ever get past
feature selection, I will select the S: drive for data. However, the S:
drive resource is online and functioning correctly inside cluster
administrator. I can also write to it from the resource owner.
Thanks for any help!
"Rodney R. Fournier [MVP]" wrote:

> You need the S now to install the SQL data, C for the bits.
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://www.msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "CShane" <CShane@.discussions.microsoft.com> wrote in message
> news:69BC9FF1-38C1-490A-BC6B-704D22B1A607@.microsoft.com...
>
>
|||I hope this resolves your issue.
http://www.sql-server-performance.co..._to_2005_4.asp
Thanks,
Haris.
"CShane" <CShane@.discussions.microsoft.com> wrote in message news:F055EA13-6C31-41D0-8661-1BCF97449FB9@.microsoft.com...[vbcol=seagreen]
> I'm not quite sure I understand your suggestion. The C:\Program Files\
> folder is where I'm trying to install the software. If I can ever get past
> feature selection, I will select the S: drive for data. However, the S:
> drive resource is online and functioning correctly inside cluster
> administrator. I can also write to it from the resource owner.
> Thanks for any help!
>
> "Rodney R. Fournier [MVP]" wrote:
|||Setup scans all the cluster nodes to make sure there is at least 1 common
drive between all of them. On a 32bit cluster it's usually C or D. If all
your nodes have a C: drive in common then you should be fine. Look in the
SQLSetup_machinename_WI.log file for more information.
Thanks.
"CShane" wrote:
[vbcol=seagreen]
> I'm not quite sure I understand your suggestion. The C:\Program Files\
> folder is where I'm trying to install the software. If I can ever get past
> feature selection, I will select the S: drive for data. However, the S:
> drive resource is online and functioning correctly inside cluster
> administrator. I can also write to it from the resource owner.
> Thanks for any help!
>
> "Rodney R. Fournier [MVP]" wrote:
|||Thanks for the help, but I've found an undocumented "feature" with SQL 2005
clustering. Setup will fail if you have any offline physical disk resources.
I had created an "Unused Drives" resource group to keep my unused physical
disk resources from becoming corrupted but hadn't brought them online. My
solution was to bring all physical disk resources online while running SQL
2005 setup. Keep in mind, it wasn't the SQL disk that was offline. It was a
physical disk resource that I planned to use later for something like
Exchange or file sharing. I hope this saves someone else a bottle or two of
Asprin!
Thanks again!
Shane
"Ray Schueler[MSFT]" wrote:
[vbcol=seagreen]
> Setup scans all the cluster nodes to make sure there is at least 1 common
> drive between all of them. On a 32bit cluster it's usually C or D. If all
> your nodes have a C: drive in common then you should be fine. Look in the
> SQLSetup_machinename_WI.log file for more information.
> Thanks.
>
> "CShane" wrote:
|||That one is documented in a KB article somewhere. I can't remember where it
is at though.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"CShane" <CShane@.discussions.microsoft.com> wrote in message
news:F22BFD0D-8834-4781-AFFD-28C4454F9F6A@.microsoft.com...[vbcol=seagreen]
> Thanks for the help, but I've found an undocumented "feature" with SQL
> 2005
> clustering. Setup will fail if you have any offline physical disk
> resources.
> I had created an "Unused Drives" resource group to keep my unused physical
> disk resources from becoming corrupted but hadn't brought them online. My
> solution was to bring all physical disk resources online while running SQL
> 2005 setup. Keep in mind, it wasn't the SQL disk that was offline. It
> was a
> physical disk resource that I planned to use later for something like
> Exchange or file sharing. I hope this saves someone else a bottle or two
> of
> Asprin!
> Thanks again!
> Shane
> "Ray Schueler[MSFT]" wrote:
|||I found and reported this during the CTP process. I got a very good
explanation that boils down to "Unavoidable side effect of installing on a
clustered host". Here is the fun part: The installer fails on a clustered
system, even if you are trying to do a stand-alone install. And it fails if
ANY clustered resources are offline.
And yes, it drove me nuts figuring out this one.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Michael Hotek" <mike@.solidqualitylearning.com> wrote in message
news:uW5s1AwNGHA.2176@.TK2MSFTNGP10.phx.gbl...
> That one is documented in a KB article somewhere. I can't remember where
> it is at though.
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "CShane" <CShane@.discussions.microsoft.com> wrote in message
> news:F22BFD0D-8834-4781-AFFD-28C4454F9F6A@.microsoft.com...
>
sql

Error installing SQL 2000 on W2k3 cluster

When installing SQL 2000 on a W2K3 cluster, I get the following error: An
error occurred while creating virtual server resources for clustering.
Cluster specific registry entries couldn't be written. I followed the
instructions in KB872931 and I get the same results. Can anyone assist?
Kevin
All,
Never mind. starting the remote registry service on all nodes fixed the
problem.
Kevin
"Kevin Wheeler" <kevin.l.wheeler@.lmco.com> wrote in message
news:OMeIGELyEHA.2192@.TK2MSFTNGP14.phx.gbl...
> When installing SQL 2000 on a W2K3 cluster, I get the following error: An
> error occurred while creating virtual server resources for clustering.
> Cluster specific registry entries couldn't be written. I followed the
> instructions in KB872931 and I get the same results. Can anyone assist?
>
> Kevin
>
|||Kevin,
The error message "An error occurred while creating virtual server resources for clustering. Cluster specific registry entries couldn't be written" occurs when the SQL Server 2000 virtual server Setup program tries to
create the virtual server resources on the remote nodes in the failover cluster.
The KB872931 will be helpful only if your sqlstp.log had the errors as written in the MORE INFORMATION section of the KB.
Give us more information to be able to help you out.
Few qs that comes to mind :
1) Do you have Teminal Services installed on Win2K3 nodes? If yes, the you need to remove it. See KB 301520
2) Are you installing a named instance or a default instance of SQL2K virtual instance? If named instance, have created a named pipe alias for the server name as per KB 815431
3) Do you have mount volumes in the cluster? They are not supported for SQL 2K virtual instance. See KB 819546
4) Paste the sqlstp.log for us to look at
Interested in troubleshooting it yourself
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
Upcoming Webcast
TechNet Support WebCast: How to install a Microsoft SQL Server 2000 virtual server on a Microsoft Windows Server 2003 cluster
Discusses how to install Microsoft SQL Server 2000 clustering on Microsoft Windows Server 2003 and differences between Microsoft Windows 2000 Server and Windows Server 2003.
http://support.microsoft.com/default...b;en-us;888121
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
|||I understand that. I guess it need access to the remote nodes registry.
When the remote registry service was disabled, the install failed. When I
enabled it, the install completed with no errors.
Kevin
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:tPwDvzMyEHA.3436@.cpmsftngxa10.phx.gbl...
> Kevin,
> The error message "An error occurred while creating virtual server
resources for clustering. Cluster specific registry entries couldn't be
written" occurs when the SQL Server 2000 virtual server Setup program tries
to
> create the virtual server resources on the remote nodes in the failover
cluster.
> The KB872931 will be helpful only if your sqlstp.log had the errors as
written in the MORE INFORMATION section of the KB.
> Give us more information to be able to help you out.
> Few qs that comes to mind :
> 1) Do you have Teminal Services installed on Win2K3 nodes? If yes, the you
need to remove it. See KB 301520
> 2) Are you installing a named instance or a default instance of SQL2K
virtual instance? If named instance, have created a named pipe alias for the
server name as per KB 815431
> 3) Do you have mount volumes in the cluster? They are not supported for
SQL 2K virtual instance. See KB 819546
> 4) Paste the sqlstp.log for us to look at
> Interested in troubleshooting it yourself
> Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for
Failover Clustering
>
http://support.microsoft.com/default...ebcasts/wcd020
703/wcdblurb020703.asp
> Upcoming Webcast
> TechNet Support WebCast: How to install a Microsoft SQL Server 2000
virtual server on a Microsoft Windows Server 2003 cluster
> Discusses how to install Microsoft SQL Server 2000 clustering on
Microsoft Windows Server 2003 and differences between Microsoft Windows 2000
Server and Windows Server 2003.
> http://support.microsoft.com/default...b;en-us;888121
> 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
>
|||Glad to hear that you resolved the issue. You are correct. The "Remote Registry" service needs to be running on all cluster nodes during the installation.
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

Wednesday, March 21, 2012

Error in SQL 2005 cluster installation

I am trying to install SQL 2005 in a 2-node Windows 2003 cluster. I have tried both upgrade and fresh installation, but got same error. The error stops the installation while checking system configuration after installing prerequisites. Any idea ? The log file entry is as follows:

*******************************************
Setup Consistency Check Report for Machine: --SERVERNAME--
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: CheckPassed
Article: IIS Feature Requirement, Result: Warning
Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Performance Monitor Counter Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
<Func Name='PerformDetections'>
1
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlsval.dll Version:2005.90.1399.0
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run:
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache
Source File Name: datastore\clusterinfocollector.cpp
Compiler Timestamp: Fri Sep 16 13:20:12 2005
Function Name: ClusterInfoCollector::collectClusterVSInfo
Source Line Number: 883
-
Failed to detect VS info due to datastore exception.
Source File Name: datastore\clustergroupsproperties.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: ClusterGroupScope.SharedDisks
Source Line Number: 56
-
Failed to find a cluster group that owned shared disk: J:
WinException : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.

Source File Name: datastore\clustergroupsproperties.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: ClusterGroupScope.SharedDisks
Source Line Number: 56

Hi,

Did you resolve this? I have run into the same error and am unsure how to proceed.

Any advice would be warmly received.

Regards,

Rob.

Error in SQL 2005 cluster installation

I am trying to install SQL 2005 in a 2-node Windows 2003 cluster. I have tried both upgrade and fresh installation, but got same error. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:

*******************************************
Setup Consistency Check Report for Machine: --SERVERNAME--
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: CheckPassed
Article: IIS Feature Requirement, Result: Warning
Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Performance Monitor Counter Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
<Func Name='PerformDetections'>
1
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlsval.dll Version:2005.90.1399.0
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run:
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache
Source File Name: datastore\clusterinfocollector.cpp
Compiler Timestamp: Fri Sep 16 13:20:12 2005
Function Name: ClusterInfoCollector::collectClusterVSInfo
Source Line Number: 883
-
Failed to detect VS info due to datastore exception.
Source File Name: datastore\clustergroupsproperties.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: ClusterGroupScope.SharedDisks
Source Line Number: 56
-
Failed to find a cluster group that owned shared disk: J:
WinException : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.

Source File Name: datastore\clustergroupsproperties.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: ClusterGroupScope.SharedDisks
Source Line Number: 56

Do you have admin shares disabled on the cluster nodes? If they're disabled, it can cause all kinds of problems with clustered SQL installation.|||

Hello we have faced the same problem. Using your problem desciption helped us find the drive letter which is not configured correctly.

In our case the drive letter was used by a previous de installed SQL Server configuration. The de install was not completed as it should. To solve the problem, we removed the MSSQL.x (x is a number between 1 and 100) containing sub keys with a value point to the drive missing. You can find these MSSQL.x keys in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

Kind regards

Marcel

sql

Error in SQL 2005 cluster installation

I am trying to install SQL 2005 in a 2-node Windows 2003 cluster. I have tried both upgrade and fresh installation, but got same error. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:

*******************************************
Setup Consistency Check Report for Machine: --SERVERNAME--
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: CheckPassed
Article: IIS Feature Requirement, Result: Warning
Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Performance Monitor Counter Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
<Func Name='PerformDetections'>
1
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlsval.dll Version:2005.90.1399.0
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run:
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache
Source File Name: datastore\clusterinfocollector.cpp
Compiler Timestamp: Fri Sep 16 13:20:12 2005
Function Name: ClusterInfoCollector::collectClusterVSInfo
Source Line Number: 883
-
Failed to detect VS info due to datastore exception.
Source File Name: datastore\clustergroupsproperties.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: ClusterGroupScope.SharedDisks
Source Line Number: 56
-
Failed to find a cluster group that owned shared disk: J:
WinException : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.

Source File Name: datastore\clustergroupsproperties.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: ClusterGroupScope.SharedDisks
Source Line Number: 56

Do you have admin shares disabled on the cluster nodes? If they're disabled, it can cause all kinds of problems with clustered SQL installation.|||

Hello we have faced the same problem. Using your problem desciption helped us find the drive letter which is not configured correctly.

In our case the drive letter was used by a previous de installed SQL Server configuration. The de install was not completed as it should. To solve the problem, we removed the MSSQL.x (x is a number between 1 and 100) containing sub keys with a value point to the drive missing. You can find these MSSQL.x keys inHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

Kind regards

Marcel

Error in SQL 2005 cluster installation

I am trying to install SQL 2005 in a 2-node Windows 2003 cluster. I have tried both upgrade and fresh installation, but got same error. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:

*******************************************
Setup Consistency Check Report for Machine: --SERVERNAME--
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: CheckPassed
Article: IIS Feature Requirement, Result: Warning
Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Performance Monitor Counter Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
<Func Name='PerformDetections'>
1
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlsval.dll Version:2005.90.1399.0
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run:
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
-
Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache
Source File Name: datastore\clusterinfocollector.cpp
Compiler Timestamp: Fri Sep 16 13:20:12 2005
Function Name: ClusterInfoCollector::collectClusterVSInfo
Source Line Number: 883
-
Failed to detect VS info due to datastore exception.
Source File Name: datastore\clustergroupsproperties.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: ClusterGroupScope.SharedDisks
Source Line Number: 56
-
Failed to find a cluster group that owned shared disk: J:
WinException : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.

Source File Name: datastore\clustergroupsproperties.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: ClusterGroupScope.SharedDisks
Source Line Number: 56

Do you have admin shares disabled on the cluster nodes? If they're disabled, it can cause all kinds of problems with clustered SQL installation.|||

Hello we have faced the same problem. Using your problem desciption helped us find the drive letter which is not configured correctly.

In our case the drive letter was used by a previous de installed SQL Server configuration. The de install was not completed as it should. To solve the problem, we removed the MSSQL.x (x is a number between 1 and 100) containing sub keys with a value point to the drive missing. You can find these MSSQL.x keys in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

Kind regards

Marcel

Wednesday, March 7, 2012

Error in installation SQL 2005 SP2 on 64 Bit Cluster.

I receive the below mentioned error message each time I try to install SP2 on SQL 2005 64 Bit Cluster:

Using PrevRegRootPath: Software\Microsoft\Microsoft SQL Server\MSSQL.2

GetServiceUserGroup failed for PLMCWSM01, 5

Error Code: 0x800706fd (1789)

Windows Error Text: The trust relationship between this workstation and the primary domain failed.

Source File Name: sqlca\sqlcax.cpp

Compiler Timestamp: Fri Feb 9 22:35:02 2007

Function Name: SetInstanceProperty

Source Line Number: 1223

MSI (s) (78!08) [01:05:21:864]: Transforming table Error.

MSI (s) (78!08) [01:05:21:989]: Transforming table Error.

MSI (s) (78!08) [01:05:21:989]: Note: 1: 2262 2: Error 3: -2147287038

MSI (s) (78!08) [01:05:21:989]: Product: Microsoft SQL Server 2005 (64-bit) -- Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.

Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.

Any Help on this would be highly appreciated.

Thanks

Anurag

Hi Anurag,

did you check this workarount: http://support.microsoft.com/kb/925976/en-us?

CU

tosc

Sunday, February 26, 2012

Error in DMX query

Hi

I have the following query used to predict the values in 2006 based on cluster model built using 2004 and 2005 data. I'm using a prediction join on a cube containing the data. I can join a single dimension from the cube to a column in a the data mining model. However when I try to join to a column in a nested table I get this error:

Executing the query ...

Obtained object of type: Microsoft.AnalysisServices.AdomdClient.AdomdDataReader

Internal error: An unexpected exception occured.

Execution complete

The query I'm running is this

select t.*

, Predict([Time].[Deal Count])as predicted_deal_count

, Predict([Time].[Deal Revenue])as predicted_deal_revenue

, Cluster()

From

[Time]

prediction join

(

select {[Measures].[Deal Count], [Measures].[Deal Revenue]} on 0,

non empty {{[Time].[Month Number Of Year].[Month Number Of Year].members} *

{[Country].[KeyCountry].[KeyCountry].members} * {[Country].[Region].[Region].members}} on 1

from [DM]

where ([Time].[Year].&[2006-01-01T00:00:00])) as t

on

[Time].[Month Number Of Year] = t.[[Time]].[Month Number Of Year]].[Month Number Of Year]].[MEMBER_CAPTION]]]

and [Time].[Country].[KeyCountry] = t.[[Country]].[KeyCountry]].[KeyCountry]].[MEMBER_CAPTION]]]

and [Time].[Country].[Region] = t.[[Country]].[Region]].[Region]].[MEMBER_CAPTION]]]

I'm running SQL Server 2005 with SP2 CTP2.

Thanks

Sanjay

Given the limited error message - we need to try additional queries to see if we can narrow the problem down. Alternatively, you could send us a backup of your database - let me know if this is an option.

Can you see if this query works? Does it return what you expect?

select t.*

From

[Time]

NATURAL prediction join

(

select {[Measures].[Deal Count], [Measures].[Deal Revenue]} on 0,

non empty {{[Time].[Month Number Of Year].[Month Number Of Year].members} *

{[Country].[KeyCountry].[KeyCountry].members} * {[Country].[Region].[Region].members}} on 1

from [DM]

where ([Time].[Year].&[2006-01-01T00:00:00])) as t

|||

Hi,

Your query works as expected, all the selected data from the cube is return. It would be possible to send you the cube offline, do you need the just the cube or the relational db as well?

Thanks

Sanjay

|||

A backup of AS database with the cube and model is enough. Please remove any additional objects (e.g. cubes or mining structures) to reduce the database size. You can also do a process clear structure only on the Mining Structure to reduce the size even further. Try compressing it as well (although it should be compressed already).

You can send the data to jamie "at" sqlserverdatamining.com and we'll look into the issue

Thanks!

|||We are still looking into this issue - thanks for your patience.