Using a Windows 2003 Server SP1 that meets minimum requirements. I was using FMP Server 7 before with no issues. Now I uninstall Server 7 and install Server 8 and the helper service will not start. I can sucessfully install Server 8 on another 2003 Server with the exact same hardware specs. I can successfully start the Server Service but not the helper serfvice. Any ideas?

Did you completely stop both services before running the remove programs routine? Did you run remove program to delete Server 7 before isntalling Server 8? Did you ever have the trial version of Server 8 installed?

Steven

Thank you for the prompt response. Yes, I did stop both services and run remove programs, turned off the antivirus software before installing Server 8 (the second time). I get a Windows error 1003 when trying to start the server helper service. Filemaker tech support hadn't heard of this problem.... I can install successfully on a a hardware identical server 2003 machine that was not running FMP Server 7. Are there registry entries I should manually remove? Server8 trial was not installed.

Edited August 27, 200619 yr by Guest

The bizarre thing is that the main FMS service can't start without the helper service running...

I would uninstall FMS and then manually delete all FM registry entries, rebooting and reinstalling again.

That is the direction I was going. I will give that a try next time I can shut down the FMP server. The FMP service does start but it stops when you try to start the helper.

Start the helper first. Then the FMS service.

Steven

Still no go on starting the services. I will contact Filemaker support again, they were not helpful the first time.

Still no go on starting up the services. I find that if I try to connect to the server from FMS 8 Admin I get a RunTime Error

MicroSoft Visual C++ Runtime Library

Program: C:WINDOWSsystem32mmc.exe

Instaed of "unable to connect" message.

Any ideas anybody? I have tried all the Filemaker Support ideas....

If I put the FMS 8 on a Windows XP computer is FMS 8 limited to 10 users logged in at the same time?

FMI officially makes the caveat that using XP as an FMS box is subject to the XP licensing terms. But FMI does not expand on it. I've talked to various MS people over the years on this and some say using FMS would fall under the XP 10-user limit, others say it doesn't.

You're saying that the 2003 machine meets the minimum requirements: is all of its hardware on the Microsoft Server HCL? Or is it a no-brand machine with weird stuff in it?

Any other things installed on that machine, like SharePoints?

I am running Filemaker server 7 successfully. How ever when I install FMS Server 8, I cannot start the helper service - I get a 1003 error. I can start the Filemaker Server Service but not the Helper service - 1003 error then the Filemaker erver Service quits. If I try to connect to the FMS thru Filemaker Server Admin I get -

RunTime Error

MicroSoft Visual C++ Runtime Library

Program: C:WINDOWSsystem32mmc.exe

instead of the usual "unable to connect" error which should happen if the FMS Services are not running.

If I install FMS 8 on an identical server it launches fine.

Windows 2003 Server Standard. Both Servers are 512 RAM IBM X206 - They are both the Domain Controller in a seperate Domain. I have Powerchute software installed - from UPC, and Tapeware backup software for Travan tape drive. I was running Etrust server antivirus but I uninstalled that - although the license service is still running.

I have tried disabling other services,( if I disable a service does that rule that service out or do I have to unistall the app that uses that service?) tried adding more RAM, removing old Filemaker references in the Registry.Ran a SpyWare / Virus test.

Did you remove Server 7 before installing Server 8?

Steven

If I install FMS 8 on an identical server it launches fine.

Something's obviously not identical If you can find out what then you're set.

It probably is something very simple that is overlooked but these things are virtually impossible to troubleshoot remotely. FMS in itself is a very simple service to install. But since you have two identical machines, finding the difference shouldn't be very hard. Labor intensive though.

I did uninstall FMS 7 before installing FMS 8. I have been trying to located what is not identical in terms of software (so far TapeWare back up software and UPC PowerChute)and stopping those services. I should uninstall them and clean any Registry values that pertain to them also. I unistalled Etrust Admin software but I see the CA Licensing Service is still running.

Also check the various event logs (application & system) for any signs of things going wrong, compare those to the ones on the other machine too.

I am thinking what I will do is host the FMS 8 on an XP computer and see if that works and keep working to fix the 2003 Server - there must be something wrong with it. It aslo will not update virus definitions for Etrust Anti Virus 7.1 unless I manually stop the InoTask in Task Manger and then restart the Etrust job service.

It is interesting that the 10 user limit is so vague for XP and FMS.

I tried looking at the event logs but could find nothing helpful.

Do not run an active virus scan on hosted file. It will damage them.

Steven

Yes I read somewhere not to run virus scan on the hosted files, although they have been so far. I have changed that. But can I temporarily run FM8 on an XPP or or server 2000 computer until I get the 2003 server fixed?

Yes you can. Server 2000 is fully supported. XP is supported under some circumstances, and I would hate to put it on XP but as a stopgap it's a solution.

Thanks, I will only put it on XPP box if I have to.

So I cleaned up the registry, uninstalled all extra programs, uninstalled FMS 7, installed FMS. Now I get a Data Execution Prevention message for FMS Helper Service. If try to Allow FMS Helper under the DEP setting it still will still not start.

I'm not one to recommend this approach but I think it's time for an OS reinstall. This should not be this hard...

I think you are right. I set up a Windows 2000 server to use as FilmakerServer on the same network and it works fine. I will rebuild the 2003 Server and I am sure it will work also.

Installation of FileMaker Server 8 will fail if the following registry key value is not zero:

HKEY_LOCAL_MACHINESystemCurrentControlSetControlFileSystemNtfsDisable8dot3NameCreation

(Some security templates modify this value.)

You need to set it to 0 and restart your Windows Server before you reinstall FileMaker Server 8.