"Item specified by templateItemId does not exist or is not accessible."

[abureaux]

S123 reports aren't running. I'm logging a support case...

This happened overnight. Portal and Surveys Site are all online and accessible.

EDIT: This also is happening directly from the Surveys Site (worked less than 12 hours ago):

EDIT2: According to my IT, nothing changed overnight on our security settings.

EDIT3: In case it matters. Environment is Enterprise 11.0

[abureaux]

@ZacharySutherby @IsmaelChivite 

[abureaux]

I tried in AGO, and that worked as expected.

[RobertAnderson3]

For what it's worth, all my surveys live in AGOL and I have had no issues with any of my webhooks creating reports, I just tried from the website and it worked fine (well, it always tries to open in Word Online now and "Sorry, there was a problem and we can't open this document. If this happens again, try opening the document in Microsoft Word" but if I download it and open it in desktop Word itself it's fine)

Both Word Docs and PDFs worked when I tried.

[abureaux]

AGO worked for me as well. There is a chance this is environment-specific, but it seems very strange all the same.

[abureaux]

The two URLs I know of that S123 needs are:

• https://featurereport-prod.s3.amazonaws.com
  • Blocking this should see the report attempt to generate, but timeout instead.
• https://arcgis-prd-survey123-use1-reports.s3.amazonaws.com
  
  • Blocking this should only affect manual report generation. Furthermore, toggling off "Save to my ArcGIS account" should bypass any errors.

In both cases, reports should generate, but fail at the end. My issue is happening before report generation starts (i.e., at the checking of templateItemId stage). Don't think it's related to these URLs being potentially blocked, but who knows...

[abureaux]

Server restart didn't affect anything.

Still no ideas from Tech Support. Everything appears to be working.

[abureaux]

This just got a whole lot weirder... The error is still persisting; however, I am getting esriJobSucceded now as well! I got 7 failures (all related to templateItemId), but then the report was successfully generated:

I had to dig around the Network traffic for the URL, but when I pasted it into my browser, I got my report.

Again, nothing is working since that first error ends all processes (Power Automate and Esri's reporting service). But I can clearly see that is is in fact finding and using that templateItemId.

[abureaux · Accepted solution]

Okay, wow. Think this is resolved now...

It wasn't until I tried the Beta S123 Website that I got a little more info. Specifically, a Node.js error about white space.

After calls with Esri, we randomly checked IIS. Default Website > HTTP Responses > Strict-Transport-Security. When I edited the STS entry, there was a "space" in front of the word. As soon as I deleted that space, the error went away. I have zero clue where that space came from since I didn't modify those entries... But be warned!

Chances are some app somewhere got an update and is now stricter about parsing.

[PatriceLabbé]

Hello,

We had to add this domain to "allowedProxyHosts" to make this work : arcgis-prd-survey123-use1-reports.s3.us-east-1.amazonaws.com

An enhancement request has been made to add this domain to the documentation : ENH-000158092

In fact, this is the only domain required to make things work with our on-premise ArcGIS Enterprise. It allows report generation when the option to "Save to my ArcGIS account" is enabled.