05-01-2018 10:21 PM - edited 05-02-2018 02:24 PM
Our client is using WebMap SDI 2016 EP03. Their WFS services suddenly throw exception below in get feature request, even though the get capabilities document request is working fine.
I check the service log files and the problem seems to happen at the service source, so it doesn't get picked up in the wfs service log file and GWMlog shows fine. However, I am not sure where to look in the service source
Appreciate all suggestions and ideas on the matter
05-02-2018 04:46 AM
I don't understand the sentence 'I check and it happen on in the service source and don't get picked up in the wfs service log file and GWMlog shows fine.' - what did you actually check on the service source?
The error on screenshot clearly says that CollectionDepot layer (feature class) doesn't exist. Can you see it in the capabilities document?
05-02-2018 02:26 PM
Sorry for the confusion, I just updated my content. I do see the CollectionDepot layer in the capabilities document.
05-03-2018 03:12 PM
Some update on the problem. The capbilities document does show the feature.
I repeat the get feature with other features and they returns the same error message "File name is required".
I also check the WFS service source by repopulating it in GeoMedia workspace and it shows no problem
I also use the workspace to publish into a fresh WFS source and I also observe the same error message.
It is noted that wfs log file and GWMLog file don't show any hint of the problem.
05-03-2018 05:35 AM
05-04-2018 09:22 PM
Thank you for checking on this issue. The service source has three database connections (SQL Server Read Only type)
My test shows that the get feature request only throws exception if the feature belongs to GISAFM database, so I believe something wrong in the database. However, it is quite confusing because features in the database are showing just fine when I populate the workspace from the metadatabase.
The WFS log file shows some information about this problem
To sum up, I believe that we narrow down the issue that one of the connections has problem, but we would like to how it causes it.
Appreciate all suggestions,
05-04-2018 02:05 AM
The "File name is required" might indicate a problem in the ExportToGMLService used inside a WFS. I can't tell why this would happen but you can try to hook up ProcMon and watch MapSvr.exe process during the GetFeature request. There could be an indication of what had happened to WebMap not being able to set a temporary file name for WFS.
05-07-2018 10:33 PM - edited 05-07-2018 10:39 PM
Thank you for the suggestion. I am using ProcMon to monitor MapSvr.exe during the GetFeature request but haven't found any suspicious entries, also have a closer look around ExportToGMLService but still nothing stands out. Will look closer.
05-07-2018 06:07 AM
Can you get a detailed GWMLog from such an occurence as well? This way we can better track the place in WebMap's logic when it failed. This might put some light to the problem.
05-07-2018 02:48 PM
HI hbm and Jan,
Thank you for looking into this issue. Here is the GWMLog when I do getFeature request.