Jump to content

teukka

Members
  • Posts

    11
  • Joined

  • Last visited

teukka's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. An other thing - since we are also planning on for FMS5.5 with Win Server 2003, I'm interested on your case. Do those users get that "-20 disconnected message" or something like that...? Do you have one network card or two on the server?
  2. You can also script (& test) everything into your new version (you supposedly have your customer's current/old version). Just create all needed import scripts, possible replace/modify/etc. scripts that maybe needed because of new functionality/fields/etc. in your new version. Test & verify it a couple of times @office and do it then at your client (or if possible get the files to your office). You can rename the old files to whatever (with developer/by hand/with DOS BATCH file). They don't need to keep the relationships at that stage. Then you can place the folder containing those next to the folder containing the new version. Then just click the button (or start a script) in your new version and let the system do the job. Easy! Depending on the complexity and data amount that procedure takes from minutes to several hours. After the new version has the data and needed procedures have taken place, you can also automate the zipping of files, placing that to some ftp-folder or sending it by email directly to your customer, etc. Just spend the time before actual version change and when it comes to transfer the data to new files enjoy the work done :D
  3. If you know how to install & operate, here is a link to intl versions of fms trial sw (non english). ftp://ftp.apple.com/filemaker/trial_software/fms/INTL At least the Win versions are similar to operate so you can quite easily test it with other language... I don't know if that's the same with linux.
  4. Server's only purpose is to run FMS to host FM files. Virus scan is not scanning any .fp5 files. Crashes started before adding those additional monitoring apps. So they haven't changed the situation. Server is though having double nw cards (that is what should be avoided according to best practices). But the server was fine for two years! There has been an increase in no of simultaneous active users this year (50->70). Biggest file is round 500 megs, three next ones together about the same.
  5. For remote users you can also choose GoGlobal (pricing is ok, basic usage very easy to configure, works with Win, Mac, Linux). Major difference to TS is that with GG you can offer a remote app without a new/second/duplicate desktop! You can even work in your office with two FM6/7/8 at the same time (one with local FM installed on your HD, the other FM window opened via GG). And with GG you can have even multiple sessions open at the same time, so basicly you can for example open 3, 4, 5, ... paraller sessions open with the same db and do e.g. some load test or any other thing where multiple sessions might be of help. Check the web pages from GraphOn inc. They offer free test drive (might have been for 30 days). That is an excellent way to share your FM apps to remote users (works even via telephone line)!
  6. Thanks for your quick replies & LaRetta for your efforts in searching for possible cause! The folder is in Program Files in FM folder (in drive C together with OS). D is for swap file. Bkps are on other drive. Now we have those quite extensively - every half an hour! The crashes are not associated with the FMS bkp scripts. They happen on different times. There are not any shared folders in C. There are not any external bkps (except on weekends when tape bkp takes place). There is one automatic shutdown during weekends (since we are running on Windows). FMS cache is @ max 40 meg. Cache hit% is typically 99-100%. We have just recently reinstalled FMS but no help. There are about 80 processes running on the server, several of those related to newly installed HP monitoring/surveying apps.
  7. The FMS function LocalBigPut is causing the failure of FMS service to stop. DrWatson says: Application exception occurred: App: fmserver.exe (pid=924) When: 4/07/2006 @ 08:40:31.764 Exception number: c0000005 (access violation) In function: LocalBigPut the fault should be this: FAULT ->00408972 f6430a10 test byte ptr [ebx+0xa],0x10 ds:00819ee6=?? The system info: User Name: SYSTEM Number of Processors: 2 Processor Type: x86 Family 15 Model 2 Stepping 7 Windows 2000 Version: 5.0 Current Build: 2195 Service Pack: 4 Current Type: Multiprocessor Free It has 4gig ram, raid discs, etc. so hw should be quite enough. There are round 70 actice users, 30 files, about 1.2 gig data, 700-900 million records, tens of thousands created/edited weekly. Does anyone know what is that LocalBigPut function or what it should do? Reasons for failure might be many (according the several posts e.g. in this forum and elsewhere in internet). We've tried to test every of those. Could that simply be that FMP/FMS6 just is not enough for this amount of data/usage/filesystem? Failure can happen during hard load of nw/server or even during low activity period. So there does not seem to be any logic...
  8. Does anyone know what is the meaning for the function [color:green]LocalBigPut (in FM5.5/6 world)? Or for LocalBigGet, LocalPut/Get? You can find those in both the FMPro (exe 6 & Fmeng10.dll) and in FMS (at least in exe). That seems to be the function that is crashing. The reason...? There seems to be things related to db schema, no. of users, printer naming, wrong kind of data in the fields, FMP/FMS cache, network conditions, network cards in server, etc. that might be causing [color:blue]FM service to crash on [color:blue]Windows server. DrWatson can tell the exact row of assembler code that is failing. But not the reason for that.
  9. We are planning kind of similar configuration but haven't done it yet. What size, how many files, etc. you have in your FM solutions? Do users perform operations (e.g. sorting/searhing with huhdreds of thousands of records) that normally eate your FM client computer processor capacity quite a lot...? So I'm basically interested in the processing capacity issues of TS server serving multiple TS clients using FM on that TS server. You're saying you have about 10 users per TS server. Have you found that being a proper number of users/TS server in your case...
  10. Thanks for info & confirmation to my suspects! Like I explained everything looked ok and is still so. The bkps are running basically three times/day: round lunch time, right after busy hours ~4-5 pm (these are called everyday bkps) and then at 11 pm a weekday bkp that is then saved for the whole week. Those two day bkps are during working hours but they might be of importance (a couple of times they have been!). End of morning might save the work done during morning hours and the end of afternoon bkp the work done during business hours (if e.g. a bigger upload is done in the evening and something goes wrong). System is still being constantly developed - new versions are changed 3-5 times a year and some parts then at least the same amount. So at least we get fresh compressed copies quite often Version change in FM based big system is quite interesting... Everything goes with push of a button but requires quite a lot prework so that scripts will eventually do all the imports, possible relookups, replacements, etc. bits & pieces required for putting the data to the new version, incrementing the record id:s, making the comressed clones, putting all in zip (rar) and into extranet. No way doing that all manually anymore...
  11. One of our customers is having quite large FMS/FMP6 client/server solution (sales mgmt & control). There are approx. 40-60 simultaneous users online every day from 4-6 different locations. There are four applications under the same server and file amount is in maximum (124 files, each application having 31 files). Each app. has 1-1,5 million recors. About 100000 records are updated per week, ab. 10000-50000 new records created per week (in two out of four applications, two are just for training & testing of new functionality). Recently we've got few Error messages in Win2000 server log (& FMS log) saying Could not pause file "filename.fp5" because of an outstanding database lock from guest "username". The times when those messages occur are sometimes round the FMS bkp schedule times and sometimes when someone is doing a massive record loading/updating. But we have not found a real reason why this message occurs. It does not seem to make anything wrong or failing. HAVE YOU EXPERIENCED ANY SIMILAR OR DOES SOMEONE KNOW THE REASON or maybe even some solutions not getting those messages. Server is HP Proliant 1,4GHz, 1G RAM, RAID 1, etc. so that is quite enough. More problems causes actually nw connections and the delays in those... But that is an other topic. Thank you for any additional information
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.