Installing sql: cluster

Showing posts with label cluster. Show all posts

Friday, March 30, 2012

Instances in Virtual SQL Servers

Can someone explain setting up instances in virtual SQL Servers? I know that you can have multiple virtual SQL Servers on a cluster, but does each default instance, or is it one default instance on the cluster no matter how many virtual servers you have?
Thank you.
On a cluster you get one default instance and 15 named instances OR 16 named
instances. Of course you don't have to create all the instances, these are
just maximum numbers. The number of hosts in the cluster doesn't matter
towards the instance count.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"walkman" <walkman@.discussions.microsoft.com> wrote in message
news:232E50F3-15CA-40DA-9ABA-4026EA8400B6@.microsoft.com...
> Can someone explain setting up instances in virtual SQL Servers? I know
that you can have multiple virtual SQL Servers on a cluster, but does each
default instance, or is it one default instance on the cluster no matter how
many virtual servers you have?
> Thank you.
|||Thank you. I was confused in that I thought each virtual machine would have its own default instance.
"Geoff N. Hiten" wrote:

> On a cluster you get one default instance and 15 named instances OR 16 named
> instances. Of course you don't have to create all the instances, these are
> just maximum numbers. The number of hosts in the cluster doesn't matter
> towards the instance count.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "walkman" <walkman@.discussions.microsoft.com> wrote in message
> news:232E50F3-15CA-40DA-9ABA-4026EA8400B6@.microsoft.com...
> that you can have multiple virtual SQL Servers on a cluster, but does each
> default instance, or is it one default instance on the cluster no matter how
> many virtual servers you have?
>
>
|||Each Virtual Server gets a single instance. It can be either a named
instance or a default instance, however only one such virtual server per
cluster can hold a default instance. This is because of how SQL stores the
binaries for each instance locally on each host node.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"walkman" <walkman@.discussions.microsoft.com> wrote in message
news:1C60B13E-E2CC-4001-ABD5-55665EE35419@.microsoft.com...
> Thank you. I was confused in that I thought each virtual machine would
have its own default instance.[vbcol=seagreen]
> "Geoff N. Hiten" wrote:
named[vbcol=seagreen]
are[vbcol=seagreen]
know[vbcol=seagreen]
each[vbcol=seagreen]
how[vbcol=seagreen]
|||Don't feel bad. You are not alone. This is confusing at the beginning.
Here are some additional references that you may find useful:
================================================== ====
Microsoft Whitepaper - SQL Server 2000 Failover Clustering
http://www.microsoft.com/SQL/techinf...vercluster.asp
Microsoft SQL Server 2000 High Availability Series
http://www.microsoft.com/technet/pro...y/sqlhalp.mspx
Microsoft Webcasts
Introduction to Microsoft SQL Server 2000 Clustering
http://support.microsoft.com/default...lurb051001.asp
Microsoft SQL Server 2000 Virtual Server: Things You Should Know
http://support.microsoft.com/default...lurb032602.asp
Microsoft SQL Server 2000 Virtual Server Basic Setup, Maintenance, and Service Pack
http://support.microsoft.com/default...lurb061002.asp
Microsoft SQL Server 2000 Failover Clustering Disaster Recovery Procedures
http://support.microsoft.com/default...lurb101802.asp
Troubleshooting SQL 2000 Virtual Server and Service Pack Setups for Failover Clustering
http://support.microsoft.com/default...lurb020703.asp
Q243218 INF: Installation Order for SQL 2000 Enterprise Edition
http://support.microsoft.com/?kbid=243218
Q260758 - INF: Frequently Asked Questions - SQL Server 2000 - Failover Clustering
http://support.microsoft.com/?kbid=260758
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

Instance wil not come online

2 out of 4 instances on my 3 node cluster wil not come online on one off
the clusternodes, unless I add an alias (which I removed after
installing sp3). The application eventlog complains about not being able
to connect to the instance. I can connect to the instance remotely, but
apparently the clusterservice can not. I can not find any differences in
the registry of files. Reinstalling sql did not help. Any ideas?
Hans
Hans de Bruin wrote:
> 2 out of 4 instances on my 3 node cluster wil not come online on one off
> the clusternodes, unless I add an alias (which I removed after
> installing sp3). The application eventlog complains about not being able
> to connect to the instance. I can connect to the instance remotely, but
> apparently the clusterservice can not. I can not find any differences in
> the registry of files. Reinstalling sql did not help. Any ideas?
>
udp 1434 isn't always responding. So when the is no entry in
hkey-local_machine\software\mssqlserverclient\..\lastco nnect on my
workstation osql wil not connect. All nodes and instances report to be
8.00.818 (sp3 + latest hotfix). accoording to netstat al de nodes are
listening to udp 0.0.0.0:1434. Could W2k3 still be blocking 1434 or is
there a problem with registering the instance with the udp thing?
Hans
|||Hans de Bruin wrote:
> Hans de Bruin wrote:
>
> udp 1434 isn't always responding. So when the is no entry in
> hkey-local_machine\software\mssqlserverclient\..\lastco nnect on my
> workstation osql wil not connect. All nodes and instances report to be
> 8.00.818 (sp3 + latest hotfix). accoording to netstat al de nodes are
> listening to udp 0.0.0.0:1434. Could W2k3 still be blocking 1434 or is
> there a problem with registering the instance with the udp thing?
>
hmm, on ether node:
clear the node of all sql instances:
clear the registry on the client.
fail over one sql instance to the node.
connect to the instance: success
fail over a second instance to the node
connect to the second instance: timout on udp 1434
clear the registry on the client.
connect to the fisrt instance again: success
move the fist instance to an other node.
connect to the fisrt second again: success
So I am only able to connect to the fist activated instance on a node
useing udp 1434. Where did I go wrong?
Hans
|||Hans,
I have seen a similar problem to yours in one of our clusters.
Can you post the errors in the eventlog.
Thanks,
PK
Message posted via http://www.sqlmonster.com
|||PK via SQLMonster.com wrote:
> Hans,
> I have seen a similar problem to yours in one of our clusters.
> Can you post the errors in the eventlog.
> Thanks,
> PK
>
It looks like this one:
http://groups.google.nl/groups?threa...GP11.phx. gbl
My instances were running without local admin rights. After I
fixed this, udp1434 was behaving normally, and I could remove the
alias on the clusternodes.
I want to run some of the instances without local admin rights so I can
give developers sysadmin rights on their instance without giving them
access to the whole system.
Hans
|||Hans de Bruin wrote:
> PK via SQLMonster.com wrote:
>
> It looks like this one:
> http://groups.google.nl/groups?threa...GP11.phx. gbl
oops try this one:
http://groups.google.nl/groups?threa...0a% 40phx.gbl

>
> My instances were running without local admin rights. After I
> fixed this, udp1434 was behaving normally, and I could remove the
> alias on the clusternodes.
> I want to run some of the instances without local admin rights so I can
> give developers sysadmin rights on their instance without giving them
> access to the whole system.
>
|||Hans de Bruin wrote:
> 2 out of 4 instances on my 3 node cluster wil not come online on one off
> the clusternodes, unless I add an alias (which I removed after
> installing sp3). The application eventlog complains about not being able
> to connect to the instance. I can connect to the instance remotely, but
> apparently the clusterservice can not. I can not find any differences in
> the registry of files. Reinstalling sql did not help. Any ideas?
>
Apparently what happens is this:
- i1 come online the node as non admin and takes hold of udp 1434
- the MSCS tries to connect to the i1 and requests for the portnumber.
- i1 looks in its own the reqistry and finds the port number.
- MSCS gets an anwser an connects. i1 is online.
- i2 tries to come online on the node as either admin or non admin.
- the MSCS tries to connect to the i2 and requests for the portnumber.
- i1 tries to looks in i2's reqistry and gets an access denied.
- MSCS does not get any anwser and makes interesing calls to wins and
dns, fails to figure out the portnumer or pipename and fails i2
- i3 tries to come online on the node as either admin or non admin.
- the MSCS tries to connect to the i3 and requests for the portnumber.
- i1 tries to looks in i3's reqistry and gets an access denied.
- MSCS does not get any anwser and makes interesing calls to wins and
dns, fails to figure out the portnumer or pipename and fails i3
...
conclussion:
When running multiple sql instances (clustered or not) sql needs to run
as an local admin or system account or you need to hack the registry
permissions to let udp 1434 work, or or you need create an alias on the
server and the clients so sqlserveragent and the clients can connect.
Hans

