MSSQL 2000 Installation problem.

Hello there!
I am trying to install MS SQL 2000 Server on Windows 2003.
My problem is that when i run the autorun (autorun run well) and after i click SQL Server 200. Components and Install Database Server the autorun close normaly but doesn open the installation, dont open any new process, Nothing else happens, I tried to find the sqlstp.log file but with no success, There is no such a file in my computer, and i tryed also the event viwer too but it doesnt catched anything...

Any ideas?
Thanks to all who can help me.

Another thing, when i try to run directly setupsql.exe it says

Windows cannot open this program since it has been disabled.

I remember that the windows version is NOT the webbased edition, it is the enterprise edition.

|||i received this same error message with web edition. rebuilt my server to std edition and it worked fine.|||

Refer

http://support.microsoft.com/default.aspx?scid=kb;en-us;826961

MSSQL 2000 Installation problem.

Hello there!
I am trying to install MS SQL 2000 Server on Windows 2003.
My problem is that when i run the autorun (autorun run well) and after i click SQL Server 200. Components and Install Database Server the autorun close normaly but doesn open the installation, dont open any new process, Nothing else happens, I tried to find the sqlstp.log file but with no success, There is no such a file in my computer, and i tryed also the event viwer too but it doesnt catched anything...

Any ideas?
Thanks to all who can help me.

Another thing, when i try to run directly setupsql.exe it says

Windows cannot open this program since it has been disabled.

I remember that the windows version is NOT the webbased edition, it is the enterprise edition.

|||i received this same error message with web edition. rebuilt my server to std edition and it worked fine.|||

Refer

http://support.microsoft.com/default.aspx?scid=kb;en-us;826961

MS-SQL 2000 Enterprise clustered installation fails

Hi everyone,
I have problem installing MS-SQL 2000 enterprise on Windows Server 2003 Ent.
cluster. The message I'm getting is "Setup failed to perform required
operations on the cluster nodes." The only thing "cluster.log" says in
regards of the MS-SQL is that "the virtual SQL server name can't be found.
Now, that's not the first time I'm doing this installation. Often I got in
the same problem, but by relaxing the local Policy (we are running very
restrictive GPO) usually resolved the problem. Therefore, I thing the problem
comes from the GPO restrictions. Also, I'm using the same domain account
used to install MSCS and I had no issues there.
My question is, what's the best way to approach this problem and what are
the MS-SQL requirements (in terms account permissions)?
The install account must be an admin on all nodes.
The MS task scheduler must be enabled on all nodes. <-- this is likely the
problem.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"kkantchev@.hotmail.com" <kkantchevhotmailcom@.discussions.microsoft.com>
wrote in message news:370B4F33-07E5-43A2-B4F3-4D0F485809AC@.microsoft.com...
> Hi everyone,
> I have problem installing MS-SQL 2000 enterprise on Windows Server 2003
> Ent.
> cluster. The message I'm getting is "Setup failed to perform required
> operations on the cluster nodes." The only thing "cluster.log" says in
> regards of the MS-SQL is that "the virtual SQL server name can't be found.
> Now, that's not the first time I'm doing this installation. Often I got in
> the same problem, but by relaxing the local Policy (we are running very
> restrictive GPO) usually resolved the problem. Therefore, I thing the
> problem
> comes from the GPO restrictions. Also, I'm using the same domain account
> used to install MSCS and I had no issues there.
> My question is, what's the best way to approach this problem and what are
> the MS-SQL requirements (in terms account permissions)?
|||Are you, or the cluster service account, also a Domain Admin? If not, then
you will need to have your Domain Admins create Domain Local Groups before
the installation.
Check out the installation logs; they contain the point of failure and
specifics about why it failed.
http://support.microsoft.com/kb/910228/en-us
http://msdn2.microsoft.com/en-us/library/ms143702.aspx
Good luck.
Sincerely,
Anthony Thomas

"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OsZVE65SHHA.2256@.TK2MSFTNGP02.phx.gbl...
> The install account must be an admin on all nodes.
> The MS task scheduler must be enabled on all nodes. <-- this is likely
the
> problem.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "kkantchev@.hotmail.com" <kkantchevhotmailcom@.discussions.microsoft.com>
> wrote in message
news:370B4F33-07E5-43A2-B4F3-4D0F485809AC@.microsoft.com...[vbcol=seagreen]
found.[vbcol=seagreen]
in[vbcol=seagreen]
account[vbcol=seagreen]
are
>
sql

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
HLittle things like licensing issues a concern?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegroups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
H
Little things like licensing issues a concern?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegro ups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

MSRS Developer Edition on MS SQL 2000 STD

Hello,
I have a client installation I need to load Reporting Services on but
the disk they put into the server is Developer edition rather than
standard. This is a production server. Are their any potential issues I
might encounter?
Any information is greatly appreciated.
Thanks,
HLittle things like licensing issues a concern?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Hulicat" <dennis_A_white@.yahoo.com> wrote in message
news:1164072012.870727.39050@.m73g2000cwd.googlegroups.com...
> Hello,
> I have a client installation I need to load Reporting Services on but
> the disk they put into the server is Developer edition rather than
> standard. This is a production server. Are their any potential issues I
> might encounter?
> Any information is greatly appreciated.
> Thanks,
> H
>

MSDTC Required?

I am preparing for the installation of SQL Server 2005 Standard on a
two-node cluster. The SQL Server books Online" topic named "Before
Installing Failover Clustering" indicates that you must install MSDTC if you
are installing the Database Engine and SSIS, Notification Services or
Workstations components. I am not planning on installing SSIS or
Notification Services but would like to install the Workstations components
(specifically SSMS and the other tools) on the clustered nodes.
Is it really necessary to install MSDTC in the cluster if I don't plan on
doing distributed transactions? I want to keep the installation as simple
as possible and don't see why I need to install MSDTC in the cluster with
the Workstation components.
Any help would be appreciated.
Thanks!
Chris
SQL works a lot better with MSDTC. You can go ahead and install it in the
cluster group if you do not have a lot of distributed transactions.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:eN61fcOZHHA.348@.TK2MSFTNGP02.phx.gbl...
>I am preparing for the installation of SQL Server 2005 Standard on a
>two-node cluster. The SQL Server books Online" topic named "Before
>Installing Failover Clustering" indicates that you must install MSDTC if
>you are installing the Database Engine and SSIS, Notification Services or
>Workstations components. I am not planning on installing SSIS or
>Notification Services but would like to install the Workstations components
>(specifically SSMS and the other tools) on the clustered nodes.
> Is it really necessary to install MSDTC in the cluster if I don't plan on
> doing distributed transactions? I want to keep the installation as simple
> as possible and don't see why I need to install MSDTC in the cluster with
> the Workstation components.
> Any help would be appreciated.
> Thanks!
> Chris
>
|||Can you clarify "Works a lot better with..."
I always install it as a matter of procedure but if it's not necessary, how
does it help?
"Geoff N. Hiten" wrote:

> SQL works a lot better with MSDTC. You can go ahead and install it in the
> cluster group if you do not have a lot of distributed transactions.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
> news:eN61fcOZHHA.348@.TK2MSFTNGP02.phx.gbl...
>
|||SQL tries to initialize a DTS connection when it starts up. When MSDTC is
not there, SQL has to wait for a timeout so you get slower startups and
failovers.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"burt_king" <burt_king@.yahoo.com> wrote in message
news:CA063DB1-C405-44E5-9628-9C10AE5C7630@.microsoft.com...[vbcol=seagreen]
> Can you clarify "Works a lot better with..."
> I always install it as a matter of procedure but if it's not necessary,
> how
> does it help?
>
> "Geoff N. Hiten" wrote:
|||MS DTC is installed on each cluster node as part of the Windows OS
installation. What is required is to make it "clustered."
If you will only be installing a single SQL Server instance, then you can
configure the MS DTC cluster resource to use the same cluster resource group
as the SQL Server installation.
Otherwise, follow the instructions to set up a dedicated cluster resource
group for MS DTC, which will require a dedicated shared cluster disk, IP
address, and Network Name resources.
Do not run MS DTC as a resource in the Quorum cluster resource group.
Sincerely,
Anthony Thomas

"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:eN61fcOZHHA.348@.TK2MSFTNGP02.phx.gbl...
> I am preparing for the installation of SQL Server 2005 Standard on a
> two-node cluster. The SQL Server books Online" topic named "Before
> Installing Failover Clustering" indicates that you must install MSDTC if
you
> are installing the Database Engine and SSIS, Notification Services or
> Workstations components. I am not planning on installing SSIS or
> Notification Services but would like to install the Workstations
components
> (specifically SSMS and the other tools) on the clustered nodes.
> Is it really necessary to install MSDTC in the cluster if I don't plan on
> doing distributed transactions? I want to keep the installation as simple
> as possible and don't see why I need to install MSDTC in the cluster with
> the Workstation components.
> Any help would be appreciated.
> Thanks!
> Chris
>
|||What if this were active/active sql 2000 instances. Still one MSDTC?
"Anthony Thomas" wrote:

