Why are Multiple Processes Failing with a 7-zip error?

Connor M.

Within Datawatch Automator we have multiple Processes that are failing with the following error:

07-16-2021 09:02:50	Created.
+	07-16-2021 09:02:51	Automator process failed: System.TypeInitializationException: The type initializer for 'Datawatch.Common.Archiver.ArchiveEngine.ArchiveEngine' threw an exception. ---> SevenZip.SevenZipLibraryException: Can not load 7-zip library or internal COM error! Message: can not change the library path because the file "SevenZip\7z-x86.dll" does not exist. at SevenZip.SevenZipLibraryManager.SetLibraryPath(String libraryPath) at SevenZip.SevenZipBase.SetLibraryPath(String libraryPath) at Datawatch.Common.Archiver.ArchiveEngine.ArchiveEngine..cctor() --- End of inner exception stack trace --- at Datawatch.Common.Archiver.ArchiveEngine.ArchiveEngine.IsArchivePath(String path) at Datawatch.Services.DataPump.Processing.Helpers.WildcardExpander.ExpandWildcards(IList`1 inputItems, IList`1& wildcardInputInfos, IList`1& tempInputPathes, CredentialSet credentials) at Datawatch.Services.DataPump.Processing.Helpers.WildcardExpander.ExpandWildcards(PumpProjectFile pumpProjectFile) at Datawatch.Services.DataPump.Processing.Helpers.ProjectinItializer.InitProject(PumpProjectFile pumpProjectFile, PumpJob pumpJob, PumpManifestSerialized manifestSerialized, Boolean ignoreInputsFromFile) at Datawatch.Services.DataPump.Processing.Helpers.ProjectinItializer.InitProjects(PumpJob pumpJob, PumpManifestSerialized manifestSerialized) at Datawatch.Services.DataPump.Processing.Services.PumpLocationService.ExecuteTaskProcessing(PumpTask pumpTask, PumpJob mainPumpJob, PumpManifestSerialized manifestSerialized) at Datawatch.Services.DataPump.Processing.Services.PumpLocationService.RunPump(PumpTask pumpTask, PumpTaskStatus pumpTaskStatus, PumpJob mainPumpJob, PumpManifestSerialized manifestSerialized).
+	07-16-2021 09:02:51	Failed: The type initializer for 'Datawatch.Common.Archiver.ArchiveEngine.ArchiveEngine' threw an exception.System.TypeInitializationException: The type initializer for 'Datawatch.Common.Archiver.ArchiveEngine.ArchiveEngine' threw an exception. ---> SevenZip.SevenZipLibraryException: Can not load 7-zip library or internal COM error! Message: can not change the library path because the file "SevenZip\7z-x86.dll" does not exist. at SevenZip.SevenZipLibraryManager.SetLibraryPath(String libraryPath) at SevenZip.SevenZipBase.SetLibraryPath(String libraryPath) at Datawatch.Common.Archiver.ArchiveEngine.ArchiveEngine..cctor() --- End of inner exception stack trace --- at Datawatch.Common.Archiver.ArchiveEngine.ArchiveEngine.IsArchivePath(String path) at Datawatch.Services.DataPump.Processing.Helpers.WildcardExpander.ExpandWildcards(IList`1 inputItems, IList`1& wildcardInputInfos, IList`1& tempInputPathes, CredentialSet credentials) at Datawatch.Services.DataPump.Processing.Helpers.WildcardExpander.ExpandWildcards(PumpProjectFile pumpProjectFile) at Datawatch.Services.DataPump.Processing.Helpers.ProjectinItializer.InitProject(PumpProjectFile pumpProjectFile, PumpJob pumpJob, PumpManifestSerialized manifestSerialized, Boolean ignoreInputsFromFile) at Datawatch.Services.DataPump.Processing.Helpers.ProjectinItializer.InitProjects(PumpJob pumpJob, PumpManifestSerialized manifestSerialized) at Datawatch.Services.DataPump.Processing.Services.PumpLocationService.ExecuteTaskProcessing(PumpTask pumpTask, PumpJob mainPumpJob, PumpManifestSerialized manifestSerialized) at Datawatch.Services.DataPump.Processing.Services.PumpLocationService.RunPump(PumpTask pumpTask, PumpTaskStatus pumpTaskStatus, PumpJob mainPumpJob, PumpManifestSerialized manifestSerialized)
+	07-16-2021 09:02:51	Distribution started.
+	07-16-2021 09:02:53	Distribution completed.

 

This has been ongoing for around a year. I have worked with support and so far no solution. This is happening for multiple processes that have different inputs. Some are just excel spreadsheets while others are pervasive SQL or another SQL database. At one point restarting services would temporarily resolve this, but that hasn't been the case over the last week. This software has been moved to a new server and the issue persists. Any help or recommendations would be greatly appreciated!