Instance name contains a dash

Hello

We are in the process of upgrading our SQL 2K server to a cluster environment. Currently the server is setup as a default instance running on a single box with log shipping as a warm backup

It is required to create an instance name for the new cluster to work. My question is

1) Has anybody tried to have an instance name that dash (-) in it.

Example: \\SERVERNAME\xxx-xx-xxx

I am told that it is not possible to have a server instance named this way. Would like to know if this naming convention is possible under SQL2K If not what is the suggested workaround

This will save a lot of time in application modifications

Thanks in advance

Gabe J

Don't do it, invest the work now and you will have a much more relaxing future. If it takes much time to modify your application to work with another instance name you probably have a design issue in your application.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks for the advice.

SQL 2000 books online does not specifically mention that dash (-) cannot be used in an instance name ( you can even create tables and other objects in a database that contains a dash in them why not instance name?). Could you please be a little more specific as what exactly the issues would be if the instance name contained dashes.

I have to justify the requirement to make program changes, for that I need to understand what the issues are going to be.

Appreciate your help

Gabe J

|||

I don′t have any specific issue in mind that I can tell of if you use special characters in instance names. Sure you can have special characters in Tables and other objects, but "What you can do" is often the opposite "What is prefered to do". As from my experience I wouldn′t bet on that horse and take the risk of naming the object or even the instance with special characters, although I can. Thats just my two cents, perhaps someone has another opinion about that, but unless you have a hand on your code and have the opportunity to correct that thing (as of my opinion) I would that effort in it.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

In general I agree with what Jens has to say. As far as I know, putting a dash in the instance name is supported. I remember back in the 7.0 days testers went to a lot of trouble to make sure that dashes worked fine in the server name. I don't remember finding any issues there (but it was a long time ago). I do seem to remember that our automation at the time needed multiple changes to run on those servers. :(

The effort was worth it for Microsoft but might not be for your arbitrary application.

|||

One of the suggestions made to get around with this issue is to place a registry hack by adding a key called "Connectto" in the following node

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSSQLServer\Client\

And specify the value as the OLD server name = "XXX-XX-XXX"

and data = DBNMPNTW,\\<New Server name>\pipe\MSSQL$<Instance name>\sql\query

When applications connect irrespective of the connection string, this registry value connects to the SQL server instance.

Seems to work . Agree this is just a workaround instead of solving the real issue of making application modifications.

Has anyone tried this ?

Thanks for you suggestions

|||

Not sure where you heard about this registry hack, but I would not recommend using it unless it was mentioned in a specific Microsoft article...This ***hack*** may not work after a future release. Looks like this workaround maybe setting up a alias for the server. If this is the case, you should use SQL Server Configuration Manager instead.

As others have said, I am not really sure if dashes are supported, but I would not use...SQL Server maybe able to handle it fine, but some other external component may not.

Thanks,

Peter Saddow

|||

Agree that this is a **hack**. The SQL Server is a 2K version not 2005. How do I use the configuration manager to set up and alias name for the instance at the server level?

Thanks

|||

For SQL Server 2000, use SQL Server Client Network Utility. Select the "Alias" tab and enter the required information.

Hope this helps,

Peter Saddow

Monday, March 26, 2012

Installing SSRS 2005 in web server and cluster environment.

Hi,

I am installing SSRS 2005 with the following scenario:

- Report Server and Report Manager will be installed on web server

- The repository databases (ReportServer and ReportServerTempDB) will be hosted in SQL2005 cluster server.

Both servers are running Win2003 SP1, SQL/SSRS 2005 SP1

When I try to browse the ReportServer virtual directory from IIS on the web server, the system keep asking username and password. After 3 times trials and it failed eventhough the username and password is correct.

The error message is:

HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
Internet Information Services (IIS)

I've been searching on the web and found couple of articles talking about this issue. I've tried some of them like: http://support.microsoft.com/kb/887993 or even this one: http://groups.google.ca/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/991c9178ceab8f58/8f1a447aa60ad837?lnk=st&q=reporting+services+the+server+is+not+responding&rnum=3&hl=en#8f1a447aa60ad837

But this doesn't work.

I've checked both event viewer both web server and SQL server, but I can't see any information that tell me what had happened.

I also look at BOL, but doesn't help much.

Is there anyone can help me or point me to the right direction? Is there any guide document that explains step-by-step how to install SSRS in my scenario or similiar?

Many Thanks,

Usman Tjiudri

I have the exact same issue in a identical envirnonment configuration. Did you get this resolved?

I`m looking at a few articles re Kerberos....

|||Hi,

Yes, finally I got this issue resolved.
After looking for answer almost everywhere, I finally turn to Microsoft Support and they gave me a very quick response (less than 24 hours).
Before I talk about the solution, I need to clarify something here - my environment is Win2003 Server R2 (not Win2003 SP1 as mentioned in previous email) - may be there's a SP1 for R2.
The issue is caused by IIS. Apparently R2 has different version of IIS with normal Win2003 Server.
You need to uninstall completely IIS on your server (may be you need to backup IIS metadata) and install IIS for R2. You can get the software from R2 disc.
If you still can't solve the issue, log it to Microsoft Support.

Let me know how it goes.

Hope This Help,
Usman Tjiudri

Installing SSRS 2005 in web server and cluster environment.

Hi,

I am installing SSRS 2005 with the following scenario:

- Report Server and Report Manager will be installed on web server

- The repository databases (ReportServer and ReportServerTempDB) will be hosted in SQL2005 cluster server.

Both servers are running Win2003 SP1, SQL/SSRS 2005 SP1

The error message is:

HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
Internet Information Services (IIS)

But this doesn't work.

I've checked both event viewer both web server and SQL server, but I can't see any information that tell me what had happened.

I also look at BOL, but doesn't help much.

Is there anyone can help me or point me to the right direction? Is there any guide document that explains step-by-step how to install SSRS in my scenario or similiar?

Many Thanks,

Usman Tjiudri

I have the exact same issue in a identical envirnonment configuration. Did you get this resolved?

I`m looking at a few articles re Kerberos....

|||Hi,

Let me know how it goes.

Hope This Help,
Usman Tjiudri

sql

Installing SQL205 in a cluster with mount points

