PDA

View Full Version : cannot connect, Vista problem



LeCopain
08-19-2009, 03:42 AM
Hi,

I've got a very annoying problem and spent several hours trying to find a fix. I hope you guys can help me out.
The problem I have:
HEM cannot connect any longer to the local host. I did read the FAQ on this problem but my error is caused differently.

Yesterday I had a COM+ Event System stopped working message.
I tried several solution including reregistring a number of .dll's but I keep getting errors (the same others get) when reregistring. esp the regsvr32 es.dll keeps failing something about entry point.

It is probably caused because I used RegTool and 'reregistered' a couple of things. I now removed RegTool and run a virusscan (no result) using NOD32.

Unfortunately my restore point is corrupted (might have to do with broken COM+ event system and VSS problem)

So I then upgraded to Vista SP2, installed new drivers for LAN and Catalyst Control Centre.
My problem now is that 'A host process stopped working' if I check log files it gives a few errors cause by DCOM. The errors are authorization errors: NT AUTHORIZE\LOCAL SERVICE.

I have no clue how to proceed, and the stupid part is, everything except HEM works just fine.
Unlike others with this problem I am not using nVidia firewall, nor HP printers nor AOL IM.


error report:
Probleem met handtekening
Naam van probleemgebeurtenis: BEX64
Naam van de toepassing: svchost.exe_EventSystem
Versie van toepassing: 6.0.6001.18000
Tijdstempel van toepassing: 47919291
Naam van foutmodule: netprofm.dll_unloaded
Versie van foutmodule: 0.0.0.0
Tijdstempel van foutmodule: 4791ad84
Uitzonderingsmarge: 000007fef40a3820
Uitzonderingscode: c0000005
Uitzonderingsgegevens: 0000000000000008
Versie van besturingssysteem: 6.0.6002.2.2.0.768.2
Landinstelling-id: 1043

and:

Probleem met handtekening
Naam van probleemgebeurtenis: BEX64
Naam van de toepassing: svchost.exe_nsi
Versie van toepassing: 6.0.6001.18000
Tijdstempel van toepassing: 47919291
Naam van foutmodule: netprofm.dll_unloaded
Versie van foutmodule: 0.0.0.0
Tijdstempel van foutmodule: 4791ad84
Uitzonderingsmarge: 000007fef5f13820
Uitzonderingscode: c0000005
Uitzonderingsgegevens: 0000000000000008
Versie van besturingssysteem: 6.0.6002.2.2.0.768.2
Landinstelling-id: 1043
Aanvullende informatie 1: 98f6
Aanvullende informatie 2: 87675ed52f92c29ca9743f9c4f847526
Aanvullende informatie 3: b07c
Aanvullende informatie 4: d49704ac1ed176b8d532f7a86e9f442b


the distributedCOM log:

System

- Provider

[ Name] Microsoft-Windows-DistributedCOM
[ Guid] {1B562E86-B7AA-4131-BADC-B6F3A001407E}
[ EventSourceName] DCOM

- EventID 10016

[ Qualifiers] 49152

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2009-08-18T21:04:20.000Z

EventRecordID 55816

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel System

Computer xxxxxx

- Security

[ UserID] S-1-5-19


- EventData

param1 standaard voor deze computer
param2 Lokaal
param3 Activeren
param4 {A47979D2-C419-11D9-A5B4-001185AD2B89}
param5 NT AUTHORITY
param6 LOCAL SERVICE
param7 S-1-5-19
param8 LocalHost (via LRPC)


authorization problem: Activeren (Lokaal) voor de COM-servertoepassing met CLSID
{A47979D2-C419-11D9-A5B4-001185AD2B89}
aan de gebruiker NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) met adres LocalHost (via LRPC). Deze beveiligingsmachtiging kan worden gewijzigd met het beheerdershulpprogramma van Component Services.

fozzy71
08-19-2009, 06:16 AM
Which FAQs did you try?

1) http://www.holdemmanager.net/faq/afmviewfaq.aspx?faqid=34
2) http://www.holdemmanager.net/faq/afmviewfaq.aspx?faqid=171
3) http://www.holdemmanager.net/forum/showthread.php?t=8261

If you already tried 1 and 2, please try #3. That will often cure the problems that the first 2 faqs wont.


If none of that helps, Please email fabio@holdemmanager.net, with a link to this thread, and your forum name, so you can schedule a Teamviewer session. Download and install the www.Teamviewer.com Quick Support version.

LeCopain
08-19-2009, 06:20 AM
I did the first two FAQ, not yet the third. Will try soon.

The nature of my problem, however, is most likely to be the broken COM+ System Event service..