Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 0 subscribers
  • Views 23660 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

The MSI terminated unexpectedly.

ptex

I have been trying to install the Sophos Enterprise Console for about three weeks now. I have tried different versions of windows servers and different user accounts. But still get a The MSI terminated unexpectedly.

One log said I had said this 

6/25/2015 9:49:22 AM, INFO : About to install Sum.msi

6/25/2015 9:49:39 AM, INFO : Processing INSTALLMESSAGE_ERROR or INSTALLMESSAGE_FATALEXIT message from MSI

6/25/2015 9:49:39 AM, INFO : Deactivate state: Installing

6/25/2015 9:49:39 AM, INFO : Activate state: Failing

6/25/2015 9:49:39 AM, INFO : Installation of Sum.msi failed with error code: 1603

6/25/2015 9:49:39 AM, INFO : Ended installing Sum.msi

6/25/2015 9:49:41 AM, INFO : Installation failed with error code: 1603

6/25/2015 9:49:41 AM, INFO : Deactivate state: Failing

6/25/2015 9:49:41 AM, INFO : Activate state: Failed

MSI (s) (38:D4) [09:49:39:897]: Product: Sophos Update Manager -- Installation cannot continue. TOM is not a valid domain name.

We do have a single labeled domain "tom" will that prevent us form using the software. Tech support is not very responsive or good at this so now Im here.

:57808


This thread was automatically locked due to age.
  • 0

    I just spun up a win 8 machine to see if it wll install there.

    :57811
  • 0

    Ok that failed with the same error...

    :57815
  • 0

    Hello ptext,

    there are two (not counting yours) threads mentioning this particular error. Neither has, as far as I can see, a solution other than using local accounts.

    One post mentions an environmental issue - this might sound as an excuse. But I guess that the CustomAction generally works (or nobody is using domain accounts). From what I could glean it tries to "find" the domain in AD (which could be a forest, so an appropriate method is used). Seems that certain peculiarities in an AD setup can cause this check to fail.

    Just curious - does the installer accept an FQDN and if, what happens then?

    Christian

    :57817
  • 0

    My FQDN is "TOM" which is a single labled domain. I tried a local account and it failed also.

    :57824
  • 0
    Hello ptex,

    failed ... But with a different message? It should recognize the computername ...

    Christian
    :57826
  • 0

    I get this.

    createAccessToken: LogonUser failed
    ----- [outer exception] -----
    -- error: 0x8000FFFF (Catastrophic failure)
    -- facility: Generic (System)
    -- source: struct ISMT_CoreServices

    at __thiscall bl::CReusingManagementServiceClientBroker::Pointers::Pointers(struct ISMT_CoreServices2 *,class ATL::CComBSTR)
    at class ATL::CComPtr<struct IDispatch> __thiscall bl::CReusingManagementServiceClientBroker::logIn(const struct util::UserName &,class Loki::SmartPtr<class bl::SubEstate,class Loki::RefCountedMTAdj<class Loki::ClassLevelLockable>::RefCountedMT,struct Loki::DisallowConversion,struct util::NoDereferenceNull,class Loki::DefaultSPStorage>,const wchar_t *,class bl::UIControllerBase &)
    at int __cdecl Run(int,class bl::CommandLine,enum bl::ConsoleType::Type)
    at int __stdcall wWinMain(struct HINSTANCE__ *,struct HINSTANCE__ *,wchar_t *,int)

    :57865
  • 0

    Hello ptex,

    so the install did complete (as this message is usually seen when you try to start the console)? A quite similar error is mentioned in Management server connection failed.

    Christian

    :57866
Unfiltered HTML