I have a Cluster of Windows 2003 Enterprise Edition, When I try to install a
SQL 2000 Enterprise Edition the setup option of Virtual Server appear
unavailable I only choose between Local Install or Remote.
Thanks for your help
Hi Alejandro,
Here are few things I would try:
1) Make sure that you are using SQL Server 2000 Enterprise Edition setup CD
2) Make sure that there are no mdf, ldf or ndf files on your local disks on both nodes
3) Make sure that you do not have another "default" instance of SQL Server/MSDE on the other node.
After taking care of the above things, try the upgrade. If it fails, then cut and paste the sqlstp.log to your post.
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,
1) Yes its SQL Server 2003 Enterprise Edition
2) There are not any MDF, NDF and LDF files (Just to be shure, this files
are SQL Files?)
3) I haven't any SQL Installed on the server
I follow this Steps but when I ran the setup the Virtual Server appear
dissable (Thanks for your help)
No.
Activity
Purpose
Expected Results
Results
1.
Reboot both nodes
They should come up with no error messages
2.
Check Event Viewer on each node and make sure there are no errors that
might interfere with the installation
3.
Check account permissions for the cluster account
Should be part of the Local Administrator group
4.
On each node, on the Start menu, click Run, and then type cmd in the
text box. Click OK.
Ping the Cluster IP Address from all nodes in the cluster; repeat for
each node
To verify that the private and public networks are communicating
properly
They should replay back
5.
Ping the cluster IP address from a computer not in the cluster
They should replay back
6.
Ping the Cluster Network Name from all nodes in the cluster
They should replay back
7.
Ping the Cluster Network Name from a computer not in the cluster
They should replay back
8.
Ping all Heartbead IP Addresses from all cluster nodes
They should replay back
9.
A domain account is available for SQL Server; check permissions for the
account; also the cluster administrator account must be created at the
domain level and must be an administrator of all nodes in the cluster
10.
All nodes have access to the installation path - we recommend to copy
the installation files locally on each node, especially for the services
pack and hotfix;
11.
In Cluster Administrator, for a two SQL Server instance installation,
create 4 groups and assign the correspondent resources to each group (such
as disk resources):
1.. MSDTC Group
2.. Cluster Group
3.. SQLServer Group1
4.. SQLServer Group2
12.
Using Cluster Administrator, test moving each group back and forth
between the two Nodes - check the owner
The owner should change
13.
While one Node owns all the groups, restart the other Node and check if
resource ownership was transferred to the other Node
The owner should change
14.
Check what resources belong to the Cluster Group
It should be: Cluster IP Address, Cluster Name, and Quorum Disk
15.
MSDTC Group
MS DTC should be in its own group; follow the following article to
configure MSDTC: 301600 - How to configure Microsoft Distributed Transaction
Coordinator on a Windows Server 2003 Cluster detailed in Appendix B
Regards, Alex
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:kOTjX3ZnEHA.2640@.cpmsftngxa06.phx.gbl...
> Hi Alejandro,
> Here are few things I would try:
> 1) Make sure that you are using SQL Server 2000 Enterprise Edition setup
> CD
> 2) Make sure that there are no mdf, ldf or ndf files on your local disks
> on both nodes
> 3) Make sure that you do not have another "default" instance of SQL
> Server/MSDE on the other node.
> After taking care of the above things, try the upgrade. If it fails, then
> cut and paste the sqlstp.log to your post.
> 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 Alejandro,
Please cut and paste sqlstp.log file (search for this file on the node where you ran sql server setup).
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
|||OK, I'm not in the office right now, but on monday I'm gona to attach this
log.
But first answere me something, If I never ran the setup completely, because
I never found the option of virtual Server available, which log I'm going to
cut an paste here? or If you just run the setup program click in the first
NEXT and then Cancel It (because the option virtual server is unavailable is
in gray) the sqlstp.log is generated?
Regards, Alex
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:nGonUGdnEHA.2932@.cpmsftngxa06.phx.gbl...
> Hi Alejandro,
> Please cut and paste sqlstp.log file (search for this file on the node
> where you ran sql server setup).
> 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
>
|||Yes, it will create sqlstp.log file.
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
|||please correct me if i'm wrong. I believe you have to create a name pipe, in
order for you to install sql on a virtual address. go to run and type in
cliconfg, click on alias and create.
Calvin
"Alejandro Garreta" <alejandro_garreta@.hotmail.com> wrote in message
news:eCmFPRbnEHA.392@.tk2msftngp13.phx.gbl...
> Hi,
> 1) Yes its SQL Server 2003 Enterprise Edition
> 2) There are not any MDF, NDF and LDF files (Just to be shure, this files
> are SQL Files?)
> 3) I haven't any SQL Installed on the server
> I follow this Steps but when I ran the setup the Virtual Server appear
> dissable (Thanks for your help)
>
> No.
> Activity
> Purpose
> Expected Results
> Results
> 1.
> Reboot both nodes
> They should come up with no error messages
>
> 2.
> Check Event Viewer on each node and make sure there are no errors
that
> might interfere with the installation
>
>
> 3.
> Check account permissions for the cluster account
> Should be part of the Local Administrator group
>
> 4.
> On each node, on the Start menu, click Run, and then type cmd in the
> text box. Click OK.
> Ping the Cluster IP Address from all nodes in the cluster; repeat
for
> each node
> To verify that the private and public networks are communicating
> properly
> They should replay back
>
> 5.
> Ping the cluster IP address from a computer not in the cluster
> They should replay back
>
> 6.
> Ping the Cluster Network Name from all nodes in the cluster
> They should replay back
>
> 7.
> Ping the Cluster Network Name from a computer not in the cluster
> They should replay back
>
> 8.
> Ping all Heartbead IP Addresses from all cluster nodes
> They should replay back
>
> 9.
> A domain account is available for SQL Server; check permissions for
the
> account; also the cluster administrator account must be created at the
> domain level and must be an administrator of all nodes in the cluster
>
>
> 10.
> All nodes have access to the installation path - we recommend to copy
> the installation files locally on each node, especially for the services
> pack and hotfix;
>
>
> 11.
> In Cluster Administrator, for a two SQL Server instance installation,
> create 4 groups and assign the correspondent resources to each group (such
> as disk resources):
> 1.. MSDTC Group
> 2.. Cluster Group
> 3.. SQLServer Group1
> 4.. SQLServer Group2
>
>
> 12.
> Using Cluster Administrator, test moving each group back and forth
> between the two Nodes - check the owner
>
> The owner should change
>
> 13.
> While one Node owns all the groups, restart the other Node and check
if
> resource ownership was transferred to the other Node
> The owner should change
>
> 14.
> Check what resources belong to the Cluster Group
> It should be: Cluster IP Address, Cluster Name, and Quorum Disk
>
> 15.
> MSDTC Group
> MS DTC should be in its own group; follow the following article to
> configure MSDTC: 301600 - How to configure Microsoft Distributed
Transaction[vbcol=seagreen]
> Coordinator on a Windows Server 2003 Cluster detailed in Appendix B
>
>
> Regards, Alex
> "Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
> news:kOTjX3ZnEHA.2640@.cpmsftngxa06.phx.gbl...
then[vbcol=seagreen]
Protection
>
|||Hello Calvin,
You need to create the named pipe alias only if you are installing a Named instance of SQL Server 2000 virtual server on Windows 2000 MSCS. For default instance, you
do not need to create the alias.
Here is the related Microsoft KB
Installation of a Named Instance of SQL Server 2000 Virtual Server on a Windows 2003-Based Cluster Fails
http://support.microssoft.com/?id=815431
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
|||Here is the LOG !!
10:52:09 Begin Setup
10:52:09 8.00.194
10:52:09 Mode = Normal
10:52:09 ModeType = NORMAL
10:52:09 GetDefinitionEx returned: 0, Extended: 0x0
10:52:09 ValueFTS returned: 1
10:52:09 ValuePID returned: 1
10:52:09 ValueLic returned: 0
10:52:09 System: Windows NT Enterprise Server
10:52:09 SQL Server ProductType: Personal Edition [0x2]
10:52:09 IsNTCluster returned: 1
10:52:09 Begin Action: SetupInitialize
10:52:09 End Action SetupInitialize
10:52:09 Begin Action: SetupInstall
10:52:09 Reading Software\Microsoft\Windows\CurrentVersion\CommonFi lesDir
...
10:52:09 CommonFilesDir=C:\Program Files\Common Files
10:52:09 Windows Directory=C:\WINDOWS\
10:52:09 Program Files=C:\Program Files\
10:52:09 TEMPDIR=C:\DOCUME~1\219701\LOCALS~1\Temp\2\
10:52:09 Begin Action: SetupInstall
10:52:09 digpid size : 256
10:52:09 digpid size : 164
10:52:09 Begin Action: CheckFixedRequirements
10:52:09 Platform ID: 0xf00000
10:52:09 Version: 5.2.3790
10:52:09 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.118
10:52:09 End Action: CheckFixedRequirements
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:6xtrCOfnEHA.3312@.cpmsftngxa06.phx.gbl...
> Yes, it will create sqlstp.log file.
> Best Regards,
> Uttam Parui
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
|||I'm not installing a named instance !!!
"Calvin Do" <calvin@.spinsonic.com> wrote in message
news:OeQAZH1nEHA.536@.TK2MSFTNGP11.phx.gbl...
> please correct me if i'm wrong. I believe you have to create a name pipe,
> in
> order for you to install sql on a virtual address. go to run and type in
> cliconfg, click on alias and create.
> Calvin
>
> "Alejandro Garreta" <alejandro_garreta@.hotmail.com> wrote in message
> news:eCmFPRbnEHA.392@.tk2msftngp13.phx.gbl...
> that
> for
> the
> if
> Transaction
> then
> Protection
>