I am struggling with an installation of SQL2005 on Windows Server 2003 SP1. I
am trying to set up a 2 node cluster with a single instance of sql2005. I
need to use mount points so I create a shared disk for the mount points and 2
disks which are mounted in there. The shared disk is called M: and the other
disks have names (DB and Logs). There will be more in due course but I
thought I would start with 2.
The install proceeds okay until it gets to the point where I have to choose
a cluster group to put it in. I have created one with M: in it plus the two
mounted disks. However, when I select that one it insists in making M: the
destination for the data files and, of course there is not enough space there
for them. It seems to be completed incapable of using the mount points. In
fact ir doesn't see them at all.
Does anyone know how to fix this or is it just not possible to use mount
points with SQL2005 in a cluster despite what the documentation says
Hi Colin,
This link has information about special mount point considerations
http://msdn2.microsoft.com/en-us/library/ms189910.aspx.
Regards
Antonio Soto
Solid Quality Leaning
http://www.solidqualitylearning.com
DISCLAIMER:
Anything written in this message represents solely the point of view of the
sender. This message does not imply endorsement from Solid Quality Learning,
and it does not represent the point of view of Solid Quality Learning or any
other person, company or institution mentioned in this message
"Colin Bruce" <ColinBruce@.discussions.microsoft.com> escribi en el mensaje
news:2DA833EE-D6B1-4D53-8E2B-4374B73F7F03@.microsoft.com...
>I am struggling with an installation of SQL2005 on Windows Server 2003 SP1.
>I
> am trying to set up a 2 node cluster with a single instance of sql2005. I
> need to use mount points so I create a shared disk for the mount points
> and 2
> disks which are mounted in there. The shared disk is called M: and the
> other
> disks have names (DB and Logs). There will be more in due course but I
> thought I would start with 2.
> The install proceeds okay until it gets to the point where I have to
> choose
> a cluster group to put it in. I have created one with M: in it plus the
> two
> mounted disks. However, when I select that one it insists in making M: the
> destination for the data files and, of course there is not enough space
> there
> for them. It seems to be completed incapable of using the mount points. In
> fact ir doesn't see them at all.
> Does anyone know how to fix this or is it just not possible to use mount
> points with SQL2005 in a cluster despite what the documentation says
|||Dear Antonio,
Thanks for the info. The bit that is mssing from that document - at least I
cannot find it is how big the base drive has to be. As far as I can see what
is not mentioned is that the SQL 2005 installation will put some files in the
base drive. Most of the installation goes somewhere such as C:\Program
Files\... but some files are put in the shared drive which is acting as the
base drive. I have tried creating the base drive with about 50 GB and SQL
2005 then installs. I don't know how much will go in there for different
installation choices but I am now trying a 30GB base drive to see if that is
big enough.
Anyway, to summarise, the base drive isn't just for mount points as the
document suggests but also holds quite a few installation files which I guess
need to be shared between the cluster nodes.
Best wishes...
Colin
"Antonio Soto" wrote:

> Hi Colin,
> This link has information about special mount point considerations
> http://msdn2.microsoft.com/en-us/library/ms189910.aspx.
> Regards
> Antonio Soto
> Solid Quality Leaning
> http://www.solidqualitylearning.com
> DISCLAIMER:
> Anything written in this message represents solely the point of view of the
> sender. This message does not imply endorsement from Solid Quality Learning,
> and it does not represent the point of view of Solid Quality Learning or any
> other person, company or institution mentioned in this message
>
> "Colin Bruce" <ColinBruce@.discussions.microsoft.com> escribió en el mensaje
> news:2DA833EE-D6B1-4D53-8E2B-4374B73F7F03@.microsoft.com...
>
>

Friday, March 23, 2012

Installing SQL Server on a Cluster

Hello All,
If SQL Server is installed on a cluster will it be able to utilize the CPU and memory of all of the servers that are part of the cluster. For example, currently we run SQL Server on one server and at certain peak time the server CPU is maxed out. Will a cluster environment allow SQL Server to utilize mutiple servers for processing eliminating this problem?
Thanks, Gary

There are lots of clustering technologies but typically you're probably talking about a fail-over cluster. These are, to all intensive purposes, separate machines and there is no load balancing across them. That's not to say you could try and partion across the databases but that's not a free feature you get from the cluster.
sql

Monday, March 19, 2012

Installing SQL Server 2005 Developer Edition 64-bit extended on Windows 2003 SP2 cluster

Hello

I've installed Windows 2003 SP2 in a stand-alone cluster (will be adding a second node later). I'm now installing SQL Server 2005 Developer Edition 64-bit extended and would like to have the "Create a SQL Server Failover Cluster" box to not be grayed out. Even when I check the "SQL Server Database Services" box, it still has the cluster box grayed out.

Any idea's?

TIA!

Have you created and configured the cluster service (MSCS)?|||This is resolved. As per usual, SQL 2005 seems to install with more success when you copy the cabs local to the machine, and then run setup (versus over the network).thank anyways Arnie.

Friday, February 24, 2012

Installing SQL 2005 on a failover cluster

