Error 3315 Message

[dancagle]

After exploring the problem of not transferring all my kma files to the database and getting a 3315 error message I have found another error after trying to get my songs back that are on my external hard drive. It says " duplicate KMA files ( same discID and track # ) detected during DB merge.

C:\MTU\Hoster\MergeSongDBlog.txt

I have all my songs on my external hard drive which is E. Can I delete the duplicates that I beleive to be somewhere on my C: drive? Or is my thinking wrong?

Dan

[Beavis]

merge them.

[dancagle]

starting to get a little flustrating because when I try to merge it keeps stoping on certain files and will come up with the message " cannot be a zero -length string) 3315. I've tried to rebuild the database also. When looking at the c: drive I have the MTU file under it but I also have under c:/programs the Micro tecnology Unlimited file that has the demo file in it with a songs file also. Should this file still be here or can I delete it?

[Beavis]

manually delete that file.

[ddouglass]

If you don't have the demo still installed then you can delete those files. If it is still installed the uninstall it first then delete what is left.
If you have copied all your kma files from the C: drive to the external then you should be able to delete those too and just rebuild the database using the external drive folder.
The 3315 error means those files are corrupt. Sometimes this happens if one of the fields is too long. The only way to recover those files is to re-import them.

[dancagle]

Thanks i'll see what I can do.

Dan

[bobcox- with the Lord]

Originally Posted by ddouglass

If you don't have the demo still installed then you can delete those files. If it is still installed the uninstall it first then delete what is left.
If you have copied all your kma files from the C: drive to the external then you should be able to delete those too and just rebuild the database using the external drive folder.
The 3315 error means those files are corrupt. Sometimes this happens if one of the fields is too long. The only way to recover those files is to re-import them.

Dale, I get this all the time, and the files are fine.
it is something in hoster and MS that is doing this. Bob

[ddouglass]

Originally Posted by bobcox

Dale, I get this all the time, and the files are fine.
it is something in hoster and MS that is doing this. Bob

You are correct but the only way to correct the problem is to reimport them. If one of the fields is too long then either program ends up deleting the information rather than truncating it. Admin said they would look into this, but as you know they have been pretty busy with Hoster 4.

[dancagle]

I know it will load some of the songs but not all of them ( a large amount of them are missing). I had no problem until I loaded 4.0 yesterday. The problem is trying to find the songs that are missing and re-importing them.
My ID starts at 101 and goes to 17410 any songs after that number is no longer in the database, yet I see them on my external hard drive E:/ So I am trying to get them back in today before my gig tomorrow night, plus I don't know what this will do to my songbooks.
Thanks for your help.
Dan

[ddouglass]

The way to figure out which song files are missing is to run the rebuild again and when you get the error message not what number it stopped on. The is the record number in the songs.mdb database file.
You will need Microsoft Access to be able to open the database file, open the songs table, sort ascending by record number. Look for the first record number (it will be missing) and note what files are around it. You should be able to determine from them what disk they came from so you can re-import them.
It is time consuming to do it this way but that is the only way to do it unfortunately.

[dancagle]

Thanks for your help on this problem. But does anyone have any idea what may cause this type of problem. The only thing I did was upgrade to 4.0, and could this happen again when the other upgrades become available. Thanks again i''m back to re-importing now.

Dan

[admin]

Dan, I believe Dale is correct. In the past, our KMA importer could allow filenames exactly 64 bytes long. When we went to 4.00, we needed to put an "end-of-field" character in that 64-byte string, so we had to limit the DATA to 63 characters, and the last byte became the "delimiter". I believe that is where we may have a bug. It would only show up if you had 64 bytes in a Title or Name field, or (I forget the field size) the maximum bytes for the Brand (Mfgr) field. These 3 were limited to 1 byte less than before.

It was a judgment call I agree with so we didn't have to redo the KMA Header on every KMA file. That would have required making a backup, and running a Utility program that would convert all your KMA files to a new KMA Header. We felt that was too extreme. Problem is there seems to be a bug in this "truncation" that we didn't find before releasing 4.00.

I've written it up for review tomorrow.

[admin]

In Hoster 4.04, we searched for and found causes for the "3315" errors. Please test this and let us know if your files import now without errors. We expect to release 4.04 either September 2nd or 3rd (Tues/Weds).