span8
span4
span8
span4
This article applies to FME 2015 and older.
When uploading a workspace from FME Workbench to FME Server,one of the following errors is encountered:
Error occurred during configuring services or workspaces: COM.亚搏在线safe.fmeserver.api.FMEServerException: QSMessageReadFailedAn existing connection was forcibly closed by the remote host
Publish failed - FME Server encountered an error and reported the following message.Additionally,the processMonitor log indicates the FME Server Core is attempting to restart with an entry similar to the following:Request to <host_url> returned status code 503 Could not read FME Server response message.Connection may have been lost.An existing connection was forcibly closed by the remote host
Thu-16-Jan-2014 02:19:28 PM WARN Core 393562 : Process "Core" ended unexpectedly.Being restarted on attempt 1...
These errors may be the result of a conflict when loading the necessary DLLs on the host system.The conflict may appear in the path environment variable of the host system when other enterprise software applications are also installed.
Option 1
Update your system's path environment variable so that the following path is at the start:
C:\Program Files\FMEServer\Server\lib\fmeutil
Try publishing the workspace again.
Option 2
Copy these files:
from C:\Program Files\FMEServer\Server\lib\fmeutil to C:\Program Files\FMEServer\Utilities\jre\bin
Try publishing the workspace again.
Data Download Link Returning 404 Error
Workspace (FME 2012) Published to FME Server 2013 Does Not Register to Notification Service
Data Upload Part 1: Read Data from a URL
Data Upload Fails to Work after Modification of the FME_DATA_REPOSITORY Value
Including additional files in the data download result zip file
Streaming GeoJSON with FME Server
Unable to Run Workspaces Registered to Notification Service When SSL is Configured
403 Forbidden Error When Making FME Server Request
© 2019 亚搏在线Safe Software Inc |法律