Wednesday, October 24, 2012 0 comments

Moving a Content Database Between Farms


Below are the five basic steps needed to move a content database from one farm (F1) to another (F2.) This post assumes that you are performing the task manually, not using a migration tool.
  1. Detach the content database from F1 using theDismount-SPContentDatabase PowerShell cmdlet .
  2. Detach the content database in SSMS for F1.
  3. Move the the content database files (.mdf, .ldf, .ndf) to F2.
  4. Attach the content database in SSMS for F2.
  5. Attach the content database to F2 using the Mount-SPContentDatabase PowerShell cmdlet.
For a higher level of detail, visit
Monday, October 1, 2012 0 comments

Workflow Initiation Form Error


While creating a solution for a client, I encountered this issue. The goal was to copy and modify the out of the box (OOB) SharePoint 2010 workflow; customize it; and associate it to a content type.
The Problem
Upon completing and submitting the workflow initiation form; the form presents an error: The form cannot be submitted because of an error.
The Solution
Uninstall KB2553322, a security update for both InfoPath 2010 and SharePoint Designer 2010. I uninstalled both patches and rebooted the server. From there I was able to copy and modify the workflow, eventually submitting the workflow initiation form. Of course, before trying any of this in the client’s environment I took the time to create a VM. I tested my updates on the VM and then repeated it for the client. There have not been any subsequent issues. Hopefully Microsoft will issue an update patch in the near future.
For additional information:
Some do not seem to have the same luck that I did uninstalling the security update for InfoPath. For those people, there are several other "solutions" that have worked for other people.

  • This issue is also posted by Paul Quilty using a different approach. He resolves the issue by editing a  xoml.wconfig.xml file.
  • Yash Goley has a series of steps that one can try.
 
;