System.IO.FileNotFoundException: Could not load file or assembly 'Symantec.Platform.AltirisAgent' or one of its dependencies

Products

• Workflow Solution

Issue/Introduction

When running a workflow the following error is thrown;

Error, date , System.IO.FileNotFoundException: Could not load file or assembly 'Symantec.Platform.AltirisAgent' or one of its dependencies. The system cannot find the file specified.
File name: 'Symantec.Platform.AltirisAgent'
   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at LogicBase.Core.AbstractOrchestrationProject.InitialResourceLoad()
   at LogicBase.Core.AbstractOrchestrationProject.GetDynamicAssemblies()
   at LogicBase.Core.AbstractOrchestrationProject.GetComponentModelPrivate(Model model, Type componentModelType)
   at LogicBase.Core.Models.Monitoring.MonitoringExecutionEngine..ctor(FileInfo info)
 
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Cause

This error has been seen, when publishing a version 6.5 workflow project to a 6.0 server.
The environment this was seen in, was where the development environment and designer was version 6.5 and the actual production workflow server was installed as version 6.0.

This would be expected in the same or very similar fashion when the version between design/development and production of workflow is different.

Resolution

This particular issue was solved by (re) installing the Workflow server component as version 6.5 matching the development and designer environments version.

NOTE; Best practice is to keep all versions of Workflow the same to avoid amongst other things assembly issues like this.

Applies To
Workflow server 6.0
Workflow designer 6.5