Package Generation Disabled Due to CLStorage Error 0x00000003

Products

• Carbon Black App Control

Issue/Introduction

• Package Generation is disabled immediately after either
  • Uploading a new Host Package Installer
  • Enabling the relevant Shepherd Config (ex: GenerateWindowsInstaller)
• Package Generation Logs include entries similar to the following:

  CLStorage: Error publishing CL file from C:\Program Files (x86)\Bit9\Parity Server\configxml\configlist_v2.xml.egk to C:\Program Files\Bit9\Parity Server\hostpkg\configlist_v2.xml.egk. Error (0x00000003): The system cannot find the path specified.

Environment

• App Control Server: 8.11.0 or higher
• Carbon Black Agent Packages

Cause

A mismatch in the database settings and the actual App Control Server installation path exists.

Resolution

1. Log in to the application server hosting the Console as the Carbon Black Service Account.
2. Verify the current installation path for App Control Server
   • Initial default for Server 8.11.0 and higher

     C:\Program Files\Bit9\Parity Server\

   • Initial default for Server 8.10.4 and lower

     C:\Program Files (x86)\Bit9\Parity Server\

3. Run SQL Server Management Studio as the Carbon Black Service Account and execute the following query:

   USE das;
   SELECT name, value FROM dbo.shepherd_configs (NOLOCK) WHERE value LIKE '%Bit9\Parity%';
   

4. Verify each value returned matches the actual location on disk.
   • If the returned value matches, make no changes and open a case with Support.
5. If necessary, update the relevant value(s) accordingly, example:

   USE das;
   exec dbo.UpdateShepherdConfig 'hostPackagesFolder', 'C:\Program Files (x86)\Bit9\Parity Server\hostpkg\'
   
   exec dbo.UpdateShepherdConfig 'publishersFolder', 'C:\Program Files (x86)\Bit9\Parity Server\publishers\'
   
   exec dbo.UpdateShepherdConfig 'ManifestDirectory', 'C:\Program Files (x86)\Bit9\Parity Server\manifests\'
   
   exec dbo.UpdateShepherdConfig 'ArchivedEventsFolder', 'C:\Program Files (x86)\Bit9\Parity Server\archivelogs\'

6. Re-upload the relevant Agent Host Package Installer.

Additional Information

• These values are set in the database during Server installation and never should need adjustment.
• Most commonly this mismatch is caused due to an unexpected/unsupported Server migration method.
• Any Server migration should follow the proper Server migration procedure.