Workflow Soluiton

We recently built a new workflow server and are in the process of migrating our projects over. Most of my projects have SD ties. When i attempt to open those i get an error saying that the SD componnents DLL(SD.Components.dll) was unable to load. I tried removing the SD dlls (SD.Components.dll, SD.data.dll, SD.dataServices.NSreports, SD.DatatypesCore.dll, SD.WorkflowExtensions.dll) from the project, packaging it on the old server, moving the package to the new server, unpackaging the project, opening it, and readding the SD libraries, but it still doesnt work. I really dont want to have to recreate these projects.






When I try to add the servicedesk dlls, i get the following...

Clicking on details gets you...

"   System.Exception: Error adding library. Details below ---> System.Exception: could not load assembly SD.Components, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null ---> System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
   at System.Reflection.Module._GetTypesInternal(StackCrawlMark& stackMark)
   at System.Reflection.Assembly.GetTypes()
   at LogicBase.Core.AbstractOrchestrationProject.CheckDuplicateTypes()
   --- End of inner exception stack trace ---
   at LogicBase.Core.AbstractOrchestrationProject.CheckDuplicateTypes()
   at LogicBase.Core.AbstractOrchestrationProject.AddResourceToAssemblies(String filePath)
   at LogicBase.Core.AbstractOrchestrationProject.AddResource(String originalFilePath, Boolean isLib, Boolean copyLocal, String relativePath)
   at LogicBase.Tool.UI.AddLibraryForm.AddLocalLibraries(Dictionary`2 existingLibraryNames, List`1 addedLibs)
   --- End of inner exception stack trace ---
   at LogicBase.Tool.UI.AddLibraryForm.AddLocalLibraries(Dictionary`2 existingLibraryNames, List`1 addedLibs)
   at LogicBase.Tool.UI.AddLibraryForm.btnOK_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)"

This error is also received when I create a brand new project and try to import the SD.Components.dll

We had a similar issue (but not exactly the same) in two cases:

1) Integration libraries compiled on SW 7.1 SP1 didn't load with project on SW 7.1 SP2. We had to copy the sources of integration projects to SW 7.1 SP2 and recompile them to build new DLL libraries. The original libraries from SP1 has been replaced by these new one in workflow projects and then the projects was able to open on SP2.

2) We had our own component libraries (written directly in C#) working on SP1 and it occured that the changes made in SP2 caused them incompatibile. We had to correct some code and rebuild them.

For clarification, we are upgrading from Workflow 7 to WF 7.1.1460.1974

Check the dependencies (referenced assemblies) of this SD.Components.dll library to be sure all required assemblies are present on workflow server.

Check GAC on workflow server to verify if it doesn't contains two different versions of the base workflow libraries: LogicBase.Core.dll, LogicBase.Framework.dll and Symantec.SymQ.dll. It is possible that the project has already loaded the newer version when the SD library tries to load the older one.

Although it does not look like a license issue, is SD licensed on the new server? 

Symantec was called. According to them, you can't develop or edit projects designed to work with SD 7.0 in WF 7.1. GOTCHA!!

I'm just going to move my WF 7.0 projects with SD ties to the SD server and be done with it.