Open KCI-Ablowers opened 5 years ago
We are submitting inspection records with no issues using the KCI_1 Web map and Survey123.
Let me try restarting the inventory map services (my VM now has direct access to the DMZ servers).
I just restarted KCI_1 and CENT services; please let me know if that fixed anything. If it did, then I assume we will need to restart the others as well.
@johnshiu It may have been that structure. I still have the issue with 0806413.002, but another one close by saved the geometry edit.
@KCI-Ablowers hmm, that is strange. Let me see what I can find about that.
@johnshiu Sounds good, I told him to recreate the feature and delete the existing. I'm not sure if he's done that yet. If so, I had the same issue in our (KCI_1) version.
@johnshiu and @talllguy - WBCM is having issues saving updates in their edit app. I tested out the edits they attempted using their app on my end, and the attribute updates are not saving. Could we restart the feature services without affecting the BMP Inspection side of things?
@KCI-Ablowers, I just restarted WBCM's inventory service. Please give it another shot.
@johnshiu - I just tried with both the edit app and web map, but no luck. I'm sure that the field I am in has always been editable and nothing should have changed at the AGOL level.
The park & ride service was glitchy yesterday and needed a service restart. I wonder if this is related.
I brought the WBCM service to a full stop and then restarted it. Try again?
java.lang.Exception: Service 'NPDES_Next_Gen/NPDES_Inventory_WBCM_Version_Prod_Maryland_SHA.MapServer' not found. Check if the service exists and is started. at com.esri.arcgis.discovery.wsh.ServiceHandlerServlet.lookup(ServiceHandlerServlet.java:638) at com.esri.arcgis.discovery.wsh.ServiceHandlerServlet.service(ServiceHandlerServlet.java:186) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:378) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338) at com.esri.arcgis.discovery.wsh.DispatcherServlet.service(DispatcherServlet.java:181) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:423) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1079) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Caused by: javax.naming.NameNotFoundException: Could not find a service with the name 'NPDES_Next_Gen/MapServer/NPDES_Inventory_WBCM_Version_Prod_Maryland_SHA' in the configured clusters. Service may be stopped or ArcGIS Server may not be running. at com.esri.arcgis.discovery.ejb.ServicesDirectory.a(ServicesDirectory.java:213) at com.esri.arcgis.discovery.ejb.ServicesDirectory.lookup(ServicesDirectory.java:233) at com.esri.arcgis.discovery.wsh.ServiceHandlerServlet.lookup(ServiceHandlerServlet.java:633) ... 29 more
These errors repeat a few times
I brought the WBCM service to a full stop and then restarted it. Try again?
@talllguy It doesn't look like that fixed it. I tried a couple different features and attributes and those will not save either.
🤔 hmm. It could be something on the version side.
Here's some detail on that 10:25 AM error:
<?xml version="1.0" encoding="utf-8" ?>
<Msg time='2019-07-16T10:24:18,334' type='SEVERE' code='17000' target='NPDES_Next_Gen/NPDES_Inventory_WBCM_Version_Prod_Maryland_SHA.MapServer' methodName='GraphicFeatureLayer.Update' machine='SHAGBDMZWEB1.SHADMZ.MDOT.MDSTATE' process='42816' thread='42616' user='NPDESSecure' >An error occurred.</Msg>
<Msg time='2019-07-16T10:24:18,403' type='SEVERE' code='17000' target='NPDES_Next_Gen/NPDES_Inventory_WBCM_Version_Prod_Maryland_SHA.MapServer' methodName='GraphicFeatureServer.HandleREST_ApplyEditsOperation' machine='SHAGBDMZWEB1.SHADMZ.MDOT.MDSTATE' process='42816' thread='42616' user='NPDESSecure' >An error occurred.</Msg>
<Msg time='2019-07-16T10:25:45,604' type='SEVERE' code='17000' target='NPDES_Next_Gen/NPDES_Inventory_WBCM_Version_Prod_Maryland_SHA.MapServer' methodName='GraphicFeatureLayer.Update' machine='SHAGBDMZWEB1.SHADMZ.MDOT.MDSTATE' process='42816' thread='42616' user='NPDESSecure' >An error occurred.</Msg>
<Msg time='2019-07-16T10:25:45,641' type='SEVERE' code='17000' target='NPDES_Next_Gen/NPDES_Inventory_WBCM_Version_Prod_Maryland_SHA.MapServer' methodName='GraphicFeatureServer.HandleREST_ApplyEditsOperation' machine='SHAGBDMZWEB1.SHADMZ.MDOT.MDSTATE' process='42816' thread='42616' user='NPDESSecure' >An error occurred.</Msg>
10:10 AM
<?xml version="1.0" encoding="utf-8" ?>
<Msg time='2019-07-16T09:30:39,625' type='SEVERE' code='17000' target='NPDES_Next_Gen/NPDES_Inventory_WBCM_Version_Prod_Maryland_SHA.MapServer' methodName='GraphicFeatureLayer.Update' machine='SHAGBDMZWEB1.SHADMZ.MDOT.MDSTATE' process='8312' thread='33924' user='NPDESSecure' >An error occurred.</Msg>
<Msg time='2019-07-16T09:30:39,665' type='SEVERE' code='17000' target='NPDES_Next_Gen/NPDES_Inventory_WBCM_Version_Prod_Maryland_SHA.MapServer' methodName='GraphicFeatureServer.HandleREST_ApplyEditsOperation' machine='SHAGBDMZWEB1.SHADMZ.MDOT.MDSTATE' process='8312' thread='33924' user='NPDESSecure' >An error occurred.</Msg>
Typical unhelpful ESRI logs...
Are any of the other versions experiencing problems, or is it isolated to WBCM?
I ran a test where I used the publish-MXD on the DMZ AGS machine to perform an edit. I had no issues adding a structure, making an update, and then saving. Structure Global ID is {CCAF29B3-CAB4-4E32-83E9-BDA7B883FA03}
.
I was able to save an edit in KCI 1. The initial email from WBCM is below-
Brent
We are having one of our interns work on updating the stormdrain inventory for our inspection records and have a question for you:
- If the VIC_BMP is “Null” then the LOC_BMP is not saving the updates to the address that we want to make. Is there a way for us to add LOC_BMP without having to update the VIC_BMP?
Let me know.
@KCI-Ablowers let me try to replicate that edit workflow in the publish-MXD
I edited SWM_FAC_NO
040173
. It has a null VIC_BMP
. I added the comment, " Looks like an underground BMP." to the LOC_BMP
. This edit took successfully.
Let's try the same thing on the web editor.
I added more to the comment on the AGOL edit app. Again no issues.
I added more to the comment on the AGOL edit app. Again no issues.
Was that in the WBCM version?
Yes, although I'm checking to see if it appears to have saved on the publish-MXD side and it does not look like it did. Let me restart arcmap
OK. The edit worked.
Let's get some more information about where the failure is occurring. What BMP is it, who is editing, etc.
@talllguy, based on your testing, it sounds like the database version is working okay since you can edit with the MXD. It sounds like the issue is stemming from the feature service itself since the logs are throwing an error. Usually, restarting the service fixes these types of problems, but this time it has not.
Is it possible to try republishing the WBCM feature service?
Is it possible to try republishing the WBCM feature service?
We would need them to push their inventory updates to SHA correct?
@KCI-Ablowers, no, their edits would stay where they are in the FIELD.WBCM version. Republishing the feature service will not clear/delete the version.
@johnshiu :expressionless: I always mix up republishing and the source to field for some reason. We can try a republish when time allows.
Do you want me to overwrite the service? That would be the most seamless, but can cause other problems. The other option is to create a brand new service and migrate all the maps and apps--not ideal!
Overwriting the service sounds like the best option, but I wasn’t aware it would cause problems. If you think it’s okay, I’d try that option first.
There can be problems if the schema changes, but that shouldn't be an issue here. I am tied up until tomorrow though and will not be able to get this republished until then. Did we happen to check if they tried one more time? I had no issues making edits in both the MXD and on AGOL (WBCM edit app).
@talllguy, ah, that makes sense. @KCI-Ablowers, can we ask them to try again? Perhaps there is something on their end if the AGOL editing is working for Elliott.
@talllguy and @johnshiu - I just realized I didn't include the SWMFACs in question in the earlier comments:
I tried to make edits on a few of these features and nothing sticks. They appear to be all grass swales. Trying on other BMPS (130514 and 030102) the edits appear to work fine. We didn't set up anything specific for grass swale editing, so not sure what the hold up maybe.
I think this is along the same lines-
DEW got in touch with me today about an issue with the offline sync-
Hi Andrew,
We have been attempting to conduct our SWMFAC inventory edits in an offline copy of the SHA’s geodatabase. We have been received the following error message when we finish editing and go to synchronize our edits with the server:
Any ideas what is causing this? I don’t believe we have made any edits to the VIC_BMP field, so I’m not sure why that would be the subject of the error. We were able to successfully sync our edits yesterday morning and during a few offline editing sessions we conducted earlier in the task, but have started having this issue yesterday afternoon.
Thank you, Mark
I inquired back looking for the specific SWMFAC and Mark (DEW) sent this -
Hi Andrew,
I believe I may have resolved the issue. For some reason, I am unable to synchronize my edits when I edit some SWMFAC records with a Null value in the VIC_BMP field. If I add “9999” to this field, then I am able to sync my edits. This does not appear to be true for all SWMFAC records, only random ones thus far. At first I thought there was some type of business rule on the backend that was not allowing VIC_BMP to be Null if other edits are made, but the fact that the error occurs for some SWMFAC records but not others doesn’t make much sense.
If you would still like to replicate the error, two of the SWMFAC records that had this issue were 130744 and 130747. Both now have 9999 in the VIC_BMP field, but if I change them back to Null and try to sync I get the error again.
Thanks, Mark
I made some edits to a few test BMPS, just north of 030102 and had no issues with any of mine going through.
@KCI-Ablowers, hmm, this is really weird behavior. I will check the database and logs and see if I can dig something up. It might have something to do with the versioning? But I will take a look and let you know what I find. If firms need to, I would recommend setting VIC_BMP to 9999 so that they can proceed, and then we can go back and clean those up in source later after they're committed.
John,
New email from Mark -
Hi Andrew,
Sounds good. One thing I noticed yesterday afternoon was the VIC_BMP error only appears to occur when the LOC_BMP and ROAD_NAME fields are edited. If I’ve only edited other SWMFAC fields prior to the sync then I receive no errors.
We’ll continue with the use of 9999 for now and let you know if we run into any other issues.
Thank you, Mark
On Wed, Aug 7, 2019 at 10:22 PM -0400, "John Shiu" notifications@github.com<mailto:notifications@github.com> wrote:
https://github.com/KCI-Ablowers
https://github.com/KCI-Ablowers From IT@KCI.COM 410-316-7820 This is an External Email from outside of KCI.***
@KCI-Ablowers, hmm, this is really weird behavior. I will check the database and logs and see if I can dig something up. It might have something to do with the versioning? But I will take a look and let you know what I find. If firms need to, I would recommend setting VIC_BMP to 9999 so that they can proceed, and then we can go back and clean those up in source later after they're committed.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/kcigeospatial/MDOT-SHA-NPDES-Next-Gen/issues/355?email_source=notifications&email_token=AIORJ4HOUGUF4576RFJIL2LQDN7OFA5CNFSM4H3IYHK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD32HHHY#issuecomment-519336863, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIORJ4F6H6KUROXJ5NRPNITQDN7OFANCNFSM4H3IYHKQ.
Issue
Edits, geometry or attributes are not saving in the firm inventory views.
Background
CENT contacted me about edits not saving via the Edit App this morning. I tested both a geometry and attribute update in their version for structure 0806413.002. Nothing saved. Tested the edit in the KCI_1 edit app and again, nothing saved.