Skip to main content
Solved

|WARN |There are no specified feature types in 'read()'. No features will be read

jorge_vidinha
Contributor
Forum|alt.badge.img+2

Im frequently receiving this warning that forces me to delete postgres or postgis readers and add the readers again. There are cases that forces me to always keep the workspace open otherwise i will need to re-ad readers and set again exposed params. Anyone else noticing similar thing with PG readers ?

Thanks

Jorge

Best answer by mark2atsafe

Hi Jorge (@jorge_vidinha)

I searched for this error message and found a support case with the same error. In that case the support person said:

The behaviour that you are describing here sounds like it matches an issue that has been affecting some of the database readers inside FME. The problem is present in FME 2015 builds 15488 - 15482 and can be difficult to reproduce as it only happens under a specific set of circumstances. This problem was fixed for FME 2015.1.0.3 (build 15483 and higher). So any workspace opened with that newer version should fix itself and start working again

I think that might be a typo in there, and it should be 15478 - 15482. Anyway, could that be the problem? The error message and behaviour is exactly the same. If so updating to a newer FME will probably resolve the issue.

Hope this helps

Regards

Mark

Mark Ireland

Product Evangelist

Safe Software Inc.

View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

mark2atsafe
Safer
Forum|alt.badge.img+44
  • mark2atsafeSafer
  • Safer
  • Best Answer
  • February 23, 2016

Hi Jorge (@jorge_vidinha)

I searched for this error message and found a support case with the same error. In that case the support person said:

The behaviour that you are describing here sounds like it matches an issue that has been affecting some of the database readers inside FME. The problem is present in FME 2015 builds 15488 - 15482 and can be difficult to reproduce as it only happens under a specific set of circumstances. This problem was fixed for FME 2015.1.0.3 (build 15483 and higher). So any workspace opened with that newer version should fix itself and start working again

I think that might be a typo in there, and it should be 15478 - 15482. Anyway, could that be the problem? The error message and behaviour is exactly the same. If so updating to a newer FME will probably resolve the issue.

Hope this helps

Regards

Mark

Mark Ireland

Product Evangelist

Safe Software Inc.

jorge_vidinha
Contributor
Forum|alt.badge.img+2
  • jorge_vidinhaContributor
  • Author
  • Contributor
  • February 23, 2016

Thanks Mark - So i am within the range of bugged versions since im using 15400 and 15482 that is and been bugged by this for long time . Hopefully 2016 updates will come in soon at our sites.

Will keep you posted.

Regards,

Jorge

Helpful Members This Week

Community Stats

31,328
Posts
118,862
Replies
38,956
Members

Latest FME

Terms & ConditionsCookie settings

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
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.