I'm attaching a log file that reflects an error in my metadata when I ran a database diagnosis.
[attachment deleted by admin]
This looks like a problem caused by a bug that was fixed one or two versions ago.
Is this an older database? If so, the problem may have been there for a while (it's not an error, just a warning).
Run a diagnosis daily and check if the problem shows up again.
To that, I definitely did run the diagnosis a second time, and the second time, no error. I then compacted the database.
That's the expected outcome. The diagnosis fixed that warning and it should not show up again.
This has to do with file relations (versions) and if you work with these (adding new versions, removing versions etc.) the bug will show up if this is not caused by the problem I fixed two versions ago (which I'm pretty sure of).
Just do your normal testing and run the diagnosis a bit more often. If it does not show up again, it's fixed already and was just a left-over from an older database / IMatch build.
Yesterday I started IM and let i be for 2 hour
still same message
now I started it and opened DB diagnose (NO error) and closed ==> no errors (tested 2 times)
after that I opened IM and only wait for user interface and closed ==>Same errors as above (tested this 3 times)
Sven Åke
This error can only happen when master files are added, removed or relation rules are changed and re-applied.
Did IMatch rescan a folder, adding new files during your test?
(Please alway include the diagnosis log and the application log in your posts).
I rescanned all folders and rebuild cache for the last 12 hours
And now it's no error message
Thanks
Sven Åke