Skip to main content
  • EN

Like a poster who previously posted a similar question moving from 2015 -> 2016

My WFS reader has suddenly stopped working in 2019 moving from 2016.

I get the following error message 

Sending HTTP 'GET' request to 'http://spatial.bom.gov.au:80/cgi-bin/mapserver/users/bomw0296/wxs?SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&TYPENAME=IDQ65470_wtr_lvl&NAMESPACE=xmlns%28%3Dhttp%3A%2F%2Fwww.opengis.net%2Fwfs%29&MAXFEATURES=1000', waiting for response ...

Parsing XML document 'http://spatial.bom.gov.au:80/cgi-bin/mapserver/users/bomw0296/wxs?SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&TYPENAME=IDQ65470_wtr_lvl&NAMESPACE=xmlns%28%3Dhttp%3A%2F%2Fwww.opengis.net%2Fwfs%29&MAXFEATURES=1000'

HTTP transfer error: 'Couldn't connect to server'

XML Parser error: 'Error in input dataset:'http://spatial.bom.gov.au:80/cgi-bin/mapserver/users/bomw0296/wxs?SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&TYPENAME=IDQ65470_wtr_lvl&NAMESPACE=xmlns%28%3Dhttp%3A%2F%2Fwww.opengis.net%2Fwfs%29&MAXFEATURES=1000' line:1 column:1 message:invalid document structure'

The XML Module halted on error, see the logfile for details

<WFS> An error occurred while reading a GetFeature response, to ignore the error and avoid losing the previously read features, set the WFS "Ignore GetFeature Error" parameter.  Total features downloaded: '0'

A fatal error has occurred. Check the logfile above for details

Is that a connection issue?   Even though it's working when setting up the reader and obtaining the schema?   If I paste that WFS request into a browser it is almost identical from what is requested from FME2016.  BTW that WFS is IP filtered.  If you try at your end you will be asked for a login.

Hi @peterkt

 

 

I tried to access this WFS in the browser, but a loing and passwod was requered.

Do you have these informations?

 

Thanks,

Danilo

 

I'm also presented with a password dialog like Danilo reported, and get a 401 Authorization Required error. You will need to add login credentials to FME's WFS reader settings in order to read features from this WFS.

It's important to remember that just because your browser doesn't show you a login doesn't mean FME can access the URL. It may be that you logged in with your web browser some time in the past and your browser remembers the login / authentication. FME does not automatically inherit this from your browser.

One way to test your browser to see if there is a login requirement is: try another browser (say IE if you normally use Chrome) or try a new private window which won't make use of any exiting cookies. In this case it is clear that FME requires security credentials, and if you were to try FME 2016 on the same WFS server you would have similar problems.

For more info on how to troubleshoot a WFS connection see: https://knowledge.safe.com/articles/19452/troubleshooting-wfs-errors.html

I'm also presented with a password dialog like Danilo reported, and get a 401 Authorization Required error. You will need to add login credentials to FME's WFS reader settings in order to read features from this WFS.

It's important to remember that just because your browser doesn't show you a login doesn't mean FME can access the URL. It may be that you logged in with your web browser some time in the past and your browser remembers the login / authentication. FME does not automatically inherit this from your browser.

One way to test your browser to see if there is a login requirement is: try another browser (say IE if you normally use Chrome) or try a new private window which won't make use of any exiting cookies. In this case it is clear that FME requires security credentials, and if you were to try FME 2016 on the same WFS server you would have similar problems.

For more info on how to troubleshoot a WFS connection see: https://knowledge.safe.com/articles/19452/troubleshooting-wfs-errors.html

That service has IP filtering and usually works without a password. I added the login details and it works now.

 

Was able to find solution after I was supplied with alternative login details that didn't work with our IP and using the details it worked.

So something might be happening with IP address when using FME2019. But whatever the reason it works by filling in the details.

This is still an issue for me - any workspace using a WFS reader no longer works in 2019 or 2019.1, absolutely fine in 2018.0.

 

All run on the same machine using the same workspace, the only difference is the version of the software.

Can we get this looked at please - I've had to re-install 2018 to get updated data and its a pain having so many version of the same software on the same machine (using 32 and 64 bit versions as well)

This is still an issue for me - any workspace using a WFS reader no longer works in 2019 or 2019.1, absolutely fine in 2018.0.

 

All run on the same machine using the same workspace, the only difference is the version of the software.

Can we get this looked at please - I've had to re-install 2018 to get updated data and its a pain having so many version of the same software on the same machine (using 32 and 64 bit versions as well)

Hello @cwinfield

Are you able to share the workspace or the WFS Server URL itself that works in 2018 but does not in 2019?

 

 

If you would prefer not to share it on the forums, you could create a case here: https://www.safe.com/support/report-a-problem/ and we can take a look to see exactly what is occurring.

 

This is still an issue for me - any workspace using a WFS reader no longer works in 2019 or 2019.1, absolutely fine in 2018.0.

 

All run on the same machine using the same workspace, the only difference is the version of the software.

Can we get this looked at please - I've had to re-install 2018 to get updated data and its a pain having so many version of the same software on the same machine (using 32 and 64 bit versions as well)

We are having the same issue, i.e. WFS reader works in 2018 but not 2019. Has any progress been made on resolving this?

 

-- sorry, just re-tested using 2019.2 and the problem is resolved.

Hy !

Same here !

I have a Wfs Connection(User&pw known) which works on 2017 but not on 2019 !

Always getting:

HTTP transfer error: 'SSL connect error'

Hy !

Same here !

I have a Wfs Connection(User&pw known) which works on 2017 but not on 2019 !

Always getting:

HTTP transfer error: 'SSL connect error'

Hi @virtual

Ca you try the latest 2019.2 release and let me know if you are still encountering the issue?

Reply


Community Stats

30,109
Posts
114,302
Replies
37,745
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.