We are migrating and upgrading from vault 2013 to 2014.
Currently running 2013 on W2K3 server with remote SQL2008R2 server
I have built a new 2014 server on W2k8 and pointed it at a fresh AutodeskVault instance on SQL2008R2
I take a backup from the 2013 server and then attempt to restore it to the 2014 server.
The problem i have having is that the server reports these errors
Exception: IncompatibleKnowledgeVault [306]
Have attached logs
The vlog only contains client/server information. Can you attach the ADMS Console log from the day you attempted the migration?
-Hywell
In the Vault client, goto Help -> About. What is the build number listed?
-Hywell
Can you install SP1 for Vault 2014 and that will force the databases to migrate again when you open the console?
-Hywell
I've attached all the logs from today.
This morning (15/10/13 - 8:00am) i restored a 2013 DB/Filestore onto our 2014 server.
Let the server do its Filerstore indexing
Tested a backup - failed.
I then installed SP1 and migrated the vaults.
Tested a backup which completed successfully
Great
The logs still are showing some errors. - IncompatibleKnowledgeMaster [307] and some Webservice timeouts
So now when i want to cutover from 2013 to 2014 this weekend, i should be able to restore the 2013 DB/Filestore onto the Vault 2014 SP1 server fine?
FYI
Did another restore of our latest 2013 backup. This went through fine apart from the
Exception: IncompatibleKnowledgeVault
errors.
Ran a backup and that ran fine, no more Wenservice timeouts.
What do you think of the Exception: IncompatibleKnowledgeVault errors? RedHerring?
Test clients can connect fine and browse the filestores.
Are you currently using connected workgroups?
If you are on Subscription, could you log a case or if not, have your resellelog a case on your behalf?
-Hywell
Hi,
Based on the timing in the logs, the IncompatibleKnowledgeMaster errors occured before the databases were fully migrated. After the time migration completed, it looks like background events are running normally. So unless you continue to see such messages after migration has completed, they can be safely ignored.
Paul
On our 2013 server we have 2 workgroups. Production and Test (which has its vaults disabled)
When i restore the 2013 DB/Filestore onto our 2014 server these workgroups show up as 'Unknown' so i delete them to just leave our 1 new Workgroup
Could this be the cause of the errors? So can be ignored
OK, that sounds good, we were coming to that conclusion as the Power user we got to do some testing seems to think the Vault is fine. I just wanted to be certain before we cutover.
Will check logs today and see how it looks
thanks