> MS DTC is installed on each cluster node as part of the Windows OS
> installation. What is required is to make it "clustered."
> If you will only be installing a single SQL Server instance, then you can
> configure the MS DTC cluster resource to use the same cluster resource group
> as the SQL Server installation.
> Otherwise, follow the instructions to set up a dedicated cluster resource
> group for MS DTC, which will require a dedicated shared cluster disk, IP
> address, and Network Name resources.
> Do not run MS DTC as a resource in the Quorum cluster resource group.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
> news:eN61fcOZHHA.348@.TK2MSFTNGP02.phx.gbl...
> you
> components
>
>
|||Each cluster can only have a single MSDTC instance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"SQLdba" <burt_king@.yahoo.com> wrote in message
news:D7919F72-F753-4232-80CE-DCD52FA271EA@.microsoft.com...[vbcol=seagreen]
> What if this were active/active sql 2000 instances. Still one MSDTC?
>
> "Anthony Thomas" wrote:
|||In which case, the recommended solution is to have a dedicated MS DTC
cluster resource group with dedicated dependencies (Shared Disk, IP Address,
and Network Name).
In times past, Microsoft recommended adding this resource to the Quorum
group; however, it was determined that this was a bad practices because
whenever the quorum goes offline, and DTC handles are destroyed if the two
resources are collocated.
In a dedicated group, even if the quorum group is moved, or the DTC group is
moved, pending DTC transactions and SQL Server handles are maintained.
Sincerely,
Anthony Thomas

"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:eKAYYTxaHHA.3272@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> Each cluster can only have a single MSDTC instance.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "SQLdba" <burt_king@.yahoo.com> wrote in message
> news:D7919F72-F753-4232-80CE-DCD52FA271EA@.microsoft.com...
can[vbcol=seagreen]
resource[vbcol=seagreen]
IP[vbcol=seagreen]
plan
>
|||Actually, the recommendation was changed based on testing high-volume
systems where certain storage systems could be saturated by the DTC traffic
to the point where the Quorum disk appeared unresponsive, thus causing a
cluster failure. Since Microsoft is officially hardware agnostic, this led
to a blanket recommendation for a dedicated MSDTC group, which later was
modified to apply only to high volume systems.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Anthony Thomas" <ALThomas@.kc.rr.com> wrote in message
news:eZDWpk7aHHA.4140@.TK2MSFTNGP06.phx.gbl...
> In which case, the recommended solution is to have a dedicated MS DTC
> cluster resource group with dedicated dependencies (Shared Disk, IP
> Address,
> and Network Name).
> In times past, Microsoft recommended adding this resource to the Quorum
> group; however, it was determined that this was a bad practices because
> whenever the quorum goes offline, and DTC handles are destroyed if the two
> resources are collocated.
> In a dedicated group, even if the quorum group is moved, or the DTC group
> is
> moved, pending DTC transactions and SQL Server handles are maintained.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:eKAYYTxaHHA.3272@.TK2MSFTNGP03.phx.gbl...
> can
> resource
> IP
> plan
>

MSDTC cannot move on a cluster

Today we installed on MS Cluster (W2k3) and SQL Server 2000 a MSDTC Service. The installation was succesfull, but wenn we try to move the group, then it failed. Because we have only 2 Disks on the cluster one for the Quorum, the other for the Sql Server. We installed the MSDTC as a Resource on the Quorum Disk. The other Thing, wenn we start the firts node all is running on the first node, but we cannot move. Wenn we start the second node all is running on the second node, but we cannot move the Group which contain the Msdtc resource.

Who has a solution to this problem?

Thanks to all

Did you run comclust.exe on each of the nodes before installing SQL Server?

MSDTC and SQL2000 clustered

Hi,

I'm in doubt about an installation of SQL Server 2000 (single istance hot standby) on a Win2000 Advanced Server 2 nodes cluster (2 processors per node).

I suppose MSDTC was not activated during SQL2000 setup.

Is it absolutely necessary?
Can I have problems?

In what case is it necessary?

Many thanks?Originally posted by nisant
Hi,

I'm in doubt about an installation of SQL Server 2000 (single istance hot standby) on a Win2000 Advanced Server 2 nodes cluster (2 processors per node).

I suppose MSDTC was not activated during SQL2000 setup.

Is it absolutely necessary?
Can I have problems?

In what case is it necessary?

Many thanks?

I had a problem in an active\active failover installation. MSDTC was not configured and was causing problems with the fail over function. Once I configured it as a shared resource, everything seemed fine. Hope this helps...|||True, make sure MSDTC has been started and working whenever any distributed transactions are in process.

For information refer to DB journal (http://www.databasejournal.com/features/mssql/article.php/1690901) article.

MSDN Version of SQLServer 2000 and SQLServer 2005

All,
From a SQLServer installation (both 2000 & 2005), is there a way to find out
if the installation is a MSDN installation. Select @.@.Version does not seem to
indicate anything to that effect.
The previous DBA did a SQLServer installation (2000 & 2005) and I could not
find the 32-bit version of the media. That leads me to believe that he might
have installed it from a MSDN CD/DVD.
Thanks,
rgnNo. You can only tell what edition you have installed.
Jonathan
rgn wrote:
> All,
> From a SQLServer installation (both 2000 & 2005), is there a way to find out
> if the installation is a MSDN installation. Select @.@.Version does not seem to
> indicate anything to that effect.
> The previous DBA did a SQLServer installation (2000 & 2005) and I could not
> find the 32-bit version of the media. That leads me to believe that he might
> have installed it from a MSDN CD/DVD.
> Thanks,
> rgn
>