I've read through the last 60 days of posts to this forum but I didn't see any similar threads. Forgive me if this is a repeat.

Anyone else having issues with FMSA 9 crashing out about once per week? Our installation tends to choke once a week. Sometimes existing connections are terminated and sometimes they persist but the server doesn't show any available hosted databases when a new connection attempts to load a database.

The server service is running fine on the server and no event log errors have been logged when this happens. In cases where existing connections are terminated, the FM service is running fine as well. The service has to be stopped and restarted for the environment to come back into service.

This is running on a Windows Server 2003 Enterprise system with SP2. 4 gig of RAM and 2 Xeon 2.8 GHz CPUs. I don't think it's under powered for FM duties.

Right now, FMSA is only hosting 3 databases. We haven't migrated over any other databases to this server since it's been flakey.

Anyhoo.... Just curious if I'm the only one or if this is an issue FM may be aware of and working on a fix for in an upcoming update.

Thanks

David Wolfe

Indianapolis, Indiana

We have been having some of the same issues. We really cannot pin it down. We will come into the office in the morning and our server will be down (FM Server 9 Advanced.) We restart the server and everything seems to be working fine. This has happened about 3 times already. We have noticed we have an error message that has something to do with ntdll.dll conflict and we are exploring further.

By the way, we are running IWP off this box. Are you running that as well.. Looking for something common that might be crashing the server.

Thanks Stu

Edited September 5, 200718 yr by Guest

IWP is enabled on the server but none of the three databases we have hosted on it are using IWP at this time. All our connections are coming from fat clients.

I have not seen any error about ntdll.dll being to blame.

We also usually see the problem after an idle night. The service never seems to dump out during the day when there is activity. Only after a night of idleness and in the morning we'll find the service unresponsive too.

I have never used Server 9 but, you might look for the following: Anti-Virus software checking the FP7 files(exclude them from any scans), a system backup that accesses the FM7 files (no backup should ever run on the hosted files except filemakers). I mention these two things becuase time and again I have seen them crash fm servers.

If the person setting up the server for you did not specificlly look at these two things, that is most likely the problem. (anti-virus and back-ups are both good things but default installs of these things access filemaker files, this causes corruption, with enough corruption the files will crash)

Thanks for the advice. I added the AV exclusion and backup exclusions. Wasn't an issue with our v8 server but maybe v9 is more finicky.

I'll reply in a week or so and let you know how things turn out.

David

I have never used Server 9 but, you might look for the following: Anti-Virus software checking the FP7 files(exclude them from any scans), a system backup that accesses the FM7 files (no backup should ever run on the hosted files except filemakers). I mention these two things becuase time and again I have seen them crash fm servers.

If the person setting up the server for you did not specificlly look at these two things, that is most likely the problem. (anti-virus and back-ups are both good things but default installs of these things access filemaker files, this causes corruption, with enough corruption the files will crash)

Nope. That doesn't seem to have helped. Our FM server was offline this morning. Here are some points about the service failure:

1. The FM server service in the Services Console still shows as active and running.

2. This is probably because fmservicewrapper.exe (the process launched by the FM Server service entry) is still a running process on the server even though the FM server is down.

3. fmserver.exe is no longer a running process. This is a child process normally launced by fmservicewrapper.exe.

4. Obviously, port 5003 is no longer an active listen port on the server after the FM server failure.

5. There is no kind of failure notice at all in either the System event log or the text logs maintained by FM Server in "Program FilesFileMakerFileMaker ServerLogs".

It's a real head scratcher. For some reason, fmserver.exe is just dumping out and saying "I give up".

David

Anyone else having issues with FMSA 9 crashing out about once per week? Our installation tends to choke once a week.

This is a known issue; however it has been heretofore thought to occur only on OS X.

You are running on a non-supported OS, but I'd initiate a tech Support case with FMI just in case this crashing is also a cross platform issue.

Steven

Hi

We are having exactly the same issues. We have had FMSA 9 installed on Windows Server 2003 SP2 fro a few weeks tersting one set of databases before we migrate. It has crashed 3 times at about 10 days apart. The first time it was the fmswpc sevice the subsequent 2 were the fmserver. it seems to be in idle time over the weekend when it goes down. Although we have Advanced installed we havent even started using thew web side yet. The error always refers to faulting module ntdll.dll

We have the same problem with 2003 server. IWP ,ODBC and PHP are also in use. Serveur crash now every night with this message in system event viewer 'In French: Application défaillante fmserver.exe, version 9.0.1.84, module défaillant ntdll.dll, version 5.2.3790.3959, adresse de défaillance 0x0004afb2 '.FMP Service is always running with no connection possible. On 2003 server we have another data base running (firebird)?

After Friday's crash, I upgraded an FM client that was running as a scheduled task on another NT server that hit the FM9 server every hour. This client runs under a specific AD account that is checked for in the Startup script and an automated process runs (a data export) and the client exits afterwards.

Previously, the client was an FM8 client. Now, it's an FM9 client. I doubt that is an issue but we'll see how it goes now.

We've had the same problem, although we appear to be lasting about 2 weeks at a time.

Contacted FM support, who says that they're still trying to identify the problem.

We're getting a Dr. Watson error, but nothing else - and the problem occurs while users are connected for us.

Pretty serious problem that I hope is addressed quickly!

Pretty serious problem that I hope is addressed quickly!

Yep. I agree. So serious that after this morning's crash I have given up on FM9 Server until an update is released. All of my databases have been moved back to our old FM8 server. I'd hate to be in the position of having upgraded an existing box. I'm glad I chose to put FM9 Server on new hardware.

David Wolfe

Indianapolis

I can report much the same thing. Win 2003. lasts a day dies at night. Very strange. I get the following error on reboot:

Event Type: Information

Event Source: Application Error

Event Category: (100)

Event ID: 1004

Date: 9/12/2007

Time: 9:05:51 AM

User: N/A

Computer: LON-FEP-ADMIN1

Description:

Reporting queued error: faulting application fmswpc.exe, version 9.0.1.74, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0004afb2.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 41 70 70 6c 69 63 61 74 Applicat

0008: 69 6f 6e 20 46 61 69 6c ion Fail

0010: 75 72 65 20 20 66 6d 73 ure fms

0018: 77 70 63 2e 65 78 65 20 wpc.exe

0020: 39 2e 30 2e 31 2e 37 34 9.0.1.74

0028: 20 69 6e 20 6e 74 64 6c in ntdl

0030: 6c 2e 64 6c 6c 20 35 2e l.dll 5.

0038: 32 2e 33 37 39 30 2e 33 2.3790.3

0040: 39 35 39 20 61 74 20 6f 959 at o

0048: 66 66 73 65 74 20 30 30 ffset 00

0050: 30 34 61 66 62 32 04afb2

I get this message in sys event log

Event Type: Error

Event Source: Application Error

Event Category: (100)

Event ID: 1000

Date: 9/11/2007

Time: 3:41:11 AM

User: N/A

Computer: LON-FEP-ADMIN1

Description:

Faulting application fmserver.exe, version 9.0.1.84, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0004afb2.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 41 70 70 6c 69 63 61 74 Applicat

0008: 69 6f 6e 20 46 61 69 6c ion Fail

0010: 75 72 65 20 20 66 6d 73 ure fms

0018: 65 72 76 65 72 2e 65 78 erver.ex

0020: 65 20 39 2e 30 2e 31 2e e 9.0.1.

0028: 38 34 20 69 6e 20 6e 74 84 in nt

0030: 64 6c 6c 2e 64 6c 6c 20 dll.dll

0038: 35 2e 32 2e 33 37 39 30 5.2.3790

0040: 2e 33 39 35 39 20 61 74 .3959 at

0048: 20 6f 66 66 73 65 74 20 offset

0050: 30 30 30 34 61 66 62 32 0004afb2

I get this e-mail from system

FileMaker Server 9.0.1.132 on LON-FEP-ADMIN1 reported the following event:

Wed Sep 12 08:52:29 BST 2007 FMS ERROR wpe1

Some problems were detected in the WPE COMPONENT: COMPONENT IS NOT RESPONDING.

I have turned off firewall but no effect. My server also runs microsoft SQL and IIS but apart from that is only hosting FM. Im baffled, the error on startup also concerns me as a simple reboot may not fix the issue - sometimes i have to start the service from the admin panel manually.

Any ideas?

