Write File Problems

[Hydrology]

I periodically get XMDF errors when I try to save or run a model. This has been happening for several months now. I need to be able to save my model changes. It only happens in GMS 9.x, so I have gone back to using 8.3, but I would rather use 9. I have uploaded these files to your FTP site previously, but I never heard back from anyone. Does anyone have a solution to this? The text from the error message window is shown below:

XMDF errors:

#000: src\H5L.c line 1668 in H5L_link_cb(): name already exists

major(201326597): Symbol table

minor(201326724): Object already exists

#001: src\H5Gtraverse.c line 691 in H5G_traverse_real(): traversal operator failed

major(201326597): Symbol table

minor(201326663): Callback failed

#002: src\H5Gtraverse.c line 861 in H5G_traverse(): internal path traversal failed

major(201326597): Symbol table

minor(201326723): Object not found

#003: src\H5L.c line 1856 in H5L_create_real(): can't insert link

major(201326597): Symbol table

minor(201326730): Unable to insert object

#004: src\H5L.c line 1633 in H5L_link_object(): unable to create new link to object

major(201326605): Links

minor(201326644): Unable to initialize object

#005: src\H5Dint.c line 429 in H5D_create_named(): unable to create and link to dataset

major(201326592): Dataset

minor(201326644): Unable to initialize object

#006: src\H5Ddeprec.c line 170 in H5Dcreate1(): unable to create dataset

major(201326592): Dataset

minor(201326644): Unable to initialize object

[Michael Kennard]

Looks like this is your previous forum post about this problem. The last post is Alan saying we couldn't reproduce the problem but to contact him directly. He's out of town at the moment but I've emailed him to see what he knows.

[Michael Kennard]

Please contact tech support so we can create a ticket for this. If we can get a copy of your files again we'll try to reproduce the problem here. Hopefully we'll have better luck this time.

[Hydrology]

I will call in. The problem is intermittent, so it might be hard to reproduce, but hopefully the text of the error message will point us in the right direction. This happened when I had 64bit Windows 7, and it continued when I did a clean install of 64bit Windows 8, and now with Windows 8.1 so it seems to be independent of the operating system.

It seems to occur a lot for a few days, then not at all for a few weeks, then it returns like a plague for a few days, then its gone again. Its very strange. I think the error message may be all we have to try and find the source of this problem.

Edited November 12, 2013 by Hydrology