Hi,
I am trying to install SQL2005 onto a failover cluster. the latest install
produced the following log file extract
-
Property(S): HeadText_ReadyInstall = Ready to Install the Program
Property(S): HeadText_ReadyRepair = Ready to Repair the Program
Property(S): HeadText_ReadyModify = Ready to Modify the Program
Property(S): HeadText_RemoveProgram = Remove the Program
Property(S): HeadText_OutOfDiskSpace = Out of Disk Space
Property(S): DescText_FilesInUse = Some files that need to be updated are
currently in use.
Property(S): DescText_RegistrationInformation = The following information
will personalize your installation.
Property(S): DescText_ServerImage = Setup will create a server image of
Property(S): DescText_ServerImage2 = at a specified network location. To
continue, click Next.
Property(S): DescText_InstallModifyRemove = Setup helps you install, modify
or remove
Property(S): DescText_InstallModifyRemove2 = . To continue, click Next.
Property(S): DescText_PatchInstall = The Install Wizard will install the
Patch for
Property(S): DescText_PatchInstall2 = on your computer. To continue, click
Update.
Property(S): DescText_WizardComplete = The Install Wizard will complete the
installation of
Property(S): DescText_WizardComplete2 = on your computer. To continue,
click Next.
Property(S): DescText_CompleteSuspended = The Install Wizard will complete
the suspended installation of
Property(S): DescText_CompleteSuspended2 = on your computer. To continue,
click Next.
Property(S): DescText_SuccessfulInstallation = Setup has installed
Property(S): DescText_SuccessfulInstallation2 = successfully. Click Finish
to exit.
Property(S): DescText_SuccessfulRemove = Setup has removed
Property(S): DescText_SuccessfulRemove2 = successfully. Click Finish to exit.
Property(S): DescText_SuccessfulRepair = Setup has repaired
Property(S): DescText_SuccessfulRepair2 = successfully. Click Finish to exit.
Property(S): DescText_SuccessfulModify = Setup has modified
Property(S): DescText_SuccessfulModify2 = successfully. Click Finish to exit.
Property(S): DescText_SetupInterrupted = Setup was interrupted before
Property(S): DescText_SetupInterrupted2 = could be completely installed.
Property(S): DescText_PreparingSetup = Setup is preparing the Install
Wizard which will guide you through the program setup process. Please wait.
Property(S): DescText_FeatureSelection = Select the program features you
want installed.
Property(S): DescText_ProgramFeaturesInstall = The program features you
selected are being installed.
Property(S): DescText_ProgramFeaturesUninstall = The program features you
selected are being uninstalled.
Property(S): DescText_ReadLicense = Please read the following license
agreement carefully.
Property(S): DescText_SpecifyNetworkLocation = Specify a network location
for the server image of the product.
Property(S): DescText_BrowseDestination = Browse to the destination folder.
Property(S): DescText_ModifyRepairRemove = Repair or remove the program.
Property(S): DescText_ReadyInstallation = Setup is ready to begin
installation.
Property(S): DescText_ChosenRemove = You have chosen to remove the program
from your system.
Property(S): DescText_DiskSpaceRequirements = The disk space required for
the installation of the selected features.
Property(S): DescText_DiskExceedsAvailable = Disk space required for the
installation exceeds available disk space.
Property(S): Text_ReRunSetup = Your system has not been modified. To
complete installation at another time, please run setup again.
Property(S): Text_FinishExit = Click Finish to exit Setup.
Property(S): Text_RestoreState = You can either keep any existing installed
elements on your system to continue this installation at a later time or you
can restore your system to its original state prior to the installation.
Property(S): Text_RestoreClick = Click Restore or Continue Later to exit
Setup.
Property(S): Text_InstallWait = Please wait while the Install Wizard installs
Property(S): Text_InstallWait2 = . This may take several minutes.
Property(S): Text_UninstallWaitText = Please wait while the Install Wizard
uninstalls
Property(S): Text_UninstallWaitText2 = . This may take several minutes.
Property(S): Text_UninstallWait = Please wait while the Install Wizard
uninstalls
Property(S): Text_UninstallWait2 = . This may take several minutes.
Property(S): Text_ProgressDone = Progress done
Property(S): Text_Copyright = WARNING: This program is protected by
copyright law and international treaties.
Property(S): Text_BeginInstallation = Click Install to begin the installation.
Property(S): Text_ReviewChange = If you want to review or change any of your
installation settings, click Back. Click Cancel to exit Setup.
Property(S): Text_AlterFeatureInstall = Click an icon in the following list
to change how a feature is installed.
Property(S): Text_ConfirmExit = The installation is not yet complete. Are
you sure you want to exit?
Property(S): Text_FeatureSelectionDescription = This feature requires 4 MB
on your hard drive.
Property(S): Text_EnterNetworkLocation = Enter the network location or click
Change to browse to a location. Click Install to create a server image of
Property(S): Text_EnterNetworkLocation2 = at the specified network location
or click Cancel to exit Setup.
Property(S): Text_SelectDifferentDrive = The highlighted volumes do not have
enough disk space available for the currently selected features. You can
remove files from the highlighted volumes, choose to install less features
onto local drives, or select different destination drives.
Property(S): Text_RepairInstallationErrors = Repair installation errors in
the program. This option fixes missing or corrupt files, shortcuts, and
registry entries.
Property(S): Text_RemoveFromComputer = Remove
Property(S): Text_RemoveFromComputer2 = from your computer.
Property(S): Text_UsingFilesRetry = The following applications are using
files that need to be updated by this setup. Close these applications and
click Retry to continue.
Property(S): Text_ClickRemove = Click Remove to remove
Property(S): Text_ClickRemove2 = from your computer. After removal, this
program will no longer be available for use.
Property(S): Text_ReviewChangeBack = If you want to review or change any
settings, click Back.
Property(S): Text_AllUsers = &Anyone who uses this computer (all users)
Property(S): Text_OnlyMe = Only for &me ([USERNAME])
Property(S): Text_NotAcceptTerms = I &do not accept the terms in the license
agreement
Property(S): Text_AcceptTerms = I &accept the terms in the license agreement
Property(S): Text_RegInfoNameAndOrg = Enter your name and the name of your
organization in the fields below.
Property(S): Text_RegInfoOrg = Enter the name of your organization in the
field below.
Property(S): Upgrade_Confirmation = A lower version of this product has been
detected on your system. Would you like to upgrade your existing installation?
Property(S): AdminMessage = Setup requires user to be in the administrator
group in order to continue the installation process. Setup is aborting as the
current user is not in the administrator group.
Property(S): SupportedOSMessage = Installation of this product failed
because it is not supported on this operating system. For information on
supported configurations, see the product documentation.
Property(S): ShortCutText = Microsoft SQL Server Native Client
Property(S): DialogTitle = Microsoft SQL Server Native Client Setup
Property(S): ProductName = Microsoft SQL Server Native Client
Property(S): ShortName = Microsoft SQL Server Native Client
Property(S): SupportedProcTypeMessage = This Microsoft SQL Server Native
Client package is not supported on the current processor type.
Property(S): DialogPatchTitle = Microsoft SQL Server Native Client Patch
Property(S): EnableFeatureDlg = 1
Property(S): EnableBrowseButton = 0
Property(S): CustomPath = SNAC
Property(S): AdminUser = 1
Property(S): ARPHELPLINK = http://go.microsoft.com/fwlink/?LinkId=52153
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): SqlShared = C:\Program Files\Microsoft SQL Server\
Property(S): SqlVer = C:\Program Files\Microsoft SQL Server\90\
Property(S): SqlTools = C:\Program Files\Microsoft SQL Server\90\Tools\
Property(S): SqlToolsBin = C:\Program Files\Microsoft SQL
Server\90\Tools\Binn\
Property(S): VSRetarget = C:\Program Files\Microsoft SQL Server\90\Tools\Binn\
Property(S): Ver90.84118FFB_F307_45F3_B5BC_3A4F8261108D = C:\Program
Files\Microsoft SQL Server\90\
Property(S): EULA.84118FFB_F307_45F3_B5BC_3A4F8261108D = C:\Program
Files\Microsoft SQL Server\90\EULA\
Property(S): SystemFolder = C:\WINDOWS\system32\
Property(S): SNACMainModId.335C9CFA_7DD6_41E0_8E4F_44D6ED5B1A54 =
9B634CFE_9A39_4508_9CA8_D8DE65A7B8AD
Property(S): WinSxsDirectory.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E1 8E =
C:\WINDOWS\winsxs\
Property(S): payload_ul.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E =
C:\WINDOWS\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a 1e18e3b_8.0.50727.42_none_db5f52fb98cb24ad\
Property(S): payload.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E =
C:\WINDOWS\winsxs\x86_Microsoft.VC80.CRT_1fc8b3b9a 1e18e3b_8.0.50727.42_x-ww_0de06acd\
Property(S): WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E = C:\WINDOWS\
Property(S): SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E =
C:\WINDOWS\system32\
Property(S): WinSxsManifests.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E1 8E =
C:\WINDOWS\winsxs\Manifests\
Property(S): WinSxsPolicies.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18 E =
C:\WINDOWS\winsxs\Policies\
Property(S): policydir.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E =
C:\WINDOWS\winsxs\Policies\x86_Microsoft.VC80.CRT_ 1fc8b3b9a1e18e3b_x-ww_4428b63a\
Property(S): policydir_ul.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E =
C:\WINDOWS\winsxs\x86_Microsoft.VC80.CRT_1fc8b3b9a 1e18e3b_8.0.50727.42_x-ww_0de06acd\
Property(S): WinSxsDirectory.63E949F6_03BC_5C40_FF1F_C8B3B9A1E1 8E =
C:\WINDOWS\winsxs\
Property(S): payload_ul.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E =
C:\WINDOWS\winsxs\x86_policy.8.0.microsoft.vc80.cr t_1fc8b3b9a1e18e3b_8.0.50727.42_none_5c4003bc63e94 9f6\
Property(S): WinSxsPolicies.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18 E =
C:\WINDOWS\winsxs\Policies\
Property(S): policydir.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E =
C:\WINDOWS\winsxs\Policies\x86_policy.8.0.Microsof t.VC80.CRT_1fc8b3b9a1e18e3b_x-ww_77c24773\
Property(S): WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E = C:\WINDOWS\
Property(S): SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E =
C:\WINDOWS\system32\
Property(S): WinSxsManifests.63E949F6_03BC_5C40_FF1F_C8B3B9A1E1 8E =
C:\WINDOWS\winsxs\Manifests\
Property(S): payload.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E =
C:\WINDOWS\winsxs\x86_policy.8.0.Microsoft.VC80.CR T_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_51e427d4\
Property(S): policydir_ul.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E =
C:\WINDOWS\winsxs\x86_policy.8.0.Microsoft.VC80.CR T_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_51e427d4\
Property(S): Ver.06870705_8636_410E_B591_FEE8962A550E = C:\Program
Files\Microsoft SQL Server\90\
Property(S): SqlSDK.06870705_8636_410E_B591_FEE8962A550E = C:\Program
Files\Microsoft SQL Server\90\SDK\
Property(S): SqlInclude.06870705_8636_410E_B591_FEE8962A550E = C:\Program
Files\Microsoft SQL Server\90\SDK\Include\
Property(S): SqlSDKLib.06870705_8636_410E_B591_FEE8962A550E = C:\Program
Files\Microsoft SQL Server\90\SDK\Lib\
Property(S): SqlSDKLibPlatformTarget.06870705_8636_410E_B591_FE E8962A550E =
C:\Program Files\Microsoft SQL Server\90\SDK\Lib\x86\
Property(S): PackagecodeChanging = 1
Property(S): REBOOT = ReallySuppress
Property(S): SKIPPENDINGREBOOTCHECK = 1
Property(S): CURRENTDIRECTORY = D:\SQLServer2005\Servers
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 5252
Property(S): VersionDatabase = 301
Property(S): VersionMsi = 3.01
Property(S): WindowsBuild = 3790
Property(S): ServicePackLevel = 1
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 3
Property(S): MsiNTSuiteEnterprise = 1
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = c:\documentsandsettings\LocalSettings\Temp\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Documents and
Settings\#meg.neeson\Application Data\
Property(S): FavoritesFolder = C:\Documents and
Settings\#meg.neeson\Favorites\
Property(S): NetHoodFolder = C:\Documents and Settings\#meg.neeson\NetHood\
Property(S): PersonalFolder = C:\Documents and Settings\#meg.neeson\My
Documents\
Property(S): PrintHoodFolder = C:\Documents and
Settings\#meg.neeson\PrintHood\
Property(S): RecentFolder = C:\Documents and Settings\#meg.neeson\Recent\
Property(S): SendToFolder = C:\Documents and Settings\#meg.neeson\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All
Users\Application Data\
Property(S): LocalAppDataFolder = C:\Documents and
Settings\#meg.neeson\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\Documents and Settings\#meg.neeson\My
Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 15
Property(S): PhysicalMemory = 4094
Property(S): VirtualMemory = 5949
Property(S): LogonUser = #meg.neeson
Property(S): UserSID = S-1-5-21-1614895754-507921405-1801674531-799107
Property(S): UserLanguageID = 2057
Property(S): ComputerName = LNMHCAP002
Property(S): SystemLanguageID = 2057
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 19
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 08:24:15
Property(S): Date = 24/04/2007
Property(S): MsiNetAssemblySupport = 2.0.50727.42
Property(S): MsiWin32AssemblySupport = 5.2.3790.1830
Property(S): RedirectedDllSupport = 2
Property(S): DATABASE = C:\WINDOWS\Installer\38e40cd.msi
Property(S): OriginalDatabase = D:\SQLServer2005\Servers\setup\sqlncli.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
Property(S): DOTNETCOREPATH = 1
Property(S): ROOTDRIVE = E:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
MSI (s) (D4:6C) [08:24:15:046]: Cleaning up uninstalled install packages, if
any exist
MSI (s) (D4:6C) [08:24:15:046]: MainEngineThread is returning 1603
MSI (s) (D4:F4) [08:24:15:156]: Destroying RemoteAPI object.
MSI (s) (D4:F4) [08:24:15:156]: Custom Action Manager thread ending.
=== Logging stopped: 24/04/2007 08:24:15 ===
MSI (c) (84:00) [08:24:15:156]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (84:00) [08:24:15:156]: MainEngineThread is returning 1603
=== Verbose logging stopped: 24/04/2007 08:24:15 ===
Has anyone seen this error before - I can't seem to find anything that fits
online?
cheers
Meg
hi Meg,
On what OS are you installing and are you using credentials with
administrative access to both cluster nodes?
see log:
Property(S): Upgrade_Confirmation = A lower version of this product has been
detected on your system. Would you like to upgrade your existing installation?
Property(S): AdminMessage = Setup requires user to be in the administrator
group in order to continue the installation process. Setup is aborting as the
current user is not in the administrator group.
Property(S): SupportedOSMessage = Installation of this product failed
because it is not supported on this operating system. For information on
supported configurations, see the product documentation.

