Find us on Google+ Migration Errors Moving from Autodesk Vault 2012 to 2013 - Scary! But an Easy Fix! ~ Inventor Tales

Sunday, October 13, 2013

Migration Errors Moving from Autodesk Vault 2012 to 2013 - Scary! But an Easy Fix!

“It was tough. We have some experience on our side, which is nice.”
Paul Testa

One thing about my job, is I learn something new every day.

Friday, I was upgrading a server from Autodesk Vault 2012 SP2 to Autodesk Vault 2013. 

This should be easy.  I've done it a dozens times. 

But this time, it's different.  Instead of the usual upgrade magic, I get this error.

What?!?  What does this mean?!?

Database not supported?!?!? 

How can a 2013 not be able to migrate a 2012 database?!?!?

It's Friday, 2PM.  I am not looking forward to fighting a database into the wee hours of the night. 

I call a couple of colleagues.  We puzzle over it a bit. 

Then.. The solution comes from an experienced Vault user.

"Bring Vault 2013 up to the latest service pack." 

I do it, and it works. 

I breath a sigh of relief.  As a matter of fact, I breath a couple of more sighs, just to be sure.

Finally, I ask "What happened?  I've never seen that before".

My colleague explains that he's run into cases where an older version of Vault (in this case 2012) gets a service pack that's issued after a new release (2013 in this case).

Since 2012 install I was working on had Service Pack 2 installed, and that service pack came out after Vault 2013's release.  The Vault 2013 Service Pack 0 install didn't know what to do. 

Service Pack 1 for Vault 2013 had the updates to the migration process that were required.

I'm grateful for the experience of that colleague.  Without that, I probably would have tried to rebuild the 2012 installation.  This would have worked, but it would have taken hours instead of minutes.

I would have never thought to try the service pack.  

Now I know, should I ever run into this again!

And for the rest of you out in the 'Verse, I hope this tip helps you, should you ever run into the same thing!

No comments:

Post a Comment