[color:red]All you fellows be sure to open Tech Support cases with FileMaker, Inc. and get a case number. They need to know this is happening, happening on Windows OS, and happening to more than just one or two installs.

Steven

I just found this additional FMSA uninstall guide which lists additional info I did not have at time of upgrade, maybe if Id followed this I would be OK specifically IIS stuff etc. Any thoughts.

in installing FileMaker Server 9 and FileMaker Server 9 Advanced. If you run

into any issues with the installation or configuration please refer to the

information listed below for additional assistance:

Before Installing FileMaker Server 9 or FileMaker Server 9 Advanced

1.

Read Chapter 1 of the FileMaker Server 9 Getting Started Guide.

2.

Remove FileMaker Server 8 or FileMaker Server 8 Advanced using

the 8.0 uninstaller.

3.

Open the FileMaker Server install folder and make sure no other

folders remain except Data (which has your databases) and xslttemplate-

files. If any folders like Admin/Conf or web-server-support

remain, clean them manually before you begin the installation. The

Windows operating system might prevent you from deleting files, when

some processes are using it or if the files are open. If this happens,

reboot your machine and then delete the files.

Reboot before next installation: Also, as a rule of thumb you should reboot

the machine after an uninstall and before the next installation.

FileMaker Pro: Make sure FileMaker Pro is not running when you install

FileMaker Server 9, there are port conflict issues. If you installed FileMaker

Server 9 while FileMaker Pro was running it is necessary to uninstall

FileMaker Server 9 and reboot your computer before reinstalling.

Check IIS and Apache for any left over configurations:

●

On IIS, Open Default web site and make sure fmi-test and Jakarta are

removed.

●

On Windows Server 2003, check under Web Service Extensions and

make sure PHP and FMI Web Publishing are removed.

Right click on Default Web Sites > properties

[color:red]All you fellows be sure to open Tech Support cases with FileMaker, Inc. and get a case number. They need to know this is happening, happening on Windows OS, and happening to more than just one or two installs.

Steven

Unfortunately for us, our company, in it's infinite wisdom, did not purchase a support contract with our upgrade to FM9.

I love the glorious world of outsourcing. Sure we're stuck in the water but we SAVED 4 dollars! That's all profit, baby!

David Wolfe

Indianapolis

I just got the same problem here..

I use Windows 2003 Server Standard with SP2

This is my email (in french) from the system :

----------------------------------

FileMaker Server 9.0.1.140 sur SEPT-SERVEUR a signalé lévénement suivant :

Thu Sep 13 16:57:12 EDT 2007 FMS ERROR wpe1

Des problèmes ont été détectés dans le WPE COMPONENT: COMPONENT IS NOT RESPONDING.

FileMaker Server vous a envoyé cet email automatiquement. Contactez l'administrateur si vous ne souhaitez plus recevoir ces notifications :

...

...

-------------------------------------

About twice a week.. when server idle..

I have invited the attention of appropriate persons at FMI to this issue, now apparently cross-platform in nature.

Steven

I was experiencing a similar issue (running on Server 2003), however I was server 8 that was encountering the problem. Once I disabled shadow copy service from that server, unchecked the nightly backup from backing up the FileMaker files and did not let Symantec AV scan the FilMaker subfolders the problem went away. Not sure if this is at all related to the problems being discussed here but it might be worth a try.

"Once I disabled shadow copy service from that server, unchecked the nightly backup from backing up the FileMaker files and did not let Symantec AV scan the FilMaker subfolders the problem went away."

Glad you worked it out Ron. This is almost a text-book example of how NOT to set up a FM Server! :

Shadow Copy and active anti-virus scans should not be run on FMS servers. They both interefere with I/O and cache to disk activities.

Glad you disabled these. I never even thought to ask, since these should never be enabled.

A good reminder.

Steven

This is a known issue; however it has been heretofore thought to occur only on OS X.

I'm having this issue on my OSX server, the IWP process is crashing and a server reboot is the only thing that brings it back. Do you have any more information on this? Any solution, or should I report it? Wait for a for fix?

Oh, and sorry to hijack this thread.

It's a known issue. However you could open a Tech Support case on it. The more, the merrier, I suppose.

Steven

When I started having these issues, I looked on this forum and didn't see any threads so I figured it was just me. But, we are having the EXACT same issues with Server 9 Advanced that most of you are experiencing.