Sunday, February 19, 2012

Installing SQL 2000 on Windows Server 2003

I am trying to install SQL 2000 on a Cluster Server Node
1. MS - Support informed me that I should install this as
a Virtual Server. However, Virtual server is grayed
out. This is a SQL 2000 Standard edition. I do have SLQ
Developer Edition. Does the Version matter here?
I understand their is a problem with SP2 and SP3. Do I
need to just do a local install and then upgrade to
Service Pack 3 and then re-install or something?
Any help would be greatly appreciated.
Tony
inline...
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Tony" <anonymous@.discussions.microsoft.com> wrote in message
news:0a7501c47afc$739fdb60$a501280a@.phx.gbl...
> I am trying to install SQL 2000 on a Cluster Server Node
> 1. MS - Support informed me that I should install this as
> a Virtual Server. However, Virtual server is grayed
> out. This is a SQL 2000 Standard edition. I do have SLQ
> Developer Edition. Does the Version matter here?
>
The OS needs to be 2000 Advanced server with clustering already installed or
2003 Enterprise Edition with clustering already install. SQL in both cases
has to be Enterprise Edition. Nothing else will work.

> I understand their is a problem with SP2 and SP3. Do I
> need to just do a local install and then upgrade to
> Service Pack 3 and then re-install or something?
>
Nope, install after you have clustering running with Enterprise Edition and
then apply service pack 3a. The install and service pack install will go to
all nodes of the cluster.

> Any help would be greatly appreciated.
> Tony
>
|||What about the Developers Edition? I have one of these
that I am not using. Will it work on the Clusters?
Tony
Does this qualify?
>--Original Message--
>inline...
>Cheers,
>Rod
>MVP - Windows Server - Clustering
>http://www.nw-america.com - Clustering
>"Tony" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:0a7501c47afc$739fdb60$a501280a@.phx.gbl...
as[vbcol=seagreen]
SLQ
>The OS needs to be 2000 Advanced server with clustering
already installed or
>2003 Enterprise Edition with clustering already install.
SQL in both cases
>has to be Enterprise Edition. Nothing else will work.
>
>Nope, install after you have clustering running with
Enterprise Edition and
>then apply service pack 3a. The install and service pack
install will go to
>all nodes of the cluster.
>
>.
>
|||Its not supported, so I have never tried it.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Tony" <anonymous@.discussions.microsoft.com> wrote in message
news:0c2f01c47b0f$54fbcad0$a501280a@.phx.gbl...[vbcol=seagreen]
> What about the Developers Edition? I have one of these
> that I am not using. Will it work on the Clusters?
> Tony
> Does this qualify?
> message
> as
> SLQ
> already installed or
> SQL in both cases
> Enterprise Edition and
> install will go to
|||SQL Server 2000 Developer Edition supports ALL the features of the Enterprise Edition that allow developers to write and test applications that can use the features. So,
you can use it.
NOTE: The Developer Edition is licensed for use ONLY as a development and test system, NOT a production server.
Additional Information
===================
Features Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/de...ar_ts_1cdv.asp
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
|||Great, that is what I thought. I don't see the Developer Edition on the link
you posted though. Am I right in thinking that its not supported for
Clustering, expect for testing and development.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:D8Ua$rzeEHA.1600@.cpmsftngxa06.phx.gbl...
> SQL Server 2000 Developer Edition supports ALL the features of the
Enterprise Edition that allow developers to write and test applications that
can use the features. So,
> you can use it.
> NOTE: The Developer Edition is licensed for use ONLY as a development and
test system, NOT a production server.
> Additional Information
> ===================
> Features Supported by the Editions of SQL Server 2000
>
http://msdn.microsoft.com/library/de...ar_ts_1cdv.asp
> 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 just checked the link and it does show that Developer Edition SUPPORTS Failover Clustering. Anyways, this link is the online link for the topic "Features Supported by the Editions of SQL Server 2000" in SQL Server
2000 Books Online (BOL). The Developer Edition is licensed for use ONLY as a development and test system, NOT a production server.
HTH,
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
|||In 800 X 600 you can't see the developer Edition column and there is no left
and right scroll bar. DOH! I expanded the screen and answered my own
question. Poor interface on that page

Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:9Qn7PCQfEHA.740@.cpmsftngxa06.phx.gbl...
>I just checked the link and it does show that Developer Edition SUPPORTS
>Failover Clustering. Anyways, this link is the online link for the topic
>"Features Supported by the Editions of SQL Server 2000" in SQL Server
> 2000 Books Online (BOL). The Developer Edition is licensed for use ONLY as
> a development and test system, NOT a production server.
> HTH,
> 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
>

