Latest Contributions by JustinConnerWR

A feature report that has been running without issue for years now times out when map settings are applied. I can run a report with a generic map and even when applying a size restraint. Will timeout when trying to use a specific map ID. Does not work:  ${closure_area|mapSettings:"8f3845a647d04d3c92f10be0299fa2b3": 3600 | size:600:500} Will work:  ${closure_area| size:600:500} ... View more

I'm working on the Citizen Problem Manager within the Citizen Problem Reporter Solution. I'm running into a problem when updating a citizen request after it's completed. This screen shot of Google Chrome Dev Tools shows a validateContingencyConstraints error. JustinConnerWR_0-1751313417535.png   ... View more

When AGS was installed they used the default Domain\arcgis service account. For security reasons it's recommended to change this account. I successfully ran the "Configure ArcGIS Server Account utility", confirmed the new account had permissions to the ags folders, file shares, etc. Added the user to SQL databases. Confirmed the AGS service was running as the new domain account. Everything seemed good. I am able to log into my laptop as the new domain account, access any data thats needed, read/write to SQL, and publish maps to AGS. Again everything seemed good. So I decided it was safe to disable the old domain\arcgis account. That's when the map services using OSA data connections failed, even the test map service created while logged in as the new account. Looking at the GDB locks all AGS map services were still using the domain\arcgis account. The warning I see in AGS logs when restarting a service is: The base table definition string "data layer name" is invalid. Underlying DBMS error[[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. No extended error.]. And the corresponding error on the SQL host machine. SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. Any thoughts would be helpful. ... View more

I'm getting a strange behavior with Integromat and wondering if I have a setting wrong somewhere that is causing my UTC Offset parameter to keep resetting to UTC -5?   Set correctly and hit save. Setting always defaults to UTC -5 ... View more