span8
span4
span8
span4
When experiencing this issue,the Web User Interface will appear blank or contain a 404 error.As well,you will not be able to access FME Server from FME Desktop or via any other means.
All FME services will be running and there will not be any error messages in the FME Server log files.However,if you were to look at the web application server logs,you may see an error.
For an express installation,the Tomcat log files can be found in
You will likely see the error message below: java.lang.Exception: Socket bind failed: [730013] An attempt was made to access a socket in a way forbidden by its access permissions.
This occurs when a program is using the port you are trying to connect to - likely port 80.It is possible that a service has started on the system which is using the desired port and has taken priority over FME Server.
To view applications using specific ports,you can use netstat:
Netstat is also available for Linux:
Disable services that are using FME Server's port,likely port 80.On Windows,these may include Internet Information Services (IIS),World Wide Web Publishing Service,Windows Remote Management and Skype.On Linux,there may be web servers such as Apache (httpd) or nginx.
X-Frame-Options header | FME Server Clickjacking prevention
End Client Sessions when Tomcat Restarts
Problem Publishing to FME Server using Web Connection
Request times out: Network error between Tomcat and FME Server
3 Machine Distributed Installation
FME Server Database Service Won't Start with Error 193: Not a Valid Win32 Application
Out of Memory Error on FME Server Web Page (2011 and previous)
Removing the Database Service dependency for the Core
FME Server with IIS/Tomcat integration: 401 Error
Shared Resources not accessible when workspace run on FME-Server
© 2019 亚搏在线Safe Software Inc |Legal