Jump to content

Recommended Posts

Posted (edited)

I'm working on automating the migration process for schools in our LA and am using a VM for testing. The VM is running a Green Abbey SIMS, FMS and Discover system, all on the Summer 2013 release. I've had some issues getting the process to run via a script, so am trying to do it manually. As per Capita guidance, I want to migrate SIMS and Discover at the same time but get this error:

 

http://i.imgur.com/rlpJjYy.png

 

It's weird as I built this VM specifically for testing. The SIMS and Discover databases are both used by the Discover services so I'm confused as to why it's giving this error. It's obviously not happy with something, any suggestions?

Edited by Rawns
  • 2 weeks later...
Posted
I understood Discover couldn't be auto-migrated until Autumn 13. Don't know if your procedure is allowed, unless it's stated in the manual process to do it like that...?
Posted
I understood Discover couldn't be auto-migrated until Autumn 13. Don't know if your procedure is allowed, unless it's stated in the manual process to do it like that...?

 

SOLUS3 can't be migrated until the SOLUS3 Autumn release.

Posted
I'm sure Discover had no tick by it for automation.

 

Huuum, that could explain why it errored out when I tried. Oddly, the tools allow you to select both sims and discover to migrate.

 

Anyway, why am I discussing it now?! I'm on holiday for 3 weeks!!!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...