in

Dot Net Mafia

Group site for developer blogs dealing with (usually) .NET, SharePoint 2013, SharePoint 2010, Office 365, SharePoint Online, and other Microsoft products, as well as some discussion of general programming related concepts.

This Blog

Syndication

Archives

Corey Roth [MVP]

A SharePoint MVP bringing you the latest time saving tips for SharePoint 2013, Office 365 / SharePoint Online and Visual Studio 2013.

Watch your version numbers with Metalogix Migration Manager for SharePoint

I was working with a client recently who had purchased Metalogix Migration Manager for SharePoint and I came across an issue that confused me for a minute.  I installed the Metalogix SharePoint Extensions Web Services on a few farms.  However, in the middle of this process a new version of the tool came out and I didn’t realize that some of the farms were running one version while the other farms were running a new version.  I could connect to one farm just fine.  However, when trying to connecting to the other farm (that had the newer version), I received a 404 error. 

In my round of troubleshooting, I tried reinstalling and redeploying the solution package but to no avail.  It wasn’t until I dug deep into the documentation that I realized that the version number was included in the path to the web service itself.  It was then I realized that the version number of all web service extensions as well as the Migration Manager itself all have to be the same.  If you are using this tool and run into a 404 error, be sure and check those version numbers.

Note: By writing this, I am not endorsing one particular SharePoint migration product over another.  I work with all of them.  It’s simply the tool being used on this migration.  That means I don’t need any of Metalogix’s competitors calling or E-mailing me this afternoon.  That means you Axceler and AvePoint. :)

Comments

 

Stephen Cawood said:

Hi Corey, this is no longer the case. In the latest releases of the Metalogix migration products, each one can be using a different version of the extensions service. However, they will also share when they can.

We realize with our new pricing that more of our customers will be using multiply products, so we addressed the issue you raised.

February 26, 2012 9:20 PM
 

CoreyRoth said:

Hi Steven.  I thought I had the latest version.  5.0.0.20 I believe.  In this case I was connecting to a server running 5.0.0.15 and it gave me a 404.  Is there a newer version? I thought I had the latest since I downloaded it this week.

February 26, 2012 11:29 PM
 

Stephen Cawood said:

Ah, I see what you're getting at. Thanks for the clarification. My previous statement was correct, but I think you're talking about the case where you upgrade the client, but there's a new version of the service and that new service hasn't been installed. Unfortunately, there's nothing we can do about that. We need to update the service from time to time.

Just to be clear to your readers, the service is only required for certain features. Anything that can be done through the native web services or CSOM, we don't require our extensions service.

February 27, 2012 12:33 AM

Leave a Comment

(required)  
(optional)
(required)  
Add

About CoreyRoth

Corey Roth is an Applications Architect at Infusion specializing in ECM and Search.
2012 dotnetmafia.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems