"VPP migration tool has stopped working"

Ørjan Horpestad

Vote:

I'm having some issues with the VPP migration tool. After a while the tool stops while giving this message:

"VppMigrationTool has stopped working"

Problem signature:

Problem Event Name: CLR20r3

Problem Signature 01: VppMigrationTool.exe

Problem Signature 02: 1.1.0.0

Problem Signature 03: 52cbd04f

Problem Signature 04: VppMigrationTool

Problem Signature 05: 1.1.0.0

Problem Signature 06: 52cbd04f

Problem Signature 07: 64

Problem Signature 08: d

Problem Signature 09: System.Runtime.Remoting.Remoting

OS Version: 6.1.7601.2.1.0.1296.17

Locale ID: 1044

Additional Information 1: d372

Additional Information 2: d372a259d1b087d47f3c5748caf83a06

Additional Information 3: a684

Additional Information 4: a684aee7275043875a731dd6179dc134

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

The source VPP files are on a network share and the destination blobs-folder is on the same share. I've been able to run the migration sucessfully in my local dev-environment; where both the tool, the original VPP files and the blobs-desitination folder is located.

As a side-note I noticed that the original VPP folders are ~9,5 GB (81k files), while the migrated folders are ~3,75 GB (72k files) in size. Is this normal?

Anyone else experiencing these errors?

#112131

Oct 23, 2014 9:02

Ørjan Horpestad

Vote:

Also, I found this in the event viewer log:

Application: VppMigrationTool.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.Remoting.RemotingException
Stack:
   at VppMigrationTool.Util.StatusWriter.Write(VppMigrationTool.Util.StatusEventArgs)
   at VppMigrationTool.Util.StatusHandler.SiteProxyInstance_StatusEventHandler(VppMigrationTool.Util.StatusEventArgs)
   at VppMigrationTool.Util.VppConverter.HandleExcpetion(System.Exception, Boolean)
   at VppMigrationTool.Util.VppConverter.Convert()
   at VppMigrationTool.Util.SiteProxy+<>c__DisplayClass2.<Convert>b__1(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Followed by:

Faulting application name: VppMigrationTool.exe, version: 1.1.0.0, time stamp: 0x52cbd04f
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a
Exception code: 0xe0434352
Fault offset: 0x000000000000940d
Faulting process id: 0x3454
Faulting application start time: 0x01cfee269a63c979
Faulting application path: C:\vppmigrationtool\VppMigrationTool_20140107.1\VppMigrationTool.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 8ae58a67-5a1e-11e4-956b-005056b36f81

#112133

Oct 23, 2014 9:07

Johan Björnfot

Vote:

I have seen that exception before. In that case it was caused by that the zip (that was downloaded from internet) was "blocked". The solution was to rightclick on the zip from windows explorer and choose "unblock" before unzipping it.

#112143

Oct 23, 2014 10:59

Ørjan Horpestad

Vote:

Thanks,

However - In my case there is nothing to unblock (no unblock button is showing while viewing properties on the zip-file).

Also, I suppose I shouldn't have been able to migrate as much as ~81 000 files if that was the case?

#112146

Oct 23, 2014 11:09

Ørjan Horpestad

Vote:

Update:

I did another test. I downloaded the most recent VPP-files and production database to my local environement, and were able to run the VPP tool without any error message. It took about 1,5 hours.

So I'll probably do the same when performing the upgrade on our live servers, and just uploaded the updated database and blobs-directory back when done.

I'm thinking the combination of network shared VPP source+destination, combined with a rather limited test-server, in terms of cpu/mem./disk, may be the cause of the error in the VPP tool. But I'm not sure.

#112161

Oct 23, 2014 14:30