 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion Groups Database Servers DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybaseDesktop Databases FileMakerFoxProMS AccessParadoxGeneral General DB TopicsDatabase TheoryRelated Topics Java Development.NET DevelopmentVB DevelopmentMore Topics ... |
Database Forum / FileMaker Topics / February 2004Damage errror, undamaged files
I'm doing some debugging on a rather complex solution. I'm experiencing an intermittent bug that I can't seem to track down. On occasion, I'll get the message that "This file is damaged..." followed by "Filemaker has performed an illegal error..." and then FileMaker goes down. I've checked the files using the recover command, and they don't show any damage at all. They've never crashed in stand-alone mode. The error doesn't occur consistently on any obviously common script or machine. We get the error about once a day on average. When it happens, we can re-open the files, get back to the same place and do (seemingly) the same things, with no errors. We've noticed that the bug tends to show up during scripted searches, especially where the values being searched are based on external references. A colleague said he read an article in FileMaker Advisor a year or so ago (about database structure) that linked this type of problem to some combination of external reference calculations and certain script steps. I haven't been able to find the article he's referring to, though. Does anyone have any clues, either about the problem or the potentially helpful article? I'm using FM 5.5 developer, with Server version 5.  SignatureShadenfroh shadenfroh@yahoo.com Just some comments since no one else has responded to this... > I'm doing some debugging on a rather complex solution. I'm experiencing an > intermittent bug that I can't seem to track down. [quoted text clipped - 4 lines] > I've checked the files using the recover command, and they don't show any > damage at all. They've never crashed in stand-alone mode. Use of the Recover command does not necessarily expose any or all file corruption, nor does it necessarily fix any corruption. The purpose of using the Recover command is to re-open the file in a state that allows you to get the data out for use in your original, 'clean' copy of the file. > We've noticed that the bug tends to show up during scripted searches, > especially where the values being searched are based on external references. [quoted text clipped - 6 lines] > Does anyone have any clues, either about the problem or the potentially > helpful article? I've never heard of a problem with external references. Is it one external file in particular that causes the problem? Do you have enough memory on your client machine? Is it one client or on all that this happens to? Mac or Windows on the client? And perhaps most important, what OS is running your FM Server? Signature~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Howard Schlossberg (818) 883-2846 FM Pro Solutions Los Angeles, California Associate Member, FileMaker Solutions Alliance Thanks for the clarification re: Recover. I don't know of any other way to identify whether a file is corrupted or not, though. (Heck, considering the files have never crashed on the host/server, I wouldn't expect any corruption in any of the files.) The "file damage" message doesn't indicate which file is damaged. Even if a multi-file script isn't running, numerous portals and related fields displayed on the layouts make the message vague. There's no common machine, user, file, etc. It's happened on about four or five different machines, I'd guess, and I'd estimate at least four different files have been displayed when the bug occurred at different times. We're running FM Server v. 5.0. Windows server and clients. SignatureShadenfroh shadenfroh@yahoo.com Just some comments since no one else has responded to this... Shadenfroh wrote: > I'm doing some debugging on a rather complex solution. I'm experiencing an > intermittent bug that I can't seem to track down. [quoted text clipped - 4 lines] > I've checked the files using the recover command, and they don't show any > damage at all. They've never crashed in stand-alone mode. Use of the Recover command does not necessarily expose any or all file corruption, nor does it necessarily fix any corruption. The purpose of using the Recover command is to re-open the file in a state that allows you to get the data out for use in your original, 'clean' copy of the file. > We've noticed that the bug tends to show up during scripted searches, > especially where the values being searched are based on external references. [quoted text clipped - 6 lines] > Does anyone have any clues, either about the problem or the potentially > helpful article? I've never heard of a problem with external references. Is it one external file in particular that causes the problem? Do you have enough memory on your client machine? Is it one client or on all that this happens to? Mac or Windows on the client? And perhaps most important, what OS is running your FM Server? Signature~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Howard Schlossberg (818) 883-2846 FM Pro Solutions Los Angeles, California Associate Member, FileMaker Solutions Alliance Please do yourself a favor and search in the archive at http://cdf.filemaker.fm/ for "recover", "corruption", etc to get a better handle on this. > Thanks for the clarification re: Recover. I don't know of any other way to > identify whether a file is corrupted or not, though. (Heck, considering the [quoted text clipped - 46 lines] > happens to? Mac or Windows on the client? And perhaps most important, > what OS is running your FM Server? > I'm doing some debugging on a rather complex solution. I'm experiencing an > intermittent bug that I can't seem to track down. [quoted text clipped - 22 lines] > > I'm using FM 5.5 developer, with Server version 5. Hi, I had last week a similar error. I made the mistake that I had running a couple of tables on the server and I had also the same tables on my desktop computer where I developed them. The latter just standing in a map and weren't active. When I runned the application from remote it happend that in a scriptstep a table was referenced on my desktop computer. After renaming the tables on my desktop computer or putting them in another submap the problem disappeared. Mybe this is an idea to look at. Filemaker remembers a lot, even ip-numbers, files, complete paths, etc. Marcel Thanks for your input, Marcel. :-D I've dealt with that one before, myself. I've checked that here, but I'm going to look again, anyways. I'm pretty desperate to fix this. SignatureShadenfroh shadenfroh@yahoo.com "Shadenfroh" <shadenfroh@yahoo.com> schreef in bericht news:dl9%b.20394$W74.12177@newsread1.news.atl.earthlink.net... > I'm doing some debugging on a rather complex solution. I'm experiencing an > intermittent bug that I can't seem to track down. > > On occasion, I'll get the message that "This file is damaged..." followed by > "Filemaker has performed an illegal error..." and then FileMaker goes down. > I've checked the files using the recover command, and they don't show any > damage at all. They've never crashed in stand-alone mode. [quoted text clipped - 6 lines] > We've noticed that the bug tends to show up during scripted searches, > especially where the values being searched are based on external references. > A colleague said he read an article in FileMaker Advisor a year or so ago > (about database structure) that linked this type of problem to some [quoted text clipped - 5 lines] > > I'm using FM 5.5 developer, with Server version 5. Hi, I had last week a similar error. I made the mistake that I had running a couple of tables on the server and I had also the same tables on my desktop computer where I developed them. The latter just standing in a map and weren't active. When I runned the application from remote it happend that in a scriptstep a table was referenced on my desktop computer. After renaming the tables on my desktop computer or putting them in another submap the problem disappeared. Mybe this is an idea to look at. Filemaker remembers a lot, even ip-numbers, files, complete paths, etc. Marcel I had similar problems a few years ago. It turned out one of the hubs on our network was causing intermittent errors, causing Filemaker Server to generate error messages. We replaced all our hubs with quality switches and the error messages stopped. might be worth a look... Marc |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.