cancel
Showing results for 
Search instead for 
Did you mean: 
jbaker
Level 9
Report Inappropriate Content
Message 1 of 5

5.1 Upgrade Compat. Utility Compressing Stuck @ 11%

Jump to solution

Hello everyone,

Using the Upgrade Compatibility Utility to create my Migrate.zip file. The product compatibility check passes. Once I hit migrate, everything starts off alright. Compressing starts and hits 11% then just doesn't go anywhere. Both times I've tried the Migration it has stopped at 11%.

Is there anywhere I can see a log of where it might be getting hung up?

Any help would be greatly appreciated.

1 Solution

Accepted Solutions
jbaker
Level 9
Report Inappropriate Content
Message 5 of 5

Re: 5.1 Upgrade Compat. Utility Compressing Stuck @ 11%

Jump to solution

Migration tool succeeded today. It was most likely a disk space issue. I only had about 3.5GB on my drive remaining, while the Migration zip was about 4.5GB. Saving the output file to a secondary drive was my solution.

4 Replies
jbaker
Level 9
Report Inappropriate Content
Message 2 of 5

Re: 5.1 Upgrade Compat. Utility Compressing Stuck @ 11%

Jump to solution

I should add that I'm running on Windows Server 2003 R2 using SQL Server 2005.

McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 3 of 5

Re: 5.1 Upgrade Compat. Utility Compressing Stuck @ 11%

Jump to solution

Just noticed your question but it might be late. Did it finish or did you cancel? Still need help?

jbaker
Level 9
Report Inappropriate Content
Message 4 of 5

Re: 5.1 Upgrade Compat. Utility Compressing Stuck @ 11%

Jump to solution

It never finished and remained at 11%. I restored the server from a snapshot and have not yet tried again.

I will likely be trying again sometime soon. Is there anything I can look for during the process that might assist me with figuring out what might be going wrong?

Thank you for your reply.

jbaker
Level 9
Report Inappropriate Content
Message 5 of 5

Re: 5.1 Upgrade Compat. Utility Compressing Stuck @ 11%

Jump to solution

Migration tool succeeded today. It was most likely a disk space issue. I only had about 3.5GB on my drive remaining, while the Migration zip was about 4.5GB. Saving the output file to a secondary drive was my solution.