Skip to main content
Solved

FME Server 2019.1.2 - The error number from ArcObjects is: '-2147155559'


gfaulkner
Participant
Forum|alt.badge.img

Hi,

We are using FME Server 2019.1.2 and Desktop 2019.0.2 currently. The FME Server instance is located in a VPC (removed environment) and the workbenches exist on organisation internal servers.

We have many workbenches which run fine on schedules, however those with ArcGIS SDE readers/writers are failing due to the following error:

Could not open the Enterprise Geodatabase. The error number from ArcObjects is: '-2147155559'. The error message from ArcObjects is: {Failure to access the DBMS server}

 

It then asks you to check the connection parameters for the SDE connection file being used.

These workbenches have been running fine for months however have failed within the last week.

Can anyone assist?

Thanks,

Grant

Best answer by trentatsafe

Hi @gfaulkner,

Do you by chance have FME Desktop on the Server that you could test if the Server machine is able to access the SDE Geodatabase? As it sounds like possibly a configuration change has been made on the Server that is preventing FME Server from being able to access the DBMS server.

 

 

View original
Did this help you find an answer to your question?

2 replies

trentatsafe
Safer
Forum|alt.badge.img+6
  • Safer
  • Best Answer
  • June 23, 2020

Hi @gfaulkner,

Do you by chance have FME Desktop on the Server that you could test if the Server machine is able to access the SDE Geodatabase? As it sounds like possibly a configuration change has been made on the Server that is preventing FME Server from being able to access the DBMS server.

 

 


gfaulkner
Participant
Forum|alt.badge.img
  • Author
  • Participant
  • June 24, 2020
trentatsafe wrote:

Hi @gfaulkner,

Do you by chance have FME Desktop on the Server that you could test if the Server machine is able to access the SDE Geodatabase? As it sounds like possibly a configuration change has been made on the Server that is preventing FME Server from being able to access the DBMS server.

 

 

Thanks for your response Trent. Turns out it was a new firewall commissioned last week which had not been configured to allow traffic from our VPC.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings