MS-SQL 2000 Enterprise clustered installation fails

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

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

MSI Checker fails during install

I am trying to install UPS Worldship on an XP Pro machine and when it
gets to the point where its says Verifying MSI System Compatibility
the installation just closes without completing. The info below is
from the install log and shows the last thing the installer was doing
before it closed. Hopefully someone can shed some light on this
because UPS is no help.
Thanks in advance,
Adam
Log excerpt:
MSI (s) (A4:C4) [14:20:49:264]: Note: 1: 1728
MSI (s) (A4:C4) [14:20:49:264]: Product: MSIChecker -- Configuration
completed successfully.
MSI (s) (A4:C4) [14:20:49:280]: Cleaning up uninstalled install
packages, if any exist
MSI (s) (A4:C4) [14:20:49:280]: MainEngineThread is returning 0
=== Logging stopped: 6/13/2007 14:20:49 ===
MSI (c) (8C:98) [14:20:49:280]: Decrementing counter to disable
shutdown. If counter >= 0, shutdown will be denied. Counter after
decrement: -1
MSI (c) (8C:98) [14:20:49:280]: MainEngineThread is returning 0
=== Verbose logging stopped: 6/13/2007 14:20:49 ===
hi Adam,
amn0270 wrote:
> I am trying to install UPS Worldship on an XP Pro machine and when it
> gets to the point where its says Verifying MSI System Compatibility
> the installation just closes without completing. The info below is
> from the install log and shows the last thing the installer was doing
> before it closed. Hopefully someone can shed some light on this
> because UPS is no help.
please check the lines before and after the
RETURN VALUE 3
entries..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||hi Adam,
amn0270 wrote:
> I am trying to install UPS Worldship on an XP Pro machine and when it
> gets to the point where its says Verifying MSI System Compatibility
> the installation just closes without completing. The info below is
> from the install log and shows the last thing the installer was doing
> before it closed. Hopefully someone can shed some light on this
> because UPS is no help.
please check the lines before and after the
RETURN VALUE 3
entries..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply

Msg 8127 problem.

Hi,
I need help with this sql. It works for SQL Server 2000, SP3,
(8.00.760) but it fails in SQL Server 2005 (9.00.1399.06).
SELECT DATEPART(yy, os.[CreateTS]) as 'YEARCOL', DATEPART(mm,
os.[CreateTS]) as 'MONTHCOL', DATEPART(dd, os.[CreateTS]) as 'DAYCOL
',
DATEPART(hh, os.[CreateTS]) as 'HOURCOL', min(os.[CreateTS]) as
'CreateTS',
SUM(os.[Lines]) as 'Lines'
FROM aTable os WITH (NOLOCK)
GROUP BY DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS]) ORDER BY
os.[CreateTS]
I am not good at sql, any help is greatly appreciated. The SQL is
dynamically generated by a .Net code and called using OleDb command
class.
Thanks, JoseYou must order by columns in the select list or group by list.
As you say it's not the best SQL as it is generated.
You could:
order by DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS])
or
order by min(os.[CreateTS])
or
order by 1,2,3,4
which means order by columns 1,2,3,4 in the select list.
The choice depends on the order you want and in the last case how lazy you
want to be
The syntax on SQL 2005 is generally tighter than 2000. Most people probably
had the odd issue with their code when they tested the upgrade.
Paul
"Cuellar" <cuellar1706@.gmail.com> wrote in message
news:1159915384.934558.170910@.i42g2000cwa.googlegroups.com...
> Hi,
> I need help with this sql. It works for SQL Server 2000, SP3,
> (8.00.760) but it fails in SQL Server 2005 (9.00.1399.06).
> SELECT DATEPART(yy, os.[CreateTS]) as 'YEARCOL', DATEPART(mm,
> os.[CreateTS]) as 'MONTHCOL', DATEPART(dd, os.[CreateTS]) as 'DAYC
OL',
> DATEPART(hh, os.[CreateTS]) as 'HOURCOL', min(os.[CreateTS]) as
> 'CreateTS',
> SUM(os.[Lines]) as 'Lines'
> FROM aTable os WITH (NOLOCK)
> GROUP BY DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
> DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS]) ORDER B
Y
> os.[CreateTS]
> I am not good at sql, any help is greatly appreciated. The SQL is
> dynamically generated by a .Net code and called using OleDb command
> class.
> Thanks, Jose
>|||Fantastic, that explain the problem. It works.
I end up using the ALIAS:
order by 'CreateTS'
which it seems to work too, and I assume is equivalent to the:
order by min(os.[CreateTS])
one of the versions that you mentioned.
Thank so much,
Jose
Paul Cahill wrote:[vbcol=seagreen]
> You must order by columns in the select list or group by list.
> As you say it's not the best SQL as it is generated.
>
> You could:
> order by DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
> DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS])
> or
> order by min(os.[CreateTS])
> or
> order by 1,2,3,4
> which means order by columns 1,2,3,4 in the select list.
> The choice depends on the order you want and in the last case how lazy you
> want to be
> The syntax on SQL 2005 is generally tighter than 2000. Most people probabl
y
> had the odd issue with their code when they tested the upgrade.
> Paul
>
>
> "Cuellar" <cuellar1706@.gmail.com> wrote in message
> news:1159915384.934558.170910@.i42g2000cwa.googlegroups.com...|||You are welcome.
Paul
"Cuellar" <cuellar1706@.gmail.com> wrote in message
news:1159977911.674457.60370@.m7g2000cwm.googlegroups.com...
> Fantastic, that explain the problem. It works.
> I end up using the ALIAS:
> order by 'CreateTS'
> which it seems to work too, and I assume is equivalent to the:
> order by min(os.[CreateTS])
> one of the versions that you mentioned.
> Thank so much,
> Jose
> Paul Cahill wrote:
>

Msg 8127 problem.

Hi,
I need help with this sql. It works for SQL Server 2000, SP3,
(8.00.760) but it fails in SQL Server 2005 (9.00.1399.06).
SELECT DATEPART(yy, os.[CreateTS]) as 'YEARCOL', DATEPART(mm,
os.[CreateTS]) as 'MONTHCOL', DATEPART(dd, os.[CreateTS]) as 'DAYCOL',
DATEPART(hh, os.[CreateTS]) as 'HOURCOL', min(os.[CreateTS]) as
'CreateTS',
SUM(os.[Lines]) as 'Lines'
FROM aTable os WITH (NOLOCK)
GROUP BY DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS]) ORDER BY
os.[CreateTS]
I am not good at sql, any help is greatly appreciated. The SQL is
dynamically generated by a .Net code and called using OleDb command
class.
Thanks, Jose
You must order by columns in the select list or group by list.
As you say it's not the best SQL as it is generated.
You could:
order by DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS])
or
order by min(os.[CreateTS])
or
order by 1,2,3,4
which means order by columns 1,2,3,4 in the select list.
The choice depends on the order you want and in the last case how lazy you
want to be
The syntax on SQL 2005 is generally tighter than 2000. Most people probably
had the odd issue with their code when they tested the upgrade.
Paul
"Cuellar" <cuellar1706@.gmail.com> wrote in message
news:1159915384.934558.170910@.i42g2000cwa.googlegr oups.com...
> Hi,
> I need help with this sql. It works for SQL Server 2000, SP3,
> (8.00.760) but it fails in SQL Server 2005 (9.00.1399.06).
> SELECT DATEPART(yy, os.[CreateTS]) as 'YEARCOL', DATEPART(mm,
> os.[CreateTS]) as 'MONTHCOL', DATEPART(dd, os.[CreateTS]) as 'DAYCOL',
> DATEPART(hh, os.[CreateTS]) as 'HOURCOL', min(os.[CreateTS]) as
> 'CreateTS',
> SUM(os.[Lines]) as 'Lines'
> FROM aTable os WITH (NOLOCK)
> GROUP BY DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
> DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS]) ORDER BY
> os.[CreateTS]
> I am not good at sql, any help is greatly appreciated. The SQL is
> dynamically generated by a .Net code and called using OleDb command
> class.
> Thanks, Jose
>
|||Fantastic, that explain the problem. It works.
I end up using the ALIAS:
order by 'CreateTS'
which it seems to work too, and I assume is equivalent to the:
order by min(os.[CreateTS])
one of the versions that you mentioned.
Thank so much,
Jose
Paul Cahill wrote:[vbcol=seagreen]
> You must order by columns in the select list or group by list.
> As you say it's not the best SQL as it is generated.
>
> You could:
> order by DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
> DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS])
> or
> order by min(os.[CreateTS])
> or
> order by 1,2,3,4
> which means order by columns 1,2,3,4 in the select list.
> The choice depends on the order you want and in the last case how lazy you
> want to be
> The syntax on SQL 2005 is generally tighter than 2000. Most people probably
> had the odd issue with their code when they tested the upgrade.
> Paul
>
>
> "Cuellar" <cuellar1706@.gmail.com> wrote in message
> news:1159915384.934558.170910@.i42g2000cwa.googlegr oups.com...
|||You are welcome.
Paul
"Cuellar" <cuellar1706@.gmail.com> wrote in message
news:1159977911.674457.60370@.m7g2000cwm.googlegrou ps.com...
> Fantastic, that explain the problem. It works.
> I end up using the ALIAS:
> order by 'CreateTS'
> which it seems to work too, and I assume is equivalent to the:
> order by min(os.[CreateTS])
> one of the versions that you mentioned.
> Thank so much,
> Jose
> Paul Cahill wrote:
>

Msg 8127 problem.

