Workflow not running due to missing dll with older version

Hi all,

I've just created a workflow in the SCSM 2012 R2 Authoring tool.

The workflow runs a simple powershell script.
Whenever I trigger the workflow, I get an error message saying that my workflow can't run as it is missing a needed dll:

"could not load file or assembly 'Microsoft.servicemanager.workflowauthoring.common', Version=7.0.5000"

I checked this error message and this would be due to some DLL file from the Authoring console not being present in my service manager installation, but this file is definetly there.
What the real issue is, is that the versions don't match.

The version I have present is: 7.5.3079.
The workflow seems to be looking for a much older version..

Here is a screenshot of the error message and the file which is present in the folder:http://1drv.ms/1E88P1X

Why would this be?

My SCSM Management server is 2012 R2 CU5, Authoring Console is also definetly R2..

This is the first custom workflow that I'm deploying on this installation.

Any help would be appreciated!

Thanks



August 21st, 2015 12:25pm

Hi Marat,

Thanks for your reply, but the DLL is definetly there as you can see in the screenshot that I mentioned in my opening post. The workflow seems to be thinking that it is missing, but it isn't.

I checked on all management servers, but the DLL is there on all of them..

That's what i don't understand..

Free Windows Admin Tool Kit Click here and download it now
August 22nd, 2015 2:49pm

I did do an upgrade from SP1 to R2, but nonetheless the DLL files are there

Or am I looking in the wrong location?

August 22nd, 2015 2:50pm

Oh, I'm sorry. I missed the screenshot's link. Have you tried to reboot the server?
Free Windows Admin Tool Kit Click here and download it now
August 22nd, 2015 9:58pm

Hi Marat,

When I installed the environment it had been done using the SP1 sources.
I immediatly upgraded the environment to R2.

The 2 DLL's were there, but in an older version.
When I first saw the error message, I had copied over the 2 files from the Authoring console and restarted both the Health and management services, thinking that these would reload all DLL's.

Unfortunately, this was not the case.

Rebooting the server fixed the issue, my workflow now runs

Thanks!

August 23rd, 2015 4:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics