Prev: Installation od IIS: file errors
Next: IIS Hang in Window2kSP4
From: Richard B68 on 19 Apr 2006 10:55
Component services vanishes when I expand the computers node. I've tried
reinstalling COM+ as described in Q315296 (registering ole32 & oleaut32
because I'm on XP pro). Still no luck. Is there anywhere I can look to see
what's happening when I expand this node? I worked on some COM+ components a
while ago so I suspect its a "registered but not present" kind of thing.
Thanks.

"Bernard Cheah [MVP]" wrote:

> Well, in that case fix you com+ error first,
> can you expand the component service to my computer level?
>
>
> --
> Regards,
> Bernard Cheah
> http://www.iis-resources.com/
> http://www.iiswebcastseries.com/
> http://msmvps.com/blogs/bernard/
>
>
> "Richard B68" <RichardB(a)nospam.nospam> wrote in message
> news:C9A65E66-FAE6-4525-A073-4A3143DE88EB(a)microsoft.com...
> > Not much about IIS - only
> >
> > [snip]
> > The IIS Admin service failed to start due to the following error:
> > The service did not respond to the start or control request in a timely
> > fashion.
> > [snip]
> >
> > Which isn't very helpfull. I have gone a little further since my last
> > post
> > because it looks like COM+ is broken on my system.
> >
> > Event log entries like this abound:
> >
> > [snip]
> > The run-time environment has detected an inconsistency in its internal
> > state. This indicates a potential instability in the process that could be
> > caused by the custom components running in the COM+ application, the
> > components they make use of, or other factors. Error in
> > d:\qxp_slp\com\com1x\src\comsvcs\package\cpackage.cpp(1184), hr =
> > 8007041d:
> > InitEventCollector failed
> > [snip]
> >
> > So I uninstalled IIS and tried to reinstall COM+ using the proceedure in
> > Q315296. That doesn't seem to have helped much since comexp.msc runs and
> > hides when I try to expand the computers node.
> >
> > Anywhere else I can look? I'd rather understand the problem than just
> > image
> > over the top of it.
> >
> > Thanks,
> > Richard.
>
>
>
From: Bernard Cheah [MVP] on 20 Apr 2006 04:23
Similar but you can try various method in the comment methods to see if it
helps.
The famous 'Class not registered'
http://msmvps.com/blogs/bernard/archive/2005/03/22/39216.aspx

--
Regards,
Bernard Cheah
http://www.iis-resources.com/
http://www.iiswebcastseries.com/
http://msmvps.com/blogs/bernard/


"Richard B68" <RichardB(a)nospam.nospam> wrote in message
news:CA9C71B0-B13D-47EA-B656-7687A9211987(a)microsoft.com...
> Component services vanishes when I expand the computers node. I've tried
> reinstalling COM+ as described in Q315296 (registering ole32 & oleaut32
> because I'm on XP pro). Still no luck. Is there anywhere I can look to
> see
> what's happening when I expand this node? I worked on some COM+
> components a
> while ago so I suspect its a "registered but not present" kind of thing.
> Thanks.
>
> "Bernard Cheah [MVP]" wrote:
>
>> Well, in that case fix you com+ error first,
>> can you expand the component service to my computer level?
>>
>>
>> --
>> Regards,
>> Bernard Cheah
>> http://www.iis-resources.com/
>> http://www.iiswebcastseries.com/
>> http://msmvps.com/blogs/bernard/
>>
>>
>> "Richard B68" <RichardB(a)nospam.nospam> wrote in message
>> news:C9A65E66-FAE6-4525-A073-4A3143DE88EB(a)microsoft.com...
>> > Not much about IIS - only
>> >
>> > [snip]
>> > The IIS Admin service failed to start due to the following error:
>> > The service did not respond to the start or control request in a timely
>> > fashion.
>> > [snip]
>> >
>> > Which isn't very helpfull. I have gone a little further since my last
>> > post
>> > because it looks like COM+ is broken on my system.
>> >
>> > Event log entries like this abound:
>> >
>> > [snip]
>> > The run-time environment has detected an inconsistency in its internal
>> > state. This indicates a potential instability in the process that could
>> > be
>> > caused by the custom components running in the COM+ application, the
>> > components they make use of, or other factors. Error in
>> > d:\qxp_slp\com\com1x\src\comsvcs\package\cpackage.cpp(1184), hr =
>> > 8007041d:
>> > InitEventCollector failed
>> > [snip]
>> >
>> > So I uninstalled IIS and tried to reinstall COM+ using the proceedure
>> > in
>> > Q315296. That doesn't seem to have helped much since comexp.msc runs
>> > and
>> > hides when I try to expand the computers node.
>> >
>> > Anywhere else I can look? I'd rather understand the problem than just
>> > image
>> > over the top of it.
>> >
>> > Thanks,
>> > Richard.
>>
>>
>>


From: Richard B68 on 20 Apr 2006 08:04
I'm pretty sure I've tried the solutions listed in "TFCNR". Will have to
take a deep breath and go again.

I profiled mmc.exe on the broken machine and one that works. Don't know if
this sheds any light.
A breakpoint on GetClassObject in Ole32.dll isn't hit.
Thanks for your help.



Broken machine:
00:00:22.603: LoadLibraryW("ODBC32.DLL") called from
"c:\windows\system32\COMSVCS.DLL" at address 0x766750A8 by thread 1.
00:00:22.603: Loaded "c:\windows\system32\ODBC32.DLL" at address 0x74320000
by thread 1. Successfully hooked module.
00:00:22.603: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
"c:\windows\system32\ODBC32.DLL" called by thread 1.
00:00:22.603: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
"TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL" at
address 0x7432FC07 and returned 0x7C90112B by thread 1.
00:00:22.603: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
"TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL" at
address 0x7432F02C and returned 0x7C90112B by thread 1.
00:00:22.603: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
"SetCriticalSectionSpinCount") called from "c:\windows\system32\ODBC32.DLL"
at address 0x7432F039 and returned 0x7C928260 by thread 1.
00:00:22.613: LoadLibraryExA("c:\windows\system32\odbcint.dll", 0x00000000,
LOAD_WITH_ALTERED_SEARCH_PATH) called from "c:\windows\system32\ODBC32.DLL"
at address 0x7432F479 by thread 1.
00:00:22.613: Loaded "c:\windows\system32\ODBCINT.DLL" at address 0x01CD0000
by thread 1. Successfully hooked module.
00:00:22.613: LoadLibraryExA("c:\windows\system32\odbcint.dll", 0x00000000,
LOAD_WITH_ALTERED_SEARCH_PATH) returned 0x01CD0000 by thread 1.
00:00:22.613: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
"c:\windows\system32\ODBC32.DLL" returned 1 (0x1) by thread 1.
00:00:22.613: LoadLibraryW("ODBC32.DLL") returned 0x74320000 by thread 1.
00:00:22.613: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
"SQLAllocEnv") called from "c:\windows\system32\COMSVCS.DLL" at address
0x766750C1 and returned 0x7432F2D4 by thread 1.
00:00:22.613: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
"SQLAllocConnect") called from "c:\windows\system32\COMSVCS.DLL" at address
0x766750CE and returned 0x7432A635 by thread 1.
00:00:22.623: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
"SQLBindParameter") called from "c:\windows\system32\COMSVCS.DLL" at address
0x766750DB and returned 0x7432A91C by thread 1.
00:00:22.623: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
"SQLAllocHandle") called from "c:\windows\system32\COMSVCS.DLL" at address
0x766750E8 and returned 0x74344AE7 by thread 1.
00:00:22.623: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
"SQLSetEnvAttr") called from "c:\windows\system32\COMSVCS.DLL" at address
0x766750F5 and returned 0x7432FF6B by thread 1.
00:00:22.643: Thread 1 exited with code 2131666259 (0x7F0EA553).
00:00:22.653: Thread 2 exited with code 2131666259 (0x7F0EA553).
00:00:22.663: Thread 3 exited with code 2131666259 (0x7F0EA553).
00:00:22.663: Thread 4 exited with code 2131666259 (0x7F0EA553).
00:00:22.663: Thread 5 exited with code 2131666259 (0x7F0EA553).
00:00:22.663: Thread 7 exited with code 2131666259 (0x7F0EA553).
00:00:22.663: Thread 8 exited with code 2131666259 (0x7F0EA553).
00:00:22.673: Thread 9 exited with code 2131666259 (0x7F0EA553).
00:00:22.773: Exited "c:\windows\system32\MMC.EXE" (process 0xE60) with code
2131666259 (0x7F0EA553) by thread 10.
00:00:00.140: Entrypoint reached. All implicit modules have been loaded.