Our server stops hosting files about once a week, and when you re-start the service, they hosted database files don't show up on the console. My first shut-down occurred on July 21, 2007 and it's been happening almost every weekend.

Here are the specs on our install and the Windows error message:

-IWP and PHP are on. ODBC is off.

-We have about 10 users accessing the server.

-Shadow Copy is off.

-Run backups on the backup folder, not the folder with the hosted files.

-Run TrendMicro anti-virus.

-We turned off File/Print Sharing for about a month. But we still had the same shut-downs.

This week I also turned off checking for Java updates (I'm trying to turn off every automated task that runs once-a-week).

We'll see if the Server stops hosting files again over the weekend.

Any help or additional suggestions would be greatly appreciated.

Kind Regards,

Joe Gonzalez

Austin, Texas

OS Name Microsoft® Windows® Server 2003, Standard Edition

Version 5.2.3790 Service Pack 1 Build 3790

System Manufacturer Dell Inc.

System Model PowerEdge 2950 w Two Xeon Dual Core Processors

System Type X86-based PC

Total Physical Memory 4,096.00 MB

ERROR

Event Type: Error

Event Source: Application Error

Event Category: (100)

Event ID: 1000

Date: 9/15/2007

Time: 8:16:28 AM

User: N/A

Computer: ACCDFMSA

Description:

Faulting application fmserver.exe, version 9.0.1.84, faulting module ntdll.dll, version 5.2.3790.1830, fault address 0x000396d0.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 41 70 70 6c 69 63 61 74 Applicat

0008: 69 6f 6e 20 46 61 69 6c ion Fail

0010: 75 72 65 20 20 66 6d 73 ure fms

0018: 65 72 76 65 72 2e 65 78 erver.ex

0020: 65 20 39 2e 30 2e 31 2e e 9.0.1.

0028: 38 34 20 69 6e 20 6e 74 84 in nt

0030: 64 6c 6c 2e 64 6c 6c 20 dll.dll

0038: 35 2e 32 2e 33 37 39 30 5.2.3790

0040: 2e 31 38 33 30 20 61 74 .1830 at

0048: 20 6f 66 66 73 65 74 20 offset

0050: 30 30 30 33 39 36 64 30 000396d0

Stay tuned. As I said, they are aware of this.

Steven

Hello,

I'm having the same issue here... i tried the new update to 9.0.2 but that didnot help as well!

Faulting application w3wp.exe, version 6.0.3790.3959, faulting module ntdll.dll, version 5.2.3790.3959, fault address 0x0004afb2.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 41 70 70 6c 69 63 61 74 Applicat

0008: 69 6f 6e 20 46 61 69 6c ion Fail

0010: 75 72 65 20 20 77 33 77 ure w3w

0018: 70 2e 65 78 65 20 36 2e p.exe 6.

0020: 30 2e 33 37 39 30 2e 33 0.3790.3

0028: 39 35 39 20 69 6e 20 6e 959 in n

0030: 74 64 6c 6c 2e 64 6c 6c tdll.dll

0038: 20 35 2e 32 2e 33 37 39 5.2.379

0040: 30 2e 33 39 35 39 20 61 0.3959 a

0048: 74 20 6f 66 66 73 65 74 t offset

0050: 20 30 30 30 34 61 66 62 0004afb

0058: 32 2

i have tried everything possible and followed this thread but nothing works, it was fine last morning, do you have any suggestions please? this is very urgent. thankyou

Edited September 30, 200718 yr by Guest

hello,

i'm not very sure, but this problem was not related to any performance or hardware issue.. (i'm running FMSA 9 at VPS, with 512MB RAM and shared CPU).

in my case it was related to permissions of IIS's Default Application Pool , (depends on where is your jakarta/fmi-test virtual directories installed)..

right click at your application pool > properties > identity > change it to "Local System"

this way might have security issues but in my case at i need it running at any cost and this was the only way that made it work for me.

Also the problem seemed to be fixed byself, if i changed ASP.NET version to "v2" then back to "1.1", it worked temporary until the server restarts and then again it doesnt work.

only changing the Identity of the application pool fixed it for me.

hope this will help! thanks.

Edited September 30, 200718 yr by Guest

