This article offers tips and techniques for troubleshooting problems with accessing FrameFlow’s interface when the interface is running on IIS.
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.
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.
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.
Next, open the IIS Manager from the Administrative Tools section in Windows. Verify that the application (or virtual directory for IIS 6.0 and earlier) is still present. Verify that bindings are pointing to the original ports (default port 80 for HTTP and default port 443 for HTTPS).
If you are running on a 64-bit version of Windows, check the application pool that is being used by the site. In the Advanced Settings for the application pool, make sure the “Enable 32-Bit Applications” option is set to “True”.
In rare cases the regstration for our web-based components can be reset. When this happens you will see a 500 status code in your browser when you try to access the FrameFlow interface. To re-register them open a command line Window and navigate to “C:\Program Files\FrameFlow”. Then run “regsvr32 /u FrameFlowTokenExpander.dll” and you should see a message that the DLL was unregistered. Next run “regsvr32 FrameFlowTokenExpander.dll” and you should see a message indicating that the DLL was successfully registered. Now verify that you can access the interface with a web browser.
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.