Can anybody tell me the differences, advantages or disadvantages in
installing an active/active cluster as
VIRTUAL/INSTANCE1
and
VIRTUAL/INSTANCE2
against
VIRTUAL1
and
VIRTUAL2
We did not seem to get the option to install a second instance on the first
virtual server and so opted for 2 virtual servers with names instance on
each so
VIRTUAL1 / INSTANCE1
and
VIRTUAL2 / INSTANCE2
Many Thanks
Steve
In a cluster, each instance is installed in its own virtual server.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Steve" <spam@.notformeplease.net> wrote in message
news:HLednboIr5j-OrnfRVnytg@.brightview.com...
> Can anybody tell me the differences, advantages or disadvantages in
> installing an active/active cluster as
> VIRTUAL/INSTANCE1
> and
> VIRTUAL/INSTANCE2
> against
> VIRTUAL1
> and
> VIRTUAL2
> We did not seem to get the option to install a second instance on the
first
> virtual server and so opted for 2 virtual servers with names instance on
> each so
> VIRTUAL1 / INSTANCE1
> and
> VIRTUAL2 / INSTANCE2
> Many Thanks
> Steve
>
|||Thanks Geoff
So I think that means we got it right first time.
Regards
Steve
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%2339SkcoHFHA.236@.TK2MSFTNGP14.phx.gbl...
> In a cluster, each instance is installed in its own virtual server.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Steve" <spam@.notformeplease.net> wrote in message
> news:HLednboIr5j-OrnfRVnytg@.brightview.com...
> first
>
Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts
Monday, March 26, 2012
Multi Instance Cluster Question
I decided to try and setup a multi instance cluster on my
own and seem to be fairly successful . Its SQL 2000 EE on
Windows Server 2003 EE
Just had 2 questions. When i installed the second
instance, it asked me for a virtual name.. so i gave it
one ..in my case SQL2.. and then was asked for an
instance name so i called it ins2.. Eventually this
second sql server is now called sql2\ins2 and not sql2 as
i had thought it would be.. The first instance which was
a default instance was named as SQL1 . Is this the right
way it should be ? i.e one instance called SQL1 and the
other SQL2\ins2 in my case. I was under the impression
that since its a virtual name i could get them to be
called SQL1 and SQL2
If not, then my next question is..
When i connect to those 2 virtual names from a client, it
seems to connect fine to SQL1 but when i connect to SQL2
\ins2 it fails...with SQL Server does not exist or access
denied. Any reason why ? Thanks
Answer #1.
You can have one default instance and 15 named instances OR 16 named
instances of SQL per cluster. Each named instance will be
VirtualServerName\InstanceName. For consistancy I use only named
instances on a cluster, but that is just a personal thing.
Answer #2.
You may have an older version of MDAC on your client system. I think the
breakover is MDAC 2.6, but I may be wrong. Version 2.6 and higher
understand named instances. Versions before that do not. You can make an
older version connect to a named instance if you create an alias that
includes the port number.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Ronald" <anonymous@.discussions.microsoft.com> wrote in message
news:520a01c42ca8$dfdc9680$a301280a@.phx.gbl...
> I decided to try and setup a multi instance cluster on my
> own and seem to be fairly successful . Its SQL 2000 EE on
> Windows Server 2003 EE
> Just had 2 questions. When i installed the second
> instance, it asked me for a virtual name.. so i gave it
> one ..in my case SQL2.. and then was asked for an
> instance name so i called it ins2.. Eventually this
> second sql server is now called sql2\ins2 and not sql2 as
> i had thought it would be.. The first instance which was
> a default instance was named as SQL1 . Is this the right
> way it should be ? i.e one instance called SQL1 and the
> other SQL2\ins2 in my case. I was under the impression
> that since its a virtual name i could get them to be
> called SQL1 and SQL2
> If not, then my next question is..
> When i connect to those 2 virtual names from a client, it
> seems to connect fine to SQL1 but when i connect to SQL2
> \ins2 it fails...with SQL Server does not exist or access
> denied. Any reason why ? Thanks
own and seem to be fairly successful . Its SQL 2000 EE on
Windows Server 2003 EE
Just had 2 questions. When i installed the second
instance, it asked me for a virtual name.. so i gave it
one ..in my case SQL2.. and then was asked for an
instance name so i called it ins2.. Eventually this
second sql server is now called sql2\ins2 and not sql2 as
i had thought it would be.. The first instance which was
a default instance was named as SQL1 . Is this the right
way it should be ? i.e one instance called SQL1 and the
other SQL2\ins2 in my case. I was under the impression
that since its a virtual name i could get them to be
called SQL1 and SQL2
If not, then my next question is..
When i connect to those 2 virtual names from a client, it
seems to connect fine to SQL1 but when i connect to SQL2
\ins2 it fails...with SQL Server does not exist or access
denied. Any reason why ? Thanks
Answer #1.
You can have one default instance and 15 named instances OR 16 named
instances of SQL per cluster. Each named instance will be
VirtualServerName\InstanceName. For consistancy I use only named
instances on a cluster, but that is just a personal thing.
Answer #2.
You may have an older version of MDAC on your client system. I think the
breakover is MDAC 2.6, but I may be wrong. Version 2.6 and higher
understand named instances. Versions before that do not. You can make an
older version connect to a named instance if you create an alias that
includes the port number.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Ronald" <anonymous@.discussions.microsoft.com> wrote in message
news:520a01c42ca8$dfdc9680$a301280a@.phx.gbl...
> I decided to try and setup a multi instance cluster on my
> own and seem to be fairly successful . Its SQL 2000 EE on
> Windows Server 2003 EE
> Just had 2 questions. When i installed the second
> instance, it asked me for a virtual name.. so i gave it
> one ..in my case SQL2.. and then was asked for an
> instance name so i called it ins2.. Eventually this
> second sql server is now called sql2\ins2 and not sql2 as
> i had thought it would be.. The first instance which was
> a default instance was named as SQL1 . Is this the right
> way it should be ? i.e one instance called SQL1 and the
> other SQL2\ins2 in my case. I was under the impression
> that since its a virtual name i could get them to be
> called SQL1 and SQL2
> If not, then my next question is..
> When i connect to those 2 virtual names from a client, it
> seems to connect fine to SQL1 but when i connect to SQL2
> \ins2 it fails...with SQL Server does not exist or access
> denied. Any reason why ? Thanks
Wednesday, March 21, 2012
MSTDC and windows domain
Hi,
i have this scenario :
a have web application (NT4) that use a MSTDC service on my application
server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
The service MSTDC on application server and db server start with the same
domain administration account (administrator)
Now i have install a new domain windwos 2003 and a new cluster SQL2000/MSTDC
on 2 windows 2003 server and try to modify my application to point to new
windows 2003 cluster but when i try to test it a error appared :
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator.
and found a kb article and make the modify adding a network service into
MSDTC service on cluster 2003 but the problem is not resoleved! :-(
This is because are 2 different domain and network service on 2003 isn't any
account on NT4 domain ?
If i try to trust a windows 2003 and NT4 domain i resolved it ?
The trust is only one solution or exist other solution ?
Thanks in advance.
make sure you are ussing the cluster version of DTC. On each node you
should have run comclust.exe.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
SQL2000/MSTDC
> on 2 windows 2003 server and try to modify my application to point to new
> windows 2003 cluster but when i try to test it a error appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
any
> account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
|||Hi,
yes ai use DTC cluster .
But on windows2003 for clustering DTC i don't type comclust but i must
create it manuallty ,
are you sure ?
Thanks.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:%23C7I0Pp5EHA.2572@.tk2msftngp13.phx.gbl...
> make sure you are ussing the cluster version of DTC. On each node you
> should have run comclust.exe.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> SQL2000/MSTDC
> 'SQLOLEDB'
> any
>
|||Hi,
i foun a solutiontoi my problem , the solution is :
- Trust 2 way from NT4 and 2K3
- Modify lmhost/host file for all server that are involved (i try for 2
hour first found the the optimal configuration of this file)
I habve used dctping.exe and dctester.exe for troubleshooting
And now work
Other solution instead trust is :
http://support.microsoft.com/default...b;en-us;827805
Thanks !
this is happy day!
:-)
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC on 2 windows 2003 server and try to modify my application to
> point to new windows 2003 cluster but when i try to test it a error
> appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
> any account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
i have this scenario :
a have web application (NT4) that use a MSTDC service on my application
server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
The service MSTDC on application server and db server start with the same
domain administration account (administrator)
Now i have install a new domain windwos 2003 and a new cluster SQL2000/MSTDC
on 2 windows 2003 server and try to modify my application to point to new
windows 2003 cluster but when i try to test it a error appared :
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator.
and found a kb article and make the modify adding a network service into
MSDTC service on cluster 2003 but the problem is not resoleved! :-(
This is because are 2 different domain and network service on 2003 isn't any
account on NT4 domain ?
If i try to trust a windows 2003 and NT4 domain i resolved it ?
The trust is only one solution or exist other solution ?
Thanks in advance.
make sure you are ussing the cluster version of DTC. On each node you
should have run comclust.exe.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
SQL2000/MSTDC
> on 2 windows 2003 server and try to modify my application to point to new
> windows 2003 cluster but when i try to test it a error appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
any
> account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
|||Hi,
yes ai use DTC cluster .
But on windows2003 for clustering DTC i don't type comclust but i must
create it manuallty ,
are you sure ?
Thanks.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:%23C7I0Pp5EHA.2572@.tk2msftngp13.phx.gbl...
> make sure you are ussing the cluster version of DTC. On each node you
> should have run comclust.exe.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> SQL2000/MSTDC
> 'SQLOLEDB'
> any
>
|||Hi,
i foun a solutiontoi my problem , the solution is :
- Trust 2 way from NT4 and 2K3
- Modify lmhost/host file for all server that are involved (i try for 2
hour first found the the optimal configuration of this file)
I habve used dctping.exe and dctester.exe for troubleshooting
And now work
Other solution instead trust is :
http://support.microsoft.com/default...b;en-us;827805
Thanks !
this is happy day!
:-)
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC on 2 windows 2003 server and try to modify my application to
> point to new windows 2003 cluster but when i try to test it a error
> appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
> any account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
MSTDC and windows domain
Hi,
i have this scenario :
a have web application (NT4) that use a MSTDC service on my application
server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
The service MSTDC on application server and db server start with the same
domain administration account (administrator)
Now i have install a new domain windwos 2003 and a new cluster SQL2000/MSTDC
on 2 windows 2003 server and try to modify my application to point to new
windows 2003 cluster but when i try to test it a error appared :
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator.
and found a kb article and make the modify adding a network service into
MSDTC service on cluster 2003 but the problem is not resoleved! :-(
This is because are 2 different domain and network service on 2003 isn't any
account on NT4 domain ?
If i try to trust a windows 2003 and NT4 domain i resolved it ?
The trust is only one solution or exist other solution ?
Thanks in advance.make sure you are ussing the cluster version of DTC. On each node you
should have run comclust.exe.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
SQL2000/MSTDC
> on 2 windows 2003 server and try to modify my application to point to new
> windows 2003 cluster but when i try to test it a error appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
any
> account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>|||Hi,
yes ai use DTC cluster .
But on windows2003 for clustering DTC i don't type comclust but i must
create it manuallty ,
are you sure ?
Thanks.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:%23C7I0Pp5EHA.2572@.tk2msftngp13.phx.gbl...
> make sure you are ussing the cluster version of DTC. On each node you
> should have run comclust.exe.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> i have this scenario :
>> a have web application (NT4) that use a MSTDC service on my application
>> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
>> The service MSTDC on application server and db server start with the same
>> domain administration account (administrator)
>> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC
>> on 2 windows 2003 server and try to modify my application to point to new
>> windows 2003 cluster but when i try to test it a error appared :
>> Server: Msg 7391, Level 16, State 1, Line 2
>> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
>> was unable to begin a distributed transaction. OLE/DB provider returned
>> message: New transaction cannot enlist in the specified transaction
>> coordinator.
>> and found a kb article and make the modify adding a network service into
>> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
>> This is because are 2 different domain and network service on 2003 isn't
> any
>> account on NT4 domain ?
>> If i try to trust a windows 2003 and NT4 domain i resolved it ?
>> The trust is only one solution or exist other solution ?
>> Thanks in advance.
>>
>|||Hi,
i foun a solutiontoi my problem , the solution is :
- Trust 2 way from NT4 and 2K3
- Modify lmhost/host file for all server that are involved (i try for 2
hour first found the the optimal configuration of this file)
I habve used dctping.exe and dctester.exe for troubleshooting
And now work
Other solution instead trust is :
http://support.microsoft.com/default.aspx?scid=kb;en-us;827805http://support.microsoft.com/default.aspx?scid=kb;en-us;827805
Thanks !
this is happy day!
:-)
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC on 2 windows 2003 server and try to modify my application to
> point to new windows 2003 cluster but when i try to test it a error
> appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
> any account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
i have this scenario :
a have web application (NT4) that use a MSTDC service on my application
server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
The service MSTDC on application server and db server start with the same
domain administration account (administrator)
Now i have install a new domain windwos 2003 and a new cluster SQL2000/MSTDC
on 2 windows 2003 server and try to modify my application to point to new
windows 2003 cluster but when i try to test it a error appared :
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator.
and found a kb article and make the modify adding a network service into
MSDTC service on cluster 2003 but the problem is not resoleved! :-(
This is because are 2 different domain and network service on 2003 isn't any
account on NT4 domain ?
If i try to trust a windows 2003 and NT4 domain i resolved it ?
The trust is only one solution or exist other solution ?
Thanks in advance.make sure you are ussing the cluster version of DTC. On each node you
should have run comclust.exe.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
SQL2000/MSTDC
> on 2 windows 2003 server and try to modify my application to point to new
> windows 2003 cluster but when i try to test it a error appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
any
> account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>|||Hi,
yes ai use DTC cluster .
But on windows2003 for clustering DTC i don't type comclust but i must
create it manuallty ,
are you sure ?
Thanks.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:%23C7I0Pp5EHA.2572@.tk2msftngp13.phx.gbl...
> make sure you are ussing the cluster version of DTC. On each node you
> should have run comclust.exe.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> i have this scenario :
>> a have web application (NT4) that use a MSTDC service on my application
>> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
>> The service MSTDC on application server and db server start with the same
>> domain administration account (administrator)
>> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC
>> on 2 windows 2003 server and try to modify my application to point to new
>> windows 2003 cluster but when i try to test it a error appared :
>> Server: Msg 7391, Level 16, State 1, Line 2
>> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
>> was unable to begin a distributed transaction. OLE/DB provider returned
>> message: New transaction cannot enlist in the specified transaction
>> coordinator.
>> and found a kb article and make the modify adding a network service into
>> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
>> This is because are 2 different domain and network service on 2003 isn't
> any
>> account on NT4 domain ?
>> If i try to trust a windows 2003 and NT4 domain i resolved it ?
>> The trust is only one solution or exist other solution ?
>> Thanks in advance.
>>
>|||Hi,
i foun a solutiontoi my problem , the solution is :
- Trust 2 way from NT4 and 2K3
- Modify lmhost/host file for all server that are involved (i try for 2
hour first found the the optimal configuration of this file)
I habve used dctping.exe and dctester.exe for troubleshooting
And now work
Other solution instead trust is :
http://support.microsoft.com/default.aspx?scid=kb;en-us;827805http://support.microsoft.com/default.aspx?scid=kb;en-us;827805
Thanks !
this is happy day!
:-)
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC on 2 windows 2003 server and try to modify my application to
> point to new windows 2003 cluster but when i try to test it a error
> appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
> any account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
MSSQLServerOLAPSerice will not start.
I setup a MSSQL 2005 Cluster running on top of Virtual Server 2005. Everthing was running fine until this morning, when suddenly Analysis Services failed to start on the Cluster. When I looked in the Event Log I see the following:
Source: MSSQLServerOLAPService
Category: (289)
Type: Error
Event ID: 0
Description:
The service cannot be started: The DOM parser failed to load and parse the stream. URL:'' Reason: 'A document must contain exactly one root element.
' Source:''. File position: 0. Line: 1. The DOM parser failed to load and parse the file '\\?\N:\Microsoft SQL Server\MSSQL.2\OLAP\Data\master.vmp'.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Any idea on what I can do to resolve this problem.
Thanks.
Most likely you data became corrupted. If you can reproduce the scenario you should contact product support services to troubleshoot this problem.
To get Analysis Server to start again you delete all the files in "%AS installation folder%\data" folder.
You need to restore you databases you've backed up earlier. Alternatively you can re-create and re-process all the cubes and all dimensions you had.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Monday, March 19, 2012
MSSQLServerADHelper Service
I noticed on both nodes in my 2 node cluster the MSSQLServerADHelper service
was not started and set to manual. Is there a reason why this isnt started?
Is it safe to start and set to Automatic on both nodes?
Thanks,
JBaileyHere you can read about MSSQLServerADHelper here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_cs_9mhx.asp
Regards
---
All information provided below AS IS.
"JBailey" <abc@.123.com> wrote in message
news:uWZv$$8nDHA.488@.tk2msftngp13.phx.gbl...
> I noticed on both nodes in my 2 node cluster the MSSQLServerADHelper
service
> was not started and set to manual. Is there a reason why this isnt
started?
> Is it safe to start and set to Automatic on both nodes?
> Thanks,
> JBailey
>|||"JBailey" <abc@.123.com> wrote in message
news:uWZv$$8nDHA.488@.tk2msftngp13.phx.gbl...
> I noticed on both nodes in my 2 node cluster the MSSQLServerADHelper
service
> was not started and set to manual. Is there a reason why this isnt
started?
> Is it safe to start and set to Automatic on both nodes?
>
My understanding is this is only needed if you want to register your SQL
Server instance in Active Directory. It's not needed for your cluster...
from books online (see BOL for more information0:
The MSSQLServerADHelper service performs two functions:
a.. It adds and removes the objects used to register instances of
Microsoft® SQL ServerT 2000 relational database engine or Analysis server in
the Microsoft Windows® 2000 Active DirectoryT.
b.. It ensures that the Windows account under which a SQL Server service
is running has permissions to update all of the Active Directory objects for
the instance, as well as any replication publications and databases for that
instance.
Steve
was not started and set to manual. Is there a reason why this isnt started?
Is it safe to start and set to Automatic on both nodes?
Thanks,
JBaileyHere you can read about MSSQLServerADHelper here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_cs_9mhx.asp
Regards
---
All information provided below AS IS.
"JBailey" <abc@.123.com> wrote in message
news:uWZv$$8nDHA.488@.tk2msftngp13.phx.gbl...
> I noticed on both nodes in my 2 node cluster the MSSQLServerADHelper
service
> was not started and set to manual. Is there a reason why this isnt
started?
> Is it safe to start and set to Automatic on both nodes?
> Thanks,
> JBailey
>|||"JBailey" <abc@.123.com> wrote in message
news:uWZv$$8nDHA.488@.tk2msftngp13.phx.gbl...
> I noticed on both nodes in my 2 node cluster the MSSQLServerADHelper
service
> was not started and set to manual. Is there a reason why this isnt
started?
> Is it safe to start and set to Automatic on both nodes?
>
My understanding is this is only needed if you want to register your SQL
Server instance in Active Directory. It's not needed for your cluster...
from books online (see BOL for more information0:
The MSSQLServerADHelper service performs two functions:
a.. It adds and removes the objects used to register instances of
Microsoft® SQL ServerT 2000 relational database engine or Analysis server in
the Microsoft Windows® 2000 Active DirectoryT.
b.. It ensures that the Windows account under which a SQL Server service
is running has permissions to update all of the Active Directory objects for
the instance, as well as any replication publications and databases for that
instance.
Steve
Subscribe to:
Posts (Atom)