Debugging Windows Service Startup

From Observer GigaFlow Support | VIAVI Solutions Inc.
Revision as of 12:20, 25 October 2018 by Kevin Wilkie (Talk | contribs)

Jump to: navigation, search

Open the task manager. Check if there is a "GigaFlow.exe" application/process running.

If so, select it and then click the "End Task" button.

Open up an administrators command prompt. Navigate to the folder where GigaFlow.exe is located (default:c:\GigaFlow\Flow\resources). Run

GigaFlow.exe -debug

The output of this should tell you what the problem is (i.e. java not installed, no database access or some invalid parameter in the GigaFlow.ini file)

If java hasn't been found, re-run the java installer as sometimes customers try to upgrade the JRE which actually removes it from the registry. If you ran the full installer, the standalone java installer will be available in the dist folder (default:c:\GigaFlow\Flow\dist\jre-8*) Once, this has been installed, rerun the "GigaFlow.exe -debug" to see if the problem has been resolved. If it has, press ctrl-c to stop the debug mode and then re-start the service from the windows service console.

If you have a postgres error, open up the services.msc application to check that the postgres service is installed (postgresql-x64-xxx). If it is, ensure that it is set to start automatically and is running.

If its not installed, you can reinstall using the file in the dist folder (default:c:\GigaFlow\Flow\dist\postgresql-xxxx*) The only thing you will have to set is the postgres user password, this should be "P0stgr3s_2ME"