From my understanding, I received an email from FM tech support which says that they beleive the issue has been fixed in the FM server 9 v.2 update.

Stu

Anyone else have any information on whether or not the new FM9 Server update corrects this problem?

I've gotten no feedback from tech support at all.

Edited October 5, 200718 yr by Guest

We just upgraded from FMS8A to FMS9A and did the 9.0v2 update. The Web Engine quit working 3 days after installation. Restarting Apache got the Web Engine running again.

So it appears to me that the v2 update did not solve the problem.

FMS9 is running on Win2003 and FMS9A web engine and apache are running on OS X Server 10.4.11.

I've got the same error:

"Tue Jan 08 11:19:46 EST 2008 FMS ERROR wpe1

Some problems were detected in the WPE COMPONENT: COMPONENT IS NOT RESPONDING."

and need to reboot all services several times a day, depending on how much traffic do I have.

FMSA 9's Web Pubilishing Engine seems to simply hang-on.

Is anyone found a solution?

Be sure that both the database component and the WPE component are 9.0v2.

Steven

How Can I be sure of that?

I can read Server Version : 9.0.2.151

Look for the WPE executable and do a Get Info or a right click Properties on it.

Steven

Look for the WPE executable and do a Get Info or a right click Properties on it.

Steven

FM Web Publishing application 9.0 v2

(Library > filemaker Server > Web Publishing > publishing-engine > wpc)

we are having the same problem with IWP crashing every 4 days or so and we have the latest update v2. Now we are trying a scheduled task to close the databases and all associated services, then copy our backups manually then restart the services. Below is the batch file.

@echo off

REM shuts down IIS Service

net stop w3svc

REM disconnects all clients from filemaker databases and gives them 120 seconds to comply

"C:Program FilesFileMakerFileMaker ServerDatabase Serverfmsadmin.exe" disconnect --yes --grace-time 120 -u administrator -p lou1948

REM closes all open databases

"C:Program FilesFileMakerFileMaker ServerDatabase Serverfmsadmin.exe" close --yes -u administrator -p lou1948

REM stops the database server

"C:Program FilesFileMakerFileMaker ServerDatabase Serverfmsadmin.exe" stop --yes -u administrator -p lou1948

REM shuts down filemaker service

net stop "FileMaker Server"

REM makes backup copies of all databases and puts the files in folders for the seven days of the week

xcopy "C:Program FilesFileMakerFileMaker ServerDataDatabasesTothOS*" "D:BackupsFilemaker Daily Backups%date:~0,3%*" /Y /Q /S

REM turns on IIS Service

net start w3svc

REM turns on filemaker service

net start "FileMaker Server"

REM may not be needed because starting filemaker service should start the database server

REM "C:Program FilesFileMakerFileMaker ServerDatabase Serverfmsadmin.exe" START SERVER --yes -u administrator -p lou1948

REM may not be needed because all databases should be open by default

REM "C:Program FilesFileMakerFileMaker ServerDatabase Serverfmsadmin.exe" open --yes -u administrator -p lou1948

REM reboots the server if any error is encountered

iisreset /restart /timeout:180 /rebootonerror

Everyone having these issues please report them to FMI.

Steven

This issue is directly related to the amount of requests on FMS.

It might be worthwhile to do a network trace to see what types of packets are being received by FMS around the time of the crash. Examination of network trace results ultimately led to a better understanding of what was causing older versions of FMS to unexpectedly stop responding, as documented in the "It happened again: Lost host on network" thread in this forum.

Back then, it was random network delays in the delivery of UDP response packets from FMS to the client during the discovery phase of a client connection that were generating Internet Control Message Protocol (ICMP) port unreachable packets back to FMS; receipt of these ICMP packets would cause FMS to stop accepting new client connections. The only solution was to stop and restart the FMS service.

This problem was occurring for those who had upgraded to W2K or W2K3 servers from Windows NT servers; Windows NT did not pass these ICMP messages back to FMS, whereas W2K and W2K3 did; the versions of FMS in question (I believe it was affecting FMS3 to FMS5) were not programmed to handle receipt of ICMP messages.

The network traces were especially useful because you could see that, as soon as an ICMP packet was received, FMS would no longer respond to any more UDP packets received from clients who were attempting to connect.

