Error occurred; unable to open file.

[The Mad Jammer]

I hate this error. Using Remote Server Administration (RSA) I closed a folder containing 8 hosted files for maintenance. I then opened one of the files and copied the file as a "clone with no records" to another folder on the server. The files in the target folder were being hosetd at the time I created the new file in the target folder. Anyway, when I started the RSA again and tried to reopen the original 8 files only a couple of them would open. The rest gave me the message Error occurred; unable to open file. The file I opened and made a copy of is one of the files that won't open. What in the )!(&@*$!^((*^*@ is going on with this? I opened and closed the files in Filemaker Pro that were giving me the error but the server still won't open the stupid things. This has happened from time to time on other files that I try to open using RSA. Sonmetimes, but not always,the files finally open after repeated attempts to open them using RSA, but I've never been able to determine what prevents them from opening in the first place. Anyone know the answer to this? I searched the site but coudn't no answer to this. BTW, there are 49 files currently hosted on the server so the 125 file limit is not an issue.

Thanks

The Mad Jammer

And then... there was nothing

[Anatoli]

Platform? Version? Updates?

RE: to another folder on the server

Where? within reach of FMS? That is probably wrong.

[stanley]

I agree. More detail definitely needed.

I also agree that it sounds like you're commiting a severe breach of practice. Please don't tell me that you're cloning a file within the FileMaker Server directory, and giving it the same name as the cloned file. Please also tell me you didn't target a folder currently in use by FM Server. This is what it sounds like you're doing, and if that's so, you're just asking for trouble.

-Stanley

[The Mad Jammer]

Thanks for your explanations. In fact, I did commit the grievous error of cloning a file to another folder that was being hosted by FMS. Fotunately no ill effects seem to have been suffered. I won't do that again, ever. As it turns out, one of my users opened several of the files after they had been released from FMS, so when I tried to reopen them in FMS I couldn't because they were encumbered. After I tracked them down and had them close the files I was able to hsot the files in FMS with no problem.

Thanks again for the pointers, I appreciate them.

The Mad Jammer

And then...there was nothing