Sitecore CES based GEO IP Lookup not working. All Integration steps followed.

We have been recently upgraded to Sitecore version 7.2.

Our Env:

Sitecore 7.2

Windows Servers 2012

SQL server 2012

All integration steps listed in the doc: "set up guide for the sitecore ip geolocation service_usletter.pdf" have been followed.

(1)  Uploaded the package  "Sitecore IP Geolocation Service Client 1.1 rev. 150602.zip".

(2)  Enabled all three .ces.config files now available in \App_Config\Include\CES\  folder.

(3)  Url https://discovery-ces. cloud.sitecore.net' has been white listed on the proxy.

All Visit information has been flowing through as expected but the geo location info is not being resolved.

As soon a page visit is happening, we are seeing the below issue being listed in the log file continuously.

2812 15:25:45 DEBUG RenderingSettings.GetMultiVariateTestForLanguage (language = en) at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at Sitecore.Layouts.MultiVariateTestingExtensions.GetMultiVariateTestForLanguage(RenderingSettings settings, Language language)
at Sitecore.Analytics.Pipelines.InsertRenderings.Testing.Evaluate(InsertRenderingsArgs args, Item contextItem)
at (Object , Object[] )
at Sitecore.Pipelines.CorePipeline.Run(PipelineArgs args)
at Sitecore.Pipelines.RenderLayout.InsertRenderings.Process(RenderLayoutArgs args)
at (Object , Object[] )
at Sitecore.Pipelines.CorePipeline.Run(PipelineArgs args)
at Sitecore.Layouts.PageContext.BuildControlTree(Object sender, EventArgs e)
at System.Web.UI.Page.PerformPreInit()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)

  • Resolved !!

    We had a series of changes to be done.

    The biggest of all is that we had to make Sitecore Proxy-Aware so that requests to cloud.sitecore.net flow thru, using the defaultProxy setting in web.config:

    <system.net>
    <defaultProxy enabled="true">
    <proxy proxyaddress=".....,.." />
    </defaultProxy>
    </system.net>

    This made the difference !!
  • In reply to Veerendra Doppalapudi:

    Veerendra -- So, you are saying that, You added cloud.sitecore.net in allowed to your proxy settings? for example

    system.net>
    <defaultProxy>
    <proxy
    proxyaddress="http://myproxy.com"
    bypassonlocal="true" />
    </defaultProxy>

    then on myproxy.com configuration you added Sitecore's recommended stuff in whitelist?

    Kiran