Skip to main content
Solved

FME Server error cannot read SDE connection file for some jobs but can for others


Forum|alt.badge.img

Hey all,

So I am using FME server to run a workspace for multiple GML files. The workspace is taking the GML and transforming it for GEODFATABASE_SDE. Every job runs on same workspace and uses the same SDE connection file.

The issue is that every time I run it FME server runs 21 jobs (1 for each GML file), fails 19 of them and succeeds on 20 of them and writes features to the GDB. It's never the same two files that succeed but the ratio of 19:2 is always the same.

The error message is: An error occurred while attempting to retrieve the connection parameters from the connection file

This is the same on all 19 failed jobs.

I made a workspace runner and used a text file of all the files file paths as the input and ran them all through using that and they all worked fine first time.

I have tried deleting the Writers and re-adding them to make sure there was no issues with them but still the same result, a random 19 will fail and a random 2 will succeed and write features to GDB.

Any help or advice would be greatly appreciated with this, thanks everyone.

Best answer by mikemos

It was a silly mistake. I didn't take into account that our server instances were spread over different VMs and I hadn't fully qualified the file path to the sde file with the VM name. If anyone else has this issue, try looking at that first :p

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

3 replies

sigtill
Supporter
Forum|alt.badge.img+24
  • Supporter
  • August 7, 2019

This might be a limitation on the number of connections towards the database? Or is some of them writing to the same table?


Forum|alt.badge.img
  • Author
  • August 8, 2019
sigtill wrote:

This might be a limitation on the number of connections towards the database? Or is some of them writing to the same table?

Hi,

Some of them are writing to the same table, but on that note we have other workflows that do this same thing and it works without issue.


Forum|alt.badge.img
  • Author
  • Best Answer
  • August 8, 2019

It was a silly mistake. I didn't take into account that our server instances were spread over different VMs and I hadn't fully qualified the file path to the sde file with the VM name. If anyone else has this issue, try looking at that first :p


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