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

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.
  • Hello,

    The initial console error (0x80040154) normally points to an error with the Puremessage service being unable to start, so it would be handy to verify what state the service is in. What may have happened is that one or more of the DLL files within the Puremessage bin folder was no longer registered, so it would be a matter of running regsvr32 on all the DLLs (which could be scripted; please contact support for assistance) to ensure the service has reregistered.

    For the reporting data error, are you seeing a buildup of .xml.bad files in C:\Program Files\Sophos\PureMessage\ReportsPending\ at all? (This assumes the default installation path of C:\Program Files\Sophos\PureMessage is used.) There is a known defect pertaining to improperly encoded characters within XML files that build up, complicating communication with the database. There is a workaround available that one of our frontline support engineers can help out if you do see that, which focuses on removing those files via script.

    Otherwise, checking our internal CRM, it looks like you had been in communication with our support personnel, though your email address no longer appears to work.

    Best regards.

    :18309
  • I sure could use this script as I am getting these warning messages in my eventlog all the time, and I have 172,000 items that are .xml.bad files that I would like to remove properly.

    :40635
  • 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
  • PureMessage for Exchange 3.1.0

    I am afraid to upgrade to 3.1.2 as the other issue we have seen on occasion is the "PmE12transport" service causing our Exchange Transport service to halt, and then it will pick up again.

    So, there is a script? How do I contact one of your support engineers?

    :40669
  • Yes, there's a VBS script. Email support@sophos.com or use the phone number for your country listed on http://www.sophos.com/en-us/support/contact-support/contact-information.aspx to reach our staff 24/7.

    :40671
  • I had the same problem, same error, on an inital install of the product on my exchange server. I had to manually register the following dlls from the "\Program Files (x86)\Sophos\AutoUpdate" directory. Attached is a list of the DLLs that I found and registered. I was then able to proceed past the error and resume the setup.

    :45917