This article offers tips and techniques for troubleshooting problems with accessing FrameFlow’s interface when the interface is running on IIS.
Verify the FrameFlow Service is Running
To access FrameFlow’s interface, the FrameFlow service must be running. Use the Windows Service Manager, found in the Administrative Tools section, to verify that the service is running.
Integrated Web Server vs. IIS
FrameFlow includes an integrated web server that is used to deliver the user interface pages. New installations use the integrated web server by default but you can switch to using IIS if you want to take advantage of HTTPS/SSL encryption and other features offered by IIS. If you are running our integrated web server see this article for tips and techniques.
IIS: Check Web Services Are Installed and Running
Use the Windows Service Manager, found in the Administrative Tools, to make sure that the “World Wide Web Publishing Service” it present and running. If not then IIS might have been removed.
Check Application/Virtual Directory
Check Application Pool Settings (64-Bit Only)
Check FrameFlow’s Web Components
If you are still unable to access the interface then use the IIS Manager to remove the FrameFlow application/virtual directory. Your monitoring configuration will still be preserved as you are only removing the link to FrameFlow’s interface in IIS. Then follow the steps in this article to re-do the switch to IIS.