Hi,
I need help with this sql. It works for SQL Server 2000, SP3,
(8.00.760) but it fails in SQL Server 2005 (9.00.1399.06).
SELECT DATEPART(yy, os.[CreateTS]) as 'YEARCOL', DATEPART(mm,
os.[CreateTS]) as 'MONTHCOL', DATEPART(dd, os.[CreateTS]) as 'DAYCOL',
DATEPART(hh, os.[CreateTS]) as 'HOURCOL', min(os.[CreateTS]) as
'CreateTS',
SUM(os.[Lines]) as 'Lines'
FROM aTable os WITH (NOLOCK)
GROUP BY DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS]) ORDER BY
os.[CreateTS]
I am not good at sql, any help is greatly appreciated. The SQL is
dynamically generated by a .Net code and called using OleDb command
class.
Thanks, JoseYou must order by columns in the select list or group by list.
As you say it's not the best SQL as it is generated.
You could:
order by DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS])
or
order by min(os.[CreateTS])
or
order by 1,2,3,4
which means order by columns 1,2,3,4 in the select list.
The choice depends on the order you want and in the last case how lazy you
want to be :)
The syntax on SQL 2005 is generally tighter than 2000. Most people probably
had the odd issue with their code when they tested the upgrade.
Paul
"Cuellar" <cuellar1706@.gmail.com> wrote in message
news:1159915384.934558.170910@.i42g2000cwa.googlegroups.com...
> Hi,
> I need help with this sql. It works for SQL Server 2000, SP3,
> (8.00.760) but it fails in SQL Server 2005 (9.00.1399.06).
> SELECT DATEPART(yy, os.[CreateTS]) as 'YEARCOL', DATEPART(mm,
> os.[CreateTS]) as 'MONTHCOL', DATEPART(dd, os.[CreateTS]) as 'DAYCOL',
> DATEPART(hh, os.[CreateTS]) as 'HOURCOL', min(os.[CreateTS]) as
> 'CreateTS',
> SUM(os.[Lines]) as 'Lines'
> FROM aTable os WITH (NOLOCK)
> GROUP BY DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
> DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS]) ORDER BY
> os.[CreateTS]
> I am not good at sql, any help is greatly appreciated. The SQL is
> dynamically generated by a .Net code and called using OleDb command
> class.
> Thanks, Jose
>|||Fantastic, that explain the problem. It works.
I end up using the ALIAS:
order by 'CreateTS'
which it seems to work too, and I assume is equivalent to the:
order by min(os.[CreateTS])
one of the versions that you mentioned.
Thank so much,
Jose
Paul Cahill wrote:
> You must order by columns in the select list or group by list.
> As you say it's not the best SQL as it is generated.
>
> You could:
> order by DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
> DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS])
> or
> order by min(os.[CreateTS])
> or
> order by 1,2,3,4
> which means order by columns 1,2,3,4 in the select list.
> The choice depends on the order you want and in the last case how lazy you
> want to be :)
> The syntax on SQL 2005 is generally tighter than 2000. Most people probably
> had the odd issue with their code when they tested the upgrade.
> Paul
>
>
> "Cuellar" <cuellar1706@.gmail.com> wrote in message
> news:1159915384.934558.170910@.i42g2000cwa.googlegroups.com...
> > Hi,
> > I need help with this sql. It works for SQL Server 2000, SP3,
> > (8.00.760) but it fails in SQL Server 2005 (9.00.1399.06).
> >
> > SELECT DATEPART(yy, os.[CreateTS]) as 'YEARCOL', DATEPART(mm,
> > os.[CreateTS]) as 'MONTHCOL', DATEPART(dd, os.[CreateTS]) as 'DAYCOL',
> > DATEPART(hh, os.[CreateTS]) as 'HOURCOL', min(os.[CreateTS]) as
> > 'CreateTS',
> > SUM(os.[Lines]) as 'Lines'
> > FROM aTable os WITH (NOLOCK)
> > GROUP BY DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
> > DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS]) ORDER BY
> > os.[CreateTS]
> >
> > I am not good at sql, any help is greatly appreciated. The SQL is
> > dynamically generated by a .Net code and called using OleDb command
> > class.
> >
> > Thanks, Jose
> >|||You are welcome.
Paul
"Cuellar" <cuellar1706@.gmail.com> wrote in message
news:1159977911.674457.60370@.m7g2000cwm.googlegroups.com...
> Fantastic, that explain the problem. It works.
> I end up using the ALIAS:
> order by 'CreateTS'
> which it seems to work too, and I assume is equivalent to the:
> order by min(os.[CreateTS])
> one of the versions that you mentioned.
> Thank so much,
> Jose
> Paul Cahill wrote:
>> You must order by columns in the select list or group by list.
>> As you say it's not the best SQL as it is generated.
>>
>> You could:
>> order by DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
>> DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS])
>> or
>> order by min(os.[CreateTS])
>> or
>> order by 1,2,3,4
>> which means order by columns 1,2,3,4 in the select list.
>> The choice depends on the order you want and in the last case how lazy
>> you
>> want to be :)
>> The syntax on SQL 2005 is generally tighter than 2000. Most people
>> probably
>> had the odd issue with their code when they tested the upgrade.
>> Paul
>>
>>
>> "Cuellar" <cuellar1706@.gmail.com> wrote in message
>> news:1159915384.934558.170910@.i42g2000cwa.googlegroups.com...
>> > Hi,
>> > I need help with this sql. It works for SQL Server 2000, SP3,
>> > (8.00.760) but it fails in SQL Server 2005 (9.00.1399.06).
>> >
>> > SELECT DATEPART(yy, os.[CreateTS]) as 'YEARCOL', DATEPART(mm,
>> > os.[CreateTS]) as 'MONTHCOL', DATEPART(dd, os.[CreateTS]) as 'DAYCOL',
>> > DATEPART(hh, os.[CreateTS]) as 'HOURCOL', min(os.[CreateTS]) as
>> > 'CreateTS',
>> > SUM(os.[Lines]) as 'Lines'
>> > FROM aTable os WITH (NOLOCK)
>> > GROUP BY DATEPART(yy, os.[CreateTS]), DATEPART(mm, os.[CreateTS]),
>> > DATEPART(dd, os.[CreateTS]) , DATEPART(hh, os.[CreateTS]) ORDER BY
>> > os.[CreateTS]
>> >
>> > I am not good at sql, any help is greatly appreciated. The SQL is
>> > dynamically generated by a .Net code and called using OleDb command
>> > class.
>> >
>> > Thanks, Jose
>> >
>

MSG 605 - Server having problems with fetching the logical pages

Hi,
I'm running SQL 2000 and server quite often (3 times within the last week)
fails on insert operation with the messages like:
"Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
object '-948063835' not to object #tmp
Connection Broken"
Similar messages were for the tables in the completely different databases.
Does not look like this is directly related to the table's size.
ThanksHi
Looks like corruption. Either your RAM or disk could ber causing this.
Run DBCC CHECKDB againt all your DB's on the server and see what the output
is.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"alex" wrote:

> Hi,
> I'm running SQL 2000 and server quite often (3 times within the last week)
> fails on insert operation with the messages like:
> "Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
> object '-948063835' not to object #tmp
> Connection Broken"
> Similar messages were for the tables in the completely different databases
.
> Does not look like this is directly related to the table's size.
> Thanks
>

MSG 605 - Server having problems with fetching the logical pages

Hi,
I'm running SQL 2000 and server quite often (3 times within the last week)
fails on insert operation with the messages like:
"Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
object '-948063835' not to object #tmp
Connection Broken"
Similar messages were for the tables in the completely different databases.
Does not look like this is directly related to the table's size.
Thanks
Hi
Looks like corruption. Either your RAM or disk could ber causing this.
Run DBCC CHECKDB againt all your DB's on the server and see what the output
is.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"alex" wrote:

> Hi,
> I'm running SQL 2000 and server quite often (3 times within the last week)
> fails on insert operation with the messages like:
> "Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
> object '-948063835' not to object #tmp
> Connection Broken"
> Similar messages were for the tables in the completely different databases.
> Does not look like this is directly related to the table's size.
> Thanks
>

MSG 605 - Server having problems with fetching the logical pages

