DTC disappears - Help needed

  • Thread starter Thread starter Howard Smith
  • Start date Start date
H

Howard Smith

We have been shipping an image since february this year,
which has worked fine. I am now recreating with all QFE's
in XPE. I have image set to 0 for no reseal at FBA.

Master image works flawlessly, but after I fbreseal, the
cloned images remove (eventually) Distributed Transaction
Cordinator service, which breaks COM+ and DCOM.

Has anyone seen this before?
Many Thanks

Howard Smith
 
Hi, Howard!
We have been shipping an image since february this year,
which has worked fine. I am now recreating with all QFE's
in XPE. I have image set to 0 for no reseal at FBA.

Master image works flawlessly, but after I fbreseal, the
cloned images remove (eventually) Distributed Transaction
Cordinator service, which breaks COM+ and DCOM.

Has anyone seen this before?
Click to expand...
Yes, I've seen. IIS also generates error 500 in this case.

There is a problem with one of the last QFEs (don't know exactly which
one) and in some circumstances (in my case all works on single processor
PC and error happened on the dual processor + DirectX9b installed after
FBA).

The symptom:
After a first boot after a reseal, there are some errors in the event
log related with DTC. The DTC at this time can not start and marked for
deletion. After the next reboot the DTC disappeared.

The solution is:
1) reboot machine
2) run msdtc -install -a

The drawback:
Even in this case I'm receiving error messages in the log regarded with
DTC tracing infrastructure...
MS DTC Tracing infrastructure : the initialization of the tracing
infrastructure failed. Internal Information : msdtc_trace : File:
d:\nt\com\com1x\dtc\dtc\trace\src\tracelib.cpp, Line: 1115, StartTrace
Failed, hr=0x80070070

Hope somebody in microfost could explain more.
 
Nikolai

Thanks, I agree also on the IIS error - asp seems to bomb
as well (must be dependant on DTC).

Are you saying without DX9 it appears OK?. I am
installing DX9 also, but I dont really need it.

BR

Howard
 
Hi, Howard!
Thanks, I agree also on the IIS error - asp seems to bomb
as well (must be dependant on DTC).

Are you saying without DX9 it appears OK?. I am
installing DX9 also, but I dont really need it.
Click to expand...
In my case:
1. Dual XEON + Dx9b ~99% chance of problem. Never got a working build.
2. Dual XEON or P4 + Dx9b ~1% chance of problem. Sometimes got a problem.
3. P4 in very rare cases gives me the same error. The probability is
increased if it changes of IP address without a network cable plugged.

I didn't dig to deep, I hope ms could clarify the situation.
If you don't mind false events in the log just put msdtc -install -a as
a run-once command.
 
Nikolai

I'm using a Via M10000 motherboard, and the problem I
also sometimes get is IIS dying, and DTC still
working !!!. I'm trying multiple builds without DX9.

I wonder if Dx9b, messes with copy protection, making XPe
think its a retail product?, but it's almost the same
result that you get if you reseal to many times!!!

I'll post results in this thread Monday

Maybe MS could shed some light?

BR

Howard
 
Nikolai

I have created a new image, which is identical in every
way except for DirectX9b, and WMP9.

This image works perfectly. I didnt have time to try with
WMP9 included and DX9b excluded. Can you confirm if you
have WMP9?

If anyone from MS reads this thread, can they comment on
this issue between DTC and DX9b.

Best Regards

Howard Smith

Dynamax Technologies ltd
 
Hi, Howard!
I have created a new image, which is identical in every
way except for DirectX9b, and WMP9.

This image works perfectly. I didnt have time to try with
WMP9 included and DX9b excluded. Can you confirm if you
have WMP9?

If anyone from MS reads this thread, can they comment on
this issue between DTC and DX9b.
Click to expand...
So, I've installed:
dxsetup.exe
wmfdist.exe
WM9Codecs.exe
I didn't have enough time to check them one by one, but when I removed
all of them (install them manually after reseal stage) I didn't have
problem with DTC.

I have an impression that DirectX9b is guilty. I'm not 100% sure, but I
did installation with WMF and codecs, and it worked.
 
Nikolai

Yes I agree that it 'feels' like DX9.
I wish someone from MS would comment, but the newsgroup seems 'thin on the
ground' with MS staff at the moment.

Howard
 
Back
Top