.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Upgrade Sharepoint 2007 Custom State Machine/Sequential workflow to SharePoint 2010

Posted By:      Posted Date: October 21, 2010    Points: 0   Category :SharePoint


What's the path for upgrading the SharePoint 2007 Custom State Machine/Sequential workflow to SharePoint 2010 when the current SharePoint 2007 environment is upgraded to SharePoint 2010 by an inplace upgrade?

What's the typical estimate time for upgrading SP2007 custom workflow to SP2010 custom workflow?  My gut says 40 to 80 hrs or even less than that, what’s your thoughts?

FYI...I tried to upgrade the SharePoint custom workflow built using visual studio 2008 in SP2007 environment to visual studio 2010 solution/project in SP2010 environment, I got the error messages to refer the following dll's

Microsoft.SharePoint.dll and Microsoft.SharePoint.WorkflowActions.dll

Even after referring the new dlls still the workflow design doesn't show up in the canvas...still work on this to fix mean while want to know the experts insights on this.

View Complete Post

More Related Resource Links

How to upgrade MOSS 2007 custom site definitions to SharePoint 2010?

I would like to know how to upgrade custom site definitions of MOSS 2007 to SharePoint 2010 in detail?

After SharePoint 2007 upgrade to SharePoint 2010 issue with custom site(s)


With our 2007 site(s) we had a custom module (we developed) to swap out the application.master with our own master page which resembled the site default.master.  This worked great.

After the upgrade, out site's main pages looked fine however when navigating to the admin type pages (settings/viewlists etc.) pages the module stopped working.

1.) I have figured out something things with respect to what is going on but am still at a loss to how best resolve.  We want the layouts/admin pages to have the same master page as the main user pages.   I have read in 2010 this is now possible.  How can I achieve this?


2.) Currently, when navigating to the sites/settings page the site is using template/layouts/layoutsv3.master as the master page.  The settings.aspx page has DynamicMasterPageFile="~masterurl/default.master" .  It was my understanding that when DynamicMasterPageFile was set to default.master it would use the master page from the site.  So, with that said I am confused why it is using layoutsv3.master

any help would be appreciated



How to upgrade MOSS 2007 custom site definitions to SharePoint 2010?

I would like to know how to upgrade custom site definitions of MOSS 2007 to SharePoint 2010 in detail?

sharepoint 2010 state machine Workflow With Association column


i create sharepoint 2010 state machine Workflow  and i need to add Association column (as in designer) is it possible to do?

and if yes could u plz tell me how??

Cannot crawl sharepoint site and mysite after database attach upgrade form sharepoint 2007 to 2010.

After database attach upgrade site and mysite from sharepoint 2007 to 2010 , I have full crawl and get "The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error. ( Error from SharePoint site: HttpStatusCode ServiceUnavailable The request failed with HTTP status 503: Service Unavailable. )" for mysite and get "Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled." for sharepoint site. The content access account for search is "db_owner" of both of site and mysite. How do I solved this problem ?

Access Denied/The workflow could not copy the item workflow error after Sharepoint 2010 upgrade

We have a sharepoint designer workflow that copies a document from one library to another on the same site.  Before the upgrade to 2007 it worked fine, but now with 2010 it gives an error and cancels the workflow when it gets to the copy list item step.   The error on the workflow page: The workflow could not copy the item. Make sure the source and destination lists have the same columns and column settings.  Access Denied   Specifically it is the "copy list item current item to documentlibrary" sharepoint designer workflow action.   I have given the system account full permissions to the library and double checked that all columns are the same in both libraries. These are the verbose trace logs:   09/01/2010 09:46:04.05 w3wp.exe (0x17C4) 0x093C SharePoint Foundation Workflow Infrastructure 72er Medium System.UnauthorizedAccessException: <nativehr>0x80070005</nativehr><nativestack></nativestack>Access denied. at Microsoft.SharePoint.SPFile.UpdateInternal(Boolean migrationSemantics, Boolean reGhost) at Microsoft.SharePoint.Workflow.SPWinOEWSSService.CommitCopyFile(Transaction txn, Object[] transData) 09/01/2010 09:46:04.05 w3wp.exe (0x17C4) 0x093C SharePoint Foundation Workflow Infrastructure 72fe High Error in commiting pending workflow batch items: Sys

Delay Activity is not working with SharePoint state machine workflow

Hello,   I have a problem with Delay Activity in Sharepoint state machine workflow. This issue is kind of common to many people but so far I haven't come accross any working solution. In one of the workflow states, I want to add a delay activity to send email notification if no action is taken after certain time. Below is what I have done:   In the targeted state: 1) add one eventDriven activity to handle the normal process (approve the item) 2) add another eventDriven activity to send the reminder email. In this eventDriven activity, I first add a delayActivity, set it to 2 minutes for test purpose. Then I add a Sharepoint SentEmail activity.   With my test, the Dealy Activity is never invoked after timeout period. What should I do to make the delay activity work in the SharePoint state machine workflow? Is there any work around if the delay activity is simply not working there?   Any suggestions are appreciated.

MOSS 2007 upgrade to Sharepoint 2010 across domains

I recently did an upgrade at a customer site. I migrated their content successfully as well as their Mysites. Their MOSS farm was situated on a domain, let's say "domain 1". Due to a merger, their domain had to change to "Domain 2". The Sharepoint 2010  farm was set up on new domain. We now need to change the existing user logins from the upgraded content db to the new domain. domain1\user to Doamin2\user.  We considered a manual process, but it is simply not a viable option. Furthermore, the migrated mysites works fine, but the problem is, the users need to login with their old login details to view the content. Which is unacceptable. The mysite content now needs to be associated with the users on the new domain. Bear in mind that the users already have logins and permissions as per the previous configuration (domain1\user) I consideredd using the stsadm migrate user command, but that could also be laborious. The other concern is the SID associated to each login. I am not sure if the -ignoresidhistory switch will help, or if this command is even usable in SP 2010. I there possibly another, more effective method to accomplish these tasks, say a Powershell script or a magic wand?   Regards,   Warren  

Upgrade from MOSS 2007 Trial to Sharepoint Server 2010

I have a client who setup MOSS 2007 Trial and are coming up on the expiration.  Instead of buying a key for MOSS 2007 they purchased Sharepoint 2010.  I'm having some problems upgrading because its the trial.  What are my options for upgrading/migrating over to Sharepoitn 2010?

Receiving Error when Trying to Develop Sharepoint 2007 Workflow using VS 2010 Pro

I have created a Windows Server 2003 Enterprise (32 bit) SP2 image configured with Sharepoint 2007 Enterprise and a trial edition of Visual Studio 2010 Professional.  All software is fully patched.  When I try to create a new Sharepoint 2007 Sequential Workflow (.NET Framework 3.5) in either C# or VB, I receive a pop-up error: Exception of type 'System.PlatformNotSupportedException' was thrown. and, when I click OK and fill in the name of the workflow and a valid Sharepoint Web URL for testing, I receive the following error: SharePoint site location entered is not valid.  The SharePoint site at <removed> could not be found.  Verify that you have typed the URL correctly.  If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application. The URL in question references the default SharePoint site on this test server and does exist.  My assumption is that the second error received is a symptom of the first.  I have looked elsewhere and seen issues related to 64bit SharePoint implementations but, this is a 32 bit installation.  Based on the VS 2010 web site, I have met all of the prerequisites for developing SharePoint 2007 workflows through VS 2010 Pro.  Does anyone have any ideas on what I might be missing or what I need to

MOSS 2007 to SharePoint Server 2010 Hybrid Upgrade Approach on Windows Server 2003 x64

There's some guidance circulating about upgrading to 2010 with a mix of In-Place and Database Attach upgrade methods. My Central Admin and SharePoint Web App are on a 64 bit server, but it's running on Windows server 2003 x64 and not on Windows Server 2008 or 2008 R2. SharePoint Team Blog says Server 2008 or 2008 R2 is required for SP2010. If I want to do the hybrid upgrade approach, is it possible to first upgrade the OS to Server 2008 R2 on the server where my Central Admin and SP Web App runs?  Or will this break MOSS 2007?

SharePoint 2007 upgrade to 2010 without UI update masterpage issue

I have a public facing site on a SharePoint 2007 farm that will be upgraded to 2010.  This site has a very customized look and feel that will not initially be updated to the 2010 UI.    I have run into one small issue with 2010's handling of legacy 2007 UIs.In SharePoint 2007,  to have a different master page for the application pages and dialog boxes we utilized an HTTP Module to switch the master page on the fly.    After migrating the SP2007 into our 2010 beta test environment the HTTP Module no longer worked properly.   I did some debugging and found out that SharePoint 2010 is returning a NULL value for MasterPageFile property on the pages in the _layouts folder.   I would have expected to see the URL pointing to the application.master page (or dialog.master).   Any ideas if this is a bug in SP2010 beta and will be fixed in RTM or is this the intended behavior.If it is the intended behavior in SP2010 how could I update my HTTP Module to allow the site to continue functioning as it did on 2007?   

SharePoint 2007 to 2010 Upgrade AND Farm Merge


Hello all,

I'm curious to see if anyone has done this.  Currently, my environment has 3 seperate SharePoint 2007 server farms.  I'm currently evaluating SharePoint 2010 and so far like what I see.  I'm wondering though what would be the steps I would need to go through to actually upgrade and then merge them all to one SharePoint 2010 farm?  The steps I can think of are the following:

1. Make sure all 2007 farms are on the lastest (or at least similar) version

2. Upgrade each farm to SharePoint 2010

3. Create new 2010 farm

4. Copy upgraded farms' site collections to NEW 2010 farm.

OR can I do this:

1. Make sure all 2007 farms are on the same version

2. Create a copy of each current SharePoint 2007 site collection that I want

3. Create NEW 2007 Farm

4. Copy content to new farm

5. Upgrade new farm to 2010


Any and all help would be greatly appreciated, thanks!


Reg: Does Custom site definition created in SharePoint 2007 works in Sharepoint 2010



If one has created a custom site definition in sharepoint 2007, Once the whole site is migrated to sharePoint 2010 will that "custom site definition" created in 2007 will work without breaking in SharePoint 2010?

If No, what has to be done to make it work on 2010.






Visual Studio 2008 Professional v.s. Standard - support SharePoint 2007 sequential workflow?


I would like to ask if VS2008 Standard edition support the project type of SharePoint2007 sequential workflow?

I have a VS2008 Professional edition and it is Ok to create SharePoint2007 sequential workflow project and deply to MOSS2007 successfully.

Is it possible in a VS2008 Standard edition?

Thanks in advance.

Problems when deploying sequential workflow with association Infopath form of sharepoint 2010 using


I’ve create a workflow project with infopath in it. And I get the error

 “Error occurred in deployment step 'Activate Features': Unable to locate the workflow's association data. To restore the association data to the workflow, restart the workflow settings wizard by selecting the workflow node in Solution Explorer and then clicking the ellipsis button (…) on one of the properties in the Properties window that has an ellipsis button.”

I'd really appreciate of any help.

Looking for guidance: Integrated SharePoint SSRS migration and upgrade from 2007 to 2010


Our existing prod farm is MOSS 07 with an integrated SSRS instance using SQL Server 2008, both on Windows Server 2003 64bit boxes. SharePoint databases are on a different SQL Server 2008 server.

I have built a new SharePoint 2010 farm on Windows Server 2008 R2 boxes, using a single SQL Server 2008 R2 Enterprise server as the backend for both SharePoint databases and Reporting Services (installed in Integrated mode). We are going to be using the database-attach method of upgrading our SharePoint farm.

Is there any specific guidance out there on exactly how to migrate/upgrade Reporting Services in this scenario? I've read through some of the MSDN content (How To: Migrate a Reporting Services Installation) but nothing seems to deal specifically with doing this when in Integrated mode with SharePoint. Our business heavily relies on SSRS reports in SharePoint and also shared and custom report subscriptions via email.

We do have a dev SharePoint 2010 farm in a similar configuration that I can test migration/upgrade steps. Thanks.

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend