AnsweredAssumed Answered

FileMaker Server built-in VERIFY INTEGRIY schedule fails to re-open all files

Question asked by FileKraft on Aug 18, 2014
Latest reply on Aug 20, 2014 by disabled_ntaylor


FileMaker Server built-in VERIFY INTEGRIY schedule fails to re-open all files


FileMaker Server



Operating system version

Windows 2012 Server 64 bit Standard

Description of the issue

since FMS13v2 until now FMS13v4 i experience that after a scheduled verify all databases run the server doesn't reopen all files. as soon as there was previously a client connecting and have been kicked off - after executing the verify script that file does't reopen.
manually reopening doesn't do it either - error 38 occurs.
restarting the server doesn't fix the situation - no files are showing .

Steps to reproduce the problem

run a verify schedule - before the schedule runs - connect clients to the verified files - when server prompts to kick off user - postpone closing until server disconnects
- verification runs
- file previously touched stays closed

(this scenario might help to reproduce the issue- but the failure also can occur if no-one connected)

Expected result

files open after completion of integrity check (verify schedule)

Actual result

file stays closed - server restart make all setting disappear - only forced restart or reinstall gets things back - but sometimes auto-restart not working anymore - even flag is set - so manual server service start required

Exact text of any error message(s) that appear

error 38

Configuration information

the server is a 8 core 2.4 GHz Intel Atom 2750 with 8 GB RAM and 2 TB Server Hard Drives running Windows 2012 Server 64 bit Standard -
the load is not high - 2 files one 5 MB - the other 1.5 GB

the cache is set to 2 GB

concurrent users max 4 - the file is mostly used to sync - short sessions ..
performing scripts on server ..


force restarting the windows server actually resurrected all settings and files - normal restart didn't do it