OLF V5 server stops

[Jemimus]

We have implemented a brand new and fresh install (not an update) of OLF5 server this week. (the previous install was an in-place update)
The second night the OLF FM Server (Firebird) failed to restart at 03:00am, but last night it seemed to be ok.

I will be applying the scheduled task batch file solution until there is an update that fixes this.

[zbang]

Use this patch to resolve the problem

http://www.epoline.org/epoline/products ... ch5022.exe

Regards,
Luigi

[patentato]

I have the same problem after updating to V5. Services not restarting.
I applied patch5022. (patch5017 & patch5023 were installed directly after upgrading to V5)
While most EPO services where running (after 3am), 'EPO OLF FM Server (FireBird)' service wasn't.
So not really an improvement.

[akipelto]

[quote="DPrakopchyk"]We (in the OLF developent team) are trying to find what the issue is with services not starting properly after shutting down at night. Which particular services are not started in the morning? All OLF services or just some particular ones? What is the OS used? Windows Server 2008 or 2008 R2? Did the hint with the scheduled batch file help anyone? Another way to make starting of services more robust is to go to Service properties -> Recovery -> and set "Restart Service" instead of "Take No Action" in the First, second, ect failure combo-boxes.[/quote]

Hello

We have exactly the same problem. For some reason all services other than EPO OLF FMGRDN are shut at 3.00 AM. But this does not happen every day. Sometimes every day, but sometimes there may be a 10 day break between stops. Really annoying.

Recovery options do not help. I have set them to EPO OLF FM server (which supposedly starts others?) but no joy.

Does anyone know really what is the problem?

OLFGuardian_ext-log says: "04-06-2010 03:00:08.273: Message: An error occured in StartService. ServiceName EPO_OLF_FMMNGR_Service. Message: Service starting: The service did not respond to the start or control request in a timely fashion.; Level: 1"
Event log says: "A timeout was reached (30000 milliseconds) while waiting for the EPO OLF FM Server (FireBird) service to connect."

Windows server 2008 STD SP2 (build 6002) with latest updates. Will try epptch5022 also.

[ActiveIT]

It seems the File Manager-service need more than 30 seconds to start.
I solved it by increasing the time allowed for services to start. It has worked fine for two weeks now.

In Registry Editor, locate, and then right-click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
Point to New, and then click DWORD Value. In the right pane of Registry Editor, notice that New Value #1 (the name of a new registry entry) is selected for editing.
Type ServicesPipeTimeout to replace New Value #1, and then press ENTER.
Right-click the ServicesPipeTimeout registry entry that you created, and then click Modify. The Edit DWORD Value dialog box appears.
In the Value data text box, type 60000, and then click OK

Restart the computer.

Link to KB:
http://support.microsoft.com/kb/824344

[charlesbrends]

Use this patch to resolve the problem

http://www.epoline.org/epoline/products ... ch5022.exe

Regards,
Luigi

Thank you very much! You saved me from hours of tedious work. Thanks!

[harper36]

This was the case for V3 too. In both versions at 3 AM a shutdown is initiated by epoline itself and the automatic restart does not work in all cases. In V4 we did not experience the problem.

You can try to install a scheduled task that does a restart minutes later than 3AM.
The command to execute is


net start EPO_OLF_FMMNGR_Service

Good Luck

[vamsika24]

We have installed EPO Online 5.11 on new Azure setup and getting error when starting one of the services.

"Windows could not start the EPO OLF FMGRDN server (FireBird) service on Local Computer

Error 2: The system cannot find the file specified".

We have verified and file is available in C: Drive.