Hi,
I am installing sql 2005 on a two node cluster. I have managed to complete
the installation and then wanted to add the sql management studio on to the
cluster. I installed disk two and chose the support tools but have way
through the installation it failed with the following error:
Failed to install and configure assemblies C:\Program Files\Microsoft SQL
Server\90\NotificationServices\9.0.242\Bin\microso ft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The Transaction Manager is not available. (Exception from
HRESULT: 0x8004D01B)
I was installing this on the first node which had ownership of the shared
disks
Any ideas
Looks like you need to install a clustered instance of MSDTC.
http://www.microsoft.com/technet/prodtechnol/biztalk/2006/library/bts06clustering/55b0c81f-44a5-4069-b065-57df1cce19ac.mspx?mfr=true
Ignore the incoming caller stuff. That is for Biztalk.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:D07341A6-EDDA-4448-9C8A-23A1727E565B@.microsoft.com...
> Hi,
> I am installing sql 2005 on a two node cluster. I have managed to complete
> the installation and then wanted to add the sql management studio on to
> the
> cluster. I installed disk two and chose the support tools but have way
> through the installation it failed with the following error:
> Failed to install and configure assemblies C:\Program Files\Microsoft SQL
> Server\90\NotificationServices\9.0.242\Bin\microso ft.sqlserver.notificationservices.dll
> in the COM+ catalog. Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: The Transaction Manager is not available. (Exception
> from
> HRESULT: 0x8004D01B)
> I was installing this on the first node which had ownership of the shared
> disks
>
> Any ideas
Showing posts with label node. Show all posts
Showing posts with label node. Show all posts
Wednesday, March 28, 2012
Friday, March 23, 2012
Installing a local instance of SQL on a Cluster Node
Hi
I have an Active/Passive SQL 2000 Cluster - the OS is W3K Server.
I would like to install a local copy of SQL Server on the node that is
currently passive - if I start the SQL install process, it does give me
this option but I don't know what, if any, problems this might cause.
I appreciate if the currently active node fails, it will failover to
the node which also has a local version running as well.
Has anyone done this? I've tried searching groups and Microsoft without
success.
Thanks
Toby
It's OK to install local instances on cluster nodes. Just make sure the
instance name does not conflict with any instance on the cluster.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
<tjbeaumont@.gmail.com> wrote in message
news:1160036955.164570.322690@.i3g2000cwc.googlegro ups.com...
Hi
I have an Active/Passive SQL 2000 Cluster - the OS is W3K Server.
I would like to install a local copy of SQL Server on the node that is
currently passive - if I start the SQL install process, it does give me
this option but I don't know what, if any, problems this might cause.
I appreciate if the currently active node fails, it will failover to
the node which also has a local version running as well.
Has anyone done this? I've tried searching groups and Microsoft without
success.
Thanks
Toby
|||<tjbeaumont@.gmail.com> wrote in message
news:1160036955.164570.322690@.i3g2000cwc.googlegro ups.com...
> Hi
> I have an Active/Passive SQL 2000 Cluster - the OS is W3K Server.
> I would like to install a local copy of SQL Server on the node that is
> currently passive - if I start the SQL install process, it does give me
> this option but I don't know what, if any, problems this might cause.
Yes, you can do it, but it is a violation of the HA spirit. Meaning, why in
the world would you want to screw around and do that when the company has
obviously felt that the other SQL instances (in the cluster) require HA?
Don't mess with the HA environment!
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
|||That's true for production clusters. But we install standalone SQL instances
on a clustered node all the time on our test clusters.
Linchi
"Russ Kaufmann" wrote:
> <tjbeaumont@.gmail.com> wrote in message
> news:1160036955.164570.322690@.i3g2000cwc.googlegro ups.com...
> Yes, you can do it, but it is a violation of the HA spirit. Meaning, why in
> the world would you want to screw around and do that when the company has
> obviously felt that the other SQL instances (in the cluster) require HA?
> Don't mess with the HA environment!
>
> --
> Russ Kaufmann
> MVP - Windows Server - Clustering
> ClusterHelp.com, a Microsoft Certified Gold Partner
> Web http://www.clusterhelp.com
> Blog http://msmvps.com/clusterhelp
>
>
|||"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:6B70403B-35CF-4773-9160-8FFC9DDC8638@.microsoft.com...
> That's true for production clusters. But we install standalone SQL
> instances
> on a clustered node all the time on our test clusters.
So, your test environment doesn't mirror production?
Actually, I can see doing that.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
I have an Active/Passive SQL 2000 Cluster - the OS is W3K Server.
I would like to install a local copy of SQL Server on the node that is
currently passive - if I start the SQL install process, it does give me
this option but I don't know what, if any, problems this might cause.
I appreciate if the currently active node fails, it will failover to
the node which also has a local version running as well.
Has anyone done this? I've tried searching groups and Microsoft without
success.
Thanks
Toby
It's OK to install local instances on cluster nodes. Just make sure the
instance name does not conflict with any instance on the cluster.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
<tjbeaumont@.gmail.com> wrote in message
news:1160036955.164570.322690@.i3g2000cwc.googlegro ups.com...
Hi
I have an Active/Passive SQL 2000 Cluster - the OS is W3K Server.
I would like to install a local copy of SQL Server on the node that is
currently passive - if I start the SQL install process, it does give me
this option but I don't know what, if any, problems this might cause.
I appreciate if the currently active node fails, it will failover to
the node which also has a local version running as well.
Has anyone done this? I've tried searching groups and Microsoft without
success.
Thanks
Toby
|||<tjbeaumont@.gmail.com> wrote in message
news:1160036955.164570.322690@.i3g2000cwc.googlegro ups.com...
> Hi
> I have an Active/Passive SQL 2000 Cluster - the OS is W3K Server.
> I would like to install a local copy of SQL Server on the node that is
> currently passive - if I start the SQL install process, it does give me
> this option but I don't know what, if any, problems this might cause.
Yes, you can do it, but it is a violation of the HA spirit. Meaning, why in
the world would you want to screw around and do that when the company has
obviously felt that the other SQL instances (in the cluster) require HA?
Don't mess with the HA environment!
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
|||That's true for production clusters. But we install standalone SQL instances
on a clustered node all the time on our test clusters.
Linchi
"Russ Kaufmann" wrote:
> <tjbeaumont@.gmail.com> wrote in message
> news:1160036955.164570.322690@.i3g2000cwc.googlegro ups.com...
> Yes, you can do it, but it is a violation of the HA spirit. Meaning, why in
> the world would you want to screw around and do that when the company has
> obviously felt that the other SQL instances (in the cluster) require HA?
> Don't mess with the HA environment!
>
> --
> Russ Kaufmann
> MVP - Windows Server - Clustering
> ClusterHelp.com, a Microsoft Certified Gold Partner
> Web http://www.clusterhelp.com
> Blog http://msmvps.com/clusterhelp
>
>
|||"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:6B70403B-35CF-4773-9160-8FFC9DDC8638@.microsoft.com...
> That's true for production clusters. But we install standalone SQL
> instances
> on a clustered node all the time on our test clusters.
So, your test environment doesn't mirror production?
Actually, I can see doing that.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
Installing a cluster on an existing instance of SQL 2000 SP3A
I have been "tapped" to install a passive node on an instance of SQL
that is not currently configured for clustering on a W2003. Can I
simply install clustering services on the current production instance,
then install a new instance on what would be the passive node? Then add
it via cluster admin?
Can I run cluster communications, heartbeat, etc on the public NICs..I
do not have two interfaces on each server.
Any information would be greatly appreciated as I have only done new
deployments and this being a prod server I do not want to try the trial
and error approach.
Thanks,
Hulicat
You can use the current active node as a cluster member. You can then
install a clustered instance of SQL and migrate the databases. The final
step is to turn off the original instance. Possible, Yes. Recommended, NO.
This entire project sounds like a low-availability solution. You are
reusing equipment instead of purchasing a certified cluster configuration.
The one-NIC cluster is possible but falls into the "worst practices"
category. Not having a test platform, even a virtual one, is asking for
even more trouble.
Clustering is a hardware and systems tool to help achieve increased system
availability. Shortcutting the hardware and the procedures will result in
lower availability rather than higher availability.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1162242129.910915.61910@.e3g2000cwe.googlegrou ps.com...
>I have been "tapped" to install a passive node on an instance of SQL
> that is not currently configured for clustering on a W2003. Can I
> simply install clustering services on the current production instance,
> then install a new instance on what would be the passive node? Then add
> it via cluster admin?
> Can I run cluster communications, heartbeat, etc on the public NICs..I
> do not have two interfaces on each server.
> Any information would be greatly appreciated as I have only done new
> deployments and this being a prod server I do not want to try the trial
> and error approach.
> Thanks,
> Hulicat
>
|||Thanks for that!
I am going tp lobby for new hardware or scratch the idea.
It's a small SPS portal.
Regards~~~
Geoff N. Hiten wrote:[vbcol=seagreen]
> You can use the current active node as a cluster member. You can then
> install a clustered instance of SQL and migrate the databases. The final
> step is to turn off the original instance. Possible, Yes. Recommended, NO.
> This entire project sounds like a low-availability solution. You are
> reusing equipment instead of purchasing a certified cluster configuration.
> The one-NIC cluster is possible but falls into the "worst practices"
> category. Not having a test platform, even a virtual one, is asking for
> even more trouble.
> Clustering is a hardware and systems tool to help achieve increased system
> availability. Shortcutting the hardware and the procedures will result in
> lower availability rather than higher availability.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Hulicat" <dennis_A_white@.yahoo.com> wrote in message
> news:1162242129.910915.61910@.e3g2000cwe.googlegrou ps.com...
that is not currently configured for clustering on a W2003. Can I
simply install clustering services on the current production instance,
then install a new instance on what would be the passive node? Then add
it via cluster admin?
Can I run cluster communications, heartbeat, etc on the public NICs..I
do not have two interfaces on each server.
Any information would be greatly appreciated as I have only done new
deployments and this being a prod server I do not want to try the trial
and error approach.
Thanks,
Hulicat
You can use the current active node as a cluster member. You can then
install a clustered instance of SQL and migrate the databases. The final
step is to turn off the original instance. Possible, Yes. Recommended, NO.
This entire project sounds like a low-availability solution. You are
reusing equipment instead of purchasing a certified cluster configuration.
The one-NIC cluster is possible but falls into the "worst practices"
category. Not having a test platform, even a virtual one, is asking for
even more trouble.
Clustering is a hardware and systems tool to help achieve increased system
availability. Shortcutting the hardware and the procedures will result in
lower availability rather than higher availability.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1162242129.910915.61910@.e3g2000cwe.googlegrou ps.com...
>I have been "tapped" to install a passive node on an instance of SQL
> that is not currently configured for clustering on a W2003. Can I
> simply install clustering services on the current production instance,
> then install a new instance on what would be the passive node? Then add
> it via cluster admin?
> Can I run cluster communications, heartbeat, etc on the public NICs..I
> do not have two interfaces on each server.
> Any information would be greatly appreciated as I have only done new
> deployments and this being a prod server I do not want to try the trial
> and error approach.
> Thanks,
> Hulicat
>
|||Thanks for that!
I am going tp lobby for new hardware or scratch the idea.
It's a small SPS portal.
Regards~~~
Geoff N. Hiten wrote:[vbcol=seagreen]
> You can use the current active node as a cluster member. You can then
> install a clustered instance of SQL and migrate the databases. The final
> step is to turn off the original instance. Possible, Yes. Recommended, NO.
> This entire project sounds like a low-availability solution. You are
> reusing equipment instead of purchasing a certified cluster configuration.
> The one-NIC cluster is possible but falls into the "worst practices"
> category. Not having a test platform, even a virtual one, is asking for
> even more trouble.
> Clustering is a hardware and systems tool to help achieve increased system
> availability. Shortcutting the hardware and the procedures will result in
> lower availability rather than higher availability.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Hulicat" <dennis_A_white@.yahoo.com> wrote in message
> news:1162242129.910915.61910@.e3g2000cwe.googlegrou ps.com...
Monday, March 19, 2012
Installation SQL Server 2k Cluster on Windows 2003 failed. Please help.
Hello group,
today we tried to install a SQL 2k cluster very unsuccessfully. Would
need your support.
What we have:
2 Server (node 1, node 2) with external storage installed as a cluster
(MSCS). Partitions are C (for node 1 and 2), e and q (quorum db) - both
on the external storage.
OS is Windows 2003 Enterprise
We copied the installfiles to C:\temp on node1 and made a share. Node2
can access this share.
Antivirus was disabled.
We started the installation with a domainaccount that has local
administrative rights on both nodes and can be started as a service.
As installation target for the program we chosed C:... and the data
should be stored on e:...
Installation started - we gave the virtual server a different name than
the cluster and a free ip adress. Both nodes were seen during the next
steps and we gave an instancename like "DECGNWSSQL20007". Licensing was
choosen as 2CPU.
When the server should start the installation, it immediately stopped
with the message: Setup failed to perform required operations on the
cluster nodes.
We don=B4t have any clue how to continue. Could need your help.
Thanks in advance
Stefan
The error message "Setup failed to perform required operations on the cluster nodes." is a generic message. To understand where the setup failed, one has to review the sqlstp.log (search for this on the node
where you ran the setup). Based on this file, you will know where the error occurred and then accordingly you may need to review additional logs like sqlstpN.log (where N is an integer) on one/both nodes,
sqlclstr.log, cluster.log.
For detailed information on troubleshooting setup failures on cluster, please review
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
The above webcast may not give you the solution but will give you steps that you can use to troubleshoot and find the solution using Microsoft Knowledge Base articles.
Also, make sure that you have all the pre-reqs of installing SQL 2K on Win2K3. A list of pre-reqs and other related info can be found at
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
If you need more help, feel free to post your questions.
HTH,
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,
what IU inbetween found out is that the installed Terminal Server caused
the problems. Now the installation starts fine, runs and finishes with
the message that the "Virtual server cannot go online". Then the
uninstall started automatically. Do you know more about this problem? Is
it why we try to install SP2 first and then to update to SP3?
Thanks in advance
Stefan
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||You cannot run a SQL Cluster and Terminal Server on the same system.
SQL Server 2000 cluster does not install on Windows Server 2003-based
computers where Terminal Services is installed
http://support.microsoft.com/default...b;en-us;301520
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Stefan Gsundbrunn" <info@.gsundbrunn.de> wrote in message
news:uPYXood7EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi,
> what IU inbetween found out is that the installed Terminal Server caused
> the problems. Now the installation starts fine, runs and finishes with
> the message that the "Virtual server cannot go online". Then the
> uninstall started automatically. Do you know more about this problem? Is
> it why we try to install SP2 first and then to update to SP3?
> Thanks in advance
> Stefan
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hi,
> You cannot run a SQL Cluster and Terminal Server on the same system.
Yes, as mentioned I deinstalled Terminal Server and then the installation
started. But: At the end of the installation the message appeared like
"Virtual server cannot go online" and automatically the desintallation
starts. I don′t have any clue for the reason. Does anybody know how to fix?
Thanks in advance!
Stefan
> SQL Server 2000 cluster does not install on Windows Server 2003-based
> computers where Terminal Services is installed
> http://support.microsoft.com/default...b;en-us;301520
>
--
Stefan Gsundbrunn
Project Design - Software Design - Brain Design
http://www.gsundbrunn.de
Cell: +49.173.3426906
|||Stefan,
Looks like the unattended installation on all cluster nodes succeeded and failed during the virtual resources creation step. Ofcourse check sqlstp.log to find out where exactly the issue is. If indeed it failed during the
virtual server resources section then you will need to review sqlclstr.log and cluster.log to get to the root cause.
Additional Information
=====================
TechNet Support WebCast:
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
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
today we tried to install a SQL 2k cluster very unsuccessfully. Would
need your support.
What we have:
2 Server (node 1, node 2) with external storage installed as a cluster
(MSCS). Partitions are C (for node 1 and 2), e and q (quorum db) - both
on the external storage.
OS is Windows 2003 Enterprise
We copied the installfiles to C:\temp on node1 and made a share. Node2
can access this share.
Antivirus was disabled.
We started the installation with a domainaccount that has local
administrative rights on both nodes and can be started as a service.
As installation target for the program we chosed C:... and the data
should be stored on e:...
Installation started - we gave the virtual server a different name than
the cluster and a free ip adress. Both nodes were seen during the next
steps and we gave an instancename like "DECGNWSSQL20007". Licensing was
choosen as 2CPU.
When the server should start the installation, it immediately stopped
with the message: Setup failed to perform required operations on the
cluster nodes.
We don=B4t have any clue how to continue. Could need your help.
Thanks in advance
Stefan
The error message "Setup failed to perform required operations on the cluster nodes." is a generic message. To understand where the setup failed, one has to review the sqlstp.log (search for this on the node
where you ran the setup). Based on this file, you will know where the error occurred and then accordingly you may need to review additional logs like sqlstpN.log (where N is an integer) on one/both nodes,
sqlclstr.log, cluster.log.
For detailed information on troubleshooting setup failures on cluster, please review
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
The above webcast may not give you the solution but will give you steps that you can use to troubleshoot and find the solution using Microsoft Knowledge Base articles.
Also, make sure that you have all the pre-reqs of installing SQL 2K on Win2K3. A list of pre-reqs and other related info can be found at
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
If you need more help, feel free to post your questions.
HTH,
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,
what IU inbetween found out is that the installed Terminal Server caused
the problems. Now the installation starts fine, runs and finishes with
the message that the "Virtual server cannot go online". Then the
uninstall started automatically. Do you know more about this problem? Is
it why we try to install SP2 first and then to update to SP3?
Thanks in advance
Stefan
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||You cannot run a SQL Cluster and Terminal Server on the same system.
SQL Server 2000 cluster does not install on Windows Server 2003-based
computers where Terminal Services is installed
http://support.microsoft.com/default...b;en-us;301520
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Stefan Gsundbrunn" <info@.gsundbrunn.de> wrote in message
news:uPYXood7EHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi,
> what IU inbetween found out is that the installed Terminal Server caused
> the problems. Now the installation starts fine, runs and finishes with
> the message that the "Virtual server cannot go online". Then the
> uninstall started automatically. Do you know more about this problem? Is
> it why we try to install SP2 first and then to update to SP3?
> Thanks in advance
> Stefan
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hi,
> You cannot run a SQL Cluster and Terminal Server on the same system.
Yes, as mentioned I deinstalled Terminal Server and then the installation
started. But: At the end of the installation the message appeared like
"Virtual server cannot go online" and automatically the desintallation
starts. I don′t have any clue for the reason. Does anybody know how to fix?
Thanks in advance!
Stefan
> SQL Server 2000 cluster does not install on Windows Server 2003-based
> computers where Terminal Services is installed
> http://support.microsoft.com/default...b;en-us;301520
>
--
Stefan Gsundbrunn
Project Design - Software Design - Brain Design
http://www.gsundbrunn.de
Cell: +49.173.3426906
|||Stefan,
Looks like the unattended installation on all cluster nodes succeeded and failed during the virtual resources creation step. Ofcourse check sqlstp.log to find out where exactly the issue is. If indeed it failed during the
virtual server resources section then you will need to review sqlclstr.log and cluster.log to get to the root cause.
Additional Information
=====================
TechNet Support WebCast:
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
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
Friday, February 24, 2012
Installation fails when creating virtual resource on node
Please Help
I have spent 2 full days trying to install SQL Server 2000 Failover
Clustering on a MS Windows 2003 Enterprise Edition Server, but the
installation will not start the SQL cluster resources and complete.
Firstly, my MS Clustering service is installed and working. It is a 2-node
cluster. Both nodes have MS Windows 2003 Enterprise Edition SP1 installed.
The only cluster resource I have defined is a physical Disk, which is
connected via SAN to a Fibre Channel Shared Disk Array.
Both nodes can see the shared disk and the cluster groups failover
successfully between each node.
There are no problems reported in my event viewer or cluster log.
Moving on to the SQL Server 2000 Installation, I am using SQL Server 2000
Enterprise Edition, May 2003 (SP2)*. I have followed the microsoft guide
(Chapter 12 - Failover Clustering) and made sure the preinstall requirements
are met (Netbios disabled on private network, services stopped/started, MSDTC
cluster resource added).
*note: I recieve an error which tells me that SQL Server 2000 SP2 is not
compatible with this version of Windows, and I must apply SP3 after
installation.
I then run the Database Server installation and choose the neccessary
options for a single-instance clustered database (virtual server, name, IP,
typical install...). I am using a domain user with local administrative
permissions. The installation gets as far as checking the cluster nodes, then
(says it) installs SQL Server Fulltext and then finally errors when creating
virtual cluster resources. The installer then rolls back.
The following error in the event log is the only event I get of "Error" type:
__________________________________________________ ___
Event Type:Error
Event Source:ClusSvc
Event Category:Failover Mgr
Event ID:1069
Date:08/09/2005
Time:17:48:43
User:N/A
Computer:PR-CC-DBCLUST1
Description:
Cluster resource 'SQL Server Fulltext' in Resource Group 'Group 0' failed.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
__________________________________________________ ____
Example of cluster log (node1):
__________________________________________________ ____
000005f8.000007f0::2005/09/08-09:13:20.142 INFO [FM] FmpPropagateGroupState:
Group 7264aab2-e8fc-4952-83d0-ab22e9887fa0 state = 0, persistent state = 0
00000860.00000cd8::2005/09/08-09:13:20.173 INFO [RM] RmpSetResourceStatus,
Posting state 4 notification for resource <SQL Server Fulltext (STORM_MTP)>
000005f8.0000086c::2005/09/08-09:13:20.173 INFO [FM] NotifyCallBackRoutine:
enqueuing event
000005f8.0000086c::2005/09/08-09:13:20.173 INFO [FM] Calling RmNotifyChanges
in monitor 0860.
000005f8.000007ec::2005/09/08-09:13:20.173 INFO [CP] CppResourceNotify for
resource SQL Server Fulltext (STORM_MTP)
000005f8.000007ec::2005/09/08-09:13:20.173 INFO [FM]
FmpRmDoHandleCriticalResourceStateChange: call InterlockedDecrement on
gdwQuoBlockingResources, Resource 10d6663d-d2e4-4845-b6c9-28c4d9be12a4
000005f8.000007f0::2005/09/08-09:13:20.173 WARN [FM]
FmpHandleResourceTransition: Resource Name =
10d6663d-d2e4-4845-b6c9-28c4d9be12a4 [SQL Server Fulltext (STORM_MTP)] old
state=129 new state=4
000005f8.000007f0::2005/09/08-09:13:20.173 WARN [FM]
FmpHandleResourceTransition: Resource failed, post a work item
00000860.00000cd8::2005/09/08-09:13:20.173 ERR Microsoft Search Service
Instance <SQL Server Fulltext (STORM_MTP)>: An error occurred during the
online operation for instance <SQL Server Fulltext (STORM_MTP)>: 80070002 -
The system cannot find the file specified.
__________________________________________________ __
Example of cluster log (node2):
__________________________________________________ __
__________________________________________________ __
To resolve this, I have tried:
0. Following the steps for this event in the help and support center.
1. Installing a local (non clustered) database and upgrading it to a
clustered database.
- the same problem exisits
2. Installing a local (non clustered) database and then installing a new
clustered database as a seperate named instance
- the same problem exisits
3. Installing a local (non clustered) database, installing SP3 and upgrading
it to a clustered database.
- the same problem exisits
4. Installing a local (non clustered) database, installing SP3 and then
installing a new clustered database as a seperate named instance
- the same problem exisits
5. Installing a local (non clustered) database, installing SP4 and upgrading
it to a clustered database.
- the same problem exisits
6. Installing a local (non clustered) database, installing SP4 and then
installing a new clustered database as a seperate named instance
- the same problem exisits
7. Installing SQL Server Fulltext service from SP3 prior to install.
- the same problem exisits
8. Selecting only node 1 of the cluster to install to (not selecting node 2).
9. Evicting node 2 and then installing solely to node 1.
10. Rebuilding the Cluster Service
I have not (yet) tried:
1. Uninstalling Windows Server 2003 Ent Ed SP1, then repeat previous steps
2. Rebuilding Windows.
To conclude, all of my hardware is HCL certified: HP MSA 1000 packaged
cluster (2 x ProLiant DL380 G4).
I am now getting worried that SQL Server might not be compatible with my
shared disk driver. Could this be possible?
Any solutions would be greatly appreciated. Thank you in advance.
DaleDBA wrote:
> Firstly, my MS Clustering service is installed and working. It is a
> 2-node cluster. Both nodes have MS Windows 2003 Enterprise Edition
> SP1 installed. The only cluster resource I have defined is a
> physical Disk, which is connected via SAN to a Fibre Channel Shared
> Disk Array.
Is this the quorum disk or the disk that you will use for SQL Server
instance?
Is there another disk resource other than the quorum disk?
Bye
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
|||Yes there is 1 other disk resource other than the Quorum.
"Luca Bianchi" wrote:
> DaleDBA wrote:
> Is this the quorum disk or the disk that you will use for SQL Server
> instance?
> Is there another disk resource other than the quorum disk?
> Bye
> --
> Luca Bianchi
> Microsoft MVP - SQL Server
> http://mvp.support.microsoft.com
>
>
|||Actually, you will need three seperate Cluster Resource Groups. Each group
will require its own Disk, IP, and Network Name resource:
1. Cluster Group: Quorum Disk.
2. MS DTC Group: MS DTC Disk.
3. SQL Server Group: SQL Server Disk(s).
Although, you can get by with just one disk for both the Quorum and MS DTC,
Microsoft recommends placing the MS DTC in its own reource group.
Furthermore, you will want at least three Disk resources for the SQL Server
group: one for your data, one for the transaction logs, and one for database
backups.
If your installation will be supporting multiple databases and/or a high
transaction volume, you may also want another disk to seperate out the
TempDB database data files and transaction logs from the other databases.
Sincerely,
Anthony Thomas
"DaleDBA" <DaleDBA@.discussions.microsoft.com> wrote in message
news:50396684-C9B2-46D9-9F71-31EC9F3F21AD@.microsoft.com...
Yes there is 1 other disk resource other than the Quorum.
"Luca Bianchi" wrote:
> DaleDBA wrote:
> Is this the quorum disk or the disk that you will use for SQL Server
> instance?
> Is there another disk resource other than the quorum disk?
> Bye
> --
> Luca Bianchi
> Microsoft MVP - SQL Server
> http://mvp.support.microsoft.com
>
>
|||Thanks for the disk recommendation. I had planned on using the Quorum as my
MS DTC disk resource.
I have actually tried both methods of setting up a resource group for MS DTC
and I have have tried using the Q drive also. None of these resolve my
original problem: the SQL Server installation is failing when
creating/bringing online virtual resources.
Is there an explanation/resolution for this? I have most recently tried
using an alias via named pipes, but this is not the solution either.
Thanks in advance
Dale
"Anthony Thomas" wrote:
> Actually, you will need three seperate Cluster Resource Groups. Each group
> will require its own Disk, IP, and Network Name resource:
> 1. Cluster Group: Quorum Disk.
> 2. MS DTC Group: MS DTC Disk.
> 3. SQL Server Group: SQL Server Disk(s).
> Although, you can get by with just one disk for both the Quorum and MS DTC,
> Microsoft recommends placing the MS DTC in its own reource group.
> Furthermore, you will want at least three Disk resources for the SQL Server
> group: one for your data, one for the transaction logs, and one for database
> backups.
> If your installation will be supporting multiple databases and/or a high
> transaction volume, you may also want another disk to seperate out the
> TempDB database data files and transaction logs from the other databases.
> Sincerely,
>
> Anthony Thomas
>
> --
> "DaleDBA" <DaleDBA@.discussions.microsoft.com> wrote in message
> news:50396684-C9B2-46D9-9F71-31EC9F3F21AD@.microsoft.com...
> Yes there is 1 other disk resource other than the Quorum.
> "Luca Bianchi" wrote:
>
>
|||I am repeatedly getting error in cluster log:
Instance <SQL Server Fulltext (STORM_MTP)>: An error occurred during the
online operation for instance <SQL Server Fulltext (STORM_MTP)>: 80070002 -
The system cannot find the file specified.
The Full text resource is failing and causing the installer to end.
I have installed mssearch on each node successfully
I have registered gathercl.dll successfully
"DaleDBA" wrote:
[vbcol=seagreen]
> Thanks for the disk recommendation. I had planned on using the Quorum as my
> MS DTC disk resource.
> I have actually tried both methods of setting up a resource group for MS DTC
> and I have have tried using the Q drive also. None of these resolve my
> original problem: the SQL Server installation is failing when
> creating/bringing online virtual resources.
> Is there an explanation/resolution for this? I have most recently tried
> using an alias via named pipes, but this is not the solution either.
> Thanks in advance
> Dale
>
> "Anthony Thomas" wrote:
|||Have you looked through the logs? There is a setup log in the WinNT or
Windows folder, depending on OS version. You shouldn't have to setup
MSSEARCH or FULLTEXT on your own. SQL Server 2000 does a pretty good job
installing on clusters; however, you do have to have the correct setup
beforehand. Read through the README doc and FAILOVER CLUSTER in Books
Online for the prerequesites.
I need to be able to see the messages in the setup log prior to this error
message. There will be three log files and two .iss files. A general log
file for the installation, and then the setup associated with each .iss
install on each node. They are all in the Windows/WinNT directories on each
node. Each time you run setup, the old copy has a numeric increment and
appended to the end of the file. The latest one will always be marked
setup.log, sqlsp.log, and setup.iss.
Sincerely,
Anthony Thomas
"DaleDBA" <DaleDBA@.discussions.microsoft.com> wrote in message
news:71DEED81-83EA-4663-8407-3FBBB74D895B@.microsoft.com...
I am repeatedly getting error in cluster log:
Instance <SQL Server Fulltext (STORM_MTP)>: An error occurred during the
online operation for instance <SQL Server Fulltext (STORM_MTP)>: 80070002 -
The system cannot find the file specified.
The Full text resource is failing and causing the installer to end.
I have installed mssearch on each node successfully
I have registered gathercl.dll successfully
"DaleDBA" wrote:
> Thanks for the disk recommendation. I had planned on using the Quorum as
my
> MS DTC disk resource.
> I have actually tried both methods of setting up a resource group for MS
DTC[vbcol=seagreen]
> and I have have tried using the Q drive also. None of these resolve my
> original problem: the SQL Server installation is failing when
> creating/bringing online virtual resources.
> Is there an explanation/resolution for this? I have most recently tried
> using an alias via named pipes, but this is not the solution either.
> Thanks in advance
> Dale
>
> "Anthony Thomas" wrote:
group[vbcol=seagreen]
DTC,[vbcol=seagreen]
Server[vbcol=seagreen]
database[vbcol=seagreen]
databases.[vbcol=seagreen]
|||sqlstp.log:
10:56:05 Begin Setup
10:56:05 8.00.194
10:56:05 Mode = Normal
10:56:05 ModeType = NORMAL
10:56:05 GetDefinitionEx returned: 0, Extended: 0x0
10:56:05 ValueFTS returned: 1
10:56:05 ValuePID returned: 1
10:56:05 ValueLic returned: 1
10:56:05 System: Windows NT Enterprise Server
10:56:05 SQL Server ProductType: Enterprise Edition [0x3]
10:56:05 IsNTCluster returned: 1
10:56:05 Begin Action: SetupInitialize
10:56:05 End Action SetupInitialize
10:56:05 Begin Action: SetupInstall
10:56:05 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
10:56:05 CommonFilesDir=C:\Program Files\Common Files
10:56:05 Windows Directory=C:\WINDOWS\
10:56:05 Program Files=C:\Program Files\
10:56:05 TEMPDIR=c:\Temp\
10:56:05 Begin Action: SetupInstall
10:56:05 digpid size : 256
10:56:05 digpid size : 164
10:56:05 Begin Action: CheckFixedRequirements
10:56:05 Platform ID: 0xf00000
10:56:05 Version: 5.2.3790
10:56:05 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.1830
10:56:05 End Action: CheckFixedRequirements
10:56:05 Begin Action: ShowDialogs
10:56:05 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
10:56:05 Begin Action ShowDialogsHlpr: 0x1
10:56:05 Begin Action: DialogShowSdWelcome
10:56:06 End Action DialogShowSdWelcome
10:56:06 Dialog 0x1 returned: 1
10:56:06 End Action ShowDialogsHlpr
10:56:06 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
10:56:06 Begin Action ShowDialogsHlpr: 0x2
10:56:06 Begin Action: DialogShowSdMachineName
10:56:13 ShowDlgMachine returned: 1
10:56:13 Name = PR-CC-DBSQLSVR, Type = 0x10000008
10:56:13 Begin Action: CheckRequirements
10:56:13 Processor Architecture: x86 (Pentium)
10:56:13 Service Pack: 256
10:56:13 ComputerName: PR-CC-DBCLUST2
10:56:13 User Name: dale warner
10:56:13 IsAllAccessAllowed returned: 1
10:56:13 OS Language: 0x409
10:56:13 End Action CheckRequirements
10:56:13 This combination of Package and Operating System allows a full
product install.
10:56:13 End Action DialogShowSdMachineName
10:56:13 begin ShowDialogsUpdateMask
10:56:13 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0
10:56:13 Updated Dialog Mask: 0xbf3c037, Disable Back = 0x1
10:56:13 Dialog 0x2 returned: 0
10:56:13 End Action ShowDialogsHlpr
10:56:13 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
10:56:13 Begin Action ShowDialogsHlpr: 0x4
10:56:13 Begin Action: DialogShowSdInstallMode
10:56:13 InstallMode : 0x1
10:56:13 End Action DialogShowSdInstallMode
10:56:13 begin ShowDialogsUpdateMask
10:56:13 nFullMask = 0xbf3c037, nCurrent = 0x4, nDirection = 1
10:56:13 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:13 Dialog 0x4 returned: 1
10:56:13 End Action ShowDialogsHlpr
10:56:13 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
10:56:13 Begin Action ShowDialogsHlpr: 0x10
10:56:13 Begin Action: DialogShowSdRegisterUserEx
10:56:14 End Action DialogShowSdRegisterUserEx
10:56:14 begin ShowDialogsUpdateMask
10:56:14 nFullMask = 0x1bf7c037, nCurrent = 0x10, nDirection = 1
10:56:14 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:14 Dialog 0x10 returned: 1
10:56:14 End Action ShowDialogsHlpr
10:56:14 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
10:56:14 Begin Action ShowDialogsHlpr: 0x20
10:56:14 Begin Action: DialogShowSdLicense
10:56:15 End Action DialogShowSdLicense
10:56:15 Dialog 0x20 returned: 1
10:56:15 End Action ShowDialogsHlpr
10:56:15 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14
10:56:15 Begin Action ShowDialogsHlpr: 0x4000
10:56:15 Begin Action: DialogShowSdVirtualServer
10:56:23 ShowDlgVirtualServer returned: 0
10:56:23 Ipaddress = 10.126.33.111,255.255.255.128,Public
10:56:23 szNewList = 10.126.33.111,255.255.255.128,Public
10:56:23 szModifiedList =
10:56:23 szRemovedList =
10:56:23 End Action DialogShowSdVirtualServer
10:56:23 begin ShowDialogsUpdateMask
10:56:23 nFullMask = 0x1bf7c037, nCurrent = 0x4000, nDirection = 1
10:56:23 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:23 Dialog 0x4000 returned: 1
10:56:23 End Action ShowDialogsHlpr
10:56:23 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15
10:56:23 Begin Action ShowDialogsHlpr: 0x8000
10:56:23 Begin Action : DialogShowSdDiskGroups
10:56:27 ShowDlgDiskGroups returned: 1
10:56:27 Disk Group = Group 0
10:56:27 End Action : DialogShowSdDiskGroups
10:56:27 begin ShowDialogsUpdateMask
10:56:27 nFullMask = 0x1bf7c037, nCurrent = 0x8000, nDirection = 1
10:56:27 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:27 Dialog 0x8000 returned: 1
10:56:27 End Action ShowDialogsHlpr
10:56:27 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16
10:56:27 Begin Action ShowDialogsHlpr: 0x10000
10:56:27 Begin Action: DialogShowSdClusterDef
10:56:28 ShowDlgClusterDef returned: 1
10:56:28 PrefOwners = PR-CC-DBCLUST2, NumIp = 1
10:56:28 Begin Action : ValidateNodeActions
10:56:28 Begin Action : ValidateNodeActions
10:56:28 End Action : ValidateNodeActions
10:56:28 End Action : ValidateNodeActions
10:56:28 End Action DialogShowSdClusterDef
10:56:28 begin ShowDialogsUpdateMask
10:56:28 nFullMask = 0x1bf7c037, nCurrent = 0x10000, nDirection = 1
10:56:28 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:28 Dialog 0x10000 returned: 1
10:56:28 End Action ShowDialogsHlpr
10:56:28 ShowDialogsGetDialog returned: nCurrent=0x20000,index=17
10:56:28 Begin Action ShowDialogsHlpr: 0x20000
10:56:28 Begin Action : Cluster Security - DlgAcct
10:56:33 ShowDlgAcct returned: 1
10:56:33 [DlgAccount]
10:56:33 Domain = UK
10:56:33 DomainAcct = Dale Warner
10:56:33 DomainPwd
10:56:33 Result = 1
10:56:33 End Action : Cluster Security - DlgAcct
10:56:33 begin ShowDialogsUpdateMask
10:56:33 nFullMask = 0x1bf7c037, nCurrent = 0x20000, nDirection = 1
10:56:33 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:33 Dialog 0x20000 returned: 1
10:56:33 End Action ShowDialogsHlpr
10:56:33 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
10:56:33 Begin Action ShowDialogsHlpr: 0x40000
10:56:33 Begin Action: DialogShowSdCliSvr
10:56:33 DisplaySystemPreReq
10:56:33 ShowDlgClientServerSelect returned: 1
10:56:33 Type : 0x2
10:56:33 End Action DialogShowSdCliSvr
10:56:33 begin ShowDialogsUpdateMask
10:56:33 nFullMask = 0x1bf7c037, nCurrent = 0x40000, nDirection = 1
10:56:33 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:56:33 Dialog 0x40000 returned: 1
10:56:33 End Action ShowDialogsHlpr
10:56:33 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
10:56:33 Begin Action ShowDialogsHlpr: 0x80000
10:56:33 Begin Action: DialogShowSdInstanceName
10:56:33 Begin Action: ShowDlgInstanceName
10:56:35 End Action: ShowDlgInstanceName
10:56:35 ShowDlgInstanceName returned : 1
10:56:35 InstanceName : MSSQLSERVER
10:56:37 CreateSetupTopology(PR-CC-DBSQLSVR), Handle : 0x1284090, returned : 0
10:56:37 CreateSetupTopology returned : 0, Handle : 0x1284090
10:56:37 Topology Type : 34, Return Value : 0
10:56:37 ST_GetPhysicalNode returned : 0, PNHandle : 0x12840e0
10:56:37 PN_EnumerateEx returned : 0
10:56:37 PN_GetSQLStates returned : 0, SqlStates : 0x0
10:56:37 PN_StartScan [0x12840e0] returned : 0
10:56:37 PN_GetNext [0x12840e0] returned : 18, Handle: [0x0]
10:56:37 No more items in enumeration.
10:56:37 ReleaseSetupTopology
10:56:37 End Action DialogShowSdInstanceName
10:56:37 begin ShowDialogsUpdateMask
10:56:37 nFullMask = 0x1bffc037, nCurrent = 0x80000, nDirection = 1
10:56:37 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:56:37 Dialog 0x80000 returned: 1
10:56:37 End Action ShowDialogsHlpr
10:56:37 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
10:56:37 Begin Action ShowDialogsHlpr: 0x100000
10:56:37 Begin Action: DialogShowSdSetupType
10:56:37 Begin Action: Setup Type
10:56:44 [SetupTypeSQL]
10:56:44 szDir = C:\Program Files\Microsoft SQL Server
10:56:44 szDir = C:\Program Files\Microsoft SQL Server
10:56:44 Result = 303
10:56:44 szDataDir = D:\Program Files\Microsoft SQL Server
10:56:44 szDataDir = D:\Program Files\Microsoft SQL Server
10:56:44 End Action: Setup Type
10:56:44 Setup Type: Custom (303)
10:56:44 End Action DialogShowSdSetupType
10:56:44 begin ShowDialogsUpdateMask
10:56:44 nFullMask = 0x1bffc037, nCurrent = 0x100000, nDirection = 303
10:56:44 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:56:44 Dialog 0x100000 returned: 303
10:56:44 End Action ShowDialogsHlpr
10:56:44 ShowDialogsGetDialog returned: nCurrent=0x200000,index=21
10:56:44 Begin Action ShowDialogsHlpr: 0x200000
10:56:44 Begin Action: DialogShowSdComponentMult
10:56:44 basesys = 0, baseinst = 0, basedata = 0
10:56:44 Begin Action: Component Handler
10:56:53 SQL program folder: C:\Program Files\Microsoft SQL Server\MSSQL
10:56:53 SQL data folder: D:\Program Files\Microsoft SQL Server\MSSQL
10:56:53 Windows system folder: C:\WINDOWS\system32\
10:56:53 Prog req: 38205, Data req: 34432, Sys req: 183105
10:56:53 Prog avail: 30259768, Data avail: 141671008, Sys avail: 30259768
10:56:53 Prog req vs. avail, 221310, 30259768
10:56:53 Data req vs. avail, 34432, 141671008
10:56:53 Sys req vs. avail, 183105, 30259768
10:56:53 DisplaySystemPreReq
10:56:53 [SQLComponentMult]
10:56:53 Component =
10:56:53 Result = 1
10:56:53 End Action: Component Handler
10:56:53 End Action DialogShowSdComponentMult
10:56:53 begin ShowDialogsUpdateMask
10:56:53 nFullMask = 0x1bffc037, nCurrent = 0x200000, nDirection = 1
10:56:53 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:56:53 Dialog 0x200000 returned: 1
10:56:53 End Action ShowDialogsHlpr
10:56:53 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
10:56:53 Begin Action ShowDialogsHlpr: 0x400000
10:56:53 Begin Action: DlgServices
10:56:58 ShowDlgServices returned: 1
10:56:58 [DlgServices]
10:56:58 Local-Domain= 61680
10:56:58 AutoStart= 0
10:56:58 SQLDomain= UK
10:56:58 SQLDomainAcct= Dale Warner
10:56:58 SQLDomainPwd
10:56:58 AgtDomain= UK
10:56:58 AgtDomainAcct= Dale Warner
10:56:58 AgtDomainPwd
10:56:58 Result= 1
10:56:58 End Action DlgServices
10:56:58 begin ShowDialogsUpdateMask
10:56:58 nFullMask = 0x1bffc037, nCurrent = 0x400000, nDirection = 1
10:56:58 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:56:58 Dialog 0x400000 returned: 1
10:56:58 End Action ShowDialogsHlpr
10:56:58 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
10:56:58 Begin Action ShowDialogsHlpr: 0x800000
10:56:58 Begin Action: DlgSQLSecurity
10:57:00 ShowDlgSQLSecurity returned: 1
10:57:00 LoginMode = 1,szPwd
10:57:00 End Action DlgSQLSecurity
10:57:00 begin ShowDialogsUpdateMask
10:57:00 nFullMask = 0x1bffc037, nCurrent = 0x800000, nDirection = 1
10:57:00 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:57:00 Dialog 0x800000 returned: 1
10:57:00 End Action ShowDialogsHlpr
10:57:00 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
10:57:00 Begin Action ShowDialogsHlpr: 0x1000000
10:57:00 Begin Action: DlgCollation
10:57:06 ShowDlgCollation returned: 1
10:57:06 collation_name = Latin1_General_CI_AS,locale_name =
Latin1_General,lcid = 0x409,SortId = 0,dwCompFlags = 0x30001
10:57:06 End Action DlgCollation
10:57:06 begin ShowDialogsUpdateMask
10:57:06 nFullMask = 0x1bffc037, nCurrent = 0x1000000, nDirection = 1
10:57:06 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:57:06 Dialog 0x1000000 returned: 1
10:57:06 End Action ShowDialogsHlpr
10:57:06 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
10:57:06 Begin Action ShowDialogsHlpr: 0x2000000
10:57:06 Begin Action: DlgNetwork
10:57:07 ShowDlgNetwork returned: 1
10:57:07 [DlgServerNetwork]
10:57:07 NetworkLibs = 255
10:57:07 TCPPort = 1433
10:57:07 TCPPrxy = Default
10:57:07 NMPPipeName = \\.\pipe\sql\query
10:57:07 Result = 1
10:57:07 End Action DlgNetwork
10:57:07 begin ShowDialogsUpdateMask
10:57:07 nFullMask = 0x1bffc037, nCurrent = 0x2000000, nDirection = 1
10:57:07 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:57:07 Dialog 0x2000000 returned: 1
10:57:07 End Action ShowDialogsHlpr
10:57:07 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
10:57:07 Begin Action ShowDialogsHlpr: 0x8000000
10:57:07 Begin Action: DialogShowSdStartCopy
10:57:09 End Action DialogShowSdStartCopy
10:57:09 begin ShowDialogsUpdateMask
10:57:09 nFullMask = 0x1bffc037, nCurrent = 0x8000000, nDirection = 1
10:57:09 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:57:09 Dialog 0x8000000 returned: 1
10:57:09 End Action ShowDialogsHlpr
10:57:09 ShowDialogsGetDialog returned: nCurrent=0x10000000,index=28
10:57:09 Begin Action ShowDialogsHlpr: 0x10000000
10:57:09 Begin Action: DialogShowSdLicenseMode
10:58:44 ShowDlgLicense returned: 1
10:58:44 ShowDlgLicense returned: LicenseMode = 2, LicenseLimit = 2
10:58:44 End Action DialogShowSdLicenseMode
10:58:44 Dialog 0x10000000 returned: 1
10:58:44 End Action ShowDialogsHlpr
10:58:44 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
10:58:44 End Action ShowDialogs
10:58:44 Setup is installing Microsoft Distributed Transaction Coordinator
(MSDTC) ...
10:58:44 c:\Temp\SqlSetup\Bin\cldtcstp.exe -SupportDir
"c:\Temp\SqlSetup\Bin" -DTCPkg "E:\x86\Other\dtcsetup.exe" -LogFile
"C:\WINDOWS\sqlstp.log" -CtxAcct "UK\Dale Warner" -CtxEPwd
10:58:46 Process Exit Code: (0)
10:58:46 Begin Action : ClusterSetupHelper
10:58:46 Begin Action : CreateClustISSFiles
10:58:46 End Action : CreateClustISSFiles
10:58:46 Begin Action : ClusterWriteRemIni
10:58:46 End Action : ClusterWriteRemIni
10:58:46 Begin Action : Run setup on cluster nodes
[args]
NumRemoteServers=1
Server.1=PR-CC-DBCLUST2
[Server.1]
NumRemoteServices=1
1.app=\\PR-CC-DBCLUST2\E$\x86\setup\setupsql.exe
1.server=PR-CC-DBCLUST2
1.script=\\PR-CC-DBCLUST2\admin$\PR-CC-DBCLUST2_MSSQLSERVER.iss
1.cmdlineformat=%s k=Nb k=Rm k=Cl -SMS -s -f
"\\PR-CC-DBCLUST2\E$\x86\setup\setup.ins" -f1 %s -f2
"\\PR-CC-DBCLUST2\admin$\setup.log" -e "stpsilnt._ex" -b -x "c:\Temp\"
1.user=UK\Dale Warner
1.password=09571c279df22ffb9c71
1.name=SQLSetup1
1.sqlsetup=Y
1.copyexe=cnvsvc1.exe
10:58:46 Setup is performing required operations on cluster nodes. This may
take a few minutes...
10:58:46 c:\Temp\SqlSetup\Bin\remsetup.exe C:\WINDOWS\remsetup.ini
11:02:08 Process Exit Code: (0)
11:02:08 Begin Action : GetRemsetupRetCode
11:02:08 Installation return status on PR-CC-DBCLUST2 : 0
11:02:08 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 09/13/05 10:58:46 ####
CThreadPool::RunUntilCompleteHlpr create thread, index=0
CThread::Run thread [0x40] created for execution.
CThreadPool::RunUntilCompleteHlpr start thread [0x40],index=0
CThread::Process [0x40]
Running '\\PR-CC-DBCLUST2\E$\x86\setup\setupsql.exe k=Nb k=Rm k=Cl -SMS -s
-f "\\PR-CC-DBCLUST2\E$\x86\setup\setup.ins" -f1
\\PR-CC-DBCLUST2\admin$\PR-CC-DBCLUST2_MSSQLSERVER.iss -f2
"\\PR-CC-DBCLUST2\admin$\setup.log" -e "stpsilnt._ex" -b -x "c:\Temp\"'
(PR-CC-DBCLUST2) ...
CProcess::RunUntilComplete [0x40] exit code: 0
Remote process exit code was '0' (PR-CC-DBCLUST2).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x40]
Thread [0x40] exit code: [0x0]
CThreadPool::RunUntilComplete returned 0
CThreadPool::RunUntilComplete execution level=1, need execution: 0
Disconnecting from remote machine (PR-CC-DBCLUST2)...
Service removed successfully.
Remote files could not be removed.
#### SQL Server Remote Setup - Stop Time 09/13/05 11:02:08 ####
11:02:08 End Action : Run setup on cluster nodes
11:02:08 SetClusterSecuritySQL (UK\Dale Warner) and (UK\Dale Warner)
returned: 0
11:02:08 Begin Action : CreateVirtualServerResources
11:02:46 End Action : CreateVirtualServerResources
11:02:50 The cluster resource failed to come online.If extended error
information was reported by the clustering service it can be obtained from
the event log.
11:02:56 DoUnClusterInstance returned: 0
11:02:56 Begin Action : ClusterErrorCleanup
11:02:58 CreateSetupTopology(PR-CC-DBSQLSVR), Handle : 0x1284090, returned : 0
11:02:58 CreateSetupTopology returned : 0, Handle : 0x1284090
11:02:58 Topology Type : 34, Return Value : 0
11:02:58 ST_GetPhysicalNode returned : 0, PNHandle : 0x12840e0
11:02:58 PN_EnumerateEx returned : 0
11:02:58 PN_GetSQLStates returned : 0, SqlStates : 0x0
11:02:58 PN_GetInstance for MSSQLSERVER [0x12840e0] returned : 1609
11:02:58 ReleaseSetupTopology
[args]
NumRemoteServers=1
Server.1=PR-CC-DBCLUST2
[Server.1]
NumRemoteServices=1
1.app=\\PR-CC-DBCLUST2\E$\x86\setup\setupsql.exe
1.server=PR-CC-DBCLUST2
1.script=
1.cmdlineformat=%s -u "C:\WINDOWS\ISUNINST.EXE" -f
"\\PR-CC-DBCLUST2\C$\Program Files\Microsoft SQL Server\MSSQL\uninst.isu" -C
"\\PR-CC-DBCLUST2\C$\Program Files\Microsoft SQL Server\MSSQL\sqlsun.dll" -m
"MSSQLSERVER.MIF" -i MSSQLSERVER -b
1.user=UK\Dale Warner
1.password=09571c279df22ffb9c71
1.name=SQLUninstall1
1.sqlsetup=
1.copyexe=cnvsvc1.exe
11:02:58 Setup is performing cleanup operations on cluster nodes and will
exit once the cleanup is complete...
11:02:58 c:\Temp\SqlSetup\Bin\remsetup.exe C:\WINDOWS\remsetup.ini
11:03:14 Process Exit Code: (3010) The requested operation is successful.
Changes will not be effective until the system is rebooted.
11:03:14 Begin Action : GetRemsetupRetCode
11:03:14 Uninstall status on PR-CC-DBCLUST2 (MSSQLSERVER.MIF) : 3010
11:03:14 Uninstall message on PR-CC-DBCLUST2 (MSSQLSERVER.MIF) : Uninstall
completed. Some elements could not be removed. You should manually remove
items related to the application.
11:03:14 One or more nodes of the cluster need to be rebooted
11:03:14 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 09/13/05 11:02:58 ####
CThreadPool::RunUntilCompleteHlpr create thread, index=0
CThread::Run thread [0x40] created for execution.
CThreadPool::RunUntilCompleteHlpr start thread [0x40],index=0
CThread::Process [0x40]
Running '\\PR-CC-DBCLUST2\E$\x86\setup\setupsql.exe -u
"C:\WINDOWS\ISUNINST.EXE" -f "\\PR-CC-DBCLUST2\C$\Program Files\Microsoft SQL
Server\MSSQL\uninst.isu" -C "\\PR-CC-DBCLUST2\C$\Program Files\Microsoft SQL
Server\MSSQL\sqlsun.dll" -m "MSSQLSERVER.MIF" -i MSSQLSERVER -b'
(PR-CC-DBCLUST2) ...
CProcess::RunUntilComplete [0x40] exit code: 3010
Remote process exit code was '3010' (PR-CC-DBCLUST2).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x40]
Thread [0x40] exit code: [0xbc2]
CThreadPool::RunUntilComplete returned 3010
CThreadPool::RunUntilComplete execution level=1, need execution: 0
Disconnecting from remote machine (PR-CC-DBCLUST2)...
Service removed successfully.
Remote files removed successfully.
#### SQL Server Remote Setup - Stop Time 09/13/05 11:03:14 ####
11:03:14 End Action : ClusterErrorCleanup
11:03:14 Begin Action : ClusterErrorCleanup
11:03:14 End Action : ClusterErrorCleanup
11:03:14 End Action : ClusterSetupHelper
|||sqlstp7.log continued...
Service "SQLSERVERAGENT" -Dependencies MSSQLSERVER -ExePath "C:\Program
Files\Microsoft SQL Server\MSSQL\binn\sqlagent.exe" -SvcAccount "UK\Dale
Warner" -SvcEPwd
11:02:06 Process Exit Code: (0)
11:02:06 SetupSQLExecSecurity returned: 0
11:02:06 PerfmonLoad returned: 0
11:02:06 C:\PROGRA~1\MICROS~1\80\Tools\Binn\dcomscm.exe /RegServer
11:02:06 Process Exit Code: (0)
11:02:06 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\sqldbreg.ex e -RegServer
11:02:06 Process Exit Code: (-2147312566) Error loading type library/DLL.
11:02:06 regsvr32.exe /s "C:\PROGRA~1\MICROS~1\80\COM\repldsui.dll"
11:02:06 Process Exit Code: (0)
11:02:06 **** File registered: C:\Program Files\Microsoft SQL
Server\80\COM\repldsui.dll
11:02:06 MSSearch ApplicationName: SQLServer
11:02:06 E:\x86\FullText\ftsetup.exe SQLServer UK\Dale Warner 1 0 1 0
11:02:06 E:\x86\FullText\ftsetup.exe SQLServer UK\Dale Warner 1 0 1 0
11:02:07 Process Exit Code: (0)
11:02:07 FulltextSetup returned: 0
11:02:07 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe
-i -lcid 1033
11:02:07 Process Exit Code: (0)
11:02:07 End Action PostSetupRegistry
11:02:07 Begin Action SetupFolders:
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Enterprise Manager
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Enterprise Manager
11:02:07 Tracking\Shortcuts\Enterprise Manager
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Query Analyzer
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Query Analyzer
11:02:07 Tracking\Shortcuts\Query Analyzer
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Profiler
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Profiler
11:02:07 Tracking\Shortcuts\Profiler
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Client Network Utility
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Client Network
Utility
11:02:07 Tracking\Shortcuts\Client Network Utility
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Configure SQL XML Support in IIS
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Configure SQL XML
Support in IIS
11:02:07 Tracking\Shortcuts\Configure SQL XML Support in IIS
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Import and Export Data
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Import and Export
Data
11:02:07 Tracking\Shortcuts\Import and Export Data
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Service Manager
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Service Manager
11:02:07 Tracking\Shortcuts\Service Manager
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Server Network Utility
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Server Network
Utility
11:02:07 Tracking\Shortcuts\Server Network Utility
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Books Online
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Books Online
11:02:07 Tracking\Shortcuts\Books Online
11:02:07 Microsoft SQL Server Folder refreshed.
11:02:07 End Action SetupFolders
11:02:07 Action CleanUpInstall:
11:02:07 Uninstall command: C:\WINDOWS\IsUninst.exe -f"C:\Program
Files\Microsoft SQL Server\MSSQL\Uninst.isu" -c"C:\Program Files\Microsoft
SQL Server\MSSQL\sqlsun.dll" -msql.mif i=MSSQLSERVER
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA4-5A21-11d2-9DAD-00C04F79D434}
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA5-5A21-11d2-9DAD-00C04F79D434}
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA6-5A21-11d2-9DAD-00C04F79D434}
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{6DC86044-0C71-11d3-9E18-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDA8-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA8-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDA9-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA9-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAA-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAA-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAB-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAB-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAC-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAC-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAD-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAD-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAF-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAF-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDB2-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDB2-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDBE-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDBF-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
11:02:07 StatsGenerate returned: 2
11:02:07 StatsGenerate (0x0,0x1,0xf00000,0x100,1033,303,0x0,0x1000000a,0, 0,0
11:02:07 StatsGenerate -1,dale warner)
11:02:07 Installation Succeeded
|||setup.iss
[InstallShield Silent]
Version=v5.00.000
File=Response File
[File Transfer]
OverwriteReadOnly=NoToAll
[DlgOrder]
Dlg0=SdWelcome-0
Count=20
Dlg1=DlgMachine-0
Dlg2=DlgInstallMode-0
Dlg3=SdRegisterUser-0
Dlg4=SdLicense-0
Dlg5=DlgVirtServer-0
Dlg6=DlgDiskGroups-0
Dlg7=DlgClusterDef-0
Dlg8=DlgAccount-0
Dlg9=DlgClientServer-0
Dlg10=DlgInstanceName-0
Dlg11=SetupTypeSQL-0
Dlg12=SdRemoteInfo-0
Dlg13=SQLComponentMult-0
Dlg14=DlgServices-0
Dlg15=DlgSQLSecurity-0
Dlg16=DlgCollation-0
Dlg17=DlgServerNetwork-0
Dlg18=SdStartCopy-0
Dlg19=SdFinish-0
[SdWelcome-0]
Result=1
[DlgMachine-0]
Name=PR-CC-DBSQLSVR
Type=268435466
Result=1
[DlgInstallMode-0]
Type=1
Result=1
[SdRegisterUser-0]
szName=STORM C&C
Result=1
[SdLicense-0]
Result=1
[DlgVirtServer-0]
VirtServerName=PR-CC-DBSQLSVR
IpAddresses=10.126.33.111,255.255.255.128,Public
Result=0
[DlgDiskGroups-0]
GroupName=Group 0
Result=1
[DlgClusterDef-0]
VirtServerName=PR-CC-DBSQLSVR
nNumNodes=1
Result=1
ClusterPrefOwners=PR-CC-DBCLUST2
[DlgAccount-0]
Domain=UK
DomainAcct=Dale Warner
DomainPwd=09571c279df22ffb9c71
Result=1
[DlgClientServer-0]
Type=2
Result=1
[DlgInstanceName-0]
InstanceName=MSSQLSERVER
Result=1
[SetupTypeSQL-0]
szDir=C:\Program Files\Microsoft SQL Server
Result=303
szDataDir=D:\Program Files\Microsoft SQL Server
SharedDataDir=D:\Program Files\Microsoft SQL Server
[SdRemoteInfo-0]
svEdit1=Dale Warner
svEdit2=09571c279df22ffb9c71
svEdit3=UK
svEdit4=PR-CC-DBSQLSVR
svEdit5=\\PR-CC-DBSQLSVR\C$\Program Files\Microsoft SQL Server
svEdit6=\\PR-CC-DBCLUST2\E$\x86\setup\
Result=1
[SQLComponentMult-0]
SQLProg\SQLServr\SCMDev-type=string
SQLProg\SQLServr\SCMDev-count=3
SQLProg\SQLServr\SCMDev-0=SQLProg\SQLServr\SCMDev\SCMh
SQLProg\SQLServr\SCMDev-1=SQLProg\SQLServr\SCMDev\SCMX86Lb
SQLProg\SQLServr\SCMDev-2=SQLProg\SQLServr\SCMDev\SCMALb
SQLProg\SQLServr-type=string
SQLProg\SQLServr-count=6
SQLProg\SQLServr-0=SQLProg\SQLServr\Help
SQLProg\SQLServr-1=SQLProg\SQLServr\SCMDev
SQLProg\SQLServr-2=SQLProg\SQLServr\Rs1033
SQLProg\SQLServr-3=SQLProg\SQLServr\RsIntl
SQLProg\SQLServr-4=SQLProg\SQLServr\ActiveX
SQLProg\SQLServr-5=SQLProg\SQLServr\System
SQLProg\UpgTools-type=string
SQLProg\UpgTools-count=5
SQLProg\UpgTools-0=SQLProg\UpgTools\UpgSys
SQLProg\UpgTools-1=SQLProg\UpgTools\ActiveX
SQLProg\UpgTools-2=SQLProg\UpgTools\Res1033
SQLProg\UpgTools-3=SQLProg\UpgTools\ResOther
SQLProg\UpgTools-4=SQLProg\UpgTools\Resld
SQLProg\ReplSupp-type=string
SQLProg\ReplSupp-count=4
SQLProg\ReplSupp-0=SQLProg\ReplSupp\ReplDat
SQLProg\ReplSupp-1=SQLProg\ReplSupp\RepComm
SQLProg\ReplSupp-2=SQLProg\ReplSupp\RepNoDk
SQLProg\ReplSupp-3=SQLProg\ReplSupp\ActiveX
SQLProg\SvrExt-type=string
SQLProg\SvrExt-count=3
SQLProg\SvrExt-0=SQLProg\SvrExt\Help
SQLProg\SvrExt-1=SQLProg\SvrExt\SvrExtRs
SQLProg\SvrExt-2=SQLProg\SvrExt\ResIntl
SQLProg\MSSearch-type=string
SQLProg\MSSearch-count=2
SQLProg\MSSearch-0=SQLProg\MSSearch\Help
SQLProg\MSSearch-1=SQLProg\MSSearch\ActiveX
SQLProg\Symbols-type=string
SQLProg\Symbols-count=2
SQLProg\Symbols-0=SQLProg\Symbols\EXE
SQLProg\Symbols-1=SQLProg\Symbols\DLL
SQLProg\Perfmon-type=string
SQLProg\Perfmon-count=1
SQLProg\Perfmon-0=SQLProg\Perfmon\System
SQLProg-type=string
SQLProg-count=15
SQLProg-0=SQLProg\SQLServr
SQLProg-1=SQLProg\UpgTools
SQLProg-2=SQLProg\ReplSupp
SQLProg-3=SQLProg\Install
SQLProg-4=SQLProg\System
SQLProg-5=SQLProg\SvrExt
SQLProg-6=SQLProg\Dat
SQLProg-7=SQLProg\DatSmpl
SQLProg-8=SQLProg\BaseSys
SQLProg-9=SQLProg\BaseBinn
SQLProg-10=SQLProg\MSSearch
SQLProg-11=SQLProg\BaseInst
SQLProg-12=SQLProg\Symbols
SQLProg-13=SQLProg\Perfmon
SQLProg-14=SQLProg\Root
MgtTool\SEM\ActiveX-type=string
MgtTool\SEM\ActiveX-count=2
MgtTool\SEM\ActiveX-0=MgtTool\SEM\ActiveX\Res1033
MgtTool\SEM\ActiveX-1=MgtTool\SEM\ActiveX\ResIntl
MgtTool\SEM\OLEDB-type=string
MgtTool\SEM\OLEDB-count=2
MgtTool\SEM\OLEDB-0=MgtTool\SEM\OLEDB\Res1033
MgtTool\SEM\OLEDB-1=MgtTool\SEM\OLEDB\ResIntl
MgtTool\SEM-type=string
MgtTool\SEM-count=12
MgtTool\SEM-0=MgtTool\SEM\HTML
MgtTool\SEM-1=MgtTool\SEM\MSD98
MgtTool\SEM-2=MgtTool\SEM\MSD98SYS
MgtTool\SEM-3=MgtTool\SEM\MSD98Res
MgtTool\SEM-4=MgtTool\SEM\MSD98Hlp
MgtTool\SEM-5=MgtTool\SEM\Help
MgtTool\SEM-6=MgtTool\SEM\Res1033
MgtTool\SEM-7=MgtTool\SEM\ResIntl
MgtTool\SEM-8=MgtTool\SEM\MSD98RsI
MgtTool\SEM-9=MgtTool\SEM\ActiveX
MgtTool\SEM-10=MgtTool\SEM\Scripts
MgtTool\SEM-11=MgtTool\SEM\OLEDB
MgtTool\Profiler-type=string
MgtTool\Profiler-count=3
MgtTool\Profiler-0=MgtTool\Profiler\Help
MgtTool\Profiler-1=MgtTool\Profiler\Res1033
MgtTool\Profiler-2=MgtTool\Profiler\ResIntl
MgtTool\Qryanlz-type=string
MgtTool\Qryanlz-count=3
MgtTool\Qryanlz-0=MgtTool\Qryanlz\Help
MgtTool\Qryanlz-1=MgtTool\Qryanlz\Res1033
MgtTool\Qryanlz-2=MgtTool\Qryanlz\ResIntl
MgtTool\Wzcnflct-type=string
MgtTool\Wzcnflct-count=4
MgtTool\Wzcnflct-0=MgtTool\Wzcnflct\WzcnHlp
MgtTool\Wzcnflct-1=MgtTool\Wzcnflct\Wzcn1033
MgtTool\Wzcnflct-2=MgtTool\Wzcnflct\WzcnOthr
MgtTool\Wzcnflct-3=MgtTool\Wzcnflct\WzcnCmn
MgtTool-type=string
MgtTool-count=7
MgtTool-0=MgtTool\SEM
MgtTool-1=MgtTool\Profiler
MgtTool-2=MgtTool\Qryanlz
MgtTool-3=MgtTool\DTCCLi
MgtTool-4=MgtTool\Wzcnflct
MgtTool-5=MgtTool\UtilSys
MgtTool-6=MgtTool\UtilBinn
Connect-type=string
Connect-count=1
Connect-0=Connect\ConnSys
Books\Bookso-type=string
Books\Bookso-count=1
Books\Bookso-0=Books\Bookso\Utils
Books-type=string
Books-count=1
Books-0=Books\Bookso
DevTools\Dbg Int-type=string
DevTools\Dbg Int-count=2
DevTools\Dbg Int-0=DevTools\Dbg Int\Dbg Int Common
DevTools\Dbg Int-1=DevTools\Dbg Int\EXE
DevTools-type=string
DevTools-count=1
DevTools-0=DevTools\Dbg Int
CoreRepl-type=string
CoreRepl-count=2
CoreRepl-0=CoreRepl\Res1033
CoreRepl-1=CoreRepl\ResIntl
Core-type=string
Core-count=2
Core-0=Core\Res1033
Core-1=Core\ResOther
Repostry-type=string
Repostry-count=3
Repostry-0=Repostry\RepstSys
Repostry-1=Repostry\Res1033
Repostry-2=Repostry\ResIntl
CoreMisc\ActiveX-type=string
CoreMisc\ActiveX-count=2
CoreMisc\ActiveX-0=CoreMisc\ActiveX\Res1033
CoreMisc\ActiveX-1=CoreMisc\ActiveX\ResIntl
CoreMisc-type=string
CoreMisc-count=2
CoreMisc-0=CoreMisc\ActiveX
CoreMisc-1=CoreMisc\Res1033
Monarch-type=string
Monarch-count=2
Monarch-0=Monarch\Monr1033
Monarch-1=Monarch\MonrIntl
CoreCOM-type=string
CoreCOM-count=2
CoreCOM-0=CoreCOM\Res1033
CoreCOM-1=CoreCOM\ResIntl
CoreTool-type=string
CoreTool-count=2
CoreTool-0=CoreTool\Res1033
CoreTool-1=CoreTool\ResOther
SFExt\ActiveX-type=string
SFExt\ActiveX-count=2
SFExt\ActiveX-0=SFExt\ActiveX\Res1033
SFExt\ActiveX-1=SFExt\ActiveX\ResIntl
SFExt-type=string
SFExt-count=3
SFExt-0=SFExt\ActiveX
SFExt-1=SFExt\Res1033
SFExt-2=SFExt\ResIntl
Trace-type=string
Trace-count=2
Trace-0=Trace\Res1033
Trace-1=Trace\ResOther
MC-type=string
MC-count=3
MC-0=MC\MC1033
MC-1=MC\MCIntl
MC-2=MC\Help
SQLMgr-type=string
SQLMgr-count=2
SQLMgr-0=SQLMgr\Res1033
SQLMgr-1=SQLMgr\ResIntl
SvrTool-type=string
SvrTool-count=2
SvrTool-0=SvrTool\Res1033
SvrTool-1=SvrTool\ResIntl
DTSUI-type=string
DTSUI-count=2
DTSUI-0=DTSUI\Res1033
DTSUI-1=DTSUI\ResIntl
MSOlap-type=string
MSOlap-count=2
MSOlap-0=MSOlap\Res1033
MSOlap-1=MSOlap\ResIntl
ATL-type=string
ATL-count=2
ATL-0=ATL\winnt
ATL-1=ATL\win9x
SQLAdHlp-type=string
SQLAdHlp-count=2
SQLAdHlp-0=SQLAdHlp\Res1033
SQLAdHlp-1=SQLAdHlp\ResOther
Component-type=string
Component-count=32
Component-0=SQLProg
Component-1=MgtTool
Component-2=Connect
Component-3=Books
Component-4=DevTools
Component-5=CoreRepl
Component-6=Core
Component-7=Repostry
Component-8=CoreMisc
Component-9=Monarch
Component-10=Jet
Component-11=CoreInst
Component-12=CoreCOM
Component-13=CoreTool
Component-14=DBLibCli
Component-15=SFExt
Component-16=Trace
Component-17=MiscCore
Component-18=MC
Component-19=ClstSys
Component-20=SQLMgr
Component-21=SvrTool
Component-22=DTSUI
Component-23=ClFTSys
Component-24=ClFtdata
Component-25=MSOlap
Component-26=ATL
Component-27=MFC42U
Component-28=VC
Component-29=VB
Component-30=OCX1
Component-31=SQLAdHlp
Result=1
[DlgServices-0]
Local-Domain=61680
AutoStart=0
SQLDomain=UK
SQLDomainAcct=Dale Warner
SQLDomainPwd=09571c279df22ffb9c71
AgtDomain=UK
AgtDomainAcct=Dale Warner
AgtDomainPwd=09571c279df22ffb9c71
Result=1
[DlgSQLSecurity-0]
LoginMode=1
Result=1
[DlgCollation-0]
collation_name=Latin1_General_CI_AS
Result=1
[DlgServerNetwork-0]
NetworkLibs=255
TCPPort=1433
TCPPrxy=Default
NMPPipeName=\\.\pipe\sql\query
Result=1
[SdStartCopy-0]
Result=1
[License]
LicenseMode=PERDEVICE
LicenseLimit=2
[SdFinish-0]
Result=1
bOpt1=0
bOpt2=0
I have spent 2 full days trying to install SQL Server 2000 Failover
Clustering on a MS Windows 2003 Enterprise Edition Server, but the
installation will not start the SQL cluster resources and complete.
Firstly, my MS Clustering service is installed and working. It is a 2-node
cluster. Both nodes have MS Windows 2003 Enterprise Edition SP1 installed.
The only cluster resource I have defined is a physical Disk, which is
connected via SAN to a Fibre Channel Shared Disk Array.
Both nodes can see the shared disk and the cluster groups failover
successfully between each node.
There are no problems reported in my event viewer or cluster log.
Moving on to the SQL Server 2000 Installation, I am using SQL Server 2000
Enterprise Edition, May 2003 (SP2)*. I have followed the microsoft guide
(Chapter 12 - Failover Clustering) and made sure the preinstall requirements
are met (Netbios disabled on private network, services stopped/started, MSDTC
cluster resource added).
*note: I recieve an error which tells me that SQL Server 2000 SP2 is not
compatible with this version of Windows, and I must apply SP3 after
installation.
I then run the Database Server installation and choose the neccessary
options for a single-instance clustered database (virtual server, name, IP,
typical install...). I am using a domain user with local administrative
permissions. The installation gets as far as checking the cluster nodes, then
(says it) installs SQL Server Fulltext and then finally errors when creating
virtual cluster resources. The installer then rolls back.
The following error in the event log is the only event I get of "Error" type:
__________________________________________________ ___
Event Type:Error
Event Source:ClusSvc
Event Category:Failover Mgr
Event ID:1069
Date:08/09/2005
Time:17:48:43
User:N/A
Computer:PR-CC-DBCLUST1
Description:
Cluster resource 'SQL Server Fulltext' in Resource Group 'Group 0' failed.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
__________________________________________________ ____
Example of cluster log (node1):
__________________________________________________ ____
000005f8.000007f0::2005/09/08-09:13:20.142 INFO [FM] FmpPropagateGroupState:
Group 7264aab2-e8fc-4952-83d0-ab22e9887fa0 state = 0, persistent state = 0
00000860.00000cd8::2005/09/08-09:13:20.173 INFO [RM] RmpSetResourceStatus,
Posting state 4 notification for resource <SQL Server Fulltext (STORM_MTP)>
000005f8.0000086c::2005/09/08-09:13:20.173 INFO [FM] NotifyCallBackRoutine:
enqueuing event
000005f8.0000086c::2005/09/08-09:13:20.173 INFO [FM] Calling RmNotifyChanges
in monitor 0860.
000005f8.000007ec::2005/09/08-09:13:20.173 INFO [CP] CppResourceNotify for
resource SQL Server Fulltext (STORM_MTP)
000005f8.000007ec::2005/09/08-09:13:20.173 INFO [FM]
FmpRmDoHandleCriticalResourceStateChange: call InterlockedDecrement on
gdwQuoBlockingResources, Resource 10d6663d-d2e4-4845-b6c9-28c4d9be12a4
000005f8.000007f0::2005/09/08-09:13:20.173 WARN [FM]
FmpHandleResourceTransition: Resource Name =
10d6663d-d2e4-4845-b6c9-28c4d9be12a4 [SQL Server Fulltext (STORM_MTP)] old
state=129 new state=4
000005f8.000007f0::2005/09/08-09:13:20.173 WARN [FM]
FmpHandleResourceTransition: Resource failed, post a work item
00000860.00000cd8::2005/09/08-09:13:20.173 ERR Microsoft Search Service
Instance <SQL Server Fulltext (STORM_MTP)>: An error occurred during the
online operation for instance <SQL Server Fulltext (STORM_MTP)>: 80070002 -
The system cannot find the file specified.
__________________________________________________ __
Example of cluster log (node2):
__________________________________________________ __
__________________________________________________ __
To resolve this, I have tried:
0. Following the steps for this event in the help and support center.
1. Installing a local (non clustered) database and upgrading it to a
clustered database.
- the same problem exisits
2. Installing a local (non clustered) database and then installing a new
clustered database as a seperate named instance
- the same problem exisits
3. Installing a local (non clustered) database, installing SP3 and upgrading
it to a clustered database.
- the same problem exisits
4. Installing a local (non clustered) database, installing SP3 and then
installing a new clustered database as a seperate named instance
- the same problem exisits
5. Installing a local (non clustered) database, installing SP4 and upgrading
it to a clustered database.
- the same problem exisits
6. Installing a local (non clustered) database, installing SP4 and then
installing a new clustered database as a seperate named instance
- the same problem exisits
7. Installing SQL Server Fulltext service from SP3 prior to install.
- the same problem exisits
8. Selecting only node 1 of the cluster to install to (not selecting node 2).
9. Evicting node 2 and then installing solely to node 1.
10. Rebuilding the Cluster Service
I have not (yet) tried:
1. Uninstalling Windows Server 2003 Ent Ed SP1, then repeat previous steps
2. Rebuilding Windows.
To conclude, all of my hardware is HCL certified: HP MSA 1000 packaged
cluster (2 x ProLiant DL380 G4).
I am now getting worried that SQL Server might not be compatible with my
shared disk driver. Could this be possible?
Any solutions would be greatly appreciated. Thank you in advance.
DaleDBA wrote:
> Firstly, my MS Clustering service is installed and working. It is a
> 2-node cluster. Both nodes have MS Windows 2003 Enterprise Edition
> SP1 installed. The only cluster resource I have defined is a
> physical Disk, which is connected via SAN to a Fibre Channel Shared
> Disk Array.
Is this the quorum disk or the disk that you will use for SQL Server
instance?
Is there another disk resource other than the quorum disk?
Bye
Luca Bianchi
Microsoft MVP - SQL Server
http://mvp.support.microsoft.com
|||Yes there is 1 other disk resource other than the Quorum.
"Luca Bianchi" wrote:
> DaleDBA wrote:
> Is this the quorum disk or the disk that you will use for SQL Server
> instance?
> Is there another disk resource other than the quorum disk?
> Bye
> --
> Luca Bianchi
> Microsoft MVP - SQL Server
> http://mvp.support.microsoft.com
>
>
|||Actually, you will need three seperate Cluster Resource Groups. Each group
will require its own Disk, IP, and Network Name resource:
1. Cluster Group: Quorum Disk.
2. MS DTC Group: MS DTC Disk.
3. SQL Server Group: SQL Server Disk(s).
Although, you can get by with just one disk for both the Quorum and MS DTC,
Microsoft recommends placing the MS DTC in its own reource group.
Furthermore, you will want at least three Disk resources for the SQL Server
group: one for your data, one for the transaction logs, and one for database
backups.
If your installation will be supporting multiple databases and/or a high
transaction volume, you may also want another disk to seperate out the
TempDB database data files and transaction logs from the other databases.
Sincerely,
Anthony Thomas
"DaleDBA" <DaleDBA@.discussions.microsoft.com> wrote in message
news:50396684-C9B2-46D9-9F71-31EC9F3F21AD@.microsoft.com...
Yes there is 1 other disk resource other than the Quorum.
"Luca Bianchi" wrote:
> DaleDBA wrote:
> Is this the quorum disk or the disk that you will use for SQL Server
> instance?
> Is there another disk resource other than the quorum disk?
> Bye
> --
> Luca Bianchi
> Microsoft MVP - SQL Server
> http://mvp.support.microsoft.com
>
>
|||Thanks for the disk recommendation. I had planned on using the Quorum as my
MS DTC disk resource.
I have actually tried both methods of setting up a resource group for MS DTC
and I have have tried using the Q drive also. None of these resolve my
original problem: the SQL Server installation is failing when
creating/bringing online virtual resources.
Is there an explanation/resolution for this? I have most recently tried
using an alias via named pipes, but this is not the solution either.
Thanks in advance
Dale
"Anthony Thomas" wrote:
> Actually, you will need three seperate Cluster Resource Groups. Each group
> will require its own Disk, IP, and Network Name resource:
> 1. Cluster Group: Quorum Disk.
> 2. MS DTC Group: MS DTC Disk.
> 3. SQL Server Group: SQL Server Disk(s).
> Although, you can get by with just one disk for both the Quorum and MS DTC,
> Microsoft recommends placing the MS DTC in its own reource group.
> Furthermore, you will want at least three Disk resources for the SQL Server
> group: one for your data, one for the transaction logs, and one for database
> backups.
> If your installation will be supporting multiple databases and/or a high
> transaction volume, you may also want another disk to seperate out the
> TempDB database data files and transaction logs from the other databases.
> Sincerely,
>
> Anthony Thomas
>
> --
> "DaleDBA" <DaleDBA@.discussions.microsoft.com> wrote in message
> news:50396684-C9B2-46D9-9F71-31EC9F3F21AD@.microsoft.com...
> Yes there is 1 other disk resource other than the Quorum.
> "Luca Bianchi" wrote:
>
>
|||I am repeatedly getting error in cluster log:
Instance <SQL Server Fulltext (STORM_MTP)>: An error occurred during the
online operation for instance <SQL Server Fulltext (STORM_MTP)>: 80070002 -
The system cannot find the file specified.
The Full text resource is failing and causing the installer to end.
I have installed mssearch on each node successfully
I have registered gathercl.dll successfully
"DaleDBA" wrote:
[vbcol=seagreen]
> Thanks for the disk recommendation. I had planned on using the Quorum as my
> MS DTC disk resource.
> I have actually tried both methods of setting up a resource group for MS DTC
> and I have have tried using the Q drive also. None of these resolve my
> original problem: the SQL Server installation is failing when
> creating/bringing online virtual resources.
> Is there an explanation/resolution for this? I have most recently tried
> using an alias via named pipes, but this is not the solution either.
> Thanks in advance
> Dale
>
> "Anthony Thomas" wrote:
|||Have you looked through the logs? There is a setup log in the WinNT or
Windows folder, depending on OS version. You shouldn't have to setup
MSSEARCH or FULLTEXT on your own. SQL Server 2000 does a pretty good job
installing on clusters; however, you do have to have the correct setup
beforehand. Read through the README doc and FAILOVER CLUSTER in Books
Online for the prerequesites.
I need to be able to see the messages in the setup log prior to this error
message. There will be three log files and two .iss files. A general log
file for the installation, and then the setup associated with each .iss
install on each node. They are all in the Windows/WinNT directories on each
node. Each time you run setup, the old copy has a numeric increment and
appended to the end of the file. The latest one will always be marked
setup.log, sqlsp.log, and setup.iss.
Sincerely,
Anthony Thomas
"DaleDBA" <DaleDBA@.discussions.microsoft.com> wrote in message
news:71DEED81-83EA-4663-8407-3FBBB74D895B@.microsoft.com...
I am repeatedly getting error in cluster log:
Instance <SQL Server Fulltext (STORM_MTP)>: An error occurred during the
online operation for instance <SQL Server Fulltext (STORM_MTP)>: 80070002 -
The system cannot find the file specified.
The Full text resource is failing and causing the installer to end.
I have installed mssearch on each node successfully
I have registered gathercl.dll successfully
"DaleDBA" wrote:
> Thanks for the disk recommendation. I had planned on using the Quorum as
my
> MS DTC disk resource.
> I have actually tried both methods of setting up a resource group for MS
DTC[vbcol=seagreen]
> and I have have tried using the Q drive also. None of these resolve my
> original problem: the SQL Server installation is failing when
> creating/bringing online virtual resources.
> Is there an explanation/resolution for this? I have most recently tried
> using an alias via named pipes, but this is not the solution either.
> Thanks in advance
> Dale
>
> "Anthony Thomas" wrote:
group[vbcol=seagreen]
DTC,[vbcol=seagreen]
Server[vbcol=seagreen]
database[vbcol=seagreen]
databases.[vbcol=seagreen]
|||sqlstp.log:
10:56:05 Begin Setup
10:56:05 8.00.194
10:56:05 Mode = Normal
10:56:05 ModeType = NORMAL
10:56:05 GetDefinitionEx returned: 0, Extended: 0x0
10:56:05 ValueFTS returned: 1
10:56:05 ValuePID returned: 1
10:56:05 ValueLic returned: 1
10:56:05 System: Windows NT Enterprise Server
10:56:05 SQL Server ProductType: Enterprise Edition [0x3]
10:56:05 IsNTCluster returned: 1
10:56:05 Begin Action: SetupInitialize
10:56:05 End Action SetupInitialize
10:56:05 Begin Action: SetupInstall
10:56:05 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir ...
10:56:05 CommonFilesDir=C:\Program Files\Common Files
10:56:05 Windows Directory=C:\WINDOWS\
10:56:05 Program Files=C:\Program Files\
10:56:05 TEMPDIR=c:\Temp\
10:56:05 Begin Action: SetupInstall
10:56:05 digpid size : 256
10:56:05 digpid size : 164
10:56:05 Begin Action: CheckFixedRequirements
10:56:05 Platform ID: 0xf00000
10:56:05 Version: 5.2.3790
10:56:05 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.1830
10:56:05 End Action: CheckFixedRequirements
10:56:05 Begin Action: ShowDialogs
10:56:05 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
10:56:05 Begin Action ShowDialogsHlpr: 0x1
10:56:05 Begin Action: DialogShowSdWelcome
10:56:06 End Action DialogShowSdWelcome
10:56:06 Dialog 0x1 returned: 1
10:56:06 End Action ShowDialogsHlpr
10:56:06 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
10:56:06 Begin Action ShowDialogsHlpr: 0x2
10:56:06 Begin Action: DialogShowSdMachineName
10:56:13 ShowDlgMachine returned: 1
10:56:13 Name = PR-CC-DBSQLSVR, Type = 0x10000008
10:56:13 Begin Action: CheckRequirements
10:56:13 Processor Architecture: x86 (Pentium)
10:56:13 Service Pack: 256
10:56:13 ComputerName: PR-CC-DBCLUST2
10:56:13 User Name: dale warner
10:56:13 IsAllAccessAllowed returned: 1
10:56:13 OS Language: 0x409
10:56:13 End Action CheckRequirements
10:56:13 This combination of Package and Operating System allows a full
product install.
10:56:13 End Action DialogShowSdMachineName
10:56:13 begin ShowDialogsUpdateMask
10:56:13 nFullMask = 0x183000f7, nCurrent = 0x2, nDirection = 0
10:56:13 Updated Dialog Mask: 0xbf3c037, Disable Back = 0x1
10:56:13 Dialog 0x2 returned: 0
10:56:13 End Action ShowDialogsHlpr
10:56:13 ShowDialogsGetDialog returned: nCurrent=0x4,index=2
10:56:13 Begin Action ShowDialogsHlpr: 0x4
10:56:13 Begin Action: DialogShowSdInstallMode
10:56:13 InstallMode : 0x1
10:56:13 End Action DialogShowSdInstallMode
10:56:13 begin ShowDialogsUpdateMask
10:56:13 nFullMask = 0xbf3c037, nCurrent = 0x4, nDirection = 1
10:56:13 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:13 Dialog 0x4 returned: 1
10:56:13 End Action ShowDialogsHlpr
10:56:13 ShowDialogsGetDialog returned: nCurrent=0x10,index=4
10:56:13 Begin Action ShowDialogsHlpr: 0x10
10:56:13 Begin Action: DialogShowSdRegisterUserEx
10:56:14 End Action DialogShowSdRegisterUserEx
10:56:14 begin ShowDialogsUpdateMask
10:56:14 nFullMask = 0x1bf7c037, nCurrent = 0x10, nDirection = 1
10:56:14 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:14 Dialog 0x10 returned: 1
10:56:14 End Action ShowDialogsHlpr
10:56:14 ShowDialogsGetDialog returned: nCurrent=0x20,index=5
10:56:14 Begin Action ShowDialogsHlpr: 0x20
10:56:14 Begin Action: DialogShowSdLicense
10:56:15 End Action DialogShowSdLicense
10:56:15 Dialog 0x20 returned: 1
10:56:15 End Action ShowDialogsHlpr
10:56:15 ShowDialogsGetDialog returned: nCurrent=0x4000,index=14
10:56:15 Begin Action ShowDialogsHlpr: 0x4000
10:56:15 Begin Action: DialogShowSdVirtualServer
10:56:23 ShowDlgVirtualServer returned: 0
10:56:23 Ipaddress = 10.126.33.111,255.255.255.128,Public
10:56:23 szNewList = 10.126.33.111,255.255.255.128,Public
10:56:23 szModifiedList =
10:56:23 szRemovedList =
10:56:23 End Action DialogShowSdVirtualServer
10:56:23 begin ShowDialogsUpdateMask
10:56:23 nFullMask = 0x1bf7c037, nCurrent = 0x4000, nDirection = 1
10:56:23 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:23 Dialog 0x4000 returned: 1
10:56:23 End Action ShowDialogsHlpr
10:56:23 ShowDialogsGetDialog returned: nCurrent=0x8000,index=15
10:56:23 Begin Action ShowDialogsHlpr: 0x8000
10:56:23 Begin Action : DialogShowSdDiskGroups
10:56:27 ShowDlgDiskGroups returned: 1
10:56:27 Disk Group = Group 0
10:56:27 End Action : DialogShowSdDiskGroups
10:56:27 begin ShowDialogsUpdateMask
10:56:27 nFullMask = 0x1bf7c037, nCurrent = 0x8000, nDirection = 1
10:56:27 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:27 Dialog 0x8000 returned: 1
10:56:27 End Action ShowDialogsHlpr
10:56:27 ShowDialogsGetDialog returned: nCurrent=0x10000,index=16
10:56:27 Begin Action ShowDialogsHlpr: 0x10000
10:56:27 Begin Action: DialogShowSdClusterDef
10:56:28 ShowDlgClusterDef returned: 1
10:56:28 PrefOwners = PR-CC-DBCLUST2, NumIp = 1
10:56:28 Begin Action : ValidateNodeActions
10:56:28 Begin Action : ValidateNodeActions
10:56:28 End Action : ValidateNodeActions
10:56:28 End Action : ValidateNodeActions
10:56:28 End Action DialogShowSdClusterDef
10:56:28 begin ShowDialogsUpdateMask
10:56:28 nFullMask = 0x1bf7c037, nCurrent = 0x10000, nDirection = 1
10:56:28 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:28 Dialog 0x10000 returned: 1
10:56:28 End Action ShowDialogsHlpr
10:56:28 ShowDialogsGetDialog returned: nCurrent=0x20000,index=17
10:56:28 Begin Action ShowDialogsHlpr: 0x20000
10:56:28 Begin Action : Cluster Security - DlgAcct
10:56:33 ShowDlgAcct returned: 1
10:56:33 [DlgAccount]
10:56:33 Domain = UK
10:56:33 DomainAcct = Dale Warner
10:56:33 DomainPwd
10:56:33 Result = 1
10:56:33 End Action : Cluster Security - DlgAcct
10:56:33 begin ShowDialogsUpdateMask
10:56:33 nFullMask = 0x1bf7c037, nCurrent = 0x20000, nDirection = 1
10:56:33 Updated Dialog Mask: 0x1bf7c037, Disable Back = 0x1
10:56:33 Dialog 0x20000 returned: 1
10:56:33 End Action ShowDialogsHlpr
10:56:33 ShowDialogsGetDialog returned: nCurrent=0x40000,index=18
10:56:33 Begin Action ShowDialogsHlpr: 0x40000
10:56:33 Begin Action: DialogShowSdCliSvr
10:56:33 DisplaySystemPreReq
10:56:33 ShowDlgClientServerSelect returned: 1
10:56:33 Type : 0x2
10:56:33 End Action DialogShowSdCliSvr
10:56:33 begin ShowDialogsUpdateMask
10:56:33 nFullMask = 0x1bf7c037, nCurrent = 0x40000, nDirection = 1
10:56:33 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:56:33 Dialog 0x40000 returned: 1
10:56:33 End Action ShowDialogsHlpr
10:56:33 ShowDialogsGetDialog returned: nCurrent=0x80000,index=19
10:56:33 Begin Action ShowDialogsHlpr: 0x80000
10:56:33 Begin Action: DialogShowSdInstanceName
10:56:33 Begin Action: ShowDlgInstanceName
10:56:35 End Action: ShowDlgInstanceName
10:56:35 ShowDlgInstanceName returned : 1
10:56:35 InstanceName : MSSQLSERVER
10:56:37 CreateSetupTopology(PR-CC-DBSQLSVR), Handle : 0x1284090, returned : 0
10:56:37 CreateSetupTopology returned : 0, Handle : 0x1284090
10:56:37 Topology Type : 34, Return Value : 0
10:56:37 ST_GetPhysicalNode returned : 0, PNHandle : 0x12840e0
10:56:37 PN_EnumerateEx returned : 0
10:56:37 PN_GetSQLStates returned : 0, SqlStates : 0x0
10:56:37 PN_StartScan [0x12840e0] returned : 0
10:56:37 PN_GetNext [0x12840e0] returned : 18, Handle: [0x0]
10:56:37 No more items in enumeration.
10:56:37 ReleaseSetupTopology
10:56:37 End Action DialogShowSdInstanceName
10:56:37 begin ShowDialogsUpdateMask
10:56:37 nFullMask = 0x1bffc037, nCurrent = 0x80000, nDirection = 1
10:56:37 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:56:37 Dialog 0x80000 returned: 1
10:56:37 End Action ShowDialogsHlpr
10:56:37 ShowDialogsGetDialog returned: nCurrent=0x100000,index=20
10:56:37 Begin Action ShowDialogsHlpr: 0x100000
10:56:37 Begin Action: DialogShowSdSetupType
10:56:37 Begin Action: Setup Type
10:56:44 [SetupTypeSQL]
10:56:44 szDir = C:\Program Files\Microsoft SQL Server
10:56:44 szDir = C:\Program Files\Microsoft SQL Server
10:56:44 Result = 303
10:56:44 szDataDir = D:\Program Files\Microsoft SQL Server
10:56:44 szDataDir = D:\Program Files\Microsoft SQL Server
10:56:44 End Action: Setup Type
10:56:44 Setup Type: Custom (303)
10:56:44 End Action DialogShowSdSetupType
10:56:44 begin ShowDialogsUpdateMask
10:56:44 nFullMask = 0x1bffc037, nCurrent = 0x100000, nDirection = 303
10:56:44 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:56:44 Dialog 0x100000 returned: 303
10:56:44 End Action ShowDialogsHlpr
10:56:44 ShowDialogsGetDialog returned: nCurrent=0x200000,index=21
10:56:44 Begin Action ShowDialogsHlpr: 0x200000
10:56:44 Begin Action: DialogShowSdComponentMult
10:56:44 basesys = 0, baseinst = 0, basedata = 0
10:56:44 Begin Action: Component Handler
10:56:53 SQL program folder: C:\Program Files\Microsoft SQL Server\MSSQL
10:56:53 SQL data folder: D:\Program Files\Microsoft SQL Server\MSSQL
10:56:53 Windows system folder: C:\WINDOWS\system32\
10:56:53 Prog req: 38205, Data req: 34432, Sys req: 183105
10:56:53 Prog avail: 30259768, Data avail: 141671008, Sys avail: 30259768
10:56:53 Prog req vs. avail, 221310, 30259768
10:56:53 Data req vs. avail, 34432, 141671008
10:56:53 Sys req vs. avail, 183105, 30259768
10:56:53 DisplaySystemPreReq
10:56:53 [SQLComponentMult]
10:56:53 Component =
10:56:53 Result = 1
10:56:53 End Action: Component Handler
10:56:53 End Action DialogShowSdComponentMult
10:56:53 begin ShowDialogsUpdateMask
10:56:53 nFullMask = 0x1bffc037, nCurrent = 0x200000, nDirection = 1
10:56:53 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:56:53 Dialog 0x200000 returned: 1
10:56:53 End Action ShowDialogsHlpr
10:56:53 ShowDialogsGetDialog returned: nCurrent=0x400000,index=22
10:56:53 Begin Action ShowDialogsHlpr: 0x400000
10:56:53 Begin Action: DlgServices
10:56:58 ShowDlgServices returned: 1
10:56:58 [DlgServices]
10:56:58 Local-Domain= 61680
10:56:58 AutoStart= 0
10:56:58 SQLDomain= UK
10:56:58 SQLDomainAcct= Dale Warner
10:56:58 SQLDomainPwd
10:56:58 AgtDomain= UK
10:56:58 AgtDomainAcct= Dale Warner
10:56:58 AgtDomainPwd
10:56:58 Result= 1
10:56:58 End Action DlgServices
10:56:58 begin ShowDialogsUpdateMask
10:56:58 nFullMask = 0x1bffc037, nCurrent = 0x400000, nDirection = 1
10:56:58 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:56:58 Dialog 0x400000 returned: 1
10:56:58 End Action ShowDialogsHlpr
10:56:58 ShowDialogsGetDialog returned: nCurrent=0x800000,index=23
10:56:58 Begin Action ShowDialogsHlpr: 0x800000
10:56:58 Begin Action: DlgSQLSecurity
10:57:00 ShowDlgSQLSecurity returned: 1
10:57:00 LoginMode = 1,szPwd
10:57:00 End Action DlgSQLSecurity
10:57:00 begin ShowDialogsUpdateMask
10:57:00 nFullMask = 0x1bffc037, nCurrent = 0x800000, nDirection = 1
10:57:00 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:57:00 Dialog 0x800000 returned: 1
10:57:00 End Action ShowDialogsHlpr
10:57:00 ShowDialogsGetDialog returned: nCurrent=0x1000000,index=24
10:57:00 Begin Action ShowDialogsHlpr: 0x1000000
10:57:00 Begin Action: DlgCollation
10:57:06 ShowDlgCollation returned: 1
10:57:06 collation_name = Latin1_General_CI_AS,locale_name =
Latin1_General,lcid = 0x409,SortId = 0,dwCompFlags = 0x30001
10:57:06 End Action DlgCollation
10:57:06 begin ShowDialogsUpdateMask
10:57:06 nFullMask = 0x1bffc037, nCurrent = 0x1000000, nDirection = 1
10:57:06 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:57:06 Dialog 0x1000000 returned: 1
10:57:06 End Action ShowDialogsHlpr
10:57:06 ShowDialogsGetDialog returned: nCurrent=0x2000000,index=25
10:57:06 Begin Action ShowDialogsHlpr: 0x2000000
10:57:06 Begin Action: DlgNetwork
10:57:07 ShowDlgNetwork returned: 1
10:57:07 [DlgServerNetwork]
10:57:07 NetworkLibs = 255
10:57:07 TCPPort = 1433
10:57:07 TCPPrxy = Default
10:57:07 NMPPipeName = \\.\pipe\sql\query
10:57:07 Result = 1
10:57:07 End Action DlgNetwork
10:57:07 begin ShowDialogsUpdateMask
10:57:07 nFullMask = 0x1bffc037, nCurrent = 0x2000000, nDirection = 1
10:57:07 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:57:07 Dialog 0x2000000 returned: 1
10:57:07 End Action ShowDialogsHlpr
10:57:07 ShowDialogsGetDialog returned: nCurrent=0x8000000,index=27
10:57:07 Begin Action ShowDialogsHlpr: 0x8000000
10:57:07 Begin Action: DialogShowSdStartCopy
10:57:09 End Action DialogShowSdStartCopy
10:57:09 begin ShowDialogsUpdateMask
10:57:09 nFullMask = 0x1bffc037, nCurrent = 0x8000000, nDirection = 1
10:57:09 Updated Dialog Mask: 0x1bffc037, Disable Back = 0x1
10:57:09 Dialog 0x8000000 returned: 1
10:57:09 End Action ShowDialogsHlpr
10:57:09 ShowDialogsGetDialog returned: nCurrent=0x10000000,index=28
10:57:09 Begin Action ShowDialogsHlpr: 0x10000000
10:57:09 Begin Action: DialogShowSdLicenseMode
10:58:44 ShowDlgLicense returned: 1
10:58:44 ShowDlgLicense returned: LicenseMode = 2, LicenseLimit = 2
10:58:44 End Action DialogShowSdLicenseMode
10:58:44 Dialog 0x10000000 returned: 1
10:58:44 End Action ShowDialogsHlpr
10:58:44 ShowDialogsGetDialog returned: nCurrent=0x0,index=0
10:58:44 End Action ShowDialogs
10:58:44 Setup is installing Microsoft Distributed Transaction Coordinator
(MSDTC) ...
10:58:44 c:\Temp\SqlSetup\Bin\cldtcstp.exe -SupportDir
"c:\Temp\SqlSetup\Bin" -DTCPkg "E:\x86\Other\dtcsetup.exe" -LogFile
"C:\WINDOWS\sqlstp.log" -CtxAcct "UK\Dale Warner" -CtxEPwd
10:58:46 Process Exit Code: (0)
10:58:46 Begin Action : ClusterSetupHelper
10:58:46 Begin Action : CreateClustISSFiles
10:58:46 End Action : CreateClustISSFiles
10:58:46 Begin Action : ClusterWriteRemIni
10:58:46 End Action : ClusterWriteRemIni
10:58:46 Begin Action : Run setup on cluster nodes
[args]
NumRemoteServers=1
Server.1=PR-CC-DBCLUST2
[Server.1]
NumRemoteServices=1
1.app=\\PR-CC-DBCLUST2\E$\x86\setup\setupsql.exe
1.server=PR-CC-DBCLUST2
1.script=\\PR-CC-DBCLUST2\admin$\PR-CC-DBCLUST2_MSSQLSERVER.iss
1.cmdlineformat=%s k=Nb k=Rm k=Cl -SMS -s -f
"\\PR-CC-DBCLUST2\E$\x86\setup\setup.ins" -f1 %s -f2
"\\PR-CC-DBCLUST2\admin$\setup.log" -e "stpsilnt._ex" -b -x "c:\Temp\"
1.user=UK\Dale Warner
1.password=09571c279df22ffb9c71
1.name=SQLSetup1
1.sqlsetup=Y
1.copyexe=cnvsvc1.exe
10:58:46 Setup is performing required operations on cluster nodes. This may
take a few minutes...
10:58:46 c:\Temp\SqlSetup\Bin\remsetup.exe C:\WINDOWS\remsetup.ini
11:02:08 Process Exit Code: (0)
11:02:08 Begin Action : GetRemsetupRetCode
11:02:08 Installation return status on PR-CC-DBCLUST2 : 0
11:02:08 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 09/13/05 10:58:46 ####
CThreadPool::RunUntilCompleteHlpr create thread, index=0
CThread::Run thread [0x40] created for execution.
CThreadPool::RunUntilCompleteHlpr start thread [0x40],index=0
CThread::Process [0x40]
Running '\\PR-CC-DBCLUST2\E$\x86\setup\setupsql.exe k=Nb k=Rm k=Cl -SMS -s
-f "\\PR-CC-DBCLUST2\E$\x86\setup\setup.ins" -f1
\\PR-CC-DBCLUST2\admin$\PR-CC-DBCLUST2_MSSQLSERVER.iss -f2
"\\PR-CC-DBCLUST2\admin$\setup.log" -e "stpsilnt._ex" -b -x "c:\Temp\"'
(PR-CC-DBCLUST2) ...
CProcess::RunUntilComplete [0x40] exit code: 0
Remote process exit code was '0' (PR-CC-DBCLUST2).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x40]
Thread [0x40] exit code: [0x0]
CThreadPool::RunUntilComplete returned 0
CThreadPool::RunUntilComplete execution level=1, need execution: 0
Disconnecting from remote machine (PR-CC-DBCLUST2)...
Service removed successfully.
Remote files could not be removed.
#### SQL Server Remote Setup - Stop Time 09/13/05 11:02:08 ####
11:02:08 End Action : Run setup on cluster nodes
11:02:08 SetClusterSecuritySQL (UK\Dale Warner) and (UK\Dale Warner)
returned: 0
11:02:08 Begin Action : CreateVirtualServerResources
11:02:46 End Action : CreateVirtualServerResources
11:02:50 The cluster resource failed to come online.If extended error
information was reported by the clustering service it can be obtained from
the event log.
11:02:56 DoUnClusterInstance returned: 0
11:02:56 Begin Action : ClusterErrorCleanup
11:02:58 CreateSetupTopology(PR-CC-DBSQLSVR), Handle : 0x1284090, returned : 0
11:02:58 CreateSetupTopology returned : 0, Handle : 0x1284090
11:02:58 Topology Type : 34, Return Value : 0
11:02:58 ST_GetPhysicalNode returned : 0, PNHandle : 0x12840e0
11:02:58 PN_EnumerateEx returned : 0
11:02:58 PN_GetSQLStates returned : 0, SqlStates : 0x0
11:02:58 PN_GetInstance for MSSQLSERVER [0x12840e0] returned : 1609
11:02:58 ReleaseSetupTopology
[args]
NumRemoteServers=1
Server.1=PR-CC-DBCLUST2
[Server.1]
NumRemoteServices=1
1.app=\\PR-CC-DBCLUST2\E$\x86\setup\setupsql.exe
1.server=PR-CC-DBCLUST2
1.script=
1.cmdlineformat=%s -u "C:\WINDOWS\ISUNINST.EXE" -f
"\\PR-CC-DBCLUST2\C$\Program Files\Microsoft SQL Server\MSSQL\uninst.isu" -C
"\\PR-CC-DBCLUST2\C$\Program Files\Microsoft SQL Server\MSSQL\sqlsun.dll" -m
"MSSQLSERVER.MIF" -i MSSQLSERVER -b
1.user=UK\Dale Warner
1.password=09571c279df22ffb9c71
1.name=SQLUninstall1
1.sqlsetup=
1.copyexe=cnvsvc1.exe
11:02:58 Setup is performing cleanup operations on cluster nodes and will
exit once the cleanup is complete...
11:02:58 c:\Temp\SqlSetup\Bin\remsetup.exe C:\WINDOWS\remsetup.ini
11:03:14 Process Exit Code: (3010) The requested operation is successful.
Changes will not be effective until the system is rebooted.
11:03:14 Begin Action : GetRemsetupRetCode
11:03:14 Uninstall status on PR-CC-DBCLUST2 (MSSQLSERVER.MIF) : 3010
11:03:14 Uninstall message on PR-CC-DBCLUST2 (MSSQLSERVER.MIF) : Uninstall
completed. Some elements could not be removed. You should manually remove
items related to the application.
11:03:14 One or more nodes of the cluster need to be rebooted
11:03:14 End Action : GetRemsetupRetCode
#### SQL Server Remote Setup - Start Time 09/13/05 11:02:58 ####
CThreadPool::RunUntilCompleteHlpr create thread, index=0
CThread::Run thread [0x40] created for execution.
CThreadPool::RunUntilCompleteHlpr start thread [0x40],index=0
CThread::Process [0x40]
Running '\\PR-CC-DBCLUST2\E$\x86\setup\setupsql.exe -u
"C:\WINDOWS\ISUNINST.EXE" -f "\\PR-CC-DBCLUST2\C$\Program Files\Microsoft SQL
Server\MSSQL\uninst.isu" -C "\\PR-CC-DBCLUST2\C$\Program Files\Microsoft SQL
Server\MSSQL\sqlsun.dll" -m "MSSQLSERVER.MIF" -i MSSQLSERVER -b'
(PR-CC-DBCLUST2) ...
CProcess::RunUntilComplete [0x40] exit code: 3010
Remote process exit code was '3010' (PR-CC-DBCLUST2).
CThreadPool::RunUntilCompleteHlpr WaitForMultipleObjects returned: 0
CThreadPool::RunUntilCompleteHlpr signaled thread [0x40]
Thread [0x40] exit code: [0xbc2]
CThreadPool::RunUntilComplete returned 3010
CThreadPool::RunUntilComplete execution level=1, need execution: 0
Disconnecting from remote machine (PR-CC-DBCLUST2)...
Service removed successfully.
Remote files removed successfully.
#### SQL Server Remote Setup - Stop Time 09/13/05 11:03:14 ####
11:03:14 End Action : ClusterErrorCleanup
11:03:14 Begin Action : ClusterErrorCleanup
11:03:14 End Action : ClusterErrorCleanup
11:03:14 End Action : ClusterSetupHelper
|||sqlstp7.log continued...
Service "SQLSERVERAGENT" -Dependencies MSSQLSERVER -ExePath "C:\Program
Files\Microsoft SQL Server\MSSQL\binn\sqlagent.exe" -SvcAccount "UK\Dale
Warner" -SvcEPwd
11:02:06 Process Exit Code: (0)
11:02:06 SetupSQLExecSecurity returned: 0
11:02:06 PerfmonLoad returned: 0
11:02:06 C:\PROGRA~1\MICROS~1\80\Tools\Binn\dcomscm.exe /RegServer
11:02:06 Process Exit Code: (0)
11:02:06 C:\PROGRA~1\COMMON~1\MICROS~1\SQLDEB~1\sqldbreg.ex e -RegServer
11:02:06 Process Exit Code: (-2147312566) Error loading type library/DLL.
11:02:06 regsvr32.exe /s "C:\PROGRA~1\MICROS~1\80\COM\repldsui.dll"
11:02:06 Process Exit Code: (0)
11:02:06 **** File registered: C:\Program Files\Microsoft SQL
Server\80\COM\repldsui.dll
11:02:06 MSSearch ApplicationName: SQLServer
11:02:06 E:\x86\FullText\ftsetup.exe SQLServer UK\Dale Warner 1 0 1 0
11:02:06 E:\x86\FullText\ftsetup.exe SQLServer UK\Dale Warner 1 0 1 0
11:02:07 Process Exit Code: (0)
11:02:07 FulltextSetup returned: 0
11:02:07 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe
-i -lcid 1033
11:02:07 Process Exit Code: (0)
11:02:07 End Action PostSetupRegistry
11:02:07 Begin Action SetupFolders:
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Enterprise Manager
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Enterprise Manager
11:02:07 Tracking\Shortcuts\Enterprise Manager
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Query Analyzer
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Query Analyzer
11:02:07 Tracking\Shortcuts\Query Analyzer
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Profiler
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Profiler
11:02:07 Tracking\Shortcuts\Profiler
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Client Network Utility
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Client Network
Utility
11:02:07 Tracking\Shortcuts\Client Network Utility
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Configure SQL XML Support in IIS
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Configure SQL XML
Support in IIS
11:02:07 Tracking\Shortcuts\Configure SQL XML Support in IIS
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Import and Export Data
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Import and Export
Data
11:02:07 Tracking\Shortcuts\Import and Export Data
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Service Manager
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Service Manager
11:02:07 Tracking\Shortcuts\Service Manager
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Server Network Utility
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Server Network
Utility
11:02:07 Tracking\Shortcuts\Server Network Utility
11:02:07 C:\Documents and Settings\All Users\Start Menu\Programs\Microsoft
SQL Server\Books Online
11:02:07 Software\Microsoft\MSSQLServer\Tracking\Shortcuts\ Books Online
11:02:07 Tracking\Shortcuts\Books Online
11:02:07 Microsoft SQL Server Folder refreshed.
11:02:07 End Action SetupFolders
11:02:07 Action CleanUpInstall:
11:02:07 Uninstall command: C:\WINDOWS\IsUninst.exe -f"C:\Program
Files\Microsoft SQL Server\MSSQL\Uninst.isu" -c"C:\Program Files\Microsoft
SQL Server\MSSQL\sqlsun.dll" -msql.mif i=MSSQLSERVER
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA4-5A21-11d2-9DAD-00C04F79D434}
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA5-5A21-11d2-9DAD-00C04F79D434}
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA6-5A21-11d2-9DAD-00C04F79D434}
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{6DC86044-0C71-11d3-9E18-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDA8-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA8-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDA9-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDA9-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAA-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAA-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAB-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAB-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAC-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAC-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAD-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAD-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDAF-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDAF-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDB2-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDB2-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDBE-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
11:02:07 Software\Microsoft\Microsoft SQL
Server\80\Tools\Tracking\{E07FDDBF-5A21-11d2-9DAD-00C04F79D434} (1)
11:02:07
Software\Microsoft\MSSQLServer\Tracking\{E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
11:02:07 StatsGenerate returned: 2
11:02:07 StatsGenerate (0x0,0x1,0xf00000,0x100,1033,303,0x0,0x1000000a,0, 0,0
11:02:07 StatsGenerate -1,dale warner)
11:02:07 Installation Succeeded
|||setup.iss
[InstallShield Silent]
Version=v5.00.000
File=Response File
[File Transfer]
OverwriteReadOnly=NoToAll
[DlgOrder]
Dlg0=SdWelcome-0
Count=20
Dlg1=DlgMachine-0
Dlg2=DlgInstallMode-0
Dlg3=SdRegisterUser-0
Dlg4=SdLicense-0
Dlg5=DlgVirtServer-0
Dlg6=DlgDiskGroups-0
Dlg7=DlgClusterDef-0
Dlg8=DlgAccount-0
Dlg9=DlgClientServer-0
Dlg10=DlgInstanceName-0
Dlg11=SetupTypeSQL-0
Dlg12=SdRemoteInfo-0
Dlg13=SQLComponentMult-0
Dlg14=DlgServices-0
Dlg15=DlgSQLSecurity-0
Dlg16=DlgCollation-0
Dlg17=DlgServerNetwork-0
Dlg18=SdStartCopy-0
Dlg19=SdFinish-0
[SdWelcome-0]
Result=1
[DlgMachine-0]
Name=PR-CC-DBSQLSVR
Type=268435466
Result=1
[DlgInstallMode-0]
Type=1
Result=1
[SdRegisterUser-0]
szName=STORM C&C
Result=1
[SdLicense-0]
Result=1
[DlgVirtServer-0]
VirtServerName=PR-CC-DBSQLSVR
IpAddresses=10.126.33.111,255.255.255.128,Public
Result=0
[DlgDiskGroups-0]
GroupName=Group 0
Result=1
[DlgClusterDef-0]
VirtServerName=PR-CC-DBSQLSVR
nNumNodes=1
Result=1
ClusterPrefOwners=PR-CC-DBCLUST2
[DlgAccount-0]
Domain=UK
DomainAcct=Dale Warner
DomainPwd=09571c279df22ffb9c71
Result=1
[DlgClientServer-0]
Type=2
Result=1
[DlgInstanceName-0]
InstanceName=MSSQLSERVER
Result=1
[SetupTypeSQL-0]
szDir=C:\Program Files\Microsoft SQL Server
Result=303
szDataDir=D:\Program Files\Microsoft SQL Server
SharedDataDir=D:\Program Files\Microsoft SQL Server
[SdRemoteInfo-0]
svEdit1=Dale Warner
svEdit2=09571c279df22ffb9c71
svEdit3=UK
svEdit4=PR-CC-DBSQLSVR
svEdit5=\\PR-CC-DBSQLSVR\C$\Program Files\Microsoft SQL Server
svEdit6=\\PR-CC-DBCLUST2\E$\x86\setup\
Result=1
[SQLComponentMult-0]
SQLProg\SQLServr\SCMDev-type=string
SQLProg\SQLServr\SCMDev-count=3
SQLProg\SQLServr\SCMDev-0=SQLProg\SQLServr\SCMDev\SCMh
SQLProg\SQLServr\SCMDev-1=SQLProg\SQLServr\SCMDev\SCMX86Lb
SQLProg\SQLServr\SCMDev-2=SQLProg\SQLServr\SCMDev\SCMALb
SQLProg\SQLServr-type=string
SQLProg\SQLServr-count=6
SQLProg\SQLServr-0=SQLProg\SQLServr\Help
SQLProg\SQLServr-1=SQLProg\SQLServr\SCMDev
SQLProg\SQLServr-2=SQLProg\SQLServr\Rs1033
SQLProg\SQLServr-3=SQLProg\SQLServr\RsIntl
SQLProg\SQLServr-4=SQLProg\SQLServr\ActiveX
SQLProg\SQLServr-5=SQLProg\SQLServr\System
SQLProg\UpgTools-type=string
SQLProg\UpgTools-count=5
SQLProg\UpgTools-0=SQLProg\UpgTools\UpgSys
SQLProg\UpgTools-1=SQLProg\UpgTools\ActiveX
SQLProg\UpgTools-2=SQLProg\UpgTools\Res1033
SQLProg\UpgTools-3=SQLProg\UpgTools\ResOther
SQLProg\UpgTools-4=SQLProg\UpgTools\Resld
SQLProg\ReplSupp-type=string
SQLProg\ReplSupp-count=4
SQLProg\ReplSupp-0=SQLProg\ReplSupp\ReplDat
SQLProg\ReplSupp-1=SQLProg\ReplSupp\RepComm
SQLProg\ReplSupp-2=SQLProg\ReplSupp\RepNoDk
SQLProg\ReplSupp-3=SQLProg\ReplSupp\ActiveX
SQLProg\SvrExt-type=string
SQLProg\SvrExt-count=3
SQLProg\SvrExt-0=SQLProg\SvrExt\Help
SQLProg\SvrExt-1=SQLProg\SvrExt\SvrExtRs
SQLProg\SvrExt-2=SQLProg\SvrExt\ResIntl
SQLProg\MSSearch-type=string
SQLProg\MSSearch-count=2
SQLProg\MSSearch-0=SQLProg\MSSearch\Help
SQLProg\MSSearch-1=SQLProg\MSSearch\ActiveX
SQLProg\Symbols-type=string
SQLProg\Symbols-count=2
SQLProg\Symbols-0=SQLProg\Symbols\EXE
SQLProg\Symbols-1=SQLProg\Symbols\DLL
SQLProg\Perfmon-type=string
SQLProg\Perfmon-count=1
SQLProg\Perfmon-0=SQLProg\Perfmon\System
SQLProg-type=string
SQLProg-count=15
SQLProg-0=SQLProg\SQLServr
SQLProg-1=SQLProg\UpgTools
SQLProg-2=SQLProg\ReplSupp
SQLProg-3=SQLProg\Install
SQLProg-4=SQLProg\System
SQLProg-5=SQLProg\SvrExt
SQLProg-6=SQLProg\Dat
SQLProg-7=SQLProg\DatSmpl
SQLProg-8=SQLProg\BaseSys
SQLProg-9=SQLProg\BaseBinn
SQLProg-10=SQLProg\MSSearch
SQLProg-11=SQLProg\BaseInst
SQLProg-12=SQLProg\Symbols
SQLProg-13=SQLProg\Perfmon
SQLProg-14=SQLProg\Root
MgtTool\SEM\ActiveX-type=string
MgtTool\SEM\ActiveX-count=2
MgtTool\SEM\ActiveX-0=MgtTool\SEM\ActiveX\Res1033
MgtTool\SEM\ActiveX-1=MgtTool\SEM\ActiveX\ResIntl
MgtTool\SEM\OLEDB-type=string
MgtTool\SEM\OLEDB-count=2
MgtTool\SEM\OLEDB-0=MgtTool\SEM\OLEDB\Res1033
MgtTool\SEM\OLEDB-1=MgtTool\SEM\OLEDB\ResIntl
MgtTool\SEM-type=string
MgtTool\SEM-count=12
MgtTool\SEM-0=MgtTool\SEM\HTML
MgtTool\SEM-1=MgtTool\SEM\MSD98
MgtTool\SEM-2=MgtTool\SEM\MSD98SYS
MgtTool\SEM-3=MgtTool\SEM\MSD98Res
MgtTool\SEM-4=MgtTool\SEM\MSD98Hlp
MgtTool\SEM-5=MgtTool\SEM\Help
MgtTool\SEM-6=MgtTool\SEM\Res1033
MgtTool\SEM-7=MgtTool\SEM\ResIntl
MgtTool\SEM-8=MgtTool\SEM\MSD98RsI
MgtTool\SEM-9=MgtTool\SEM\ActiveX
MgtTool\SEM-10=MgtTool\SEM\Scripts
MgtTool\SEM-11=MgtTool\SEM\OLEDB
MgtTool\Profiler-type=string
MgtTool\Profiler-count=3
MgtTool\Profiler-0=MgtTool\Profiler\Help
MgtTool\Profiler-1=MgtTool\Profiler\Res1033
MgtTool\Profiler-2=MgtTool\Profiler\ResIntl
MgtTool\Qryanlz-type=string
MgtTool\Qryanlz-count=3
MgtTool\Qryanlz-0=MgtTool\Qryanlz\Help
MgtTool\Qryanlz-1=MgtTool\Qryanlz\Res1033
MgtTool\Qryanlz-2=MgtTool\Qryanlz\ResIntl
MgtTool\Wzcnflct-type=string
MgtTool\Wzcnflct-count=4
MgtTool\Wzcnflct-0=MgtTool\Wzcnflct\WzcnHlp
MgtTool\Wzcnflct-1=MgtTool\Wzcnflct\Wzcn1033
MgtTool\Wzcnflct-2=MgtTool\Wzcnflct\WzcnOthr
MgtTool\Wzcnflct-3=MgtTool\Wzcnflct\WzcnCmn
MgtTool-type=string
MgtTool-count=7
MgtTool-0=MgtTool\SEM
MgtTool-1=MgtTool\Profiler
MgtTool-2=MgtTool\Qryanlz
MgtTool-3=MgtTool\DTCCLi
MgtTool-4=MgtTool\Wzcnflct
MgtTool-5=MgtTool\UtilSys
MgtTool-6=MgtTool\UtilBinn
Connect-type=string
Connect-count=1
Connect-0=Connect\ConnSys
Books\Bookso-type=string
Books\Bookso-count=1
Books\Bookso-0=Books\Bookso\Utils
Books-type=string
Books-count=1
Books-0=Books\Bookso
DevTools\Dbg Int-type=string
DevTools\Dbg Int-count=2
DevTools\Dbg Int-0=DevTools\Dbg Int\Dbg Int Common
DevTools\Dbg Int-1=DevTools\Dbg Int\EXE
DevTools-type=string
DevTools-count=1
DevTools-0=DevTools\Dbg Int
CoreRepl-type=string
CoreRepl-count=2
CoreRepl-0=CoreRepl\Res1033
CoreRepl-1=CoreRepl\ResIntl
Core-type=string
Core-count=2
Core-0=Core\Res1033
Core-1=Core\ResOther
Repostry-type=string
Repostry-count=3
Repostry-0=Repostry\RepstSys
Repostry-1=Repostry\Res1033
Repostry-2=Repostry\ResIntl
CoreMisc\ActiveX-type=string
CoreMisc\ActiveX-count=2
CoreMisc\ActiveX-0=CoreMisc\ActiveX\Res1033
CoreMisc\ActiveX-1=CoreMisc\ActiveX\ResIntl
CoreMisc-type=string
CoreMisc-count=2
CoreMisc-0=CoreMisc\ActiveX
CoreMisc-1=CoreMisc\Res1033
Monarch-type=string
Monarch-count=2
Monarch-0=Monarch\Monr1033
Monarch-1=Monarch\MonrIntl
CoreCOM-type=string
CoreCOM-count=2
CoreCOM-0=CoreCOM\Res1033
CoreCOM-1=CoreCOM\ResIntl
CoreTool-type=string
CoreTool-count=2
CoreTool-0=CoreTool\Res1033
CoreTool-1=CoreTool\ResOther
SFExt\ActiveX-type=string
SFExt\ActiveX-count=2
SFExt\ActiveX-0=SFExt\ActiveX\Res1033
SFExt\ActiveX-1=SFExt\ActiveX\ResIntl
SFExt-type=string
SFExt-count=3
SFExt-0=SFExt\ActiveX
SFExt-1=SFExt\Res1033
SFExt-2=SFExt\ResIntl
Trace-type=string
Trace-count=2
Trace-0=Trace\Res1033
Trace-1=Trace\ResOther
MC-type=string
MC-count=3
MC-0=MC\MC1033
MC-1=MC\MCIntl
MC-2=MC\Help
SQLMgr-type=string
SQLMgr-count=2
SQLMgr-0=SQLMgr\Res1033
SQLMgr-1=SQLMgr\ResIntl
SvrTool-type=string
SvrTool-count=2
SvrTool-0=SvrTool\Res1033
SvrTool-1=SvrTool\ResIntl
DTSUI-type=string
DTSUI-count=2
DTSUI-0=DTSUI\Res1033
DTSUI-1=DTSUI\ResIntl
MSOlap-type=string
MSOlap-count=2
MSOlap-0=MSOlap\Res1033
MSOlap-1=MSOlap\ResIntl
ATL-type=string
ATL-count=2
ATL-0=ATL\winnt
ATL-1=ATL\win9x
SQLAdHlp-type=string
SQLAdHlp-count=2
SQLAdHlp-0=SQLAdHlp\Res1033
SQLAdHlp-1=SQLAdHlp\ResOther
Component-type=string
Component-count=32
Component-0=SQLProg
Component-1=MgtTool
Component-2=Connect
Component-3=Books
Component-4=DevTools
Component-5=CoreRepl
Component-6=Core
Component-7=Repostry
Component-8=CoreMisc
Component-9=Monarch
Component-10=Jet
Component-11=CoreInst
Component-12=CoreCOM
Component-13=CoreTool
Component-14=DBLibCli
Component-15=SFExt
Component-16=Trace
Component-17=MiscCore
Component-18=MC
Component-19=ClstSys
Component-20=SQLMgr
Component-21=SvrTool
Component-22=DTSUI
Component-23=ClFTSys
Component-24=ClFtdata
Component-25=MSOlap
Component-26=ATL
Component-27=MFC42U
Component-28=VC
Component-29=VB
Component-30=OCX1
Component-31=SQLAdHlp
Result=1
[DlgServices-0]
Local-Domain=61680
AutoStart=0
SQLDomain=UK
SQLDomainAcct=Dale Warner
SQLDomainPwd=09571c279df22ffb9c71
AgtDomain=UK
AgtDomainAcct=Dale Warner
AgtDomainPwd=09571c279df22ffb9c71
Result=1
[DlgSQLSecurity-0]
LoginMode=1
Result=1
[DlgCollation-0]
collation_name=Latin1_General_CI_AS
Result=1
[DlgServerNetwork-0]
NetworkLibs=255
TCPPort=1433
TCPPrxy=Default
NMPPipeName=\\.\pipe\sql\query
Result=1
[SdStartCopy-0]
Result=1
[License]
LicenseMode=PERDEVICE
LicenseLimit=2
[SdFinish-0]
Result=1
bOpt1=0
bOpt2=0
Sunday, February 19, 2012
Installation Error - Need some Help
Hello All:
Had a working SQL cluster but we had to uninstall SQL. When we go to
reinstall SQL (virtual server) on node 1, we get the following error.
"An error occured while creating SQL virtual server resources for
clustering. Setup could not connect to the database to update
cluster-specific information is the system tables."
Setup then goes to cleaning up etc and exits. However, SQL server is not
succesfully installed. I cannot find referrence to this error anywhere and
cannot figure out what the problem is. I would greatly appreciate any help.
Stan,
I see no one has answered you. I am having a similar problem with almost the same error message. The one I'm getting is more like:
"An error occured while creating SQL virtual server resources for
clustering. The specified module could not be found".
My problem is on a brand new cluster, both nodes working fine, passing all failover tests. This is on the initial installation attempt. I don't know what gives.
I am seeking help as well, but there aren't a whole lot of individuals out there that have gone down this path. What a piece of crap Microsoft has dumped on us now. Good luck in finding your answer.
"stan" wrote:
> Hello All:
> Had a working SQL cluster but we had to uninstall SQL. When we go to
> reinstall SQL (virtual server) on node 1, we get the following error.
> "An error occured while creating SQL virtual server resources for
> clustering. Setup could not connect to the database to update
> cluster-specific information is the system tables."
> Setup then goes to cleaning up etc and exits. However, SQL server is not
> succesfully installed. I cannot find referrence to this error anywhere and
> cannot figure out what the problem is. I would greatly appreciate any help.
>
>
|||Guy
I similar problem If you uninstall sql server and reinstall
it with same name make sure you do clean up record in
Wins and Dns server and replicate if you use AD.
good luck
>--Original Message--
>Stan,
>I see no one has answered you. I am having a similar
problem with almost the same error message. The one I'm
getting is more like:
>"An error occured while creating SQL virtual server
resources for
> clustering. The specified module could not be found".
>My problem is on a brand new cluster, both nodes working
fine, passing all failover tests. This is on the initial
installation attempt. I don't know what gives.
>I am seeking help as well, but there aren't a whole lot
of individuals out there that have gone down this path.
What a piece of crap Microsoft has dumped on us now. Good
luck in finding your answer.[vbcol=seagreen]
>"stan" wrote:
When we go to[vbcol=seagreen]
following error.[vbcol=seagreen]
resources for[vbcol=seagreen]
update[vbcol=seagreen]
SQL server is not[vbcol=seagreen]
this error anywhere and[vbcol=seagreen]
appreciate any help.
>.
>
|||Guy
I similar problem If you uninstall sql server and reinstall
it with same name make sure you do clean up record in
Wins and Dns server and replicate if you use AD.
good luck
>--Original Message--
>Stan,
>I see no one has answered you. I am having a similar
problem with almost the same error message. The one I'm
getting is more like:
>"An error occured while creating SQL virtual server
resources for
> clustering. The specified module could not be found".
>My problem is on a brand new cluster, both nodes working
fine, passing all failover tests. This is on the initial
installation attempt. I don't know what gives.
>I am seeking help as well, but there aren't a whole lot
of individuals out there that have gone down this path.
What a piece of crap Microsoft has dumped on us now. Good
luck in finding your answer.[vbcol=seagreen]
>"stan" wrote:
When we go to[vbcol=seagreen]
following error.[vbcol=seagreen]
resources for[vbcol=seagreen]
update[vbcol=seagreen]
SQL server is not[vbcol=seagreen]
this error anywhere and[vbcol=seagreen]
appreciate any help.
>.
>
Had a working SQL cluster but we had to uninstall SQL. When we go to
reinstall SQL (virtual server) on node 1, we get the following error.
"An error occured while creating SQL virtual server resources for
clustering. Setup could not connect to the database to update
cluster-specific information is the system tables."
Setup then goes to cleaning up etc and exits. However, SQL server is not
succesfully installed. I cannot find referrence to this error anywhere and
cannot figure out what the problem is. I would greatly appreciate any help.
Stan,
I see no one has answered you. I am having a similar problem with almost the same error message. The one I'm getting is more like:
"An error occured while creating SQL virtual server resources for
clustering. The specified module could not be found".
My problem is on a brand new cluster, both nodes working fine, passing all failover tests. This is on the initial installation attempt. I don't know what gives.
I am seeking help as well, but there aren't a whole lot of individuals out there that have gone down this path. What a piece of crap Microsoft has dumped on us now. Good luck in finding your answer.
"stan" wrote:
> Hello All:
> Had a working SQL cluster but we had to uninstall SQL. When we go to
> reinstall SQL (virtual server) on node 1, we get the following error.
> "An error occured while creating SQL virtual server resources for
> clustering. Setup could not connect to the database to update
> cluster-specific information is the system tables."
> Setup then goes to cleaning up etc and exits. However, SQL server is not
> succesfully installed. I cannot find referrence to this error anywhere and
> cannot figure out what the problem is. I would greatly appreciate any help.
>
>
|||Guy
I similar problem If you uninstall sql server and reinstall
it with same name make sure you do clean up record in
Wins and Dns server and replicate if you use AD.
good luck
>--Original Message--
>Stan,
>I see no one has answered you. I am having a similar
problem with almost the same error message. The one I'm
getting is more like:
>"An error occured while creating SQL virtual server
resources for
> clustering. The specified module could not be found".
>My problem is on a brand new cluster, both nodes working
fine, passing all failover tests. This is on the initial
installation attempt. I don't know what gives.
>I am seeking help as well, but there aren't a whole lot
of individuals out there that have gone down this path.
What a piece of crap Microsoft has dumped on us now. Good
luck in finding your answer.[vbcol=seagreen]
>"stan" wrote:
When we go to[vbcol=seagreen]
following error.[vbcol=seagreen]
resources for[vbcol=seagreen]
update[vbcol=seagreen]
SQL server is not[vbcol=seagreen]
this error anywhere and[vbcol=seagreen]
appreciate any help.
>.
>
|||Guy
I similar problem If you uninstall sql server and reinstall
it with same name make sure you do clean up record in
Wins and Dns server and replicate if you use AD.
good luck
>--Original Message--
>Stan,
>I see no one has answered you. I am having a similar
problem with almost the same error message. The one I'm
getting is more like:
>"An error occured while creating SQL virtual server
resources for
> clustering. The specified module could not be found".
>My problem is on a brand new cluster, both nodes working
fine, passing all failover tests. This is on the initial
installation attempt. I don't know what gives.
>I am seeking help as well, but there aren't a whole lot
of individuals out there that have gone down this path.
What a piece of crap Microsoft has dumped on us now. Good
luck in finding your answer.[vbcol=seagreen]
>"stan" wrote:
When we go to[vbcol=seagreen]
following error.[vbcol=seagreen]
resources for[vbcol=seagreen]
update[vbcol=seagreen]
SQL server is not[vbcol=seagreen]
this error anywhere and[vbcol=seagreen]
appreciate any help.
>.
>
Subscribe to:
Posts (Atom)