Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 18 replies
  • Subscribers 0 subscribers
  • Views 55239 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

Enterprise Console issue

zaqwsx1234

Hi,

I am trying to push through Sophos to a Windows server 2012 Standard from the enterprise console and I am getting this error:

< Error 00000067 'The MSI has failed', seen after installing, upgrading or updating Endpoint Security and Control

and this: 80070057 The installation could not be started the paramater is incorrect

Could you please assist

:56603


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

    Hello Jessica,

    We set up a share on this server that contains all set up files

    you don't have to set up a share manually although you can do - but then you should know what you are doing (no offence meant). Endpoints install (and update) from the appropriate CID in the SophosUpdate share, a SUM is installed from the (existing) SUMInstallSet share (please see Endpoint Security and Control: How to install an additional update manager for details). If you also want to use the SUM as message relay also see Configure message relay in ver 5.2.2.

    If your secondary SUM is correctly installed you should see it in the Update managers view on the console. Normally one would install the Endpoint (AV) software from a CID hosted on the secondary SUM (especially when it's also a message relay). Thus I'd first configure the additional update manager and make sure it's working and populating its SophosUpdate share.

    The 25010 error is rather general - from the screenshot it looks like starting the newly installed AutoUpdate service fails. How and where from did you install? As you've posted a screenshot I assume it was an interactive install this time. AFAIK setup.exe writes the logs to the user's %TEMP% (or a subfolder), shouldn't be too hard to locate the log(s). Perhaps a more specific error reason can be found (likely near a line containing StartSAUService).

    Christian   

    :56630
Reply
  • 0

    Hello Jessica,

    We set up a share on this server that contains all set up files

    you don't have to set up a share manually although you can do - but then you should know what you are doing (no offence meant). Endpoints install (and update) from the appropriate CID in the SophosUpdate share, a SUM is installed from the (existing) SUMInstallSet share (please see Endpoint Security and Control: How to install an additional update manager for details). If you also want to use the SUM as message relay also see Configure message relay in ver 5.2.2.

    If your secondary SUM is correctly installed you should see it in the Update managers view on the console. Normally one would install the Endpoint (AV) software from a CID hosted on the secondary SUM (especially when it's also a message relay). Thus I'd first configure the additional update manager and make sure it's working and populating its SophosUpdate share.

    The 25010 error is rather general - from the screenshot it looks like starting the newly installed AutoUpdate service fails. How and where from did you install? As you've posted a screenshot I assume it was an interactive install this time. AFAIK setup.exe writes the logs to the user's %TEMP% (or a subfolder), shouldn't be too hard to locate the log(s). Perhaps a more specific error reason can be found (likely near a line containing StartSAUService).

    Christian   

    :56630
Children
No Data
Unfiltered HTML