Hi,
I'm running SQL 2000 and server quite often (3 times within the last week)
fails on insert operation with the messages like:
"Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
object '-948063835' not to object #tmp
Connection Broken"
Similar messages were for the tables in the completely different databases.
Does not look like this is directly related to the table's size.
ThanksHi
Looks like corruption. Either your RAM or disk could ber causing this.
Run DBCC CHECKDB againt all your DB's on the server and see what the output
is.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"alex" wrote:
> Hi,
> I'm running SQL 2000 and server quite often (3 times within the last week)
> fails on insert operation with the messages like:
> "Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
> object '-948063835' not to object #tmp
> Connection Broken"
> Similar messages were for the tables in the completely different databases.
> Does not look like this is directly related to the table's size.
> Thanks
>|||Also check your backups (restore to a different sql server, run dbcc checkdb
on those). Find a backup that does not contain the corruption.
You may lose data.
If DBCC reports the minimal repair level is "repair_allow_data_loss" it's
not kidding.
If you run that, be prepared to lose some data. It might be a row, a page,
whole tables. There's really no telling.
Going back to a known good state is often a better alternative. At least
you know what data you lost.
:D
Donna Lambert
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Looks like corruption. Either your RAM or disk could ber causing this.
> Run DBCC CHECKDB againt all your DB's on the server and see what the output
> is.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "alex" wrote:
> > Hi,
> > I'm running SQL 2000 and server quite often (3 times within the last week)
> > fails on insert operation with the messages like:
> >
> > "Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
> > object '-948063835' not to object #tmp
> >
> > Connection Broken"
> >
> > Similar messages were for the tables in the completely different databases.
> >
> > Does not look like this is directly related to the table's size.
> >
> > Thanks
> >
> >|||Thanks. Did that and got:
....
CHECKDB found 0 allocation errors and 0 consistency errors in database
'tempdb'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Looks like database itself is OK. Can the problem be a result of some
application's
activities like the following scenario:
main stored procedure calls, withing a cycle, underlying stored procedure
and this
procedure contains the following:
create table #tmp(....)
....
drop table #tmp
It looks like after few repetitions of this scenario (number of the
iterations varies)
breakdown occurs. After replacement of the temp table with a regular one,
situation seems to be remedied.
Can it be that tempdb may have problems with a repeated re-creation of a
dropped temp. table within a single session?
Thanks
"Donna Lambert" wrote:
> Also check your backups (restore to a different sql server, run dbcc checkdb
> on those). Find a backup that does not contain the corruption.
> You may lose data.
> If DBCC reports the minimal repair level is "repair_allow_data_loss" it's
> not kidding.
> If you run that, be prepared to lose some data. It might be a row, a page,
> whole tables. There's really no telling.
> Going back to a known good state is often a better alternative. At least
> you know what data you lost.
> :D
> Donna Lambert
>
> "Mike Epprecht (SQL MVP)" wrote:
> > Hi
> >
> > Looks like corruption. Either your RAM or disk could ber causing this.
> >
> > Run DBCC CHECKDB againt all your DB's on the server and see what the output
> > is.
> >
> > Regards
> > --
> > Mike Epprecht, Microsoft SQL Server MVP
> > Zurich, Switzerland
> >
> > MVP Program: http://www.microsoft.com/mvp
> >
> > Blog: http://www.msmvps.com/epprecht/
> >
> >
> >
> > "alex" wrote:
> >
> > > Hi,
> > > I'm running SQL 2000 and server quite often (3 times within the last week)
> > > fails on insert operation with the messages like:
> > >
> > > "Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
> > > object '-948063835' not to object #tmp
> > >
> > > Connection Broken"
> > >
> > > Similar messages were for the tables in the completely different databases.
> > >
> > > Does not look like this is directly related to the table's size.
> > >
> > > Thanks
> > >
> > >|||> Can the problem be a result of some
> application's
> activities like the following scenario:
Basically, no. No TSQL code should be able to corrupt a database. If you can find such code that
reproduces, you have found a bug in SQL Server. You should investigate for hardware errors. See
general recommendations at http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp. Also,
remember that tempdb is re-created at each startup...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"alex" <alex@.discussions.microsoft.com> wrote in message
news:8D8B81BF-1C2A-4088-ACAE-1609A0FC5223@.microsoft.com...
> Thanks. Did that and got:
> ....
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'tempdb'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> Looks like database itself is OK. Can the problem be a result of some
> application's
> activities like the following scenario:
> main stored procedure calls, withing a cycle, underlying stored procedure
> and this
> procedure contains the following:
> create table #tmp(....)
> ....
> drop table #tmp
> It looks like after few repetitions of this scenario (number of the
> iterations varies)
> breakdown occurs. After replacement of the temp table with a regular one,
> situation seems to be remedied.
> Can it be that tempdb may have problems with a repeated re-creation of a
> dropped temp. table within a single session?
> Thanks
> "Donna Lambert" wrote:
>> Also check your backups (restore to a different sql server, run dbcc checkdb
>> on those). Find a backup that does not contain the corruption.
>> You may lose data.
>> If DBCC reports the minimal repair level is "repair_allow_data_loss" it's
>> not kidding.
>> If you run that, be prepared to lose some data. It might be a row, a page,
>> whole tables. There's really no telling.
>> Going back to a known good state is often a better alternative. At least
>> you know what data you lost.
>> :D
>> Donna Lambert
>>
>> "Mike Epprecht (SQL MVP)" wrote:
>> > Hi
>> >
>> > Looks like corruption. Either your RAM or disk could ber causing this.
>> >
>> > Run DBCC CHECKDB againt all your DB's on the server and see what the output
>> > is.
>> >
>> > Regards
>> > --
>> > Mike Epprecht, Microsoft SQL Server MVP
>> > Zurich, Switzerland
>> >
>> > MVP Program: http://www.microsoft.com/mvp
>> >
>> > Blog: http://www.msmvps.com/epprecht/
>> >
>> >
>> >
>> > "alex" wrote:
>> >
>> > > Hi,
>> > > I'm running SQL 2000 and server quite often (3 times within the last week)
>> > > fails on insert operation with the messages like:
>> > >
>> > > "Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
>> > > object '-948063835' not to object #tmp
>> > >
>> > > Connection Broken"
>> > >
>> > > Similar messages were for the tables in the completely different databases.
>> > >
>> > > Does not look like this is directly related to the table's size.
>> > >
>> > > Thanks
>> > >
>> > >|||Thanks but I did not say that DB was corrupted: DBCC CHECKDATABASE indicated
that there are no problems.
Is corruption the only reason for getting Msg 605?
"Tibor Karaszi" wrote:
> > Can the problem be a result of some
> > application's
> > activities like the following scenario:
> Basically, no. No TSQL code should be able to corrupt a database. If you can find such code that
> reproduces, you have found a bug in SQL Server. You should investigate for hardware errors. See
> general recommendations at http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp. Also,
> remember that tempdb is re-created at each startup...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "alex" <alex@.discussions.microsoft.com> wrote in message
> news:8D8B81BF-1C2A-4088-ACAE-1609A0FC5223@.microsoft.com...
> > Thanks. Did that and got:
> > ....
> > CHECKDB found 0 allocation errors and 0 consistency errors in database
> > 'tempdb'.
> > DBCC execution completed. If DBCC printed error messages, contact your
> > system administrator.
> >
> > Looks like database itself is OK. Can the problem be a result of some
> > application's
> > activities like the following scenario:
> >
> > main stored procedure calls, withing a cycle, underlying stored procedure
> > and this
> > procedure contains the following:
> >
> > create table #tmp(....)
> > ....
> > drop table #tmp
> >
> > It looks like after few repetitions of this scenario (number of the
> > iterations varies)
> > breakdown occurs. After replacement of the temp table with a regular one,
> > situation seems to be remedied.
> >
> > Can it be that tempdb may have problems with a repeated re-creation of a
> > dropped temp. table within a single session?
> >
> > Thanks
> >
> > "Donna Lambert" wrote:
> >
> >> Also check your backups (restore to a different sql server, run dbcc checkdb
> >> on those). Find a backup that does not contain the corruption.
> >> You may lose data.
> >> If DBCC reports the minimal repair level is "repair_allow_data_loss" it's
> >> not kidding.
> >> If you run that, be prepared to lose some data. It might be a row, a page,
> >> whole tables. There's really no telling.
> >> Going back to a known good state is often a better alternative. At least
> >> you know what data you lost.
> >> :D
> >> Donna Lambert
> >>
> >>
> >> "Mike Epprecht (SQL MVP)" wrote:
> >>
> >> > Hi
> >> >
> >> > Looks like corruption. Either your RAM or disk could ber causing this.
> >> >
> >> > Run DBCC CHECKDB againt all your DB's on the server and see what the output
> >> > is.
> >> >
> >> > Regards
> >> > --
> >> > Mike Epprecht, Microsoft SQL Server MVP
> >> > Zurich, Switzerland
> >> >
> >> > MVP Program: http://www.microsoft.com/mvp
> >> >
> >> > Blog: http://www.msmvps.com/epprecht/
> >> >
> >> >
> >> >
> >> > "alex" wrote:
> >> >
> >> > > Hi,
> >> > > I'm running SQL 2000 and server quite often (3 times within the last week)
> >> > > fails on insert operation with the messages like:
> >> > >
> >> > > "Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
> >> > > object '-948063835' not to object #tmp
> >> > >
> >> > > Connection Broken"
> >> > >
> >> > > Similar messages were for the tables in the completely different databases.
> >> > >
> >> > > Does not look like this is directly related to the table's size.
> >> > >
> >> > > Thanks
> >> > >
> >> > >
>|||Probably the corruption disappeared since objects are created and dropped all the time in tempdb.
Also, you possibly re-started SQL server in between so tempdb was rebuilt. However, you have had a
corruption, and that it something you should investigate further.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"alex" <alex@.discussions.microsoft.com> wrote in message
news:E28034E7-9F14-46EB-B491-CB690F52E0D0@.microsoft.com...
> Thanks but I did not say that DB was corrupted: DBCC CHECKDATABASE indicated
> that there are no problems.
> Is corruption the only reason for getting Msg 605?
> "Tibor Karaszi" wrote:
>> > Can the problem be a result of some
>> > application's
>> > activities like the following scenario:
>> Basically, no. No TSQL code should be able to corrupt a database. If you can find such code that
>> reproduces, you have found a bug in SQL Server. You should investigate for hardware errors. See
>> general recommendations at http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp. Also,
>> remember that tempdb is re-created at each startup...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "alex" <alex@.discussions.microsoft.com> wrote in message
>> news:8D8B81BF-1C2A-4088-ACAE-1609A0FC5223@.microsoft.com...
>> > Thanks. Did that and got:
>> > ....
>> > CHECKDB found 0 allocation errors and 0 consistency errors in database
>> > 'tempdb'.
>> > DBCC execution completed. If DBCC printed error messages, contact your
>> > system administrator.
>> >
>> > Looks like database itself is OK. Can the problem be a result of some
>> > application's
>> > activities like the following scenario:
>> >
>> > main stored procedure calls, withing a cycle, underlying stored procedure
>> > and this
>> > procedure contains the following:
>> >
>> > create table #tmp(....)
>> > ....
>> > drop table #tmp
>> >
>> > It looks like after few repetitions of this scenario (number of the
>> > iterations varies)
>> > breakdown occurs. After replacement of the temp table with a regular one,
>> > situation seems to be remedied.
>> >
>> > Can it be that tempdb may have problems with a repeated re-creation of a
>> > dropped temp. table within a single session?
>> >
>> > Thanks
>> >
>> > "Donna Lambert" wrote:
>> >
>> >> Also check your backups (restore to a different sql server, run dbcc checkdb
>> >> on those). Find a backup that does not contain the corruption.
>> >> You may lose data.
>> >> If DBCC reports the minimal repair level is "repair_allow_data_loss" it's
>> >> not kidding.
>> >> If you run that, be prepared to lose some data. It might be a row, a page,
>> >> whole tables. There's really no telling.
>> >> Going back to a known good state is often a better alternative. At least
>> >> you know what data you lost.
>> >> :D
>> >> Donna Lambert
>> >>
>> >>
>> >> "Mike Epprecht (SQL MVP)" wrote:
>> >>
>> >> > Hi
>> >> >
>> >> > Looks like corruption. Either your RAM or disk could ber causing this.
>> >> >
>> >> > Run DBCC CHECKDB againt all your DB's on the server and see what the output
>> >> > is.
>> >> >
>> >> > Regards
>> >> > --
>> >> > Mike Epprecht, Microsoft SQL Server MVP
>> >> > Zurich, Switzerland
>> >> >
>> >> > MVP Program: http://www.microsoft.com/mvp
>> >> >
>> >> > Blog: http://www.msmvps.com/epprecht/
>> >> >
>> >> >
>> >> >
>> >> > "alex" wrote:
>> >> >
>> >> > > Hi,
>> >> > > I'm running SQL 2000 and server quite often (3 times within the last week)
>> >> > > fails on insert operation with the messages like:
>> >> > >
>> >> > > "Attempt to fetch logical page (1:202685) in database 'tempdb' belongs to
>> >> > > object '-948063835' not to object #tmp
>> >> > >
>> >> > > Connection Broken"
>> >> > >
>> >> > > Similar messages were for the tables in the completely different databases.
>> >> > >
>> >> > > Does not look like this is directly related to the table's size.
>> >> > >
>> >> > > Thanks
>> >> > >
>> >> > >
>>|||Also, CHECKDB doesn't check everything in TEMPDB so may not pick up on the
problem you have. You also can't run repair on TEMPDB as its impossible to
put TEMPDB into single_user mode (prerequisite for running repair).
If you can repro the problem, you should call product support
(http://support.microsoft.com)
Thanks
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eBmRC1EbFHA.2420@.TK2MSFTNGP12.phx.gbl...
> Probably the corruption disappeared since objects are created and dropped
> all the time in tempdb. Also, you possibly re-started SQL server in
> between so tempdb was rebuilt. However, you have had a corruption, and
> that it something you should investigate further.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "alex" <alex@.discussions.microsoft.com> wrote in message
> news:E28034E7-9F14-46EB-B491-CB690F52E0D0@.microsoft.com...
>> Thanks but I did not say that DB was corrupted: DBCC CHECKDATABASE
>> indicated
>> that there are no problems.
>> Is corruption the only reason for getting Msg 605?
>> "Tibor Karaszi" wrote:
>> > Can the problem be a result of some
>> > application's
>> > activities like the following scenario:
>> Basically, no. No TSQL code should be able to corrupt a database. If you
>> can find such code that
>> reproduces, you have found a bug in SQL Server. You should investigate
>> for hardware errors. See
>> general recommendations at
>> http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp. Also,
>> remember that tempdb is re-created at each startup...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "alex" <alex@.discussions.microsoft.com> wrote in message
>> news:8D8B81BF-1C2A-4088-ACAE-1609A0FC5223@.microsoft.com...
>> > Thanks. Did that and got:
>> > ....
>> > CHECKDB found 0 allocation errors and 0 consistency errors in database
>> > 'tempdb'.
>> > DBCC execution completed. If DBCC printed error messages, contact your
>> > system administrator.
>> >
>> > Looks like database itself is OK. Can the problem be a result of some
>> > application's
>> > activities like the following scenario:
>> >
>> > main stored procedure calls, withing a cycle, underlying stored
>> > procedure
>> > and this
>> > procedure contains the following:
>> >
>> > create table #tmp(....)
>> > ....
>> > drop table #tmp
>> >
>> > It looks like after few repetitions of this scenario (number of the
>> > iterations varies)
>> > breakdown occurs. After replacement of the temp table with a regular
>> > one,
>> > situation seems to be remedied.
>> >
>> > Can it be that tempdb may have problems with a repeated re-creation of
>> > a
>> > dropped temp. table within a single session?
>> >
>> > Thanks
>> >
>> > "Donna Lambert" wrote:
>> >
>> >> Also check your backups (restore to a different sql server, run dbcc
>> >> checkdb
>> >> on those). Find a backup that does not contain the corruption.
>> >> You may lose data.
>> >> If DBCC reports the minimal repair level is "repair_allow_data_loss"
>> >> it's
>> >> not kidding.
>> >> If you run that, be prepared to lose some data. It might be a row, a
>> >> page,
>> >> whole tables. There's really no telling.
>> >> Going back to a known good state is often a better alternative. At
>> >> least
>> >> you know what data you lost.
>> >> :D
>> >> Donna Lambert
>> >>
>> >>
>> >> "Mike Epprecht (SQL MVP)" wrote:
>> >>
>> >> > Hi
>> >> >
>> >> > Looks like corruption. Either your RAM or disk could ber causing
>> >> > this.
>> >> >
>> >> > Run DBCC CHECKDB againt all your DB's on the server and see what
>> >> > the output
>> >> > is.
>> >> >
>> >> > Regards
>> >> > --
>> >> > Mike Epprecht, Microsoft SQL Server MVP
>> >> > Zurich, Switzerland
>> >> >
>> >> > MVP Program: http://www.microsoft.com/mvp
>> >> >
>> >> > Blog: http://www.msmvps.com/epprecht/
>> >> >
>> >> >
>> >> >
>> >> > "alex" wrote:
>> >> >
>> >> > > Hi,
>> >> > > I'm running SQL 2000 and server quite often (3 times within the
>> >> > > last week)
>> >> > > fails on insert operation with the messages like:
>> >> > >
>> >> > > "Attempt to fetch logical page (1:202685) in database 'tempdb'
>> >> > > belongs to
>> >> > > object '-948063835' not to object #tmp
>> >> > >
>> >> > > Connection Broken"
>> >> > >
>> >> > > Similar messages were for the tables in the completely different
>> >> > > databases.
>> >> > >
>> >> > > Does not look like this is directly related to the table's size.
>> >> > >
>> >> > > Thanks
>> >> > >
>> >> > >
>>
>

