Currently I am running 2 MSSQL SQL 2000 Enterprise servers running on Win2k3
utilizing SSL via "force protocol encryption". The systems are running fine
with the exception of Snapshots and/or DTS packages that write to the local
disk. When trying to get a snapshot to run for the local machine I recieve
the following error:
General network error. Check your network documentation.
(Source: SERVER (Data source); Error number: 11)
If I turn off "force protocol encryption" the snapshot works just fine.
I suspect the replication binaries do not support SSL. You should contact MS
(PSS) for further clarification on how to configure this.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"PSchultz" <PSchultz@.discussions.microsoft.com> wrote in message
news:A6ECD0B1-87BD-4D41-9A80-48E26BAA155A@.microsoft.com...
> Currently I am running 2 MSSQL SQL 2000 Enterprise servers running on
> Win2k3
> utilizing SSL via "force protocol encryption". The systems are running
> fine
> with the exception of Snapshots and/or DTS packages that write to the
> local
> disk. When trying to get a snapshot to run for the local machine I
> recieve
> the following error:
> General network error. Check your network documentation.
> (Source: SERVER (Data source); Error number: 11)
> If I turn off "force protocol encryption" the snapshot works just fine.
>
|||Some tables will successfully produce a snapshot, however, it is quite hit or
miss so I believe that the binaries do support SSL. I've also looked into it
being a possible issue with a timeout, however, that isn't the root cause as
the error occurs within seconds of the snapshot starting
"Hilary Cotter" wrote:
> I suspect the replication binaries do not support SSL. You should contact MS
> (PSS) for further clarification on how to configure this.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "PSchultz" <PSchultz@.discussions.microsoft.com> wrote in message
> news:A6ECD0B1-87BD-4D41-9A80-48E26BAA155A@.microsoft.com...
>
>
sql
Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts
Friday, March 30, 2012
MSSQL 2000 SP4 Memory Leak
Greetings all!
On one of our intranet SQL servers running under Windows 2000 SP 3,
MSsql 2000 SP4 seems to gradually "eat" away all available memory (with no obvious reason for it) until a certain limit is reached, forcing the server to slow down substantially since the OS has to SWAP continuously.
I would appreciate any suggestions at this point on how to tackle this problem :)
Thank you!
VincentJSThat is the nature of SQL Server. By default, it will continue to claim available memory that is not being used by applications. It's not a memory leak. Most of this memory is used for data cache, which greatly improves performance. You want SQL Server to have plenty of memory. But you can limit this amout if you view the server properties in enterprise manager.
Bill|||if you can afford it, you should have your web and database servers on different machines. I believe you can limit the amount memory sql server consums with the max server memory option in sp_configure but I have never used it
On one of our intranet SQL servers running under Windows 2000 SP 3,
MSsql 2000 SP4 seems to gradually "eat" away all available memory (with no obvious reason for it) until a certain limit is reached, forcing the server to slow down substantially since the OS has to SWAP continuously.
I would appreciate any suggestions at this point on how to tackle this problem :)
Thank you!
VincentJSThat is the nature of SQL Server. By default, it will continue to claim available memory that is not being used by applications. It's not a memory leak. Most of this memory is used for data cache, which greatly improves performance. You want SQL Server to have plenty of memory. But you can limit this amout if you view the server properties in enterprise manager.
Bill|||if you can afford it, you should have your web and database servers on different machines. I believe you can limit the amount memory sql server consums with the max server memory option in sp_configure but I have never used it
Wednesday, March 28, 2012
MSSQL 2000
MSSQL 2000 Replication between two servers on a workgroup
Is it possible? How do you set it up?
You have to decide on which type of replication strategy you need - transactional, snapshot or merge. For an idea on how it works, check out http://www.devarticles.com/c/a/SQL-Server/Replication-SQL-Server-2000--Part-1/|||Yes it is possible -as long as at least one of the servers is NOT SQL Server 2005 Express.
Check the source that Paul gave you above...
sqlMSSQL 2000
MSSQL 2000 Replication between two servers on a workgroup
Is it possible? How do you set it up?
You have to decide on which type of replication strategy you need - transactional, snapshot or merge. For an idea on how it works, check out http://www.devarticles.com/c/a/SQL-Server/Replication-SQL-Server-2000--Part-1/|||Yes it is possible -as long as at least one of the servers is NOT SQL Server 2005 Express.
Check the source that Paul gave you above...
Monday, March 26, 2012
MSreplication_subscriptions
Hello. I need to schedule a job on a database that subscribes to a
transactional publication on another server. Replication between these
two servers goes down frequently. I've been told the job that runs at
the subscriber needs to determine if replication is up and current at
the time the job runs, and if replication is NOT up and current, the
job needs to exit and run at a later time. The purpose of this
instruction seems to be so that personnel monitoring replication, do
not have to monitor and/or re-run processing on the subscriber.
It's been suggested that checking the MSreplication_subscription.time
value in the subscriber database is a solution. I see from BOL that
column is defined as the last time the Distribution agent updates the
subscriber. What's its usefulness as an indicator that replication is
working?
TIA
You could set up the inbuilt alerts to notify you if an agent has stopped
abrubtly and then take action (automatically) as a result. To see the
current state of the job, you can use this script:
http://www.replicationanswers.com/Do...unningJobs.txt
HTH
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks Paul, I'll check out the script. But it's a litlte more
complicated than simply stopping the regularly-scheduled job.
Basically, they want any and all regularly-scheduled processing at the
subscriber, to be completely self-repairing when it comes to
replication being up, down, or in the progress of catching up. The
personnel that monitor this repository are somoewhat restricted in how
they can use the inbuilt SQL Server alerts, because of security
concerns. They use that and the fact that replication is undependable,
to justify this requirement that jobs be replication-proof.
as a side question, am I way off base in my opinion that production
DBA's should moniitor jobs on production boxes, as a matter of course?
thanks again...
|||OK - if the replication setup should be self-repairing then I must ask -
what errors are causing it to go down? If it is an unreliable connection
then the agents can be set in a loop to restart automatically, but if it is
anything more difficult then the source should be registered and in most
cases needs to be dealt with. Replication alerts will allow your DBAs to
know via email when something has caused the agents to stop, and the
alternative is to effectively poll the system - either manually by going in
to replication monitor and looking for the red icons or or in code, but for
my money this is reinventing the wheel as the alerts are there for this
purpose. I definitely agree that monitoring of jobs is part of the
Production DBAs work - that's what the Notifications tab is for on the Jobs
form - and most DBAs Demand this info rather than have to be persuaded that
it's worthwhile
.
Rgds
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I think their replication IS set up to be self-repairing. The problem
is they want JOBS to be self-repairing, when it comes to replication
being down.
This job creates a dataset for use by a downstream process (that occurs
hours later). If replication is down when this job runs, the dataset
*may* be missing data, with no way for the processes that use it to
tell. My solution to that issue was for monitoring personnel to have
the knowledge that if replication is down, this job has to be manually
re-run. They want that situation to be automated in some fashion.
They have suggested that the job run in a continuous loop until it can
determine that replication is up-to-date. Thus, the suggestion to use
MSreplication_subscriptions.
I agree with you that the real issue is why replication is so
undependable. At this point I feel like saying, what is the point of
having a subscriber repository if processing that runs there always has
to check whether data is current?
thanks for letting me vent :-)
sql
transactional publication on another server. Replication between these
two servers goes down frequently. I've been told the job that runs at
the subscriber needs to determine if replication is up and current at
the time the job runs, and if replication is NOT up and current, the
job needs to exit and run at a later time. The purpose of this
instruction seems to be so that personnel monitoring replication, do
not have to monitor and/or re-run processing on the subscriber.
It's been suggested that checking the MSreplication_subscription.time
value in the subscriber database is a solution. I see from BOL that
column is defined as the last time the Distribution agent updates the
subscriber. What's its usefulness as an indicator that replication is
working?
TIA
You could set up the inbuilt alerts to notify you if an agent has stopped
abrubtly and then take action (automatically) as a result. To see the
current state of the job, you can use this script:
http://www.replicationanswers.com/Do...unningJobs.txt
HTH
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks Paul, I'll check out the script. But it's a litlte more
complicated than simply stopping the regularly-scheduled job.
Basically, they want any and all regularly-scheduled processing at the
subscriber, to be completely self-repairing when it comes to
replication being up, down, or in the progress of catching up. The
personnel that monitor this repository are somoewhat restricted in how
they can use the inbuilt SQL Server alerts, because of security
concerns. They use that and the fact that replication is undependable,
to justify this requirement that jobs be replication-proof.
as a side question, am I way off base in my opinion that production
DBA's should moniitor jobs on production boxes, as a matter of course?
thanks again...
|||OK - if the replication setup should be self-repairing then I must ask -
what errors are causing it to go down? If it is an unreliable connection
then the agents can be set in a loop to restart automatically, but if it is
anything more difficult then the source should be registered and in most
cases needs to be dealt with. Replication alerts will allow your DBAs to
know via email when something has caused the agents to stop, and the
alternative is to effectively poll the system - either manually by going in
to replication monitor and looking for the red icons or or in code, but for
my money this is reinventing the wheel as the alerts are there for this
purpose. I definitely agree that monitoring of jobs is part of the
Production DBAs work - that's what the Notifications tab is for on the Jobs
form - and most DBAs Demand this info rather than have to be persuaded that
it's worthwhile
.Rgds
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I think their replication IS set up to be self-repairing. The problem
is they want JOBS to be self-repairing, when it comes to replication
being down.
This job creates a dataset for use by a downstream process (that occurs
hours later). If replication is down when this job runs, the dataset
*may* be missing data, with no way for the processes that use it to
tell. My solution to that issue was for monitoring personnel to have
the knowledge that if replication is down, this job has to be manually
re-run. They want that situation to be automated in some fashion.
They have suggested that the job run in a continuous loop until it can
determine that replication is up-to-date. Thus, the suggestion to use
MSreplication_subscriptions.
I agree with you that the real issue is why replication is so
undependable. At this point I feel like saying, what is the point of
having a subscriber repository if processing that runs there always has
to check whether data is current?
thanks for letting me vent :-)
sql
Wednesday, March 21, 2012
MSI and SQL Server Detection
how do they provide the dialog box in the start kits, the one with the combo boxes of available servers, and a test connection button?
You can add custom forms in visual studio setup wizard project, but I haven't been able to figure it out yet - what do they use in the starter kits?view post 360458 discusses it. You can also call the sproc sp_helpserver which returns a recordset with the names of the available Sql Servers and MSDEs.
Monday, March 19, 2012
Msg 7314 while querying across linked servers
Hello
I am beginning to think that linked server are more trouble than they are wo
rth and MS will need to work harder to get these to work properly. Here is t
he latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."t
ables"'. The table either does not exist or the current user does not have
permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not conta
in the table: ProviderName='srv2', TableName='"db1"."information_schema"."ta
bles"'].
It works if I connect to srv2 with the login being used to link the 2 server
s and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
ArunArun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are
worth and MS will need to work harder to get these to work properly. Here is
the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema".
"tables"'. The table either does not exist or the current user does not hav
e permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not con
tain the table: ProviderName='srv2', TableName='"db1"."information_schema"."
tables"'].
> It works if I connect to srv2 with the login being used to link the 2 serv
ers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>|||It works. Thanks Mark
Arun
"Mark Allison" wrote:
> Arun,
> Try this:
> exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Arun wrote:
>
I am beginning to think that linked server are more trouble than they are wo
rth and MS will need to work harder to get these to work properly. Here is t
he latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."t
ables"'. The table either does not exist or the current user does not have
permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not conta
in the table: ProviderName='srv2', TableName='"db1"."information_schema"."ta
bles"'].
It works if I connect to srv2 with the login being used to link the 2 server
s and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
ArunArun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are
worth and MS will need to work harder to get these to work properly. Here is
the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema".
"tables"'. The table either does not exist or the current user does not hav
e permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not con
tain the table: ProviderName='srv2', TableName='"db1"."information_schema"."
tables"'].
> It works if I connect to srv2 with the login being used to link the 2 serv
ers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>|||It works. Thanks Mark
Arun
"Mark Allison" wrote:
> Arun,
> Try this:
> exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Arun wrote:
>
Msg 7314 while querying across linked servers
Hello
I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
It works if I connect to srv2 with the login being used to link the 2 servers and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
Arun
Arun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
> It works if I connect to srv2 with the login being used to link the 2 servers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>
|||It works. Thanks Mark
Arun
"Mark Allison" wrote:
> Arun,
> Try this:
> exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Arun wrote:
>
I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
It works if I connect to srv2 with the login being used to link the 2 servers and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
Arun
Arun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
> It works if I connect to srv2 with the login being used to link the 2 servers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>
|||It works. Thanks Mark
Arun
"Mark Allison" wrote:
> Arun,
> Try this:
> exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Arun wrote:
>
Msg 7314 while querying across linked servers
Hello
I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
It works if I connect to srv2 with the login being used to link the 2 servers and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
ArunArun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
> It works if I connect to srv2 with the login being used to link the 2 servers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>
I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
From srv1, when I do
select * from srv2.db1.information_schema.tables
I get
Server: Msg 7314, Level 16, State 1, Line 1
OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
It works if I connect to srv2 with the login being used to link the 2 servers and do
use db1
go
select * from information_schema.tables
go
Also if I do <<<select * from srv2.db1.dbo.someothertable>> it works.
Trying this on SQL Server 2000 enterprise hotfix 837.
Any clues?
Thanks for reading and appreciate your help
ArunArun,
Try this:
exec srv2.db1.dbo.sp_executesql N'select * from information_schema.tables'
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Arun wrote:
> Hello
> I am beginning to think that linked server are more trouble than they are worth and MS will need to work harder to get these to work properly. Here is the latest problem.
>
> From srv1, when I do
> select * from srv2.db1.information_schema.tables
> I get
> Server: Msg 7314, Level 16, State 1, Line 1
> OLE DB provider 'srv2' does not contain table '"db1"."information_schema"."tables"'. The table either does not exist or the current user does not have permissions on that table.
> OLE DB error trace [Non-interface error: OLE DB provider does not contain the table: ProviderName='srv2', TableName='"db1"."information_schema"."tables"'].
> It works if I connect to srv2 with the login being used to link the 2 servers and do
> use db1
> go
> select * from information_schema.tables
> go
> Also if I do <<<select * from srv2.db1.dbo.someothertable>> it works.
> Trying this on SQL Server 2000 enterprise hotfix 837.
> Any clues?
> Thanks for reading and appreciate your help
> Arun
>
Wednesday, March 7, 2012
MSDTC unable to go online
Hi,
I have a problem starting my MSDTC.
I have enable network DTC access (following the instructions in MS KB
817064) on two of my servers before I clustered them. The DTC services run
well. After that, I configured my servers in cluster Node A and B
(Active/Passive). The DTC immediately failed to start. I carried on and
configured my MSDTC resources (following the instructions in MS KB 301600) on
Node A. The other resources like IP, Physical disk, Network name able to
bring online except for DTC.
What is happening? I have tried my best to follow all instructions as
closely as possible. I seems to be struck. Still have to install SQL 2005
but now spend days to resolve the MSDTC issue. Please kindly help me!
Thanks a lot in advance!
Received error like
MS DTC was unable to start because the installation was not configured to
run on a cluster. Please create a MS DTC resource through cluster
administrator. Error Specifics:
d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:534, Pid: 3192,
CmdLine: C:\WINDOWS\system32\msdtc.exe
Could not start the MS DTC Transaction Manager.
MS DTC Transaction Manager start failed. LogInit returned error 0x3.
Dear Shann Lim,
Have a look at this KB http://support.microsoft.com/kb/867520
and let us know if that solved your problem
good luck,
Edwin.
"Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message
news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
> Hi,
> I have a problem starting my MSDTC.
> I have enable network DTC access (following the instructions in MS KB
> 817064) on two of my servers before I clustered them. The DTC services
run
> well. After that, I configured my servers in cluster Node A and B
> (Active/Passive). The DTC immediately failed to start. I carried on and
> configured my MSDTC resources (following the instructions in MS KB 301600)
on
> Node A. The other resources like IP, Physical disk, Network name able to
> bring online except for DTC.
> What is happening? I have tried my best to follow all instructions as
> closely as possible. I seems to be struck. Still have to install SQL
2005
> but now spend days to resolve the MSDTC issue. Please kindly help me!
> Thanks a lot in advance!
> Received error like
> MS DTC was unable to start because the installation was not configured to
> run on a cluster. Please create a MS DTC resource through cluster
> administrator. Error Specifics:
> d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:534, Pid:
3192,
> CmdLine: C:\WINDOWS\system32\msdtc.exe
> Could not start the MS DTC Transaction Manager.
> MS DTC Transaction Manager start failed. LogInit returned error 0x3.
>
>
>
>
|||Microsoft has a fix that I have used several times. Free from PSS. Only the web page for version 6 & 7 are not on the net today.
Google shows this though:
Availability of the Windows Server 2003 Post-Service Pack 1 COM+ ...897667 (http://support.microsoft.com/kb/897667/) Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...
support.microsoft.com/kb/921981 - Similar pages
Could be because SP2 is right around the corner now...
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
> Hi,
> I have a problem starting my MSDTC.
> I have enable network DTC access (following the instructions in MS KB
> 817064) on two of my servers before I clustered them. The DTC services run
> well. After that, I configured my servers in cluster Node A and B
> (Active/Passive). The DTC immediately failed to start. I carried on and
> configured my MSDTC resources (following the instructions in MS KB 301600) on
> Node A. The other resources like IP, Physical disk, Network name able to
> bring online except for DTC.
> What is happening? I have tried my best to follow all instructions as
> closely as possible. I seems to be struck. Still have to install SQL 2005
> but now spend days to resolve the MSDTC issue. Please kindly help me!
> Thanks a lot in advance!
> Received error like
> MS DTC was unable to start because the installation was not configured to
> run on a cluster. Please create a MS DTC resource through cluster
> administrator. Error Specifics:
> d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:534, Pid: 3192,
> CmdLine: C:\WINDOWS\system32\msdtc.exe
> Could not start the MS DTC Transaction Manager.
> MS DTC Transaction Manager start failed. LogInit returned error 0x3.
>
>
>
>
|||Hi,
I appreciate all the helps.
But may I noe where to d/l the COM+ patch?
Thank you.
"Rodney R. Fournier [MVP]" wrote:
[vbcol=seagreen]
> Microsoft has a fix that I have used several times. Free from PSS. Only the web page for version 6 & 7 are not on the net today.
> Google shows this though:
> Availability of the Windows Server 2003 Post-Service Pack 1 COM+ ...897667 (http://support.microsoft.com/kb/897667/) Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...
> support.microsoft.com/kb/921981 - Similar pages
>
> Could be because SP2 is right around the corner now...
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
|||Hi,
Sorry. I think I forgotten to include that I am using Win2k3 SP 1 for my
nodes. THe articles given by Mr Fournier and Mr Mierlo seems to be for
Win2k. Is it applicable for my case?
Thanks again.
"Rodney R. Fournier [MVP]" wrote:
[vbcol=seagreen]
> Microsoft has a fix that I have used several times. Free from PSS. Only the web page for version 6 & 7 are not on the net today.
> Google shows this though:
> Availability of the Windows Server 2003 Post-Service Pack 1 COM+ ...897667 (http://support.microsoft.com/kb/897667/) Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...
> support.microsoft.com/kb/921981 - Similar pages
>
> Could be because SP2 is right around the corner now...
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
|||Dear Shann Lim,
http://support.microsoft.com/kb/897667
is for Windows 2003
HTH,
Edwin.
"Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message
news:D3B191E6-503E-445A-8B0D-20109E5D1E7F@.microsoft.com...[vbcol=seagreen]
> Hi,
> Sorry. I think I forgotten to include that I am using Win2k3 SP 1 for my
> nodes. THe articles given by Mr Fournier and Mr Mierlo seems to be for
> Win2k. Is it applicable for my case?
> Thanks again.
> "Rodney R. Fournier [MVP]" wrote:
the web page for version 6 & 7 are not on the net today.[vbcol=seagreen]
....897667 (http://support.microsoft.com/kb/897667/) Availability of Windows
Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...[vbcol=seagreen]
news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...[vbcol=seagreen]
services run[vbcol=seagreen]
and[vbcol=seagreen]
301600) on[vbcol=seagreen]
to[vbcol=seagreen]
2005[vbcol=seagreen]
to[vbcol=seagreen]
Pid: 3192,[vbcol=seagreen]
I have a problem starting my MSDTC.
I have enable network DTC access (following the instructions in MS KB
817064) on two of my servers before I clustered them. The DTC services run
well. After that, I configured my servers in cluster Node A and B
(Active/Passive). The DTC immediately failed to start. I carried on and
configured my MSDTC resources (following the instructions in MS KB 301600) on
Node A. The other resources like IP, Physical disk, Network name able to
bring online except for DTC.
What is happening? I have tried my best to follow all instructions as
closely as possible. I seems to be struck. Still have to install SQL 2005
but now spend days to resolve the MSDTC issue. Please kindly help me!
Thanks a lot in advance!
Received error like
MS DTC was unable to start because the installation was not configured to
run on a cluster. Please create a MS DTC resource through cluster
administrator. Error Specifics:
d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:534, Pid: 3192,
CmdLine: C:\WINDOWS\system32\msdtc.exe
Could not start the MS DTC Transaction Manager.
MS DTC Transaction Manager start failed. LogInit returned error 0x3.
Dear Shann Lim,
Have a look at this KB http://support.microsoft.com/kb/867520
and let us know if that solved your problem
good luck,
Edwin.
"Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message
news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
> Hi,
> I have a problem starting my MSDTC.
> I have enable network DTC access (following the instructions in MS KB
> 817064) on two of my servers before I clustered them. The DTC services
run
> well. After that, I configured my servers in cluster Node A and B
> (Active/Passive). The DTC immediately failed to start. I carried on and
> configured my MSDTC resources (following the instructions in MS KB 301600)
on
> Node A. The other resources like IP, Physical disk, Network name able to
> bring online except for DTC.
> What is happening? I have tried my best to follow all instructions as
> closely as possible. I seems to be struck. Still have to install SQL
2005
> but now spend days to resolve the MSDTC issue. Please kindly help me!
> Thanks a lot in advance!
> Received error like
> MS DTC was unable to start because the installation was not configured to
> run on a cluster. Please create a MS DTC resource through cluster
> administrator. Error Specifics:
> d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:534, Pid:
3192,
> CmdLine: C:\WINDOWS\system32\msdtc.exe
> Could not start the MS DTC Transaction Manager.
> MS DTC Transaction Manager start failed. LogInit returned error 0x3.
>
>
>
>
|||Microsoft has a fix that I have used several times. Free from PSS. Only the web page for version 6 & 7 are not on the net today.
Google shows this though:
Availability of the Windows Server 2003 Post-Service Pack 1 COM+ ...897667 (http://support.microsoft.com/kb/897667/) Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...
support.microsoft.com/kb/921981 - Similar pages
Could be because SP2 is right around the corner now...
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
> Hi,
> I have a problem starting my MSDTC.
> I have enable network DTC access (following the instructions in MS KB
> 817064) on two of my servers before I clustered them. The DTC services run
> well. After that, I configured my servers in cluster Node A and B
> (Active/Passive). The DTC immediately failed to start. I carried on and
> configured my MSDTC resources (following the instructions in MS KB 301600) on
> Node A. The other resources like IP, Physical disk, Network name able to
> bring online except for DTC.
> What is happening? I have tried my best to follow all instructions as
> closely as possible. I seems to be struck. Still have to install SQL 2005
> but now spend days to resolve the MSDTC issue. Please kindly help me!
> Thanks a lot in advance!
> Received error like
> MS DTC was unable to start because the installation was not configured to
> run on a cluster. Please create a MS DTC resource through cluster
> administrator. Error Specifics:
> d:\srvrtm\com\complus\dtc\shared\mtxclu\mtxclusetu phelper.cpp:534, Pid: 3192,
> CmdLine: C:\WINDOWS\system32\msdtc.exe
> Could not start the MS DTC Transaction Manager.
> MS DTC Transaction Manager start failed. LogInit returned error 0x3.
>
>
>
>
|||Hi,
I appreciate all the helps.
But may I noe where to d/l the COM+ patch?
Thank you.
"Rodney R. Fournier [MVP]" wrote:
[vbcol=seagreen]
> Microsoft has a fix that I have used several times. Free from PSS. Only the web page for version 6 & 7 are not on the net today.
> Google shows this though:
> Availability of the Windows Server 2003 Post-Service Pack 1 COM+ ...897667 (http://support.microsoft.com/kb/897667/) Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...
> support.microsoft.com/kb/921981 - Similar pages
>
> Could be because SP2 is right around the corner now...
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
|||Hi,
Sorry. I think I forgotten to include that I am using Win2k3 SP 1 for my
nodes. THe articles given by Mr Fournier and Mr Mierlo seems to be for
Win2k. Is it applicable for my case?
Thanks again.
"Rodney R. Fournier [MVP]" wrote:
[vbcol=seagreen]
> Microsoft has a fix that I have used several times. Free from PSS. Only the web page for version 6 & 7 are not on the net today.
> Google shows this though:
> Availability of the Windows Server 2003 Post-Service Pack 1 COM+ ...897667 (http://support.microsoft.com/kb/897667/) Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...
> support.microsoft.com/kb/921981 - Similar pages
>
> Could be because SP2 is right around the corner now...
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...
|||Dear Shann Lim,
http://support.microsoft.com/kb/897667
is for Windows 2003
HTH,
Edwin.
"Shann Lim" <ShannLim@.discussions.microsoft.com> wrote in message
news:D3B191E6-503E-445A-8B0D-20109E5D1E7F@.microsoft.com...[vbcol=seagreen]
> Hi,
> Sorry. I think I forgotten to include that I am using Win2k3 SP 1 for my
> nodes. THe articles given by Mr Fournier and Mr Mierlo seems to be for
> Win2k. Is it applicable for my case?
> Thanks again.
> "Rodney R. Fournier [MVP]" wrote:
the web page for version 6 & 7 are not on the net today.[vbcol=seagreen]
....897667 (http://support.microsoft.com/kb/897667/) Availability of Windows
Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 ...[vbcol=seagreen]
news:36DA21D5-FF1C-47D7-82EC-585E86597416@.microsoft.com...[vbcol=seagreen]
services run[vbcol=seagreen]
and[vbcol=seagreen]
301600) on[vbcol=seagreen]
to[vbcol=seagreen]
2005[vbcol=seagreen]
to[vbcol=seagreen]
Pid: 3192,[vbcol=seagreen]
MSDTC settings in a cluster.
Hi everyone,
I am new to this so any help will be much appreciated.
I have a problem running triggers between two SQL servers. I am running
Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
which pointed me to enable MSDTC by checking the Allow Outbound and
Allow Inbound checkboxes. My question is where do I set these boxes on
the cluster, on the nodes that make up the cluster or on both?
Thanks for your help!
Eugene.On the node that has control of the MSDTC resource. The cluster service take
care of replicating the setting to the other possible nodes.
Linchi
"Eugene" wrote:
> Hi everyone,
> I am new to this so any help will be much appreciated.
> I have a problem running triggers between two SQL servers. I am running
> Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> which pointed me to enable MSDTC by checking the Allow Outbound and
> Allow Inbound checkboxes. My question is where do I set these boxes on
> the cluster, on the nodes that make up the cluster or on both?
> Thanks for your help!
> Eugene.
>|||Also in the cluster manager you can create the service to be handle by the
clusters nodes and you will have the setting on all notes just in case.
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Linchi Shea" wrote:
[vbcol=seagreen]
> On the node that has control of the MSDTC resource. The cluster service ta
ke
> care of replicating the setting to the other possible nodes.
> Linchi
> "Eugene" wrote:
>
I am new to this so any help will be much appreciated.
I have a problem running triggers between two SQL servers. I am running
Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
which pointed me to enable MSDTC by checking the Allow Outbound and
Allow Inbound checkboxes. My question is where do I set these boxes on
the cluster, on the nodes that make up the cluster or on both?
Thanks for your help!
Eugene.On the node that has control of the MSDTC resource. The cluster service take
care of replicating the setting to the other possible nodes.
Linchi
"Eugene" wrote:
> Hi everyone,
> I am new to this so any help will be much appreciated.
> I have a problem running triggers between two SQL servers. I am running
> Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> which pointed me to enable MSDTC by checking the Allow Outbound and
> Allow Inbound checkboxes. My question is where do I set these boxes on
> the cluster, on the nodes that make up the cluster or on both?
> Thanks for your help!
> Eugene.
>|||Also in the cluster manager you can create the service to be handle by the
clusters nodes and you will have the setting on all notes just in case.
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Linchi Shea" wrote:
[vbcol=seagreen]
> On the node that has control of the MSDTC resource. The cluster service ta
ke
> care of replicating the setting to the other possible nodes.
> Linchi
> "Eugene" wrote:
>
MSDTC settings in a cluster.
Hi everyone,
I am new to this so any help will be much appreciated.
I have a problem running triggers between two SQL servers. I am running
Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
which pointed me to enable MSDTC by checking the Allow Outbound and
Allow Inbound checkboxes. My question is where do I set these boxes on
the cluster, on the nodes that make up the cluster or on both?
Thanks for your help!
Eugene.On the node that has control of the MSDTC resource. The cluster service take
care of replicating the setting to the other possible nodes.
Linchi
"Eugene" wrote:
> Hi everyone,
> I am new to this so any help will be much appreciated.
> I have a problem running triggers between two SQL servers. I am running
> Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> which pointed me to enable MSDTC by checking the Allow Outbound and
> Allow Inbound checkboxes. My question is where do I set these boxes on
> the cluster, on the nodes that make up the cluster or on both?
> Thanks for your help!
> Eugene.
>|||Also in the cluster manager you can create the service to be handle by the
clusters nodes and you will have the setting on all notes just in case.
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Linchi Shea" wrote:
> On the node that has control of the MSDTC resource. The cluster service take
> care of replicating the setting to the other possible nodes.
> Linchi
> "Eugene" wrote:
> > Hi everyone,
> >
> > I am new to this so any help will be much appreciated.
> >
> > I have a problem running triggers between two SQL servers. I am running
> > Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> > which pointed me to enable MSDTC by checking the Allow Outbound and
> > Allow Inbound checkboxes. My question is where do I set these boxes on
> > the cluster, on the nodes that make up the cluster or on both?
> >
> > Thanks for your help!
> > Eugene.
> >
> >
I am new to this so any help will be much appreciated.
I have a problem running triggers between two SQL servers. I am running
Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
which pointed me to enable MSDTC by checking the Allow Outbound and
Allow Inbound checkboxes. My question is where do I set these boxes on
the cluster, on the nodes that make up the cluster or on both?
Thanks for your help!
Eugene.On the node that has control of the MSDTC resource. The cluster service take
care of replicating the setting to the other possible nodes.
Linchi
"Eugene" wrote:
> Hi everyone,
> I am new to this so any help will be much appreciated.
> I have a problem running triggers between two SQL servers. I am running
> Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> which pointed me to enable MSDTC by checking the Allow Outbound and
> Allow Inbound checkboxes. My question is where do I set these boxes on
> the cluster, on the nodes that make up the cluster or on both?
> Thanks for your help!
> Eugene.
>|||Also in the cluster manager you can create the service to be handle by the
clusters nodes and you will have the setting on all notes just in case.
Santos Martinez,MCSE, MCDBA, MCTS
IT Community Staff of Puerto Rico
http://www.itcspr.org
"Linchi Shea" wrote:
> On the node that has control of the MSDTC resource. The cluster service take
> care of replicating the setting to the other possible nodes.
> Linchi
> "Eugene" wrote:
> > Hi everyone,
> >
> > I am new to this so any help will be much appreciated.
> >
> > I have a problem running triggers between two SQL servers. I am running
> > Windows Server 2003 and SQL server 2000 SP4. I found Microsoft article
> > which pointed me to enable MSDTC by checking the Allow Outbound and
> > Allow Inbound checkboxes. My question is where do I set these boxes on
> > the cluster, on the nodes that make up the cluster or on both?
> >
> > Thanks for your help!
> > Eugene.
> >
> >
MSDTC Problem
Hi,
I recently moved & upgraded a database from 7.0 to 2000 that makes use of linked servers. After upgrading, a number of queries started failing with the error below. These linked servers with this problem either had a stopped MSDTC or were behind a firewall. I've read the articles on how to configure MSDTC to work through a firewall, but before I do this I'm wondering why this is even happening. There were no problems when the database was at SQL 7.0. Does anyone know why sql 2000 would need to use MSDTC, but SQL7.0 would not? I don't need to use a distributed transaction, so ideally I'd like to somehow tell SQL not to use MSDTC at all. Any ideas?
Thanks
Server: Msg 7391, Level 16, State 1, Line 1
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].Thanks in advance for any help you can offer.
I have same problem as cpyne.
I recently upgraded a SQL server 7.0 box to SQL server 2000.
(Standard edition)
I had several stored procs selecting data from linked servers and inserting into local tables.
They all ran fine for the last 2 years but after the upgrade they all fail.
Linked servers include SQL Server, ORACLE and INFORMIX databases.
Error report indicates that MSDTC is now unable to begin distributed transaction.
Anybody know why MSDTC is suddenly failing after I switched from version 7 to 2000?|||On most of our servers that had this problem, MSDTC was stopped on the remote server. Starting it and setting it to automatic fixed the issue. There were a few queries that didn't even appear to be distributed transactions. They were just local tables with joins to linked servers. I spoke with MS about this and they said that SQL 2000 makes more use for MSDTC in places where SQL 7.0 didn't. The only servers where we had difficulty getting this working were ones where there was a firewall between the master server and the linked ones. In the end we dicided to chang the logic of our application, but MS suggested some articles that listed which ports needed to be opened. I don't have them handy, but if you have this problem, search on Firewall and MSDTC.
Charlie
I recently moved & upgraded a database from 7.0 to 2000 that makes use of linked servers. After upgrading, a number of queries started failing with the error below. These linked servers with this problem either had a stopped MSDTC or were behind a firewall. I've read the articles on how to configure MSDTC to work through a firewall, but before I do this I'm wondering why this is even happening. There were no problems when the database was at SQL 7.0. Does anyone know why sql 2000 would need to use MSDTC, but SQL7.0 would not? I don't need to use a distributed transaction, so ideally I'd like to somehow tell SQL not to use MSDTC at all. Any ideas?
Thanks
Server: Msg 7391, Level 16, State 1, Line 1
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].Thanks in advance for any help you can offer.
I have same problem as cpyne.
I recently upgraded a SQL server 7.0 box to SQL server 2000.
(Standard edition)
I had several stored procs selecting data from linked servers and inserting into local tables.
They all ran fine for the last 2 years but after the upgrade they all fail.
Linked servers include SQL Server, ORACLE and INFORMIX databases.
Error report indicates that MSDTC is now unable to begin distributed transaction.
Anybody know why MSDTC is suddenly failing after I switched from version 7 to 2000?|||On most of our servers that had this problem, MSDTC was stopped on the remote server. Starting it and setting it to automatic fixed the issue. There were a few queries that didn't even appear to be distributed transactions. They were just local tables with joins to linked servers. I spoke with MS about this and they said that SQL 2000 makes more use for MSDTC in places where SQL 7.0 didn't. The only servers where we had difficulty getting this working were ones where there was a firewall between the master server and the linked ones. In the end we dicided to chang the logic of our application, but MS suggested some articles that listed which ports needed to be opened. I don't have them handy, but if you have this problem, search on Firewall and MSDTC.
Charlie
MSDTC on server xx is unavailable
Hi:
We have 2 sql server(both sql2000) and using update/insert
triggers to replicate between the 2 servers. the
replication has been working and now We got this error
when doing an update:
ole/db provider returned message, new transaction cannot
enlist in the specified transaction coordinator. the
operation could not be performed because the oledb
provider 'sqloledb' was unable to begin a distributed
transaction.
So I restarted msdtc service on both sql servers, now when
running an update, I got msdtc on server
destinationservernm is unavailable, but both dtc services
are started. Any thoughts? thanks.Which OS version?
--
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2003 All rights reserved.
"dean" <dean@.hotmail.com> wrote in message
news:016b01c377c6$693f1e40$a401280a@.phx.gbl...
> Hi:
> We have 2 sql server(both sql2000) and using update/insert
> triggers to replicate between the 2 servers. the
> replication has been working and now We got this error
> when doing an update:
> ole/db provider returned message, new transaction cannot
> enlist in the specified transaction coordinator. the
> operation could not be performed because the oledb
> provider 'sqloledb' was unable to begin a distributed
> transaction.
> So I restarted msdtc service on both sql servers, now when
> running an update, I got msdtc on server
> destinationservernm is unavailable, but both dtc services
> are started. Any thoughts? thanks.
We have 2 sql server(both sql2000) and using update/insert
triggers to replicate between the 2 servers. the
replication has been working and now We got this error
when doing an update:
ole/db provider returned message, new transaction cannot
enlist in the specified transaction coordinator. the
operation could not be performed because the oledb
provider 'sqloledb' was unable to begin a distributed
transaction.
So I restarted msdtc service on both sql servers, now when
running an update, I got msdtc on server
destinationservernm is unavailable, but both dtc services
are started. Any thoughts? thanks.Which OS version?
--
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2003 All rights reserved.
"dean" <dean@.hotmail.com> wrote in message
news:016b01c377c6$693f1e40$a401280a@.phx.gbl...
> Hi:
> We have 2 sql server(both sql2000) and using update/insert
> triggers to replicate between the 2 servers. the
> replication has been working and now We got this error
> when doing an update:
> ole/db provider returned message, new transaction cannot
> enlist in the specified transaction coordinator. the
> operation could not be performed because the oledb
> provider 'sqloledb' was unable to begin a distributed
> transaction.
> So I restarted msdtc service on both sql servers, now when
> running an update, I got msdtc on server
> destinationservernm is unavailable, but both dtc services
> are started. Any thoughts? thanks.
Saturday, February 25, 2012
MSDTC name resolution - two servers same bios name
Is there any way to set up name resolution for DTC when there are two servers with the same name? I have three servers - two production systems named "SQL" and an archive system "DMART". I want to run DTC procedures to archive data from both SQL's to the DMART. Is there any way to set up the DMART so it can properly resolve the names from each of the SQL's? They are on separate networks, but unfortunately have the same NetBIOS name.When two computers that are not running in the same domain use MSDTC for communication and for distributed transactions, the mutual authentication may fail.
And I don't think its possible to set name resolution if the BIOS is similar.|||Can the #DOM: option in the lmhosts file be used to specify different networks for hosts with the same BIOS name? Will DTC recognize the #DOM: option during name resolution?|||Added after an entry to associate that entry with the domain specified by domain. This keyword affects how the Browser and Logon services behave in routed TCP/IP environments.
Still I'm bit unsure about the approach, may try and take help of network admin.
And I don't think its possible to set name resolution if the BIOS is similar.|||Can the #DOM: option in the lmhosts file be used to specify different networks for hosts with the same BIOS name? Will DTC recognize the #DOM: option during name resolution?|||Added after an entry to associate that entry with the domain specified by domain. This keyword affects how the Browser and Logon services behave in routed TCP/IP environments.
Still I'm bit unsure about the approach, may try and take help of network admin.
msdtc is down
The resource msdtc is down. Every time, it works pretty well , after we restart the servers(node1 and node2). But, about half a hour later, the problem is there. We reintalled msdtc. It didn't work out too. msdtc and sql server is on a cluster. Can anyone help me out?
What has this got to do with SSIS, the title of this forum?
Have you looked at any MS DTC troubleshooting resources?
Have you looked in the event log?
MSDTC Fails
SQL Server 2000 servers are running on two different servers on Windows 2003.
One is part of domain but the other one is not part of any domain.
MSDTC failed to communicate with error msg 7391.
Followed the instruction as mentioned in KB-329332, but still failed.
Followed the instruction as mentioned in KB-827805 but failed too. In
KB-827805, it only tells to add the registry with value name
"TurnOffRpcSecurity". Is it the only thing to do ?
OR both server must be run under the same domain.
Can any SQL Server MVP or Microsoft technical support persons help ?
"Johnny" wrote:
> SQL Server 2000 servers are running on two different servers on Windows 2003.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>
|||Have you enabled Network COM+ and DTC access under application server on the
add\remove windows components portion of add\remove programs?
nivek
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
> SQL Server 2000 servers are running on two different servers on Windows
> 2003.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>
|||I also went through the KB-816701. The components Network COM+ and Network
DTC access are already enable by default.
When I put the two servers to the same domain, MSDTC works beautifully. But
why Windows 2003 has this restriction.
"nivek" wrote:
> Have you enabled Network COM+ and DTC access under application server on the
> add\remove windows components portion of add\remove programs?
> --
> nivek
>
>
> "Johnny" <Johnny@.discussions.microsoft.com> wrote in message
> news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
>
>
One is part of domain but the other one is not part of any domain.
MSDTC failed to communicate with error msg 7391.
Followed the instruction as mentioned in KB-329332, but still failed.
Followed the instruction as mentioned in KB-827805 but failed too. In
KB-827805, it only tells to add the registry with value name
"TurnOffRpcSecurity". Is it the only thing to do ?
OR both server must be run under the same domain.
Can any SQL Server MVP or Microsoft technical support persons help ?
"Johnny" wrote:
> SQL Server 2000 servers are running on two different servers on Windows 2003.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>
|||Have you enabled Network COM+ and DTC access under application server on the
add\remove windows components portion of add\remove programs?
nivek
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
> SQL Server 2000 servers are running on two different servers on Windows
> 2003.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>
|||I also went through the KB-816701. The components Network COM+ and Network
DTC access are already enable by default.
When I put the two servers to the same domain, MSDTC works beautifully. But
why Windows 2003 has this restriction.
"nivek" wrote:
> Have you enabled Network COM+ and DTC access under application server on the
> add\remove windows components portion of add\remove programs?
> --
> nivek
>
>
> "Johnny" <Johnny@.discussions.microsoft.com> wrote in message
> news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
>
>
MSDTC Fails
SQL Server 2000 servers are running on two different servers on Windows 2003.
One is part of domain but the other one is not part of any domain.
MSDTC failed to communicate with error msg 7391.
Followed the instruction as mentioned in KB-329332, but still failed.
Followed the instruction as mentioned in KB-827805 but failed too. In
KB-827805, it only tells to add the registry with value name
"TurnOffRpcSecurity". Is it the only thing to do ?
OR both server must be run under the same domain.Can any SQL Server MVP or Microsoft technical support persons help ?
"Johnny" wrote:
> SQL Server 2000 servers are running on two different servers on Windows 2003.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>|||Have you enabled Network COM+ and DTC access under application server on the
add\remove windows components portion of add\remove programs?
--
nivek
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
> SQL Server 2000 servers are running on two different servers on Windows
> 2003.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>|||I also went through the KB-816701. The components Network COM+ and Network
DTC access are already enable by default.
When I put the two servers to the same domain, MSDTC works beautifully. But
why Windows 2003 has this restriction.
"nivek" wrote:
> Have you enabled Network COM+ and DTC access under application server on the
> add\remove windows components portion of add\remove programs?
> --
> nivek
>
>
> "Johnny" <Johnny@.discussions.microsoft.com> wrote in message
> news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
> > SQL Server 2000 servers are running on two different servers on Windows
> > 2003.
> > One is part of domain but the other one is not part of any domain.
> > MSDTC failed to communicate with error msg 7391.
> >
> > Followed the instruction as mentioned in KB-329332, but still failed.
> > Followed the instruction as mentioned in KB-827805 but failed too. In
> > KB-827805, it only tells to add the registry with value name
> > "TurnOffRpcSecurity". Is it the only thing to do ?
> >
> > OR both server must be run under the same domain.
> >
>
>
One is part of domain but the other one is not part of any domain.
MSDTC failed to communicate with error msg 7391.
Followed the instruction as mentioned in KB-329332, but still failed.
Followed the instruction as mentioned in KB-827805 but failed too. In
KB-827805, it only tells to add the registry with value name
"TurnOffRpcSecurity". Is it the only thing to do ?
OR both server must be run under the same domain.Can any SQL Server MVP or Microsoft technical support persons help ?
"Johnny" wrote:
> SQL Server 2000 servers are running on two different servers on Windows 2003.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>|||Have you enabled Network COM+ and DTC access under application server on the
add\remove windows components portion of add\remove programs?
--
nivek
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
> SQL Server 2000 servers are running on two different servers on Windows
> 2003.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>|||I also went through the KB-816701. The components Network COM+ and Network
DTC access are already enable by default.
When I put the two servers to the same domain, MSDTC works beautifully. But
why Windows 2003 has this restriction.
"nivek" wrote:
> Have you enabled Network COM+ and DTC access under application server on the
> add\remove windows components portion of add\remove programs?
> --
> nivek
>
>
> "Johnny" <Johnny@.discussions.microsoft.com> wrote in message
> news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
> > SQL Server 2000 servers are running on two different servers on Windows
> > 2003.
> > One is part of domain but the other one is not part of any domain.
> > MSDTC failed to communicate with error msg 7391.
> >
> > Followed the instruction as mentioned in KB-329332, but still failed.
> > Followed the instruction as mentioned in KB-827805 but failed too. In
> > KB-827805, it only tells to add the registry with value name
> > "TurnOffRpcSecurity". Is it the only thing to do ?
> >
> > OR both server must be run under the same domain.
> >
>
>
MSDTC Fails
SQL Server 2000 servers are running on two different servers on Windows 2003
.
One is part of domain but the other one is not part of any domain.
MSDTC failed to communicate with error msg 7391.
Followed the instruction as mentioned in KB-329332, but still failed.
Followed the instruction as mentioned in KB-827805 but failed too. In
KB-827805, it only tells to add the registry with value name
"TurnOffRpcSecurity". Is it the only thing to do ?
OR both server must be run under the same domain.Can any SQL Server MVP or Microsoft technical support persons help ?
"Johnny" wrote:
> SQL Server 2000 servers are running on two different servers on Windows 20
03.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>|||Have you enabled Network COM+ and DTC access under application server on the
add\remove windows components portion of add\remove programs?
nivek
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
> SQL Server 2000 servers are running on two different servers on Windows
> 2003.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>|||I also went through the KB-816701. The components Network COM+ and Network
DTC access are already enable by default.
When I put the two servers to the same domain, MSDTC works beautifully. But
why Windows 2003 has this restriction.
"nivek" wrote:
> Have you enabled Network COM+ and DTC access under application server on t
he
> add\remove windows components portion of add\remove programs?
> --
> nivek
>
>
> "Johnny" <Johnny@.discussions.microsoft.com> wrote in message
> news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
>
>
.
One is part of domain but the other one is not part of any domain.
MSDTC failed to communicate with error msg 7391.
Followed the instruction as mentioned in KB-329332, but still failed.
Followed the instruction as mentioned in KB-827805 but failed too. In
KB-827805, it only tells to add the registry with value name
"TurnOffRpcSecurity". Is it the only thing to do ?
OR both server must be run under the same domain.Can any SQL Server MVP or Microsoft technical support persons help ?
"Johnny" wrote:
> SQL Server 2000 servers are running on two different servers on Windows 20
03.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>|||Have you enabled Network COM+ and DTC access under application server on the
add\remove windows components portion of add\remove programs?
nivek
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
> SQL Server 2000 servers are running on two different servers on Windows
> 2003.
> One is part of domain but the other one is not part of any domain.
> MSDTC failed to communicate with error msg 7391.
> Followed the instruction as mentioned in KB-329332, but still failed.
> Followed the instruction as mentioned in KB-827805 but failed too. In
> KB-827805, it only tells to add the registry with value name
> "TurnOffRpcSecurity". Is it the only thing to do ?
> OR both server must be run under the same domain.
>|||I also went through the KB-816701. The components Network COM+ and Network
DTC access are already enable by default.
When I put the two servers to the same domain, MSDTC works beautifully. But
why Windows 2003 has this restriction.
"nivek" wrote:
> Have you enabled Network COM+ and DTC access under application server on t
he
> add\remove windows components portion of add\remove programs?
> --
> nivek
>
>
> "Johnny" <Johnny@.discussions.microsoft.com> wrote in message
> news:80C3DF07-4C7C-4A1E-B2B4-8D091C09B73B@.microsoft.com...
>
>
Monday, February 20, 2012
MSDTC and Full Text Indexing
Happy Christmas everyone,
I have just visited an active/active win2K(sp2) and SQL 2000(sp3a) cluster
that is not too happy. The virtual servers will not fail over between the
nodes as the MSDTC will not restart if moved. Full text indexing exists
only in one virtual server and needs to be on both instances.
I suspect that comclust wasn't run at installation but has been subsequently
run on one node only. Is there a safe way of now recreating the MSDTC or
reinstalling somehow without reinstalling SQL?
Thanks in advance.
Tim
I never wish I was not what I was not when I didn't wish what I was not was
not what I am not.
Hi Tim!
Yes, you can remove and reinstall MSDTC 'underneath' SQL.
However, the health of this cluster sounds pretty suspect!
I would caution you to BACK EVERYTHING UP before you do anything to this
cluster.
:-)
All system db's...everything.
If it's not moving, back it up!
Ok, with that said, you can follow this KB article on moving and rebuilding
the MSDTC resource:
294209 How to rebuild or move MSDTC used with a SQL failover cluster
There is also this article:
Microsoft Distributed Transaction Coordinator (MSDTC) Recovery Techniques
in Windows 2000 Cluster Server (243204)
Which is not really SQL specific.
As for the FTSearch issue...that is a little more complicated.
Generally there are two reasons FTS doesn't work in a cluster.
1. Search setup was not successful
2. You have missing registry keys.
For number 1, you will need to do some detective work.
First collect the most recent sqlstp#.log from both nodes.
Look for the searchsetup.exe section.
Any errors? If there is an error number, go to a cmd prompt, type net
helpmsg <errornumber>
What's the error? This will be important. At that point you should engage
PSS to rebuild FTS, as it's tricky at best.
For number 2, follow this article to confirm you have the correct registry
entries for FTS:
http://support.microsoft.com/default...B;EN-US;810056
INF: You Must Use Resource-Specific Registry Keys for SQL Server Cluster
Resources (810056)
If missing, put them in there. If that doesn't fix it, again, call PSS,
you probably have more at play than just missing registry keys.
Hope your sickly cluster recovers!
Thanks!
Donna Lambert
SQL Server Product Support
I have just visited an active/active win2K(sp2) and SQL 2000(sp3a) cluster
that is not too happy. The virtual servers will not fail over between the
nodes as the MSDTC will not restart if moved. Full text indexing exists
only in one virtual server and needs to be on both instances.
I suspect that comclust wasn't run at installation but has been subsequently
run on one node only. Is there a safe way of now recreating the MSDTC or
reinstalling somehow without reinstalling SQL?
Thanks in advance.
Tim
I never wish I was not what I was not when I didn't wish what I was not was
not what I am not.
Hi Tim!
Yes, you can remove and reinstall MSDTC 'underneath' SQL.
However, the health of this cluster sounds pretty suspect!
I would caution you to BACK EVERYTHING UP before you do anything to this
cluster.
:-)
All system db's...everything.
If it's not moving, back it up!
Ok, with that said, you can follow this KB article on moving and rebuilding
the MSDTC resource:
294209 How to rebuild or move MSDTC used with a SQL failover cluster
There is also this article:
Microsoft Distributed Transaction Coordinator (MSDTC) Recovery Techniques
in Windows 2000 Cluster Server (243204)
Which is not really SQL specific.
As for the FTSearch issue...that is a little more complicated.
Generally there are two reasons FTS doesn't work in a cluster.
1. Search setup was not successful
2. You have missing registry keys.
For number 1, you will need to do some detective work.
First collect the most recent sqlstp#.log from both nodes.
Look for the searchsetup.exe section.
Any errors? If there is an error number, go to a cmd prompt, type net
helpmsg <errornumber>
What's the error? This will be important. At that point you should engage
PSS to rebuild FTS, as it's tricky at best.
For number 2, follow this article to confirm you have the correct registry
entries for FTS:
http://support.microsoft.com/default...B;EN-US;810056
INF: You Must Use Resource-Specific Registry Keys for SQL Server Cluster
Resources (810056)
If missing, put them in there. If that doesn't fix it, again, call PSS,
you probably have more at play than just missing registry keys.
Hope your sickly cluster recovers!
Thanks!
Donna Lambert
SQL Server Product Support
Subscribe to:
Posts (Atom)