The failure would occur each time a FMS response packet (UDP) would take longer than one second to traverse the network to a client anywhere on the network who was attempting to connect to the FMS. Normally, this wasn't a problem, as the traces showed that the FMS response packets are typically received by a client in well under 1 second. But randomly occurring heavier-than-usual network traffic could cause delays leading to the failure, especially when clients in regional locations (where network distances are greater) were attempting to connect.

As far as I could determine at the time, as of the version 7 product line, FMP and FMS no longer rely on a mutual exchange of UDP packets to establish a client connection, so the current issue reported in this thread likely doesn't have anything to do with UDP, but there may be some similar mechanisms at play with other packet types. I'm not currently in a work environment where FileMaker is used, so I can't do any testing with the more recent versions described in this thread.

Admittedly, the product versions are very different, but there are enough similarities in the symptoms described here with those in the earlier thread to suggest that a network trace might be revealing.

Edited February 8, 200817 yr by Guest

I installed FMS 9.0v3 for the first time last night. I haven't had any crashing problems after install but the installation was troublesome.

After installing I kept on getting a Database Won't Start... error or some message to that effect. Turns out that the reason that the DB wouldn't start is because the license was already in use on the network. Earlier in the week I had installed FMS on a virtual machine so that I could be familiar with the install process and could do some testing. I forgot to turn the test box off.

But how did it know that the license was already in use? It must have done some kind of broadcast on the LAN looking for a license with the same value.

Now this makes me wonder if perhaps FMS does a periodic broadcast on the LAN (weekly maybe) looking for another server with the same license. If it is doing this broadcast then maybe there are issues of the type that Zardoz speaks of involved with Filemaker once again. I'm not saying that the reason for the trouble is because of two licenses in use at the same time, maybe it is because the broadcast or the return message simply gets messed up and the result is that FMS goes down.

Zardoz has made an excellent suggestion. Maybe someone having this trouble can check the packets.

PS. I hope it doesn't end up being me.

I also get faulty ntdll module... Does v3 solve this problem? Ted, anyone? Replies much appreciated.

/Thanks!

(I run fms9v2 today. Solution runs fine at one place with approx 10 users, but crashes at another with 15-20 users.)

HI,

I've installed 9.0v3 tonight (on Win 2003 Ent) and it just made more problems for me.

outside everything SEEMS to work fine, BUT fmsadmin still have 9.02.151 as its version and WPE as WS seems to be down (although they are not).

AND fmsadmin keep sending me errors while the event viewr does not show any error nor warnings.

SO...If I were you...I'll wait.

Hope I could revert the installation..

Anyone else encountered an issue wityh 9.03?

Ouch, did you upgrade because you had ntdll issues or for some other reason?

If I do upgrade, I think I will do an uninstall and reinstall with a complete v3 install (without upgrade) if I can find one.

Yeap, once in several days I had the ntdll crash, and one of the fixes in update 3 is this issue.

But apperantly it causes more problems then it fixes

Thanks for a quick answer! I will try a complete v3 re-install this week, no upgrade - hope that eliminates the issues you have encountered.

I've installed 9.0v3 tonight (on Win 2003 Ent)

Enterprise is not an approved OS. Use Windows Server 2003 Standard Edition SP 2.

Steven

Thanks for a quick answer! I will try a complete v3 re-install this week, no upgrade - hope that eliminates the issues you have encountered.

Tompa79... how'd it go. Did this fix your issue??

We have the same problems here as quoted above in many other posts. Running WinServer2003 std.

Haven't opened a ticket with FM yet but guess I will.

Thanks,

JB...

I ahve a strange workaround...2 week now working perfectly..

1 - install the v2 update

2 - install the v3 update

3 - install the v2 update

after the last v2 update the version stays v3 and the v3 problems goes away and the ntdll is now stable...strange I know, but its working

Actually, I did not install v3 until last night. The v2 server ran fine for approx, 2-3 weeks but then ntdll error occured again - but now I removed v2 from the computer and installed a fresh v3 - hopefully this will work.

If I stumble upon anything with ntdll again with this server I will leave a post here...

BTW, you can use FMS9v3 Trial availiable from filemakers website if you don't have a complete v3 install file - just change the pre-entered trial serial to your bought license key. Very nice solution - Thanks FMI!

Still running here. Clean v3-install. Installed four weeks ago...