Installing SQL 2000 on Windows 2003 Clustered Nodes

Hi all,
I'm trying to install SQL 2000 on a Windows 2003 Server Cluster. I've set
up two nodes in the cluster. When I try to install SQL on Node1, I get the
following error: "can't install sql server on all clustered nodes." Anyone
have any ideas?
TIAHi,
Please check following article:
http://www.winnetmag.com/Article/ArticleID/40037/40037.html
I had problems with Cluster installation on Windows2003 before most of the
time the problem was a service which is running on both nodes. Like MOM
Agent, Antivirus SW Service, Tivoli agent, IBMDirector agent etc. So first
try to stop all unnecessary service on both nodes (take them to manual on
both nodes and reboot them then try setup again.)
Verfiy that the user you use has administrative rights on both nodes and
able to access administrative shares.
And verify that you don't have any name resolution problems. (Each node
using same DNS , WINS etc..)
Hope this helps.
"Michael C#" wrote:
> Hi all,
> I'm trying to install SQL 2000 on a Windows 2003 Server Cluster. I've set
> up two nodes in the cluster. When I try to install SQL on Node1, I get the
> following error: "can't install sql server on all clustered nodes." Anyone
> have any ideas?
> TIA
>
>|||Thanks Umut. I think I found the problem (or rather problems!) We just got
a completely new system and half the stuff that was supposed to be
pre-configured wasn't... After about 3 hours of re-configuring everything
it's finally up and running :)
Thanks again!
"Umut Nazlica" <UmutNazlica@.discussions.microsoft.com> wrote in message
news:9A933689-21BC-46B8-968F-4D1F3D0EF309@.microsoft.com...
> Hi,
> Please check following article:
> http://www.winnetmag.com/Article/ArticleID/40037/40037.html
>
> I had problems with Cluster installation on Windows2003 before most of the
> time the problem was a service which is running on both nodes. Like MOM
> Agent, Antivirus SW Service, Tivoli agent, IBMDirector agent etc. So first
> try to stop all unnecessary service on both nodes (take them to manual on
> both nodes and reboot them then try setup again.)
> Verfiy that the user you use has administrative rights on both nodes and
> able to access administrative shares.
> And verify that you don't have any name resolution problems. (Each node
> using same DNS , WINS etc..)
>
> Hope this helps.
>
> "Michael C#" wrote:
>> Hi all,
>> I'm trying to install SQL 2000 on a Windows 2003 Server Cluster. I've
>> set
>> up two nodes in the cluster. When I try to install SQL on Node1, I get
>> the
>> following error: "can't install sql server on all clustered nodes."
>> Anyone
>> have any ideas?
>> TIA
>>

Installing SQL 2000 on Windows 2003 Clustered Nodes

Thanks again!
"Umut Nazlica" <UmutNazlica@.discussions.microsoft.com> wrote in message
news:9A933689-21BC-46B8-968F-4D1F3D0EF309@.microsoft.com...[vbcol=seagreen]
> Hi,
> Please check following article:
> http://www.winnetmag.com/Article/Art...037/40037.html
>
> I had problems with Cluster installation on Windows2003 before most of the
> time the problem was a service which is running on both nodes. Like MOM
> Agent, Antivirus SW Service, Tivoli agent, IBMDirector agent etc. So first
> try to stop all unnecessary service on both nodes (take them to manual on
> both nodes and reboot them then try setup again.)
> Verfiy that the user you use has administrative rights on both nodes and
> able to access administrative shares.
> And verify that you don't have any name resolution problems. (Each node
> using same DNS , WINS etc..)
>
> Hope this helps.
>
> "Michael C#" wrote:

Installing SQL 2000 on Windows 2003 Clustered Nodes

Thanks again!
"Umut Nazlica" <UmutNazlica@.discussions.microsoft.com> wrote in message
news:9A933689-21BC-46B8-968F-4D1F3D0EF309@.microsoft.com...[vbcol=seagreen]
> Hi,
> Please check following article:
> http://www.winnetmag.com/Article/Ar...0037/40037.html
>
> I had problems with Cluster installation on Windows2003 before most of the
> time the problem was a service which is running on both nodes. Like MOM
> Agent, Antivirus SW Service, Tivoli agent, IBMDirector agent etc. So first
> try to stop all unnecessary service on both nodes (take them to manual on
> both nodes and reboot them then try setup again.)
> Verfiy that the user you use has administrative rights on both nodes and
> able to access administrative shares.
> And verify that you don't have any name resolution problems. (Each node
> using same DNS , WINS etc..)
>
> Hope this helps.
>
> "Michael C#" wrote:
>

Installing SQL 2000 On active/active cluster

I am trying to install SQL 2000 Ent on a Win2k3 cluster.
I have check both local and domain privlages and they are good.
I have performed MS work around so SQL sp2 and below can be installed on win2k3.
And I keep getting the following error during install...

An error occurred while creating virtual server resources for
clustering.Cluster specific registry entries couldn't be written.

Does anybody have any ideas?Check the privilages for the service account and the Account in which you logged in for Installation has folloing privilages .

Part of Local Admin
In Local Policy
1. Act as part of operating system
2. Log on as service
Make sure in the services :Remote registry service is up|||Privlages are good and remote registry service is running !|||Did you manage to resolve this issue? Did you get any USEFULL help from Microsoft support? Please post a few words of wisdom if so.

We have exactly the same problem and I've been struggling with it for a few weeks. Any help/advice is welcome.

I use SQL 2000 EE SP3 install (i.e with SP3 already included in installation) and still get the same error: "cluster-specific registry could not be written". All the simptoms are the same. I can install single-node virtual server, but if I try to install on both-nodes I've got mentioned message. The same happens if I try add second node to successfully installed single-node virtual server.|||My issue ended up being security on the cluster was to tight.
Once I loosened my security policies it started working fine.
Specifically the registry was being locked down by a Windows 2000 DC which does'nt have all the proper setting that Windows 2003 has.
I eventually upgraded the DC to 2003 to help with this matter.

Installing SP4 on New node in cluster on Win2K3

We have a single node cluster using SQL2K EE running on Win2K EE, and this
has been running fine for a year or so. We finally have our new data centre
completed, and the additional hardware installed for us to install the second
node.
1) I installed Cluster services and added the second node to the cluster.
2) Ran COMClust to add DTC as a cluster resource
3) On the Active Node installed SQL2K, and selected advanced options,
Maintain SQL Server . . . .
4) Checked SQL Server resources in Cluster Manager, every thing looks good.
5) Tried to install SP4 from the new passive node - Failed doesn't own
resources in the Cluster
6) Tried installing SP4 from the active node . . . Got a bit further but the
install fails with a 'Setup was unable to complete the operation on all nodes
in the cluster'
At this point I am really stumped Looking at the SQLSP.log file it ends with
16:38:12 Begin SDPassword Dialog
16:38:12 Begin: CheckSAPassword
16:38:12 WARNING : No Blank SA Pwd
16:38:12 End: CheckSAPassword
16:38:12 Begin: SdShowSp3WrngDlg
and searching the net threw up a reference to this
http://support.microsoft.com/kb/815431/] KB article. Although this is not
strictly relevant I am wondering if there is an issue with installing a non
SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
what SP level its at and rejecting it as it doesn't have SP3 Installed.
So then What I did, was to try failing the cluster over so that I could
apply the fix from the new node. While the cluster group fails over, the SQL
group makes and attempt, but then SQL Server fails to start and it all fails
back to the other node.
I then removed SQL Server (from the active node) on the Passive node.
Rebooted the new passive node, and Installed SQL2K SP3a on the new node
successfully. I then tried to install SP4 (From the Active Node), and that
failed with the same error.
Any one have any Ideas?
Regards
Tony
Slipstream sql server sp4 and then try to do the install from the active
node. Also make sure that nobody else is logged onto the active and passive
nodes.
AS
"BC DBA" wrote:

> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data centre
> completed, and the additional hardware installed for us to install the second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but the
> install fails with a 'Setup was unable to complete the operation on all nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the SQL
> group makes and attempt, but then SQL Server fails to start and it all fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony
|||16:38:12 Begin: SdShowSp3WrngDlg
Yes, this is your problem. However, you've indicated that you are running
on Win2K EE, which doesn't exist (only Advanced Server), plus, this security
dialog only presents itself on a Windows Server 2003.
So, let's assume that you are running Windows 2000 Advanced Server on the
active (original) node and Windows Server 2003 EE on the new node.
Your steps through the installation process is correct; however, you will
need to get the new node to the same SP level as the old before the cluster
will successfully move resources to the new node.
There are three issues. The dialog above requires you to apply SP3 or later
before resources will run on new node; however, there is a bug in the SP4
installation package that misreads the new 4 digit Build number 2039 as 203
or 039, both of which are less than the 760 Build for SP3.
You must run service packs from the node that currently owns the cluster
resources, and since you cannot move resources to the new node yet, you must
reapply SP3 on the active (original) node. The installation will detect
that it will be a Binary Only installation to the new node.
Lastly, there is one other security issue in that until the new node has
been updated to SP3, TCP/IP protocol has been disabled. To work around this
issue, on BOTH cluster nodes, you must create NAMED PIPE aliases to the
Virtual SQL Server instance. Since the RTM installation uses this protocol,
this issue does not occur, but it does for any SP installations.
Once SP3 has been applied, you will still not be able to move resources to
new node. You must reapply SP4 plus any additional hot fixes. If you use
AWE, you will definitely want to apply the 2040 HF; moreover, you may want
to consider applying the latest publicly available HF, as it is the most
current build supported, Build 2187.
After this, you should be able to move resources successfully between both
nodes; however, Microsoft only limitedly supports mixed cluster
environments. At this point, you should uninstall the original node from
the cluster, evict the node, and rebuild it as a Windows Server 2003
installation. Then, you will need to follow the procedures above to
reintroduce this node as a clustered member. (As an aside, on Win2K3, you
do not have to run the COMCLUST utility anymore).
One final word of advice, SQL Server 2000 mainstream support expires in
April 2008. You should seriously consider upgrading to SQL Server 2005 as
soon as possible. Moreover, CTP2 for SQL Server 2008 was just released in
this month, with a target EOY 2007 1st QTR 2008 launch expectation, which
means even SS2K5 mainstream support does not have a long expected lifespan.
So, get moving.
Sincerely,
Anthony Thomas

"BC DBA" <BCDBA@.discussions.microsoft.com> wrote in message
news:88FBFA1A-2239-4E19-833F-83A55858ACCC@.microsoft.com...
> We have a single node cluster using SQL2K EE running on Win2K EE, and this
> has been running fine for a year or so. We finally have our new data
centre
> completed, and the additional hardware installed for us to install the
second
> node.
> 1) I installed Cluster services and added the second node to the cluster.
> 2) Ran COMClust to add DTC as a cluster resource
> 3) On the Active Node installed SQL2K, and selected advanced options,
> Maintain SQL Server . . . .
> 4) Checked SQL Server resources in Cluster Manager, every thing looks
good.
> 5) Tried to install SP4 from the new passive node - Failed doesn't own
> resources in the Cluster
> 6) Tried installing SP4 from the active node . . . Got a bit further but
the
> install fails with a 'Setup was unable to complete the operation on all
nodes
> in the cluster'
> At this point I am really stumped Looking at the SQLSP.log file it ends
with
> 16:38:12 Begin SDPassword Dialog
> 16:38:12 Begin: CheckSAPassword
> 16:38:12 WARNING : No Blank SA Pwd
> 16:38:12 End: CheckSAPassword
> 16:38:12 Begin: SdShowSp3WrngDlg
> and searching the net threw up a reference to this
> http://support.microsoft.com/kb/815431/] KB article. Although this is not
> strictly relevant I am wondering if there is an issue with installing a
non
> SP SQL2K on Win2K3, and then when trying to install SP4 its checking to
see
> what SP level its at and rejecting it as it doesn't have SP3 Installed.
> So then What I did, was to try failing the cluster over so that I could
> apply the fix from the new node. While the cluster group fails over, the
SQL
> group makes and attempt, but then SQL Server fails to start and it all
fails
> back to the other node.
> I then removed SQL Server (from the active node) on the Passive node.
> Rebooted the new passive node, and Installed SQL2K SP3a on the new node
> successfully. I then tried to install SP4 (From the Active Node), and that
> failed with the same error.
> Any one have any Ideas?
> --
> Regards
> Tony

installing SP4 for SQL 2000 on a cluster node

