[Fixed] update to database v486 error

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

[Fixed] update to database v486 error

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support >> [Fixed] update to database v486 error

Page: [1]

Message

<< Older Topic Newer Topic >>

[Fixed] update to database v486 error - 7/22/2020 5:21:34 AM

pxl919092

Posts: 12
Joined: 1/28/2020
Status: offline

I have a fairly complicated scenario that was merged multiple times under database v483.

Now I've updated CMO to version Build 1147.7, I was trying to update the database from v483 to v486, and I got this this error:

"One or more platforms are missing from the DB you are attempting to migrate to.
Weapon #0,
...
migration aborted"

I wish I can find out what "Weapon #0" is and simply delete it. I deleted the sides in this scenario one by one, and when only empty/shell sides are left I still got the same error. sounds like my .scen file is corrupted in some way due to prior merges?

Attachment (1)

< Message edited by apache85 -- 8/2/2020 7:59:58 AM >

Post #: 1

RE: update to database v486 error - 7/22/2020 5:35:37 AM

Rory Noonan

Posts: 2816
Joined: 12/18/2014
From: Brooklyn, NY
Status: offline

Can you upload the scenario file so we can look at it?

If you're unable to upload due to forum restrictions you can PM it to me (it will have to be in a .zip file)

_____________________________

(in reply to pxl919092)

Post #: 2

RE: update to database v486 error - 7/27/2020 2:49:22 AM

Rory Noonan

Posts: 2816
Joined: 12/18/2014
From: Brooklyn, NY
Status: offline

Hi pxl919092,

Thanks for the file via email.

It seems this is a quite-old scenario (I think it may have originated prior to DB 475?) and it hasn't had a deep rebuild in a very long time--for example, the submarines in the scenario don't have the discrete periscope sensors that were introduced a few years back.

Deep rebuilding the scenario seemed to work fine. Give that a try and let us know how it goes.

I've attached a copy of the scenario that has been updated to 486 using deep rebuild incase that's useful.

Attachment (1)

_____________________________

(in reply to Rory Noonan)

Post #: 3

RE: update to database v486 error - 8/2/2020 4:29:17 AM

pxl919092

Posts: 12
Joined: 1/28/2020
Status: offline

Hi apache85,

Thanks a lot of taking a look and suggested a fix that works. Yes, deep rebuild resolved the issue. In this scenario I have quite a few units (CG47/CG21, 055, etc..) that carries a payload different than any of the default settings alike, so at the end had to resolve to manually export them, deep rebuild to 486, and then re-import them. things work like a charm now.

This scenario was a follow on to the Chain of War scen 7 "Okinawa bound" (largely based on it), assuming Okinawa is taken...and Kyushu became the next.

If you don't mind, I am still hoping for the in-scenario unit editor ;) I literally called up support to ask if I can buy the PE just for that.

Many Thanks for the help!

(in reply to Rory Noonan)

Post #: 4