Analytics 1.1: Configuration, Add Resource, Website, timed out, receiving error upon retry

Ross Brewer

17. Oktober 2016 19:04

After attempting the first time to add an internal Website as a resource within Analytics 1.1, we had the Configuration page time out on us.  Then, when we attempted to re-add the same Website, Analytics returns the following error, "The Website that you are trying to add already exists."  Problem is, we can't see where the website exists in the table of contents panel to possibly remove it and retry.

 

Anyone else run into this?

 

Thanks in advance,

 

Ross

0

• 

  Permanently deleted user

  17. Oktober 2016 20:55

  Hi Ross,

   

  If the connection to Analytics timed out while adding a website, you could try the following:

   

  1) Go to the following folder:  C:\Program Files\Latitude Geographics\Geocortex Core\NSRoot\Geocortex\Analytics\Collectors\WebSiteProbe\1.1.0

   

  2) Back up your role.config file (to your desktop, Analytics will load the configuration file twice if you back it up in this folder)

   

  3) Look in the Probes element for the site you added.  It should look something like this: <Probe Name="Google" Enabled="True" Action="GET" Url="https://google.ca" UseTokenSecurity="False" UseAdminUrl="False" /> 4) Delete that line

   

  5) Try re-adding the website to Analytics.

   

  I hope this helps!

   

  Thanks,

   

  Danny

  0
• 

  Ross Brewer

  20. Oktober 2016 19:26

  Thanks for the response Daniel.

   

  Probes deleted, and new website add was deemed successful.  However, when I try to view the website in the table of contents on the left, the name of the site shows up, but underneath of the site name says, "Adding Resource..." with an ellipses that blinks indefinitely - same symptom as before._img_ alt="screenshot" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000PDZM&feoid=Body&refid=0EM60000000HTFw" _/_img_

  0
• 

  Permanently deleted user

  24. Oktober 2016 22:12

  Hi Ross,

   

  With that in mind, I would suggest opening a support case so we can help you investigate.  It sounds like a bug to me.

   

  One other thing you could try (if you haven't already) is to upgrade to Analytics 1.1.1.  There are quite a few bug fixes in there, and while I'm not sure this is one of the known issues that was fixed, it's still possible that this is working in the new version.

   

  I hope that helps!  

   

  Thanks,

   

  Danny

  0
• 

  Ross Brewer

  25. Oktober 2016 14:23

  Alright, thanks, Danny

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.