This post is old but the problem may persist for you, so, in my case, my PC is a little slow and I realized that sometimes FreeFlow Core 6.0 simply does not load and there is no effect trying to restart the FreeFlow Core or SQL services, that is, sometimes I have to restart the PC and wait for it to work the next time. What solved for me was to increase the Windows "service startup timeout" so that it waits longer for the services to start, because if a service does not start within a certain time, Windows kills it and records it in the event log. I think it´s because my PC is a little bit "old and slow".
Bellow are the instructions to modify the registry (https://support.microsoft.com/en-us/help/884495/event-id-7000-appears-in-the-system-log-and-the-isa-...)
To increase the service startup time yourself, create the following registry entry:
Data: The number of milliseconds that you want to give the services to start in.
To create this registry entry, follow these steps:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
Right-click Control, point to New, and then click DWORD Value.
In the New Value #1 box, type ServicesPipeTimeout, and then press ENTER.
Right-click ServicesPipeTimeout, and then click Modify.
Click Decimal, type the number of milliseconds that you want to wait until the service times out, and then click OK.
For example, to wait 60 seconds before the service times out, type 60000.
Quit Registry Editor, and then restart the computer.
PS.: IN MY CASE I CHOOSE 120000 AS VALUE BECAUSE I WANTED 2 MINUTES. YOU CAN TEST CAREFULLY WITH OTHER VALUES.
Fixed Device 412 Missing with another restart - Now however I cannot connect to the server from other computers on the network via web-browsers.
Wondering if the IIS service didn't start, or something else is wrong.
I'll keep this updated as I work through with the VISTTEAM.
Apparently the DB wasn't starting up - Now however when trying to resubmit jobs from the failed queue I get the error "Device 421 not found" as the error...
Has anyone run into this situation before? The computer hosting Freeflow had to be restarted, and now Freeflow itself is stuck in an initialization loop... It's been about 20 minutes now.
Any ideas of what's going on?