Msg 4712: cannot truncate table

Hello,

I am running SQL Server 2005 SP1. Whenever I issue a 'truncate' query to the DB engine it fails if the table to be modified is currently referenced by a foreign key constraint.

A code snippet (T-SQL) that demonstrates the problem is beneath.

Does anybody know a fix-it?

Thanks in advance,
Intenion

---

USE tempdb

Go

-- Clearing the 'tmpdb' database

IFOBJECT_ID('user')ISNOTNULL

DROPTABLE [user];

IFOBJECT_ID('address')ISNOTNULL

DROPTABLE address;

-- Creating tables: 'address' and 'user'

CREATETABLE address

(

id INTIDENTITY(0, 1)CONSTRAINT pk_address PRIMARYKEY,

zip SMALLINTNOTNULLCONSTRAINT chk_zip CHECK(zip > 0),

street NVARCHAR(50)NOTNULLCONSTRAINT chk_street CHECK(LEN(street)> 0),

number SMALLINTNOTNULLCONSTRAINT chk_number CHECK(number > 0)

CONSTRAINT unq_address UNIQUE(zip, street, number)

);

Go

CREATETABLE [user]

(

email VARCHAR(50)CONSTRAINT pk_user PRIMARYKEY,

address INTNULLCONSTRAINT fk_user_address FOREIGNKEYREFERENCES address (id)ONDELETESETNULL

);

