Sunday, December 20, 2009
However I managed to complete the wizard by removing the two allowInsecureTransport="true" sentences (remember not to remove the closing tag :)) from the client.config found at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile" thanks to a tip from http://www.mcpblog.net/Lists/Posts/Post.aspx?List=8f2497f6%2De77b%2D4e70%2D8400%2De020b292165c&ID=61. Note that you don't have to uninstall SharePoint, only remove the two lines.
Wednesday, March 11, 2009
Monday, March 9, 2009
.NET Runtime version 2.0.50727.3068 - Fatal Execution Engine Error. The error assumed problems with the dotnet framework, but repairing the framework and applying hot fixes didn't solve the issue. And the strange thing was that it was only when adding new item it happened, where as the workflow ran perfectly when updating items. The major difference was that the item adding was triggered from an eventhandler and therefore ran under the System account, but item updating occurred when a user changed the document. I also discovered that part of the workflow ran, before it died, so I put in excessive logging and ended up at a SPWeb.Dispose line. Once I commented out these lines the error disappeared.
// Disposing here will cause workflow to fail
Friday, February 20, 2009
Wednesday, February 11, 2009
I use the same logging feature and logging place for all of our workflows and our one and only Construction Kit Eventhandler (more on that another day). It's fairly simple, but functionally enough to keep me going.
So in the terms of C#:
- Make two global variables
public int i = 0;
StringBuilder MyStringBuilder = new StringBuilder();
- Create two functions
public void AddToLog(string msg)
MyStringBuilder.AppendLine(DateTime.Now.ToLongTimeString() + ":" + i.ToString() + "=" + msg);
public void WriteLog()
AddToLog("Log ended at i = " + i.ToString());
SPList SetupList = web2.Lists["Logs"]; //use global SPWeb here or hardcode
SPListItem myItem = SetupList.Items.Add();
myItem["Title"] = myContentType;
myItem["Log"] = MyStringBuilder;
catch (Exception Ex)
//Even logging can fail so you may want to take some action here
- In your code place a code counter and code logging like this:
i = 1;
myUrl = workflowProperties.WebUrl.ToString();
AddToLog(" Url: " + myUrl);
The code counter 'i' gives you the option of pin pointing exactly at which line of code the error occurred.
- At the end of your code execution and at your global error handling code ensure to get the log written:
The Logs list should contain two columns, 'Title' as Single line of text and 'Log' as Multiple lines of text (plain text).
Now you can hardcode your logging destination into the WriteLog function or you can setup a global SPWeb object (remember to dispose it at the end of the code execution) like I do. My code look something like this:
string myUrl = workflowProperties.WebUrl.ToString();
int startcmd = myUrl.IndexOf("//");
int startval = myUrl.IndexOf("/", startcmd + 2);
if (startval == -1) startval = myUrl.Length;
SPSite objSite = new SPSite(myUrl.Substring(0, startval).ToLower().Replace("corporate", "collaboration") + "/SubFolder/Settings");
web2 = objSite.OpenWeb();
The .Replace("corporate", "collaboration") trick is about having two different webs served by the same code, but only having one place to host the logging, e.g. at http://collaboration/SubFolder/Settings/Logs
Obviously our logging code also deals with log archiving, success or failiure logging as well as notification of sys admins, but for the sake of simplicity this is the starting point.
Here's a simple trick to display the info.
- On your form find a suitable place to add a textbox (I place mine at the bottom, right corner)
- In the new textbox property, click the Fx button and insert the following in the formula box:
concat(substring-before(substring-after(processing-instruction()[local-name(.) = "mso-infoPathSolution"]; 'href="'); '"'); " template with form version "; substring-before(substring-after(processing-instruction()[local-name(.) = "mso-infoPathSolution"]; 'solutionVersion="'); '"'))
- Now you can format the textbox with text color, size (use 'auto' as width) and position.
I found parts of this somewhere on the net, so don't blame me if it works :-)
Had an InfoPath form, published to SharePoint, needed to add some new fields, created the matching Site Columns, promoted the fields to the new columns, republished - everything looked good on our TEST server and then I did the same thing in our PROD environment: NoGo.
Yes, the form was published ok. The resulting xml documents had the changes, but the SharePoint Site Columns didn't reflect the changes. I searched logs, checked for misspells, googled for a day - nothing! It all looked correct, but it didn't work. (Actually not quite correct cause the columns where now properties of the ListItem and therefore didn't belong to the document).
Finally I found a fellow blogger that in turn had found some other bloggers and to make it short, here's the link: http://arichterwork.blogspot.com/2008/03/infopath-property-promotion-woes.html
All credit goes to these guys, but let me just sumerize the workaround (it's not a solution, nor an explanation):
- Using Central Admin, Applications, InfoPath, you need to deactivate the faulting form from all of the Site Collections it has been activated on.
- While deactivated, upload a new version of the form.
- Reactivate the form to the Site Collections where it is needed.
This made my InfoPath fields or properties work and I got the reflecting values on my SharePoint columns.
It looks like this bug occurs when you have republished your InfoPath form several time, but I really hope it will be fixed soon.
Sunday, January 18, 2009
I start by giving a short introduction to myself. I'm male and married, live in Denmark, work as a IT guy @ LEGO. I've worked a lot with automated deployment, SMS, WinPE and stuff like that, but recently I switched to being a web developer. So now, it's SharePoint, workflows, eventhandler and C#. I regulary attend conferences like TechEd, where I walk around and handout small LEGO gifts.
My wife is a landscaper and recently we got a visit from a lady from the Danish Garden society. They would like to invite their members to come for a tour in our (read: my wife's) garden for inspiration. So if you're in the neigbourhood around mid summer...