+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Error after 3.6SP1 to 3.7SP4 Upgrade

Error after 3.6SP1 to 3.7SP4 Upgrade

6 posts, 0 answered
  1. Isaac
    Isaac avatar
    63 posts
    Registered:
    01 Dec 2008
    27 Jan 2011
    Link to this post
    After the upgrade our page workflow appears to be broken.  Very rarely the workflow goes through and the page is ok, but most of the time we get the following error:

    An error occurred in the application:
    More than one runtime service exists of type "CmsWorkflowService".
    Stack Trace:
    at
    Telerik.Workflow.WorkflowRuntime.GetService(Type serviceType) at
    Telerik.Workflow.CallExternalMethodActivity.Execute(WorkflowRuntime runtime) at
    Telerik.Workflow.Activity.Execute(WorkflowRuntime runtime) at
    Telerik.Workflow.EventActivity.Execute(WorkflowRuntime runtime) at
    Telerik.Workflow.Activity.ExecuteNext(WorkflowRuntime runtime) at
    Telerik.Workflow.Activity.Execute(WorkflowRuntime runtime) at
    Telerik.Workflow.EventActivity.Execute(WorkflowRuntime runtime) at
    Telerik.Workflow.WebControls.WorkflowMenu.Button_Command(Object sender, CommandEventArgs e) at
    System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e) at
    System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) at
    System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at
    System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at
    System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Also, frequently after submitting a page for approval, there will be the message "This page has been sent For Approval" but the button still says "Send For Approval" or the status will say "This page has been Approved" while the button still says "Approve"

    If I turn off workflow everything is fine.  I have deleted the serviceassembly.dll file.  Any suggestions on this would be greatly appreciated.


  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    09 Dec 2016
    27 Jan 2011
    Link to this post
    Hi Nathan,

    It looks like the project has not been upgraded properly. Could you check the project version ? Do you run the project in a web farm? Please check whether the web.config is properly merged using a merge tool and all project files that we ship with the hotfix/patch are properly replaced.
    Please check whether you have a custom code that interacts with the workflow.

    Regards,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Isaac
    Isaac avatar
    63 posts
    Registered:
    01 Dec 2008
    27 Jan 2011
    Link to this post
    Ivan,

    Thank you for the quick reply.

    The version listed in the meta tag is:
    Sitefinity 3.7.2136.240:1

    The version listed in the properties for the Telerik.Cms.dll file is: 3.7.2136.240

    The schema version listed in the sf_CmsVariables table is: 2136

    It looks like all of those agree.

    The project is not in a web farm, but I do have a machine key specified.

    I used a merge tool called SwiftCompare to check the differences in the Web.Config files.

    I have added the urlrewrites section under configsections
    I have added two additional connection strings
    I have set identity impersonate to true
    I have added a namespace for a web control we use
    I have set customerrors to on and given a defaultredirect
    I have set debug to true
    Role manager is set to true, I assume this is because it was detected in the database
    I have switched to the urlrewrite httpModule
    I have added a machineKey
    I have added the urlrewrite module under system.webServer -> modules
    I have changed the smtp settings
    I have added a urlrewrites section
    The original file has:
    <cms defaultProvider="Sitefinity" pageExtension=".aspx" disabled="true">
    While the file on the website has
    <cms defaultProvider="Sitefinity" pageExtension=".aspx" disabled="false">
    I have set allowpageworkflow to true
    I have added multiple user controls

    Those are the extent of the differences.

    In the /bin folder I have added the ajax control toolkit, several other dlls (CookComputing.XmlRpcV2.dll, Flan.Controls.dll, Koutny.WebControls.DropDownGroupableList.Net2.dll, Microsoft.Web.Services3.dll, RssToolkit.dll

    There are also two dlls from telerik in the bin folder that aren't in the 3.7 distribution: Telerik.CrawlerSitemaps.Data.dll and Telerik.CrawlerSitemaps.dll

    Every other file in the /bin folder is the same as what came with the 3.7 distribution

    I downloaded the files from here: http://www.telerik.com/downloads/productfiles/batcg/Sitefinity_3_7_2136_standard_NET40_BlankProject.zip

    For the upgrade instructions
    Step 1 - Completed
    Step 2 - Completed
    Step 3 - I looked earlier with swift compare and identified files where we made change from the default, those were: /app_browsers/browserfile.browser, /sitefinity/admin/controltemplates/editorfile.xml, global.asax, web.config
    Step 4 - Overwrite the current web.config file with the new one, added the stuff outlined above
    Step 5 - We made no changes to the PageHistory.ascx file
    Step 6 - We made no changes
    Step 7 - deleted the service assembly (although this as part of the troubleshooting post upgrade
    Step 8 - Only one project
    Step 9 - We do not have that file
    Step 10 - We do not reference the sitefinity assemblies

    Is there anything we might have missed? Could any files not overwritten by the upgrade be causing problems?

    Thank you
    -nathan
  4. Isaac
    Isaac avatar
    63 posts
    Registered:
    01 Dec 2008
    27 Jan 2011
    Link to this post
    Our test site where I followed the same upgrade procedure as the live site is not having this issue.  Could there be something strange in the database causing the problem?

    I just went through and compared the files on our test site with those on the live site, and they are identical the only difference would be in the version of IIS (7 on the test site and 6 on the live site) and the contents of the database.
  5. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    09 Dec 2016
    28 Jan 2011
    Link to this post
    Hello Nathan,

    I sent a reply to your support request. I am not able to tell you what is causing this issue if I cannot replicate it locally and debug the project.

    Kind regards,
    Ivan Dimitrov
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  6. IT
    IT avatar
    52 posts
    Registered:
    30 Sep 2008
    25 Mar 2011
    Link to this post
    For others who stumble on this thread... we had this error after upgrading from 3.7 SP1 to 3.7 SP4. We had a custom module (in app_code) that wasn't compatible with the new version. Removing it got things working again. The code needed a few changes to be made compatible.
Register for webinar
6 posts, 0 answered