Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

COM+ error since upgrading to 7.1

As soon as we upgraded to 7.1 early last week the following message began showing up every few hours or so. Anyone have any ideas

Event Type: Error
Event Source: COM+
Event Category: Unknown
Event ID: 4786
Date: 3/26/2004
Time: 7:59:45 AM
User: N/A
Computer: MONITOR1
Description:
The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide them with the information below.
Component Prog ID:
Server Application ID: {8BF7F3C4-EF35-4968-A4C8-C84CB31C7875}
Server Application Instance ID:
{67E43FD6-EE5B-4210-A40E-C217B4D873C8}
Server Application Name: SolarWinds Orion NPM
The serious nature of this error has caused the process to terminate.
Exception: C0000005
Address: 0x031F3CE1
Call Stack:
PEGRP32C!PEgethotspotdata + 0x1ba5ec
PEGRP32C!PEgethotspotdata + 0x1b9d11
PEGRP32C!PEgethotspotdata + 0x1b9f45
USER32!GetMessageW + 0x1ee
USER32!CharUpperBuffA + 0x659
USER32!DestroyWindow + 0x38
ntdll!KiUserCallbackDispatcher + 0x13
pego32c!DllUnregisterServer + 0x7db3
pego32c!DllUnregisterServer + 0x2a415
pego32c!DllUnregisterServer + 0x120ef
pego32c!DllUnregisterServer + 0x29577
pego32c!DllUnregisterServer + 0x29780
USER32! + 0x612f
USER32!GetMessageW + 0x1ee
USER32!CharUpperBuffA + 0x659
USER32!CharUpperBuffA + 0x69c
ntdll!KiUserCallbackDispatcher + 0x13
MSVBVM60!IID_IVbaHost + 0x18d0f
MSVBVM60!BASIC_CLASS_Invoke + 0x1386
MSVBVM60!EbResetProject + 0x3ad
MSVBVM60!BASIC_CLASS_Invoke + 0x1095
MSVBVM60!__vbaNew2 + 0xf63
MSVBVM60!BASIC_CLASS_Invoke + 0xf75
MSVBVM60!BASIC_CLASS_Invoke + 0xeca
MSVBVM60!EVENT_SINK_AddRef + 0x11c
MSVBVM60!__vbaNew2 + 0xad7
ole32!IsValidIid + 0x12c6
ole32!CoImpersonateClient + 0x357
ole32!UpdateDCOMSettings + 0x49be
ole32!CoQueryAuthenticationServices + 0x2332

Find more posts tagged with

Accepted answers

All comments

Network_Guru

Did you shut down all the services and uninstall 7.0 before installing 7.1 ?
Perhaps there are some old com objects still being used?

-=Cheers=-
NG

skrause

I did shut down all the services, but I did not uninstall v7. I have never had to run an uninstall before and we've upgraded incrementally since v5.5

Is there a way I can find and get rid of the component now without uninstalling? Everything seems fine except for this error message.

I heard there was a problem with the PEGRP32C.OCX and the developers are working to track down the cause and fix.

BK
Nobody Special

tscaggs

According to tech support, this is going to be resolved in 7.2 - currently in-house beta, released soon(ish).

dimonet

This HAS been resolved in 7.2. Was having the same problem and it has been corrected by 7.2 to be released soon.

Dimo

rwbuckn

I'm still getting it on 7.2

gonzajoh

Interesting. I was getting exactly the same problem with 7.1 for the past 2 weeks. Our central server team applied the MS Hotfix against the pesky Sasser worm, and guess what, my COM+ errors have gone! Please apply this patch ASAP on your servers and let us know if you too have benefited. (You need to apply this patch anyway, it is classed as Critical by MS and therefore should be considered mandatory).

cossiart

Had the same COM+ issues as the rest of you. Tracked it down to ProEssentials OCX and DLL controls produced by www.gigasoft.com that are used by SolarWinds developers. I downloaded Gigasofts free demo ProEssentials software, installed it on another machine and extracted a newer version of PEGRP32C.DLL. Stopped Solarwinds, renamed the current DLL and replaced it with this new one. System ran fine. Couldn't get the COM+ error to re-occur. Put the old DLL back in poof broke again. The only problem is that the free DLL has a logo in it from www.gigasoft.com in it so you need a licensed distributable version. But if you don't mind the logo, COM+ problem gone. To make a long story short I am of the opinion there is a problem with the PEGRP32C.DLL. Give it a try.