Skip to main content
  • EN

Quite an odd error here. We have one workbench that calls 3 others through the FMEServerJobSubmitter transformer. We are using Named Database Connections as they are shared through the 4 workbenches.

When using one Named Database Connection, we'll call it My_Conn, it works in the 1st Workbench, then the second, but when it is called in the 3rd workbench, there's an error in the workbench, and through going through the logs, it shows as this:

 

 

2016-05-27 15:50:45| 0.3| 0.0|INFORM|Opening POSTGRES reader for dataset 'MY_CONN'
2016-05-27 15:50:45| 0.3| 0.0|ERROR |Error connecting to PostgreSQL database(host='', port='', dbname='MY_CONN', user='', password='***'): 'could not connect to server: No such file or directory

So it is effectively saying the Named Connection is actually the dbname in the connection. It isn't, and this has worked previously in the previous workbench

Any ideas?

Hi @phallett

Thank you for reaching out to our support team. We are looking at this issue now. Once the resolution is found an update will be posted here if relevant to other users.

Thanks,

Brian Pont

Do I have to raise this as an incident with SAFE as this bug is a show stopper.

Hi @phallett

Thank you for reaching out to our support team. We are looking at this issue now. Once the resolution is found an update will be posted here if relevant to other users.

Thanks,

Brian Pont

Hi @BrianAtSafe,

Have there been any findings with regards to this bug, as it is stopping our DTP in its tracks?

Thanks

Paul

Hi @BrianAtSafe,

Have there been any findings with regards to this bug, as it is stopping our DTP in its tracks?

Thanks

Paul

Hi @phallett,

Our development team are currently looking at this problem and I will update you as soon as possible via the support ticket. Once we have a resolution I will add the relevant information back to this page.

Thanks,

Brian Pont

Safe Support

Hello

we've got the same Problem, and the same message (as posted from @phallett):

After adding a postgis reader to an publisched workspace on FMEServer 2016.1, the script doesn't run anymore. On FMEDays 2016 in Germany a developer from ConTerra could identificate the problem.

Our workbench was already running on FMEServer 2015.1 AND was imported via backup-function after upgrading to the newest FMEServer version. It seems there might be problems with the named connections.

The problem can be temporabily solved, when the connection information will be embedded (right click on the reader in the leftside tree-structure) in the workspace (FMEDesktop) and afterwards uploaded to FMEServer.

@BrianAtSafe: Using "Named Connections", I don't want to save the connection in the workbench anymore. So I'm also interested in an solution from you.

Best regards

Bernd

We have been able to replicate this problem whereby a child job cannot access the database connections. In these cases, the parent job seems fine but when it calls the child job with "wait" set to "yes", the error mentioned above occurs.

This has now been fixed in FME 2016.1.1 Build 16604+ which should be made available within the next few weeks.

Reply


Community Stats

30,353
Posts
115,356
Replies
38,088
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.