Question

Error Launching Business Process After Upgrading Workflow from 9.2 to 9.2.1

Business Processes Workflow

Updated June 12, 2015

asked on May 20, 2015

I was starting business processes from the 9.2.1 client against the 9.2.0 Workflow with no problems. I then upgraded Workflow to the latest 9.2.1 patch and I can no longer stat business processes from the client. I now receive this message:

The Workflow configuration shows that everything is completed. In the Workflow Configuration I then tried to test the 2 Workflow Web Services url's. The Web Workflow URL tested fine but the Web Application Directory URL came back with this error:

It then copied the URL into a chrome tab and received this error:

The only change I made to the system was to install the Workflow 9.2.1 patch. I've restarted IIS, rebooted the server, and even ran a repair with the Workflow 9.2.1 patch. Has anyone run into this issue before?

0 0

Answers

APPROVED ANSWER

replied on June 3, 2015 • Show version history

KB article detailing the steps to fix it: https://support.laserfiche.com/KB/1013650

Edit 6/12/2015:

A fix has been released consisting of a whole new installation of Workflow 9.2.1. You can download it from the Support site. The Avante and Rio installations have been updated as well.

Unfortunately, it requires uninstalling the existing version and reinstalling the new one.

If you've already edited the config file to update the value, you don't have to use the newer build, though it is recommended for the fix to the Find Entry/Entries and Search Repository activities detailed in the release notes.

The release notes have been updated to reflect this change.

0 0

SELECTED ANSWER

replied on May 28, 2015 • Show version history

Beau, thanks for helping us track it down. It is the issue I mentioned before and it looks like sometimes we have an issue updating the web.config file on upgrades. If you look in it, there should be a section that looks like this:

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="3.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

The new version is 3.0.0.1. It's fine in the config file we install for new installs, but it does not update the existing one during upgrades.

If you make the change and save it, it should clear out the issue:

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion="3.0.0.1" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

1 0

replied on June 2, 2015

Glad it is working for the new installs. I will try it next time I have a new customer and if I get a moment, I'll try the suggestions for the upgrade. I appreciate your assistance on this.

0 0

Replies

replied on May 20, 2015

I think you're running into the issue mentioned in this post: http://blogs.msdn.com/b/webdev/archive/2014/10/16/microsoft-asp-net-mvc-security-update-broke-my-build.aspx

Can you check if you have a System.Web.MVC in C:\Windows\Microsoft.NET\assembly and what version it is?

0 0

replied on May 22, 2015 • Show version history

The update has been installed at 2 other customers: 1 it worked fine and the other now has this same issue. There is no System.Web.MVC within the Assembly folder you mentioned or any of it's sub-folders. Additionally, I looked in another customer's Assembly folder that was still on WF 9.2 and they didn't have that dll either. Shouldn't this be pulling the System.Web.Mvc from the \webLaserfiche.Workflow.Web\bin forlder? If so, it is in there and set to version 3.0.0.0.

0 0

replied on May 26, 2015

I ended up having to uninstall Workflow 9.2.1 and reinstall Workflow 9.2.0 on all 3 customers I had it installed on due to Business Processes failing to start based on an start rules, including created/changed/moved. I attempted to troubleshoot with support for a few hours but these are live environments and it was imperative to get them back up.

0 0

You are not allowed to follow up in this post.

Question

Question

Error Launching Business Process After Upgrading Workflow from 9.2 to 9.2.1

Answers

Replies

Sign in to reply to this post.