Go

-- Populating tables

INSERTINTO address VALUES(2365,'street 1', 2);

INSERTINTO address VALUES(23369,'street 2', 2);

Go

INSERTINTO [user] VALUES('someone@.isp.net', 0);

INSERTINTO [user] VALUES('somebody@.isp-r-us.com', 1);

Go

-- Truncate query that fails

TRUNCATETABLE address;

-- Delete query that passes

--DELETE address;

Hi,

this is by design. YOu either have to drop the FK first or use the DELETE statement.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

Hi,

Maybe a documentation update would be welcome for the 'truncate table' topic in Books Online.

Thank you for your answer,
Intenion.

|||

Jens K. Suessmeyer wrote:

Hi,

this is by design. YOu either have to drop the FK first or use the DELETE statement.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

I think I am running into the same situation. Would you mind showing how (using SMO) that I would drop the FK (then readd it so that the table is not changed)? It seems from the documentation that DELETE also tries to enforce the FK constraint so the error would be reasserted if I used DELETE.

Kevin

Msg 4712: cannot truncate table

Hello,

I am running SQL Server 2005 SP1. Whenever I issue a 'truncate' query to the DB engine it fails if the table to be modified is currently referenced by a foreign key constraint.

A code snippet (T-SQL) that demonstrates the problem is beneath.

Does anybody know a fix-it?

Thanks in advance,
Intenion

---

USE tempdb

Go

-- Clearing the 'tmpdb' database

IF OBJECT_ID('user') IS NOT NULL

DROP TABLE [user];

IF OBJECT_ID('address') IS NOT NULL

DROP TABLE address;

-- Creating tables: 'address' and 'user'

CREATE TABLE address

(

id INT IDENTITY (0, 1) CONSTRAINT pk_address PRIMARY KEY,

zip SMALLINT NOT NULL CONSTRAINT chk_zip CHECK (zip > 0),

street NVARCHAR(50) NOT NULL CONSTRAINT chk_street CHECK (LEN(street) > 0),

number SMALLINT NOT NULL CONSTRAINT chk_number CHECK (number > 0)

CONSTRAINT unq_address UNIQUE (zip, street, number)

);

Go

CREATE TABLE [user]

(

email VARCHAR(50) CONSTRAINT pk_user PRIMARY KEY,

address INT NULL CONSTRAINT fk_user_address FOREIGN KEY REFERENCES address (id) ON DELETE SET NULL

);

Go

-- Populating tables

INSERT INTO address VALUES (2365, 'street 1', 2);

INSERT INTO address VALUES (23369, 'street 2', 2);

Go

INSERT INTO [user] VALUES ('someone@.isp.net', 0);

INSERT INTO [user] VALUES ('somebody@.isp-r-us.com', 1);

Go

-- Truncate query that fails

TRUNCATE TABLE address;

-- Delete query that passes

--DELETE address;

Hi,

this is by design. YOu either have to drop the FK first or use the DELETE statement.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

Hi,

Maybe a documentation update would be welcome for the 'truncate table' topic in Books Online.

Thank you for your answer,
Intenion.

|||

Jens K. Suessmeyer wrote:

Hi,

this is by design. YOu either have to drop the FK first or use the DELETE statement.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

I think I am running into the same situation. Would you mind showing how (using SMO) that I would drop the FK (then readd it so that the table is not changed)? It seems from the documentation that DELETE also tries to enforce the FK constraint so the error would be reasserted if I used DELETE.

Kevin

MSDTC on Windows Server 2003

I am running a sql server 2000 cluster on a windows server 2003
machine. Every time I try to install MSDTC it fails and this is what
is in the Event Viewer:
MS DTC setup failed to populate the shared cluster registry. The DTC
resource will not be able to come online.Error Specifics:
d:\nt\com\complus\dtc\shared\mtxclu\mtxclusetuphel per.cpp:120,
CmdLine: "C:\WINDOWS\cluster\resrcmon.exe" -e 880 -m 884 -p 1204, Pid:
2524
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
The Event ID is 4389. The Source is MS DTC Client.
I've clicked on the link and Microsoft "does not have any more
information at this time."
Can anyone tell me what the problem is?
Thanks
JF
Sorry, but you need to install DTC (to W2K3) and MSDTC before installing SQL2K
on a W2K3 Cluster.
Try articles 817064 and 301600.
Gone are the nice days of running comclust.exe (as in W2K) !
Cheers
LM
On 06/05/2004 jf@.uk.com wrote:
>I am running a sql server 2000 cluster on a windows server 2003
>machine. Every time I try to install MSDTC it fails and this is what
>is in the Event Viewer:
>
>MS DTC setup failed to populate the shared cluster registry. The DTC
>resource will not be able to come online.Error Specifics:
>d:\nt\com\complus\dtc\shared\mtxclu\mtxclusetuphe lper.cpp:120,
>CmdLine: "C:\WINDOWS\cluster\resrcmon.exe" -e 880 -m 884 -p 1204, Pid:
>2524
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>
>The Event ID is 4389. The Source is MS DTC Client.
>I've clicked on the link and Microsoft "does not have any more
>information at this time."
>Can anyone tell me what the problem is?
>
>Thanks
>JF
Cheers
LM

MSDTC fails on Windows 2003 but security has been reset so its not that.

I am running SQL Server 2000 (clustered server) with Windows 2003. For some reason MSDTC is failing on distributed transactions. I can run code that begins and commits a transaction from query analyzer, or run a stored procedure from Query Analyzer with the same code in it and both work great, but if I call the stored procedure from a DTS job, then the job fails with the following error:

DTSStep_DTSExecuteSQLTask_1, Error = -2147217900 (80040E14) Error string: The operation could not be performed because the OLE DB provider 'MSDASQL' was unable to begin a distributed transaction. Error source: ..... Error string: OLE DB error trace [OLE/DB Provider 'MSDASQL' ITransactionJoin::JoinTransaction returned 0x8004d00a]. Error source: Microsoft OLE DB Provider for SQL Serve. The step failed.

Any help would be appreciated!Ensure MSDTC is started on the machine.
http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=3451 for your reference.

MSDTC fails on Windows 2000 Advanced Server SP4

I have a VB6 application that uses MTS in a COM+ package for
transaction based processing over MSDTC. This application was working
fine when run from the SQL Server machine on Windows 2000 Advanced
Server until the latest security updates were installed. Now the
application fails to connect to SQL Server when the call is made inside
a transaction context within MTS/COM+
I have verified that MSDTC is started
The DTCTester tool runs successfully
RPC port 135 is open
This application runs fine on a Windows 2000 Server machine with SP4.
What is different about Windows 2000 Advanced Server such that it no
longer works after applying security updates (SP4)?
?s your SQL server and application server are in same domain, do you have
firewall etc between SQL Server and appl. server?
We had problems after we install Windows 2003 SP1 with MSDTC, we select No
Authantication Required and the problem is gone. Maybe because of you have
applied security patches you are having the same problem.
Check out:
http://support.microsoft.com/?id=883960
Hope this helps.
"dhalb@.comcast.net" wrote:

> I have a VB6 application that uses MTS in a COM+ package for
> transaction based processing over MSDTC. This application was working
> fine when run from the SQL Server machine on Windows 2000 Advanced
> Server until the latest security updates were installed. Now the
> application fails to connect to SQL Server when the call is made inside
> a transaction context within MTS/COM+
> I have verified that MSDTC is started
> The DTCTester tool runs successfully
> RPC port 135 is open
> This application runs fine on a Windows 2000 Server machine with SP4.
> What is different about Windows 2000 Advanced Server such that it no
> longer works after applying security updates (SP4)?
>

MSDTC fails on Windows 2000 Advanced Server SP4

I have a VB6 application that uses MTS in a COM+ package for
transaction based processing over MSDTC. This application was working
fine when run from the SQL Server machine on Windows 2000 Advanced
Server until the latest security updates were installed. Now the
application fails to connect to SQL Server when the call is made inside
a transaction context within MTS/COM+
I have verified that MSDTC is started
The DTCTester tool runs successfully
RPC port 135 is open
This application runs fine on a Windows 2000 Server machine with SP4.
What is different about Windows 2000 Advanced Server such that it no
longer works after applying security updates (SP4)'Ä°s your SQL server and application server are in same domain, do you have
firewall etc between SQL Server and appl. server?
We had problems after we install Windows 2003 SP1 with MSDTC, we select No
Authantication Required and the problem is gone. Maybe because of you have
applied security patches you are having the same problem.
Check out:
http://support.microsoft.com/?id=883960
Hope this helps.
"dhalb@.comcast.net" wrote:
> I have a VB6 application that uses MTS in a COM+ package for
> transaction based processing over MSDTC. This application was working
> fine when run from the SQL Server machine on Windows 2000 Advanced
> Server until the latest security updates were installed. Now the
> application fails to connect to SQL Server when the call is made inside
> a transaction context within MTS/COM+
> I have verified that MSDTC is started
> The DTCTester tool runs successfully
> RPC port 135 is open
> This application runs fine on a Windows 2000 Server machine with SP4.
> What is different about Windows 2000 Advanced Server such that it no
> longer works after applying security updates (SP4)'
>

MSDTC fails on Windows 2000 Advanced Server SP4

I have a VB6 application that uses MTS in a COM+ package for
transaction based processing over MSDTC. This application was working
fine when run from the SQL Server machine on Windows 2000 Advanced
Server until the latest security updates were installed. Now the
application fails to connect to SQL Server when the call is made inside
a transaction context within MTS/COM+
I have verified that MSDTC is started
The DTCTester tool runs successfully
RPC port 135 is open
This application runs fine on a Windows 2000 Server machine with SP4.
What is different about Windows 2000 Advanced Server such that it no
longer works after applying security updates (SP4)'?s your SQL server and application server are in same domain, do you have
firewall etc between SQL Server and appl. server?
We had problems after we install Windows 2003 SP1 with MSDTC, we select No
Authantication Required and the problem is gone. Maybe because of you have
applied security patches you are having the same problem.
Check out:
http://support.microsoft.com/?id=883960
Hope this helps.
"dhalb@.comcast.net" wrote:

> I have a VB6 application that uses MTS in a COM+ package for
> transaction based processing over MSDTC. This application was working
> fine when run from the SQL Server machine on Windows 2000 Advanced
> Server until the latest security updates were installed. Now the
> application fails to connect to SQL Server when the call is made inside
> a transaction context within MTS/COM+
> I have verified that MSDTC is started
> The DTCTester tool runs successfully
> RPC port 135 is open
> This application runs fine on a Windows 2000 Server machine with SP4.
> What is different about Windows 2000 Advanced Server such that it no
> longer works after applying security updates (SP4)'
>

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...
>
>

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.
> >
>
>

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...
>
>

MSDTC & W2K3 & SQL 2000 issue

I have MSDTC installed in the Cluster group (no other disks available). It fails over fine, comes online on either node, no problem. My DBA alerted me, that she cannot start Distributed Transaction Coordinator on the node that is NOT in control of the MSD
TC resource using SQL Server Enterprise Manager. This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA) CAN start MSDTC on either/both nodes of the W2K cluster. W
hy won't DTC start on the other node in Ent Mgr? The DBA says that this is necessary for something to function correctly, so I have to fix it? Any ideas/help would be appreciated.
A clustered instance of SQL server uses a cluster-wide MSDTC instance
instead of a local MSDTC instance on each host node. As such, the cluster
admin tool becomes the correct tool for managing MSDTC, not SQL Enterprise
Mangler. So, the behavior your DBA noted is correct for a cluster, but
since MSDTC is running the application will function correctly.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"wbielinski at abms dot org" <wbielinski at abms dot
org@.discussions.microsoft.com> wrote in message
news:E0451843-96A1-4B57-98E0-39CD3A73304D@.microsoft.com...
> I have MSDTC installed in the Cluster group (no other disks available). It
fails over fine, comes online on either node, no problem. My DBA alerted me,
that she cannot start Distributed Transaction Coordinator on the node that
is NOT in control of the MSDTC resource using SQL Server Enterprise Manager.
This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I
configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA)
CAN start MSDTC on either/both nodes of the W2K cluster. Why won't DTC
start on the other node in Ent Mgr? The DBA says that this is necessary for
something to function correctly, so I have to fix it? Any ideas/help would
be appreciated.
|||It is a good idea to place MSDTC in its own resource group and another thing
I will check is that the Network access for DTC is enabled. YOu can look for
this in control panel/add remove programs/add remove components/Application
Server.
"Geoff N. Hiten" wrote:

> A clustered instance of SQL server uses a cluster-wide MSDTC instance
> instead of a local MSDTC instance on each host node. As such, the cluster
> admin tool becomes the correct tool for managing MSDTC, not SQL Enterprise
> Mangler. So, the behavior your DBA noted is correct for a cluster, but
> since MSDTC is running the application will function correctly.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "wbielinski at abms dot org" <wbielinski at abms dot
> org@.discussions.microsoft.com> wrote in message
> news:E0451843-96A1-4B57-98E0-39CD3A73304D@.microsoft.com...
> fails over fine, comes online on either node, no problem. My DBA alerted me,
> that she cannot start Distributed Transaction Coordinator on the node that
> is NOT in control of the MSDTC resource using SQL Server Enterprise Manager.
> This is on W2K3. This cluster will be replacing a W2K/SQL2K cluster. I
> configured the W2K3 cluster, the same as the W2K cluster, yet she (the DBA)
> CAN start MSDTC on either/both nodes of the W2K cluster. Why won't DTC
> start on the other node in Ent Mgr? The DBA says that this is necessary for
> something to function correctly, so I have to fix it? Any ideas/help would
> be appreciated.
>
>