Working machine:
00:00:15.563: LoadLibraryW("ODBC32.DLL") called from
"c:\windows\system32\COMSVCS.DLL" at address 0x766750A8 by thread 1.
00:00:15.578: Thread 11 exited with code 0 (0x0).
00:00:15.578: Loaded "c:\windows\system32\ODBC32.DLL" at address 0x74320000
by thread 1. Successfully hooked module.
00:00:15.578: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
"c:\windows\system32\ODBC32.DLL" called by thread 1.
00:00:15.578: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
"TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL" at
address 0x7432FC07 and returned 0x7C90112B by thread 1.
00:00:15.578: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
"TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL" at
address 0x7432F02C and returned 0x7C90112B by thread 1.
00:00:15.594: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
"SetCriticalSectionSpinCount") called from "c:\windows\system32\ODBC32.DLL"
at address 0x7432F039 and returned 0x7C928260 by thread 1.
00:00:15.594: LoadLibraryExA("c:\windows\system32\odbcint.dll", 0x00000000,
LOAD_WITH_ALTERED_SEARCH_PATH) called from "c:\windows\system32\ODBC32.DLL"
at address 0x7432F479 by thread 1.
00:00:15.594: Loaded "c:\windows\system32\ODBCINT.DLL" at address 0x01960000
by thread 1. Successfully hooked module.
00:00:15.594: LoadLibraryExA("c:\windows\system32\odbcint.dll", 0x00000000,
LOAD_WITH_ALTERED_SEARCH_PATH) returned 0x01960000 by thread 1.
00:00:15.594: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
"c:\windows\system32\ODBC32.DLL" returned 1 (0x1) by thread 1.
00:00:15.594: LoadLibraryW("ODBC32.DLL") returned 0x74320000 by thread 1.
00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
"SQLAllocEnv") called from "c:\windows\system32\COMSVCS.DLL" at address
0x766750C1 and returned 0x7432F2D4 by thread 1.
00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
"SQLAllocConnect") called from "c:\windows\system32\COMSVCS.DLL" at address
0x766750CE and returned 0x7432A635 by thread 1.
00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
"SQLBindParameter") called from "c:\windows\system32\COMSVCS.DLL" at address
0x766750DB and returned 0x7432A91C by thread 1.
00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
"SQLAllocHandle") called from "c:\windows\system32\COMSVCS.DLL" at address
0x766750E8 and returned 0x74344AE7 by thread 1.
00:00:15.609: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
"SQLSetEnvAttr") called from "c:\windows\system32\COMSVCS.DLL" at address
0x766750F5 and returned 0x7432FF6B by thread 1.
00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"CoGetClassObject") called from "c:\windows\system32\RPCRT4.DLL" at address
0x77E9022F and returned 0x77515DB2 by thread 1.
00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"CoGetMarshalSizeMax") called from "c:\windows\system32\RPCRT4.DLL" at
address 0x77E90249 and returned 0x77510D1F by thread 1.
00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"CoMarshalInterface") called from "c:\windows\system32\RPCRT4.DLL" at address
0x77E90263 and returned 0x7751428D by thread 1.
00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"CoUnmarshalInterface") called from "c:\windows\system32\RPCRT4.DLL" at
address 0x77E9027D and returned 0x77510E53 by thread 1.
00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"StringFromIID") called from "c:\windows\system32\RPCRT4.DLL" at address
0x77E90297 and returned 0x775548BB by thread 1.
00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"CoGetPSClsid") called from "c:\windows\system32\RPCRT4.DLL" at address
0x77E902B1 and returned 0x7751B51C by thread 1.
00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"CoTaskMemAlloc") called from "c:\windows\system32\RPCRT4.DLL" at address
0x77E902C7 and returned 0x774FD048 by thread 1.
00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"CoTaskMemFree") called from "c:\windows\system32\RPCRT4.DLL" at address
0x77E902DD and returned 0x774FD02C by thread 1.
00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"CoCreateInstance") called from "c:\windows\system32\RPCRT4.DLL" at address
0x77E902F3 and returned 0x774FFAC3 by thread 1.
00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"CoReleaseMarshalData") called from "c:\windows\system32\RPCRT4.DLL" at
address 0x77E90309 and returned 0x7750EA5B by thread 1.
00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
"DcomChannelSetHResult") called from "c:\windows\system32\RPCRT4.DLL" at
address 0x77E9031F and returned 0x7750F6BF by thread 1.
00:00:15.625: Thread 12 started in "c:\windows\system32\KERNEL32.DLL" at
address 0x7C810856.
00:00:15.656: LoadLibraryExW("C:\WINDOWS\system32\es.dll", 0x00000000,
LOAD_WITH_ALTERED_SEARCH_PATH) called from "c:\windows\system32\OLE32.DLL" at
address 0x7752E1B1 by thread 12.
00:00:15.656: Loaded "c:\windows\system32\ES.DLL" at address 0x77710000 by
thread 12. Successfully hooked module.
00:00:15.656: DllMain(0x77710000, DLL_PROCESS_ATTACH, 0x00000000) in
"c:\windows\system32\ES.DLL" called by thread 12.
00:00:15.672: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
"InitializeCriticalSectionAndSpinCount") called from
"c:\windows\system32\ES.DLL" at address 0x7772E03C and returned 0x7C80B6B1 by
thread 12.
00:00:15.672: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
"InitializeCriticalSectionAndSpinCount") called from
"c:\windows\system32\ES.DLL" at address 0x7773D1FB and returned 0x7C80B6B1 by
thread 12.


"Bernard Cheah [MVP]" wrote:

> Similar but you can try various method in the comment methods to see if it
> helps.
> The famous 'Class not registered'
> http://msmvps.com/blogs/bernard/archive/2005/03/22/39216.aspx
>
> --
> Regards,
> Bernard Cheah
> http://www.iis-resources.com/
> http://www.iiswebcastseries.com/
> http://msmvps.com/blogs/bernard/
>
>
> "Richard B68" <RichardB(a)nospam.nospam> wrote in message
> news:CA9C71B0-B13D-47EA-B656-7687A9211987(a)microsoft.com...
> > Component services vanishes when I expand the computers node. I've tried
> > reinstalling COM+ as described in Q315296 (registering ole32 & oleaut32
> > because I'm on XP pro). Still no luck. Is there anywhere I can look to
> > see
> > what's happening when I expand this node? I worked on some COM+
> > components a
> > while ago so I suspect its a "registered but not present" kind of thing.
> > Thanks.
> >
> > "Bernard Cheah [MVP]" wrote:
> >
> >> Well, in that case fix you com+ error first,
> >> can you expand the component service to my computer level?
> >>
> >>
> >> --
> >> Regards,
> >> Bernard Cheah
> >> http://www.iis-resources.com/
> >> http://www.iiswebcastseries.com/
> >> http://msmvps.com/blogs/bernard/
> >>
> >>
> >> "Richard B68" <RichardB(a)nospam.nospam> wrote in message
> >> news:C9A65E66-FAE6-4525-A073-4A3143DE88EB(a)microsoft.com...
> >> > Not much about IIS - only
> >> >
> >> > [snip]
> >> > The IIS Admin service failed to start due to the following error:
> >> > The service did not respond to the start or control request in a timely
> >> > fashion.
> >> > [snip]
> >> >
> >> > Which isn't very helpfull. I have gone a little further since my last
> >> > post
> >> > because it looks like COM+ is broken on my system.
> >> >
> >> > Event log entries like this abound:
> >> >
> >> > [snip]
> >> > The run-time environment has detected an inconsistency in its internal
> >> > state. This indicates a potential instability in the process that could
> >> > be
> >> > caused by the custom components running in the COM+ application, the
> >> > components they make use of, or other factors. Error in
> >> > d:\qxp_slp\com\com1x\src\comsvcs\package\cpackage.cpp(1184), hr =
> >> > 8007041d:
> >> > InitEventCollector failed
> >> > [snip]
> >> >
> >> > So I uninstalled IIS and tried to reinstall COM+ using the proceedure
> >> > in
> >> > Q315296. That doesn't seem to have helped much since comexp.msc runs
> >> > and
> >> > hides when I try to expand the computers node.
> >> >
> >> > Anywhere else I can look? I'd rather understand the problem than just
> >> > image
> >> > over the top of it.
> >> >
> >> > Thanks,
> >> > Richard.
> >>
> >>
> >>
>
>
>
From: Richard B68 on 20 Apr 2006 11:57
I traced a little more with windbg.
Starting after the SQLSetEnvAttr call in comsvs.dll, all seems to go OK
until CoCreateInstance fails trying to create an IEventServer2 interface.

COMSVCS.DLL
CMTSPackage::InitEventDispatcher ultimately ends up at
CEventDispatcher::GetEventServer which calls
HR = CoCreateInstance({ECABAFBC...}, 0, 0x17, {378F3CA7...}, &StackVariable)

EC... is "COM+ Event Notification Server"
37... is "IEventServer2"

HR is 8007041D - (service didn't respond in an appropriate time).

Any thoughts on where to go next?
Thanks.

"Richard B68" wrote:

> I'm pretty sure I've tried the solutions listed in "TFCNR". Will have to
> take a deep breath and go again.
>
> I profiled mmc.exe on the broken machine and one that works. Don't know if
> this sheds any light.
> A breakpoint on GetClassObject in Ole32.dll isn't hit.
> Thanks for your help.
>
>
>
> Broken machine:
> 00:00:22.603: LoadLibraryW("ODBC32.DLL") called from
> "c:\windows\system32\COMSVCS.DLL" at address 0x766750A8 by thread 1.
> 00:00:22.603: Loaded "c:\windows\system32\ODBC32.DLL" at address 0x74320000
> by thread 1. Successfully hooked module.
> 00:00:22.603: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
> "c:\windows\system32\ODBC32.DLL" called by thread 1.
> 00:00:22.603: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
> "TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL" at
> address 0x7432FC07 and returned 0x7C90112B by thread 1.
> 00:00:22.603: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
> "TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL" at
> address 0x7432F02C and returned 0x7C90112B by thread 1.
> 00:00:22.603: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
> "SetCriticalSectionSpinCount") called from "c:\windows\system32\ODBC32.DLL"
> at address 0x7432F039 and returned 0x7C928260 by thread 1.
> 00:00:22.613: LoadLibraryExA("c:\windows\system32\odbcint.dll", 0x00000000,
> LOAD_WITH_ALTERED_SEARCH_PATH) called from "c:\windows\system32\ODBC32.DLL"
> at address 0x7432F479 by thread 1.
> 00:00:22.613: Loaded "c:\windows\system32\ODBCINT.DLL" at address 0x01CD0000
> by thread 1. Successfully hooked module.
> 00:00:22.613: LoadLibraryExA("c:\windows\system32\odbcint.dll", 0x00000000,
> LOAD_WITH_ALTERED_SEARCH_PATH) returned 0x01CD0000 by thread 1.
> 00:00:22.613: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
> "c:\windows\system32\ODBC32.DLL" returned 1 (0x1) by thread 1.
> 00:00:22.613: LoadLibraryW("ODBC32.DLL") returned 0x74320000 by thread 1.
> 00:00:22.613: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
> "SQLAllocEnv") called from "c:\windows\system32\COMSVCS.DLL" at address
> 0x766750C1 and returned 0x7432F2D4 by thread 1.
> 00:00:22.613: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
> "SQLAllocConnect") called from "c:\windows\system32\COMSVCS.DLL" at address
> 0x766750CE and returned 0x7432A635 by thread 1.
> 00:00:22.623: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
> "SQLBindParameter") called from "c:\windows\system32\COMSVCS.DLL" at address
> 0x766750DB and returned 0x7432A91C by thread 1.
> 00:00:22.623: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
> "SQLAllocHandle") called from "c:\windows\system32\COMSVCS.DLL" at address
> 0x766750E8 and returned 0x74344AE7 by thread 1.
> 00:00:22.623: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
> "SQLSetEnvAttr") called from "c:\windows\system32\COMSVCS.DLL" at address
> 0x766750F5 and returned 0x7432FF6B by thread 1.
> 00:00:22.643: Thread 1 exited with code 2131666259 (0x7F0EA553).
> 00:00:22.653: Thread 2 exited with code 2131666259 (0x7F0EA553).
> 00:00:22.663: Thread 3 exited with code 2131666259 (0x7F0EA553).
> 00:00:22.663: Thread 4 exited with code 2131666259 (0x7F0EA553).
> 00:00:22.663: Thread 5 exited with code 2131666259 (0x7F0EA553).
> 00:00:22.663: Thread 7 exited with code 2131666259 (0x7F0EA553).
> 00:00:22.663: Thread 8 exited with code 2131666259 (0x7F0EA553).
> 00:00:22.673: Thread 9 exited with code 2131666259 (0x7F0EA553).
> 00:00:22.773: Exited "c:\windows\system32\MMC.EXE" (process 0xE60) with code
> 2131666259 (0x7F0EA553) by thread 10.
> 00:00:00.140: Entrypoint reached. All implicit modules have been loaded.
>
> Working machine:
> 00:00:15.563: LoadLibraryW("ODBC32.DLL") called from
> "c:\windows\system32\COMSVCS.DLL" at address 0x766750A8 by thread 1.
> 00:00:15.578: Thread 11 exited with code 0 (0x0).
> 00:00:15.578: Loaded "c:\windows\system32\ODBC32.DLL" at address 0x74320000
> by thread 1. Successfully hooked module.
> 00:00:15.578: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
> "c:\windows\system32\ODBC32.DLL" called by thread 1.
> 00:00:15.578: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
> "TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL" at
> address 0x7432FC07 and returned 0x7C90112B by thread 1.
> 00:00:15.578: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
> "TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL" at
> address 0x7432F02C and returned 0x7C90112B by thread 1.
> 00:00:15.594: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
> "SetCriticalSectionSpinCount") called from "c:\windows\system32\ODBC32.DLL"
> at address 0x7432F039 and returned 0x7C928260 by thread 1.
> 00:00:15.594: LoadLibraryExA("c:\windows\system32\odbcint.dll", 0x00000000,
> LOAD_WITH_ALTERED_SEARCH_PATH) called from "c:\windows\system32\ODBC32.DLL"
> at address 0x7432F479 by thread 1.
> 00:00:15.594: Loaded "c:\windows\system32\ODBCINT.DLL" at address 0x01960000
> by thread 1. Successfully hooked module.
> 00:00:15.594: LoadLibraryExA("c:\windows\system32\odbcint.dll", 0x00000000,
> LOAD_WITH_ALTERED_SEARCH_PATH) returned 0x01960000 by thread 1.
> 00:00:15.594: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
> "c:\windows\system32\ODBC32.DLL" returned 1 (0x1) by thread 1.
> 00:00:15.594: LoadLibraryW("ODBC32.DLL") returned 0x74320000 by thread 1.
> 00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
> "SQLAllocEnv") called from "c:\windows\system32\COMSVCS.DLL" at address
> 0x766750C1 and returned 0x7432F2D4 by thread 1.
> 00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
> "SQLAllocConnect") called from "c:\windows\system32\COMSVCS.DLL" at address
> 0x766750CE and returned 0x7432A635 by thread 1.
> 00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
> "SQLBindParameter") called from "c:\windows\system32\COMSVCS.DLL" at address
> 0x766750DB and returned 0x7432A91C by thread 1.
> 00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
> "SQLAllocHandle") called from "c:\windows\system32\COMSVCS.DLL" at address
> 0x766750E8 and returned 0x74344AE7 by thread 1.
> 00:00:15.609: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
> "SQLSetEnvAttr") called from "c:\windows\system32\COMSVCS.DLL" at address
> 0x766750F5 and returned 0x7432FF6B by thread 1.
> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "CoGetClassObject") called from "c:\windows\system32\RPCRT4.DLL" at address
> 0x77E9022F and returned 0x77515DB2 by thread 1.
> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "CoGetMarshalSizeMax") called from "c:\windows\system32\RPCRT4.DLL" at
> address 0x77E90249 and returned 0x77510D1F by thread 1.
> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "CoMarshalInterface") called from "c:\windows\system32\RPCRT4.DLL" at address
> 0x77E90263 and returned 0x7751428D by thread 1.
> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "CoUnmarshalInterface") called from "c:\windows\system32\RPCRT4.DLL" at
> address 0x77E9027D and returned 0x77510E53 by thread 1.
> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "StringFromIID") called from "c:\windows\system32\RPCRT4.DLL" at address
> 0x77E90297 and returned 0x775548BB by thread 1.
> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "CoGetPSClsid") called from "c:\windows\system32\RPCRT4.DLL" at address
> 0x77E902B1 and returned 0x7751B51C by thread 1.
> 00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "CoTaskMemAlloc") called from "c:\windows\system32\RPCRT4.DLL" at address
> 0x77E902C7 and returned 0x774FD048 by thread 1.
> 00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "CoTaskMemFree") called from "c:\windows\system32\RPCRT4.DLL" at address
> 0x77E902DD and returned 0x774FD02C by thread 1.
> 00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "CoCreateInstance") called from "c:\windows\system32\RPCRT4.DLL" at address
> 0x77E902F3 and returned 0x774FFAC3 by thread 1.
> 00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "CoReleaseMarshalData") called from "c:\windows\system32\RPCRT4.DLL" at
> address 0x77E90309 and returned 0x7750EA5B by thread 1.
> 00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
> "DcomChannelSetHResult") called from "c:\windows\system32\RPCRT4.DLL" at
> address 0x77E9031F and returned 0x7750F6BF by thread 1.
> 00:00:15.625: Thread 12 started in "c:\windows\system32\KERNEL32.DLL" at
> address 0x7C810856.
> 00:00:15.656: LoadLibraryExW("C:\WINDOWS\system32\es.dll", 0x00000000,
> LOAD_WITH_ALTERED_SEARCH_PATH) called from "c:\windows\system32\OLE32.DLL" at
> address 0x7752E1B1 by thread 12.
> 00:00:15.656: Loaded "c:\windows\system32\ES.DLL" at address 0x77710000 by
> thread 12. Successfully hooked module.
> 00:00:15.656: DllMain(0x77710000, DLL_PROCESS_ATTACH, 0x00000000) in
> "c:\windows\system32\ES.DLL" called by thread 12.
> 00:00:15.672: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
> "InitializeCriticalSectionAndSpinCount") called from
> "c:\windows\system32\ES.DLL" at address 0x7772E03C and returned 0x7C80B6B1 by
> thread 12.
> 00:00:15.672: GetProcAddress(0x7C800000 [c:\windows\system32\KERNEL32.DLL],
> "InitializeCriticalSectionAndSpinCount") called from
> "c:\windows\system32\ES.DLL" at address 0x7773D1FB and returned 0x7C80B6B1 by
> thread 12.
>
>
> "Bernard Cheah [MVP]" wrote:
>
> > Similar but you can try various method in the comment methods to see if it
> > helps.
> > The famous 'Class not registered'
> > http://msmvps.com/blogs/bernard/archive/2005/03/22/39216.aspx
> >
> > --
> > Regards,
> > Bernard Cheah
> > http://www.iis-resources.com/
> > http://www.iiswebcastseries.com/
> > http://msmvps.com/blogs/bernard/
> >
> >
> > "Richard B68" <RichardB(a)nospam.nospam> wrote in message
> > news:CA9C71B0-B13D-47EA-B656-7687A9211987(a)microsoft.com...
> > > Component services vanishes when I expand the computers node. I've tried
> > > reinstalling COM+ as described in Q315296 (registering ole32 & oleaut32
> > > because I'm on XP pro). Still no luck. Is there anywhere I can look to
> > > see
> > > what's happening when I expand this node? I worked on some COM+
> > > components a
> > > while ago so I suspect its a "registered but not present" kind of thing.
> > > Thanks.
> > >
> > > "Bernard Cheah [MVP]" wrote:
> > >
> > >> Well, in that case fix you com+ error first,
> > >> can you expand the component service to my computer level?
> > >>
> > >>
> > >> --
> > >> Regards,
> > >> Bernard Cheah
> > >> http://www.iis-resources.com/
> > >> http://www.iiswebcastseries.com/
> > >> http://msmvps.com/blogs/bernard/
> > >>
> > >>
> > >> "Richard B68" <RichardB(a)nospam.nospam> wrote in message
> > >> news:C9A65E66-FAE6-4525-A073-4A3143DE88EB(a)microsoft.com...
> > >> > Not much about IIS - only
> > >> >
> > >> > [snip]
> > >> > The IIS Admin service failed to start due to the following error:
> > >> > The service did not respond to the start or control request in a timely
> > >> > fashion.
> > >> > [snip]
> > >> >
> > >> > Which isn't very helpfull. I have gone a little further since my last
> > >> > post
> > >> > because it looks like COM+ is broken on my system.
> > >> >
> > >> > Event log entries like this abound:
> > >> >
> > >> > [snip]
> > >> > The run-time environment has detected an inconsistency in its internal
> > >> > state. This indicates a potential instability in the process that could
> > >> > be
> > >> > caused by the custom components running in the COM+ application, the
> > >> > components they make use of, or other factors. Error in
> > >> > d:\qxp_slp\com\com1x\src\comsvcs\package\cpackage.cpp(1184), hr =
> > >> > 8007041d:
> > >> > InitEventCollector failed
> > >> > [snip]
> > >> >
> > >> > So I uninstalled IIS and tried to reinstall COM+ using the proceedure
> > >> > in
> > >> > Q315296. That doesn't seem to have helped much since comexp.msc runs
> > >> > and
> > >> > hides when I try to expand the computers node.
> > >> >
> > >> > Anywhere else I can look? I'd rather understand the problem than just
> > >> > image
> > >> > over the top of it.
> > >> >
> > >> > Thanks,
> > >> > Richard.
> > >>
> > >>
> > >>
> >
> >
> >
From: Bernard Cheah [MVP] on 21 Apr 2006 03:40
Now, I don't go that deep just to get IIS started.
Can you pls uninstall IIS
a) uninstall IIS (safe or normal mode)
b) Remove files and folders
%windir%/system32/inetsvr/
/inetpub/
%windir%/iisx.log (x=5 for w2k, 6 for XP, Win03)
(use safe mode to delete)

