Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 0 subscribers
  • Views 37655 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Puremessage on exchange 0x80040154 error

AshfieldSchool

Hi,

I can't get into our PureMessage 3.1 console. Error MMC could not create the snap=in.

  • Sophos Puremessage service will not start with a 0x80040154: Class not registered error.
  • Can't uninstall (setup was unable to remove this server from the PureMessage server group. COM error-code 0x80040154:class not registered)
  • Can't re-install (Product: Sophos PureMessage -- Setup encountered an error while gathering system information.Error details: COM error-code 0x80040154 : Class not registered )

Looking back through the event log there are thousands of PM warnings:

Reporting data could not be written to the database at this time (error: -3).  Additional attempts will be made for 3 days.

<- <System>
  <Provider Name="PureMessage" />
  <EventID Qualifiers="40960">55</EventID>
  <Level>3</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2011-10-17T02:00:33.000000000Z" />
  <EventRecordID>2784526</EventRecordID>
  <Channel>Application</Channel>
  <Computer>server.domain.local</Computer>
  <Security />
  </System>
- <EventData>
  <Data>-3</Data>
  <Data>3</Data>
  </EventData>
  </Event>

I'm at a loss what to try next, could someone suggest a fix?

Thanks.

:18001


This thread was automatically locked due to age.
Parents
  • 0

    Which version of PureMessage for Exchange are you running? This was a bug that was fixed in 3.1.1 and higher, so if you are running an older version and you able to upgrade, that would be the best course of action.

    Otherwise, do contact one of our support engineers since we do have a script that's a temporary workaround for 3.1.0 -- there are certain conditions you need to be aware of prior to running it. If you are running an older version of PureMessage, those versions are no longer supported.

    :40665
Reply
  • 0

    Which version of PureMessage for Exchange are you running? This was a bug that was fixed in 3.1.1 and higher, so if you are running an older version and you able to upgrade, that would be the best course of action.

    Otherwise, do contact one of our support engineers since we do have a script that's a temporary workaround for 3.1.0 -- there are certain conditions you need to be aware of prior to running it. If you are running an older version of PureMessage, those versions are no longer supported.

    :40665
Children
No Data
Unfiltered HTML