Error Loading Workflow Could Not Deserialize Object
to the needed assembly using a type provider for your workflowb) check the xml itself of your workflow: the namespace of the item that couldnt be deserialized is possibly incomplete. It needs to be a fully qualified namespace. And this is where the editor screws up a little if it's not in the GAC.For example, the editor has a tendency to create only:xmlns:ns0="clr-namespace:Company.Lib.Activitiesbut it should create xmlns:ns0="clr-namespace:Company.Lib.Activities;Assembly=Company.Lib.Activities, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"(it's missing the assembly qualifier in the namespace declaration, wich you need to resolve the activity). Not specifying version, culture and publickeytoken works just the same.With these two tips you can generally resolve the 'Could not deserialize object'-errors. Posted by Kurt at 6:33 PM Labels: .NET, declarative workflow, exception, namespace, workflow foundation, xaml 1 comment: Infowise Solutions said... It happened to me when I left the DLL file in the bin folder, it caused the XOML to try to load the DLL without the public key token, it obviously was not found. Just removed the DLL from bin and recycled the app pool.Vladi Gubler September 5, 2011 at 9:15 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) It's a Codething Blog Archive ► 2010 (1) ► February (1) ► 2009 (1) ► May (1) ▼ 2008 (18) ► December (1) ► November (2) ► August (3) ▼ July (10) 70-504 passed Grab that icon with .NET Embedded resources and clean folder structure - ye... //You do not need to understand this Electronic flyswatter: The Art of Debugging Division by Cucumber? Beauty is only GUIdeep XmlUrlResolver: a free stream to almost anything Declarative workflows: Could not deserialize objec... Dinner's ready, I already filled the FoxPro table!... ► June (2) Contributors Dirk Kurt
as showed below. How ever, when I try to publish the workflow again,the error "Could not deserialize object. The type 'EFSPWFActivities.updateItemsByCAML' could not be resolved." popped up. I rebooted the whole SharePoint server. But the same problem is still there. Interesting. So I checked "features" folder, web.config file, GAC, workflow action files, SharePoint log, windows log, etc. Everything is OK. Hours of Googling brought mehere. This is something totally http://itsacodething.blogspot.com/2008/07/declarative-workflows-could-not.html new to me. I was surprised that SharePoint designer get (or create) the proxy dll files locally for workflow activities. After deleting all files in "%System Drive%\Documents and Settings\%user%\Local Settings\Application Data\Microsoft\WebSiteCache", then rebooted SharePoint designer, the workflow back to "normal". I got the error below, which is what I expected. So http://fangdahai.blogspot.com/2011/05/could-not-deserialize-object-from.html just need to delete that action, and then recreate it. Posted by Eric Fang at 9:29 PM Reactions: Labels: SharePoint 2010 1 comment: unknownexception.ruJune 1, 2011 at 3:35 PMAwesome! Thank you, it help me.> So I checked "features" folder, web.config > file, GAC, workflow action files, SharePoint > log, windows log, etc. Everything is OK.lol. That's just SharePoint.ReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me Eric Fang Sydney, NSW, Australia SharePoint DevOps at Uniting; Work on visual studio from 1996; Work on MS Sql server from 1998; Work on SharePoint from 2007; Open source projects: Web parts: http://efspwebparts.codeplex.com Workflow timer: http://efworkflowtimer.codeplex.com Workflow activities: http://efspwfactivities.codeplex.com File Migrating: http://spfilemigrating.codeplex.com SharePoint reminder: http://efsimplereminder.codeplex.com User authentication against AD: http://userauth.codeplex.com Convert text to GIF: http://converttexttopic.codeplex.com Inspecting unique permissions: https://efinspectuniqueperm.codeplex.com Site collection management (2010): https://spsiteadmin2010.codeplex.com Site collection management (2013): https://spsiteadmin2013.codeplex.com View my complete profile Simple template. Powered by Blogger.
to SharePoint 2013. The application had several custom http://www.sharepointnadeem.com/2014/04/sharepoint-2013-could-not-deserialize.html solutions which included components like content types, web parts, event receivers, timer jobs, workflows etc. I upgradedand deployed thesecomponentsso that they were http://www.sharepointsiren.com/2014/07/getting-useful-sharepoint-designer.html compatible with SharePoint 2013. So, all was set. However, when I tried to open the workflows associated with the lists in error loading SharePoint designer, I encountered the following error: Could not deserialize object. The type could not be resolved. I checked the ULS logs and found the following entry: The type or namespace name 'AssemblyName' could not be found (are you missing a using error loading workflow directive or an assembly reference?)". at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.LoadXomlAssembly(SPWorkflowAssociation association, SPWeb web) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.LoadDeclarativeAssembly(SPWorkflowAssociation association, Boolean fallback) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.CreateInstance(SPWorkflow workflow) at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut) at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow workflo... It turned out that there were some custom workflow activities in the projects. The entries needed to be added in the web.config file.For SharePoint 2010 custom activities to work in SharePoint 2013, the "authorizedType" node needs to be defined in a new sub-section "targetFx" under the "authorizedTypes" section. Tweet It Like It Google+ Linkedin Pin it Stumble Newer Post Older Post Home SharePoint Tools and Reports SharePoint White Papers SharePoint Ads Do you want to show high paying SharePoint ads on your site? Signup here at SharePointAds.com! +
may or may not know about a useful solution on CodePlex called "Useful SharePoint Designer Custom Workflow Activities". This WSP Solution has several pre-built workflow activities to extend SharePoint Designer including "Send Email with HTTP File Attachment", "Start Another Workflow", just to name a few. The solution, which was built for SharePoint 2010, includes a nifty Setup file that adds and deploys the feature for you. You may notice, however, that when you migrate to SharePoint 2013 you receive the following error on your workflows which use these extended activities: "The type or namespace name 'DP' could not be found (are you missing a using directive or an assembly reference)." Additionally, if you try to run the Setup file and install this Solution on a SharePoint 2013 Environment you will throw an error. Good news is there is a way around this. Bad news is, it requires editing the Web.Config and running some Powershell. Here's the Solution: First, to get the Solution deployed, download the WSP from Codeplex (https://spdactivities.codeplex.com/) and save to your C drive (or wherever you want to save it). Now do the following steps: 1. Right Click Powershell and Run As Administrator 2. Type "Add-PSSnapin Microsoft.SharePoint.Powershell -EA 0". Enter. 3. Type "Add-SPSolution -LiteralPath c:\dp.sharepoint.workflow.wsp". Enter. 4. Type "Install-SPSolution -Identity dp.sharepoint.workflow.wsp -AllWebApplications -GACDeployment -CompatibilityLevel 15". Enter This will deploy the feature for you. Now we have to edit the Web.Config to avoid the missing assembly reference error. 1. Go to c:\inetpub\wwwroot\wss\VirtualDirectories\80 2. Locate the web.config file an open in Notepad or other editor of choice 3. Find the section and paste the following lines within it: " 4. Find the section and place the following lines right below the line: " 5. Save and Close the web.config file. You might also want to reboot the pc. Sometimes it takes a reboot for the changes to take effect. The Extended Workflow Activities should now work in your SharePoint 2013 Environment. Posted by April Dunnam at 2:28 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Workflow 7 comments: Wole OdeleyeApril 15, 2015 at 6:30 AMhello good day,Thanks for this. im having difficulty using your steps. I downloaded a wsp file called customworkflowactivitiesproject.wsp which contains all the workflow actions in dp.sharepoint.workflo