@JD1016 Its hard to tell from the info in the error message. You will need to share more columns from the log to get a better idea of what caused the error. For example, which service triggered the errors? If you look at the arcgis server logs in the ArcGIS Server Admin interface you will get more info / more columns. And I find it easier to browse and scroll through the log with the Admin interface.
It could just be that one user is trying to do something that is unsupported. Not really a big deal unless it happens a lot or if these requests take a long time to execute. Every night we run a query on the web logs on our web adaptors to extract all of the requests that took more than 60 seconds to execute. I review these daily to see if I can identify problems that can be fixed. The list of long running requests is usually only a few records but sometimes it will be a few dozen.
Bernie.
Hi Bernie,
I've never looked at the logs in Admin.
I've logged into Admin, I see logs...where do I go from there?
Thanks.
Having problems with the Start Time and End Time. I keep getting "startTime must be epoch time or an ArcGIS server timestamp.
As an example, I put in "Dec 14, 2022, 10:53:53 AM" from my ArcGIS Server Manager but it does not like that form.
Any suggestions?
Unfortunately, that did not work either. However, I did find an online converter that takes the data and time converts it over to a UNIX time stamp (epoch). After applying those times it does kick out the columns you indicated but they are all blank underneath.
Through the API Reference, the Log Codes, or Process IDs or Request IDs are required. Any idea on that component?
Not a problem.
You've been a huge help as always, Bernie.
Correction...the codes are indeed optional. Sorry about that. What actually did work was replacing your slashes with dashes and then everything came in fine. I've attached another screenshot so you can comment on that run if it sheds any light on the issue from your perspective.