Migrate EM-iView Catalog script gives runtime error

Post Reply
DavidALarsen
Posts: 2
Joined: 06 Jan 23 17:23

Migrate EM-iView Catalog script gives runtime error

Post by DavidALarsen »

I have been using the Migrate MediaPro / EM / iView Catalog Sets to Portfolio Collections script mentioned here: https://repository.idimager.com/openres ... B5DA050237 to migrate catalog sets from Media Pro into Photo Supreme. The script seems to do this successfully for a small set of images. I have had success for up to 60 images at a time. However, when the selection of images to process using the script is too large, then it throws up a runtime error. The latest error I got gave me this message:

IDI.v7.ApplicationException

----- details -----

ExceptionTimeStamp=2023-01-06T17:17:53.046Z
ExceptionThreadName=Main Thread
ExceptionClass=EatScripterRuntime
Exception=SCRIPT RUNTIME ERROR
An error occurred while applying the updates in a record: database disk image is malformed when evaluating instruction PushVar ($0,$0,$0,$0,'Result').
Stack content is: [String:0A52C02AA7A642E0BFDC1CEE3B3C9058,String:4A92087C31A4443C82A1089E82829525].
Source position: 221,1
Build=7.4.3.4738
Edition=Single
Architecture=A.64 bit
Platform=macOS
OperationSystem=macOS Monterey A.64bit (Version: 12.5.0)
Display=2560x1440
AvailableMemory=4.3 GB of 8.6 GB
ProcessorCores=8
Trial=no
UptimeSeconds=6924
SystemID=FF08F6E1D7DAF0FADCD4E3E407E9E3E9
CallStack= $0000000101970134
$000000010197ED44
$000000010197E958
$000000010197DF78
$000000010197D760
$0000000101970B08
$0000000101807C18
$0000000101807948
$0000000101D8C598
$0000000100F8C0C8
$0000000100F8C8AC
$0000000100EDA4D8
$0000000100F8D6DC
$0000000100EDA8A4
$00000001014438C4
$0000000100FA5C4C
$000000010117BF64
DatabaseSystem=SQLite
ActiveCollectionCount=398
ActiveForm= frmQuickScript[TfrmQuickScript]
ActiveForm.ActiveControl= frmQuickScript[TfrmQuickScript]
vxScene1[TvxScene]

It fails if I select too many. But if I select the same images, fewer at a time, it works. I have well over 100,000 images to process in this way and if I have to break this down into sets of 50, it is going to take forever. Does anyone have a fix for me?
Hert
Posts: 7870
Joined: 13 Sep 03 6:24

Re: Migrate EM-iView Catalog script gives runtime error

Post by Hert »

First of all: a very warm welcome to the forum.

The number of images is not the issue here. You get the error:
An error occurred while applying the updates in a record: database disk image is malformed
Photo Supreme uses SQLite as its database system. This is one of the most popular desktop database systems and is typically very robust. The most common reason for SQLite to fail is when an outage occurred during a write operation. Like a power outage or when you have the catalog stored on a external or network drive and the connection drops. The latter is why you should never store the catalog files on an external or network drive unless you have a good backup strategy in place.

The error you are getting means that your SQLite file is not in a healthy state.

Best to restore your backup which hopefully is available and in a healthy state.

Since you are apparently still getting started, then I recommend to create a new catalog and import to that. You can create a new catalog by selecting Catalog -> Create a Catalog from the upper left hamburger menu. Please store the catalog on the internal drive, preferably a SSD drive.
In the Preferences you can enable the login dialog so that on starting Photo Supreme, you can select what catalog to open
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
jack208
Posts: 21
Joined: 14 Oct 22 17:55

Re: Migrate EM-iView Catalog script gives runtime error

Post by jack208 »

I'm also seeing this "database image is malformed" on my catalog.

Is there no utility that allows us to repair the SQLite DB - instead of having to start from scratch?
Hert
Posts: 7870
Joined: 13 Sep 03 6:24

Re: Migrate EM-iView Catalog script gives runtime error

Post by Hert »

I didn’t say that starting over is the solution. For the topic starter it may be because he (I assume) is not fully operational yet.
The solution for you is what I replied in Mantis: if you do not have a backup then send me the database so I can try to recover it.

Sure, Google that error message and you will find solutions because this happens a lot with SQLite databases.

The solution is too technical for me to recommend to OSU users.
Rule number one: always make sure that you create backups of you data. That is unrelated to PSU. You should backup everything on your pc that is of value to you. Your Psu catalog is typically one of such
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Post Reply