before installation, check if component servies is working correctly, and
you can drill down to component listing level.
then resintall IIS.

any error msgs during installation?
if no, can you start IIS ? if no, anything in event log and iisX.log file?

--
Regards,
Bernard Cheah
http://www.iis-resources.com/
http://www.iiswebcastseries.com/
http://msmvps.com/blogs/bernard/


"Richard B68" <RichardB(a)nospam.nospam> wrote in message
news:BE2BE9AE-DB0C-4313-A8AD-5C3FD75C9D22(a)microsoft.com...
>I traced a little more with windbg.
> Starting after the SQLSetEnvAttr call in comsvs.dll, all seems to go OK
> until CoCreateInstance fails trying to create an IEventServer2 interface.
>
> COMSVCS.DLL
> CMTSPackage::InitEventDispatcher ultimately ends up at
> CEventDispatcher::GetEventServer which calls
> HR = CoCreateInstance({ECABAFBC...}, 0, 0x17, {378F3CA7...},
> &StackVariable)
>
> EC... is "COM+ Event Notification Server"
> 37... is "IEventServer2"
>
> HR is 8007041D - (service didn't respond in an appropriate time).
>
> Any thoughts on where to go next?
> Thanks.
>
> "Richard B68" wrote:
>
>> I'm pretty sure I've tried the solutions listed in "TFCNR". Will have to
>> take a deep breath and go again.
>>
>> I profiled mmc.exe on the broken machine and one that works. Don't know
>> if
>> this sheds any light.
>> A breakpoint on GetClassObject in Ole32.dll isn't hit.
>> Thanks for your help.
>>
>>
>>
>> Broken machine:
>> 00:00:22.603: LoadLibraryW("ODBC32.DLL") called from
>> "c:\windows\system32\COMSVCS.DLL" at address 0x766750A8 by thread 1.
>> 00:00:22.603: Loaded "c:\windows\system32\ODBC32.DLL" at address
>> 0x74320000
>> by thread 1. Successfully hooked module.
>> 00:00:22.603: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
>> "c:\windows\system32\ODBC32.DLL" called by thread 1.
>> 00:00:22.603: GetProcAddress(0x7C800000
>> [c:\windows\system32\KERNEL32.DLL],
>> "TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL"
>> at
>> address 0x7432FC07 and returned 0x7C90112B by thread 1.
>> 00:00:22.603: GetProcAddress(0x7C800000
>> [c:\windows\system32\KERNEL32.DLL],
>> "TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL"
>> at
>> address 0x7432F02C and returned 0x7C90112B by thread 1.
>> 00:00:22.603: GetProcAddress(0x7C800000
>> [c:\windows\system32\KERNEL32.DLL],
>> "SetCriticalSectionSpinCount") called from
>> "c:\windows\system32\ODBC32.DLL"
>> at address 0x7432F039 and returned 0x7C928260 by thread 1.
>> 00:00:22.613: LoadLibraryExA("c:\windows\system32\odbcint.dll",
>> 0x00000000,
>> LOAD_WITH_ALTERED_SEARCH_PATH) called from
>> "c:\windows\system32\ODBC32.DLL"
>> at address 0x7432F479 by thread 1.
>> 00:00:22.613: Loaded "c:\windows\system32\ODBCINT.DLL" at address
>> 0x01CD0000
>> by thread 1. Successfully hooked module.
>> 00:00:22.613: LoadLibraryExA("c:\windows\system32\odbcint.dll",
>> 0x00000000,
>> LOAD_WITH_ALTERED_SEARCH_PATH) returned 0x01CD0000 by thread 1.
>> 00:00:22.613: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
>> "c:\windows\system32\ODBC32.DLL" returned 1 (0x1) by thread 1.
>> 00:00:22.613: LoadLibraryW("ODBC32.DLL") returned 0x74320000 by thread 1.
>> 00:00:22.613: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
>> "SQLAllocEnv") called from "c:\windows\system32\COMSVCS.DLL" at address
>> 0x766750C1 and returned 0x7432F2D4 by thread 1.
>> 00:00:22.613: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
>> "SQLAllocConnect") called from "c:\windows\system32\COMSVCS.DLL" at
>> address
>> 0x766750CE and returned 0x7432A635 by thread 1.
>> 00:00:22.623: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
>> "SQLBindParameter") called from "c:\windows\system32\COMSVCS.DLL" at
>> address
>> 0x766750DB and returned 0x7432A91C by thread 1.
>> 00:00:22.623: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
>> "SQLAllocHandle") called from "c:\windows\system32\COMSVCS.DLL" at
>> address
>> 0x766750E8 and returned 0x74344AE7 by thread 1.
>> 00:00:22.623: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
>> "SQLSetEnvAttr") called from "c:\windows\system32\COMSVCS.DLL" at address
>> 0x766750F5 and returned 0x7432FF6B by thread 1.
>> 00:00:22.643: Thread 1 exited with code 2131666259 (0x7F0EA553).
>> 00:00:22.653: Thread 2 exited with code 2131666259 (0x7F0EA553).
>> 00:00:22.663: Thread 3 exited with code 2131666259 (0x7F0EA553).
>> 00:00:22.663: Thread 4 exited with code 2131666259 (0x7F0EA553).
>> 00:00:22.663: Thread 5 exited with code 2131666259 (0x7F0EA553).
>> 00:00:22.663: Thread 7 exited with code 2131666259 (0x7F0EA553).
>> 00:00:22.663: Thread 8 exited with code 2131666259 (0x7F0EA553).
>> 00:00:22.673: Thread 9 exited with code 2131666259 (0x7F0EA553).
>> 00:00:22.773: Exited "c:\windows\system32\MMC.EXE" (process 0xE60) with
>> code
>> 2131666259 (0x7F0EA553) by thread 10.
>> 00:00:00.140: Entrypoint reached. All implicit modules have been loaded.
>>
>> Working machine:
>> 00:00:15.563: LoadLibraryW("ODBC32.DLL") called from
>> "c:\windows\system32\COMSVCS.DLL" at address 0x766750A8 by thread 1.
>> 00:00:15.578: Thread 11 exited with code 0 (0x0).
>> 00:00:15.578: Loaded "c:\windows\system32\ODBC32.DLL" at address
>> 0x74320000
>> by thread 1. Successfully hooked module.
>> 00:00:15.578: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
>> "c:\windows\system32\ODBC32.DLL" called by thread 1.
>> 00:00:15.578: GetProcAddress(0x7C800000
>> [c:\windows\system32\KERNEL32.DLL],
>> "TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL"
>> at
>> address 0x7432FC07 and returned 0x7C90112B by thread 1.
>> 00:00:15.578: GetProcAddress(0x7C800000
>> [c:\windows\system32\KERNEL32.DLL],
>> "TryEnterCriticalSection") called from "c:\windows\system32\ODBC32.DLL"
>> at
>> address 0x7432F02C and returned 0x7C90112B by thread 1.
>> 00:00:15.594: GetProcAddress(0x7C800000
>> [c:\windows\system32\KERNEL32.DLL],
>> "SetCriticalSectionSpinCount") called from
>> "c:\windows\system32\ODBC32.DLL"
>> at address 0x7432F039 and returned 0x7C928260 by thread 1.
>> 00:00:15.594: LoadLibraryExA("c:\windows\system32\odbcint.dll",
>> 0x00000000,
>> LOAD_WITH_ALTERED_SEARCH_PATH) called from
>> "c:\windows\system32\ODBC32.DLL"
>> at address 0x7432F479 by thread 1.
>> 00:00:15.594: Loaded "c:\windows\system32\ODBCINT.DLL" at address
>> 0x01960000
>> by thread 1. Successfully hooked module.
>> 00:00:15.594: LoadLibraryExA("c:\windows\system32\odbcint.dll",
>> 0x00000000,
>> LOAD_WITH_ALTERED_SEARCH_PATH) returned 0x01960000 by thread 1.
>> 00:00:15.594: DllMain(0x74320000, DLL_PROCESS_ATTACH, 0x00000000) in
>> "c:\windows\system32\ODBC32.DLL" returned 1 (0x1) by thread 1.
>> 00:00:15.594: LoadLibraryW("ODBC32.DLL") returned 0x74320000 by thread 1.
>> 00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
>> "SQLAllocEnv") called from "c:\windows\system32\COMSVCS.DLL" at address
>> 0x766750C1 and returned 0x7432F2D4 by thread 1.
>> 00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
>> "SQLAllocConnect") called from "c:\windows\system32\COMSVCS.DLL" at
>> address
>> 0x766750CE and returned 0x7432A635 by thread 1.
>> 00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
>> "SQLBindParameter") called from "c:\windows\system32\COMSVCS.DLL" at
>> address
>> 0x766750DB and returned 0x7432A91C by thread 1.
>> 00:00:15.594: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
>> "SQLAllocHandle") called from "c:\windows\system32\COMSVCS.DLL" at
>> address
>> 0x766750E8 and returned 0x74344AE7 by thread 1.
>> 00:00:15.609: GetProcAddress(0x74320000 [c:\windows\system32\ODBC32.DLL],
>> "SQLSetEnvAttr") called from "c:\windows\system32\COMSVCS.DLL" at address
>> 0x766750F5 and returned 0x7432FF6B by thread 1.
>> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "CoGetClassObject") called from "c:\windows\system32\RPCRT4.DLL" at
>> address
>> 0x77E9022F and returned 0x77515DB2 by thread 1.
>> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "CoGetMarshalSizeMax") called from "c:\windows\system32\RPCRT4.DLL" at
>> address 0x77E90249 and returned 0x77510D1F by thread 1.
>> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "CoMarshalInterface") called from "c:\windows\system32\RPCRT4.DLL" at
>> address
>> 0x77E90263 and returned 0x7751428D by thread 1.
>> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "CoUnmarshalInterface") called from "c:\windows\system32\RPCRT4.DLL" at
>> address 0x77E9027D and returned 0x77510E53 by thread 1.
>> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "StringFromIID") called from "c:\windows\system32\RPCRT4.DLL" at address
>> 0x77E90297 and returned 0x775548BB by thread 1.
>> 00:00:15.609: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "CoGetPSClsid") called from "c:\windows\system32\RPCRT4.DLL" at address
>> 0x77E902B1 and returned 0x7751B51C by thread 1.
>> 00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "CoTaskMemAlloc") called from "c:\windows\system32\RPCRT4.DLL" at address
>> 0x77E902C7 and returned 0x774FD048 by thread 1.
>> 00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "CoTaskMemFree") called from "c:\windows\system32\RPCRT4.DLL" at address
>> 0x77E902DD and returned 0x774FD02C by thread 1.
>> 00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "CoCreateInstance") called from "c:\windows\system32\RPCRT4.DLL" at
>> address
>> 0x77E902F3 and returned 0x774FFAC3 by thread 1.
>> 00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "CoReleaseMarshalData") called from "c:\windows\system32\RPCRT4.DLL" at
>> address 0x77E90309 and returned 0x7750EA5B by thread 1.
>> 00:00:15.625: GetProcAddress(0x774E0000 [c:\windows\system32\OLE32.DLL],
>> "DcomChannelSetHResult") called from "c:\windows\system32\RPCRT4.DLL" at
>> address 0x77E9031F and returned 0x7750F6BF by thread 1.
>> 00:00:15.625: Thread 12 started in "c:\windows\system32\KERNEL32.DLL" at
>> address 0x7C810856.
>> 00:00:15.656: LoadLibraryExW("C:\WINDOWS\system32\es.dll", 0x00000000,
>> LOAD_WITH_ALTERED_SEARCH_PATH) called from
>> "c:\windows\system32\OLE32.DLL" at
>> address 0x7752E1B1 by thread 12.
>> 00:00:15.656: Loaded "c:\windows\system32\ES.DLL" at address 0x77710000
>> by
>> thread 12. Successfully hooked module.
>> 00:00:15.656: DllMain(0x77710000, DLL_PROCESS_ATTACH, 0x00000000) in
>> "c:\windows\system32\ES.DLL" called by thread 12.
>> 00:00:15.672: GetProcAddress(0x7C800000
>> [c:\windows\system32\KERNEL32.DLL],
>> "InitializeCriticalSectionAndSpinCount") called from
>> "c:\windows\system32\ES.DLL" at address 0x7772E03C and returned
>> 0x7C80B6B1 by
>> thread 12.
>> 00:00:15.672: GetProcAddress(0x7C800000
>> [c:\windows\system32\KERNEL32.DLL],
>> "InitializeCriticalSectionAndSpinCount") called from
>> "c:\windows\system32\ES.DLL" at address 0x7773D1FB and returned
>> 0x7C80B6B1 by
>> thread 12.
>>
>>
>> "Bernard Cheah [MVP]" wrote:
>>
>> > Similar but you can try various method in the comment methods to see if
>> > it
>> > helps.
>> > The famous 'Class not registered'
>> > http://msmvps.com/blogs/bernard/archive/2005/03/22/39216.aspx
>> >
>> > --
>> > Regards,
>> > Bernard Cheah
>> > http://www.iis-resources.com/
>> > http://www.iiswebcastseries.com/
>> > http://msmvps.com/blogs/bernard/
>> >
>> >
>> > "Richard B68" <RichardB(a)nospam.nospam> wrote in message
>> > news:CA9C71B0-B13D-47EA-B656-7687A9211987(a)microsoft.com...
>> > > Component services vanishes when I expand the computers node. I've
>> > > tried
>> > > reinstalling COM+ as described in Q315296 (registering ole32 &
>> > > oleaut32
>> > > because I'm on XP pro). Still no luck. Is there anywhere I can look
>> > > to
>> > > see
>> > > what's happening when I expand this node? I worked on some COM+
>> > > components a
>> > > while ago so I suspect its a "registered but not present" kind of
>> > > thing.
>> > > Thanks.
>> > >
>> > > "Bernard Cheah [MVP]" wrote:
>> > >
>> > >> Well, in that case fix you com+ error first,
>> > >> can you expand the component service to my computer level?
>> > >>
>> > >>
>> > >> --
>> > >> Regards,
>> > >> Bernard Cheah
>> > >> http://www.iis-resources.com/
>> > >> http://www.iiswebcastseries.com/
>> > >> http://msmvps.com/blogs/bernard/
>> > >>
>> > >>
>> > >> "Richard B68" <RichardB(a)nospam.nospam> wrote in message
>> > >> news:C9A65E66-FAE6-4525-A073-4A3143DE88EB(a)microsoft.com...
>> > >> > Not much about IIS - only
>> > >> >
>> > >> > [snip]
>> > >> > The IIS Admin service failed to start due to the following error:
>> > >> > The service did not respond to the start or control request in a
>> > >> > timely
>> > >> > fashion.
>> > >> > [snip]
>> > >> >
>> > >> > Which isn't very helpfull. I have gone a little further since my
>> > >> > last
>> > >> > post
>> > >> > because it looks like COM+ is broken on my system.
>> > >> >
>> > >> > Event log entries like this abound:
>> > >> >
>> > >> > [snip]
>> > >> > The run-time environment has detected an inconsistency in its
>> > >> > internal
>> > >> > state. This indicates a potential instability in the process that
>> > >> > could
>> > >> > be
>> > >> > caused by the custom components running in the COM+ application,
>> > >> > the
>> > >> > components they make use of, or other factors. Error in
>> > >> > d:\qxp_slp\com\com1x\src\comsvcs\package\cpackage.cpp(1184), hr =
>> > >> > 8007041d:
>> > >> > InitEventCollector failed
>> > >> > [snip]
>> > >> >
>> > >> > So I uninstalled IIS and tried to reinstall COM+ using the
>> > >> > proceedure
>> > >> > in
>> > >> > Q315296. That doesn't seem to have helped much since comexp.msc
>> > >> > runs
>> > >> > and
>> > >> > hides when I try to expand the computers node.
>> > >> >
>> > >> > Anywhere else I can look? I'd rather understand the problem than
>> > >> > just
>> > >> > image
>> > >> > over the top of it.
>> > >> >
>> > >> > Thanks,
>> > >> > Richard.
>> > >>
>> > >>
>> > >>
>> >
>> >
>> >


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Installation od IIS: file errors
Next: IIS Hang in Window2kSP4