Hello,
I recently added a new win2k3 node to an existing SQL cluster and installed
SQL Server 2000. The SQL installation for the new node was performed from
the active node.
I also installed SP4 from the active node. However, I am having SQL
connectivity issues when I fail over to the new node. I noticed that I get
the following event log on the new node. It thinks that SP4 is not installed
although it is. Does anyone know if SP4 should be installed from the passive
node (the new node)? Does it matter which node we run the SP4 installation?
Thank-you,
WG
Event Type: Information
Event Source: MSSQLSERVER/MSDE
Event Category: None
Event ID: 1
Date: 12/3/2007
Time: 3:02:41 PM
User: N/A
Computer: EAGNMNST18C
Description:
You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
Server 2000 Desktop Engine (also called MSDE) that has known security
vulnerabilities when used in conjunction with the Microsoft Windows Server
2003 family. To reduce your computer's vulnerability to certain virus
attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE,
or both have been disabled. To enable these ports, you must install a patch,
or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.Take a look at this page and ensure you followed the right direction.
http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
--
Ekrem Ã?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> Hello,
> I recently added a new win2k3 node to an existing SQL cluster and
> installed
> SQL Server 2000. The SQL installation for the new node was performed from
> the active node.
> I also installed SP4 from the active node. However, I am having SQL
> connectivity issues when I fail over to the new node. I noticed that I
> get
> the following event log on the new node. It thinks that SP4 is not
> installed
> although it is. Does anyone know if SP4 should be installed from the
> passive
> node (the new node)? Does it matter which node we run the SP4
> installation?
> Thank-you,
> WG
> Event Type: Information
> Event Source: MSSQLSERVER/MSDE
> Event Category: None
> Event ID: 1
> Date: 12/3/2007
> Time: 3:02:41 PM
> User: N/A
> Computer: EAGNMNST18C
> Description:
> You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> Server 2000 Desktop Engine (also called MSDE) that has known security
> vulnerabilities when used in conjunction with the Microsoft Windows Server
> 2003 family. To reduce your computer's vulnerability to certain virus
> attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> MSDE,
> or both have been disabled. To enable these ports, you must install a
> patch,
> or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> http://www.microsoft.com/sql/downloads/default.asp
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>|||Thank you!
I actually came across this article and it is helpful.
Could you tell me what is the "database upgrade script"? The article says,
for my scenario, I must run "the databse upgrade script".
Thanks,
WG
"Ekrem Ã?nsoy" wrote:
> Take a look at this page and ensure you followed the right direction.
> http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
> --
> Ekrem Ã?nsoy
>
> "Walid" <Walid@.discussions.microsoft.com> wrote in message
> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
> > Hello,
> >
> > I recently added a new win2k3 node to an existing SQL cluster and
> > installed
> > SQL Server 2000. The SQL installation for the new node was performed from
> > the active node.
> > I also installed SP4 from the active node. However, I am having SQL
> > connectivity issues when I fail over to the new node. I noticed that I
> > get
> > the following event log on the new node. It thinks that SP4 is not
> > installed
> > although it is. Does anyone know if SP4 should be installed from the
> > passive
> > node (the new node)? Does it matter which node we run the SP4
> > installation?
> >
> > Thank-you,
> >
> > WG
> >
> > Event Type: Information
> > Event Source: MSSQLSERVER/MSDE
> > Event Category: None
> > Event ID: 1
> > Date: 12/3/2007
> > Time: 3:02:41 PM
> > User: N/A
> > Computer: EAGNMNST18C
> > Description:
> > You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
> > Server 2000 Desktop Engine (also called MSDE) that has known security
> > vulnerabilities when used in conjunction with the Microsoft Windows Server
> > 2003 family. To reduce your computer's vulnerability to certain virus
> > attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
> > MSDE,
> > or both have been disabled. To enable these ports, you must install a
> > patch,
> > or the most recent service pack for Microsoft SQL Server 2000 or MSDE from
> > http://www.microsoft.com/sql/downloads/default.asp
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> >
>|||I believe it must be talking about the upgrading your database scripts that
you used to be using before SP4 is apllied.
--
Ekrem Ã?nsoy
"Walid" <Walid@.discussions.microsoft.com> wrote in message
news:AE628F6C-F06F-4DBF-B36D-0D5563B1D110@.microsoft.com...
> Thank you!
> I actually came across this article and it is helpful.
> Could you tell me what is the "database upgrade script"? The article
> says,
> for my scenario, I must run "the databse upgrade script".
> Thanks,
> WG
> "Ekrem Ã?nsoy" wrote:
>> Take a look at this page and ensure you followed the right direction.
>> http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_installing_on_a_failover_cluster
>> --
>> Ekrem Ã?nsoy
>>
>> "Walid" <Walid@.discussions.microsoft.com> wrote in message
>> news:10D70424-46B0-4139-A8A4-3E0169F59389@.microsoft.com...
>> > Hello,
>> >
>> > I recently added a new win2k3 node to an existing SQL cluster and
>> > installed
>> > SQL Server 2000. The SQL installation for the new node was performed
>> > from
>> > the active node.
>> > I also installed SP4 from the active node. However, I am having SQL
>> > connectivity issues when I fail over to the new node. I noticed that I
>> > get
>> > the following event log on the new node. It thinks that SP4 is not
>> > installed
>> > although it is. Does anyone know if SP4 should be installed from the
>> > passive
>> > node (the new node)? Does it matter which node we run the SP4
>> > installation?
>> >
>> > Thank-you,
>> >
>> > WG
>> >
>> > Event Type: Information
>> > Event Source: MSSQLSERVER/MSDE
>> > Event Category: None
>> > Event ID: 1
>> > Date: 12/3/2007
>> > Time: 3:02:41 PM
>> > User: N/A
>> > Computer: EAGNMNST18C
>> > Description:
>> > You are running a version of Microsoft SQL Server 2000 or Microsoft SQL
>> > Server 2000 Desktop Engine (also called MSDE) that has known security
>> > vulnerabilities when used in conjunction with the Microsoft Windows
>> > Server
>> > 2003 family. To reduce your computer's vulnerability to certain virus
>> > attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000,
>> > MSDE,
>> > or both have been disabled. To enable these ports, you must install a
>> > patch,
>> > or the most recent service pack for Microsoft SQL Server 2000 or MSDE
>> > from
>> > http://www.microsoft.com/sql/downloads/default.asp
>> >
>> > For more information, see Help and Support Center at
>> > http://go.microsoft.com/fwlink/events.asp.
>> >

INstalling sp3a on second node

I have a active/passive cluster with W2K Adv. and SQL 2000.
I was having the issue with setting up SQL on the second node. I fixed issue by installing directly onto the second node. But their is no option with the sp3a to install onto the second node locally. The same issue that happened with trying to remote inst
all with the primary node. The install failed because of a timeout issue. Error 121. All of my settings and correct accounts are setup. The person who told me to install directly on the second node to
install SQL stated that this was actually a known problem. What is the fix for the service packs if you cannot install remotely? It looks like sp3a installed correctly because when I ran query analyzer the version that showed up was sp3a. Any comments wou
ld be appreciated.
Thanks,
dcaldwell
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
There is no 'first node' and 'second node' concept in SQL 2000 clustering.
All nodes are equal. The only difference is what node is currently hosting
the instance. Adding and removing nodes is a different process and is well
documented in BOL. It sounds like you built the cluster on a single node or
applied the service pack with one node offline. Normal installation of SQL
Service packs will update all nodes at the same time if it is run from teh
node currently hosting the instance. If you need to reapply a service pack
to update binaries on a newly added or replaced node, you must run the
Service Pack from the 'new' node while hte SQL instance is hosted on an
'old' node. This is documented in the Service Pack readme file.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%23%23T55iTgEHA.3272@.TK2MSFTNGP11.phx.gbl...
> I have a active/passive cluster with W2K Adv. and SQL 2000.
> I was having the issue with setting up SQL on the second node. I fixed
issue by installing directly onto the second node. But their is no option
with the sp3a to install onto the second node locally. The same issue that
happened with trying to remote install with the primary node. The install
failed because of a timeout issue. Error 121. All of my settings and correct
accounts are setup. The person who told me to install directly on the second
node to
> install SQL stated that this was actually a known problem. What is the fix
for the service packs if you cannot install remotely? It looks like sp3a
installed correctly because when I ran query analyzer the version that
showed up was sp3a. Any comments would be appreciated.
> Thanks,
> dcaldwell
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||What do you mean by "I fixed issue by installing directly onto the second
node. "
Did you install a local, non-clustered installation on the second node?
Perhaps now is a time to uninstall that local copy, and reinstall back as a
virtual SQL Server. You can find a clustering installation white paper at:
http://www.microsoft.com/technet/pro.../failclus.mspx
Chris Skorlinski
Microsoft SQL Server Support
Please reply directly to the thread with any updates.
This posting is provided "as is" with no warranties and confers no rights.

Friday, March 30, 2012

Instances in Virtual SQL Servers

Instance wil not come online

Instance name contains a dash

Monday, March 26, 2012

Installing SSRS 2005 in web server and cluster environment.

Installing SSRS 2005 in web server and cluster environment.

Installing SQL205 in a cluster with mount points

Friday, March 23, 2012

Installing SQL Server on a Cluster

Monday, March 19, 2012

Installing SQL Server 2005 Developer Edition 64-bit extended on Windows 2003 SP2 cluster

Friday, February 24, 2012

Installing SQL 2005 on a failover cluster

Sunday, February 19, 2012

Installing SQL 2000 on Windows Server 2003

Installing SQL 2000 on Windows 2003 Clustered Nodes

Installing SQL 2000 on Windows 2003 Clustered Nodes

Installing SQL 2000 on Windows 2003 Clustered Nodes

Installing SQL 2000 On active/active cluster

Installing SP4 on New node in cluster on Win2K3

installing SP4 for SQL 2000 on a cluster node

installing SP4 for SQL 2000 on a cluster node

installing SP4 for SQL 2000 on a cluster node

INstalling sp3a on second node

Installing sql

Blog Archive

About Me