Hello Vin!
A few questions for you:
Prepare Fiddler
1. Download Fiddler from http://www.telerik.com/fiddler
2. In Fiddler, go to the Tools menu > Options
3. In the HTTPS tab, check "Capture HTTPS CONNECTs" and "Decrypt HTTPS traffic"
4. Upon checking the second option, you should be prompted to trust the root certificate of Fiddler. This allows us to capture the information needed to see any issues. If you don't see this, click Actions on the right > Trust Root Certificate. Click allow/yes through the pop-ups.
5. Click "Decode" button on the toolbar.
Preparing to get the log
1. Get up to the point where you only have to click one button to reproduce the error we are troubleshooting.
Capture traffic
1. In Fiddler, go to File > ensure Capture Traffic is NOT checked
2. In Fiddler, go to Edit > Remove > All Sessions
3. In Fiddler go to File > turn on Capture Traffic - this will start recording all network traffic on your computer
4. Click the one button needed in the browser or your application to reproduce the error we are troubleshooting.
5. In Fiddler, go to File > turn off Capture Traffic as soon after you get the error message as possible
6. In Fiddler, go to File > Save > All Sessions and save the .SAZ file.
If you are uncomfortable with attaching your .SAZ file to this forum, feel free to create a support case and we'll assist you here in Support Services with a closer look at what you're seeing.
Thanks!
-- Rachel
Esri Support Services
Hi Rachel,
Thanks for the reply. In response to the first question, yes, I had gone through the Content folder and deleted surveys with same name that were there due to previous publishing attempts and I was still getting the error. Today, though, I didn't get any errors. Both surveys that I was previously working on published just fine. I can't prove this but it could have been connectivity related, I work for a fed agency and our network seemed slow last week and is functioning much quicker today. If it happens again I'll try Fiddler and include those files. Thanks again
Vin
Hello Vin,
Glad to hear that things are working! Network connectivity could certainly be a cause of this one!
Let us know if it comes up again!
Best regards,
Rachel
Esri Support Services