Endpoints fail to update after adding XML configuration or custom files to the update location (CID) Authentication failed error 00000067

  • Article ID: 118821
  • Rating:
  • 4 customers rated this article 2.5 out of 6
  • Updated: 17 Jul 2013

Note:

00000067 is a generic error code returned when a component or sub-component has failed to install. If this article does not deal with the issues you are seeing, refer to article 113312 for more general troubleshooting steps on this error.

Issue

Endpoints that have upgraded to the 10.2.4 package version (Sophos Auto Update version 2.9.0) fail to update following the addition of XML configuration and/or custom files to the CID using the ConfigCID.exe tool. 

The Sophos Console will show the following error:

Failed to install SAVXP: Package authentication failed with corresponding code 00000067

Note: The error will be reported against the component that failed to update.

The Auto Update log will show the following error:

Manifest failure for product [product name]

The Sophos Auto Update trace log shows the following error:

CheckCustomManifest: invalid package:invalid custom manifest: [BADFILE]: 3: 'C:\Program Files\Sophos\AutoUpdate\cache\savxp\cmanifest.dat'

Note: The package affected will vary depending on where the fixed configuration and/or custom files have been added, in this example it's the Sophos Anti-Virus folder 'savxp'.

First seen in

Sophos Anti-Virus for Windows 2000+ 10.2

Cause

Sophos Auto Update version 2.9.0 (and later) now performs a check that all files added to an update location are signed and included in the manifest. XML configuration and custom files must be added to the CID with version 2.0.17.0 of ConfigCID.exe or later, supplied with Sophos Update Manager 1.4.2 and later.

What To Do

Use the latest version of ConfigCID.exe (version 2.0.17.0 and above) to add custom files to a CID.

How to check the version you are using

Check you are using ConfigCID.exe version 2.0.17.0 and later:

  • Right click on the ConfigCID.exe file in use, select properties.
  • On the Details tab, check the File version field.
  • If the version is below 2.0.17.0 (Released around January 11th 2013), ensure you locate and use the latest version as described here (Under 'Locating the utility').

 
If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent

Comments