I had to build a fairly complex workflow not long ago. The workflow was built in SharePoint Designer 2013 and had a lot of moving parts to it. So many, that when I went to publish it I received the following error message: “Microsoft.Workflow.Client.ActivityValidationException: Workflow XAML failed validation due to the following errors: Activity “SomeXActivity” has 65 arguments, which exceeds the maximum number of arguments per activity (50).” This error message is actually telling us that our workflow has too many variables within it. Basically, this is happening because when the workflow is running the Workflow Manager has to manage more 58 (in my case) variables. Workflow Manager only allows there to be 50 variables in the workflow… by default.
I recently had a need to read data from an xml configuration file that was stored within a SharePoint library. To make things easier I of course went to Google (or Bing) and checked to see if someone else had yet blogged this. Couldn’t find anything, so in order to help out someone else that may need to do the same at some point, I wrote up a quick little blog. Note: this will only work for on-premises versions of SharePoint. I’ll update with a SharePoint Online version in the future. I’ll also write up how to add and delete contents in a future post as well.
Ugh, patching servers. Yet another reason to move to SharePoint Online. I recently started another patching process as the servers were getting out of date and needed to have the environments upgraded. So while doing one server in particular I ran into a snag where the installer wouldn’t even run past the detection point. It simply kicked off and immediately returned the error “An Error Occurred While Running Detection”
I am going to go over the different steps I took to resolve this issue. I am even going to list the ones that should have worked but didn’t in case they will work for you.
I have been working with SharePoint for a long time. An error was encountered not long ago that I have never seen when patching a SharePoint server (and unfortunately I have seen a lot of errors over the years). While running the configuration manager I received the following error:
“An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Invalid object name ‘Webs’.”
The error of course was really nice and pointed me to the log file to get more information. Opening up the log file and searching for ERR (put space at the end to have a better chance of finding an error entry instead of other words containing those letters) I was expecting loads of information to be made available to me so I could easily fix this problem. I really should have known better as I received the following:
At no point in the logs did it tell me where this problem was occurring. So where do we go from here?
Well let’s dig into it shall we?