two server call are generated, one is getting through and another is gets failed | Community
Skip to main content
Ashish_NilkanthRa
New Participant
Apr 16, 2020 5:49 AM UTC
Solved

two server call are generated, one is getting through and another is gets failed

Hi everyone,

i have noticed that two AA server calls are getting generated on my site, out of this two server calls, 1st is getting through and 2nd is getting failed,

can someone have look on below screenshot, 

 
 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Andrey_Osadchuk
Andrey_OsadchukAccepted solution
Level 10
Apr 17, 2020 11:18 AM UTC

Ashish,

There must be a bug in your implementation. The beacon URL starts with this "https://https//wordpress-137997-650849.cloudwaysapps.com//b/ss/movementstaging/"

The part "https//wordpress-137997-650849.cloudwaysapps.com/" should have been the tracking server, but for some reason it's the wordpress URL. This server call has never reached Adobe Analytics.

The part "movementstaging" is the report suite ID that seems to be dummy in your case. This is another reason why this server call would not be preccessed even if the tracking server was correct.

View reply

11 replies

jantzen_b
jantzen_b
Employee
Apr 23, 2020 9:52 PM UTC
Do any of the answers below give you the info you need? If so, could you mark the reply that answers your original question the best as correct? If not, can you provide additional details to help the community better solve your question?
Translate
Andrey_Osadchuk
Andrey_OsadchukAccepted solution
Level 10
Apr 17, 2020 11:18 AM UTC

Ashish,

There must be a bug in your implementation. The beacon URL starts with this "https://https//wordpress-137997-650849.cloudwaysapps.com//b/ss/movementstaging/"

The part "https//wordpress-137997-650849.cloudwaysapps.com/" should have been the tracking server, but for some reason it's the wordpress URL. This server call has never reached Adobe Analytics.

The part "movementstaging" is the report suite ID that seems to be dummy in your case. This is another reason why this server call would not be preccessed even if the tracking server was correct.

Translate
    Andrey_Osadchuk
    Andrey_Osadchuk
    Level 10
    Apr 16, 2020 6:29 PM UTC

    Ashish, the request in the screenshot look very odd as it's referring to the incorrect URL (URI format). There may be a bug in the implementation.

     

    Could you copy and paste here the full request (full URL) so we have a closer look and see what type of server call it is?

    Translate
      vedantr68040072
      vedantr68040072
      New Participant
      Apr 17, 2020 10:54 AM UTC
      @andrey_osadchuk i have message you the request URL, please check
      Translate
      Andrew_Wathen_
      Andrew_Wathen_
      New Participant
      Apr 16, 2020 9:47 AM UTC

      There can be a few different reasons for this (not all bad), what was the status against the failed server call?  (the successful one will have had a status of "200")

      Translate
        vedantr68040072
        vedantr68040072
        New Participant
        Apr 16, 2020 10:49 AM UTC
        @andrew_wathen_ , status is showing "(failed)"
        Translate
        Ashish_NilkanthRaAuthor
        New Participant
        Apr 16, 2020 6:37 AM UTC
        Error code is "net::ERR_NAME_NOT_RESOLVED"
        Translate
        Hyder_Ziaee
        Hyder_Ziaee
        Employee
        Apr 16, 2020 6:30 AM UTC
        Whats the error code?
        Translate
        Terms & ConditionsAccessibility statement

        Loading footer...