'analytics' connection string is not defined

Typically developers run into this error in their local environment if they do not have Sitecore Analytics enabled but for some reason have a Sitecore.Analytics.config deployed with the following settings enabled:
<!--  ANALYTICS DISABLE DATABASE
            Disables the database so that no reading or writing to the database occurs.
            Default: false
      -->
      <setting name="Analytics.DisableDatabase" value="false" />
<!--  ANALYTICS ENABLED
            Determines whether analytics is enabled or not.
            Default: true
      -->
      <setting name="Analytics.Enabled" value="true" />
Simply disabling the Analytics DB by setting the Analytics.DisableDatabase to "true" solved the problem.

Here is a related blog post about this error.

Comments

  1. Aruna RamFebruary 16, 2019 at 1:24 AM

    This comment has been removed by a blog administrator.

    ReplyDelete
  2. pavithra dassFebruary 18, 2019 at 12:53 AM

    This comment has been removed by a blog administrator.

    ReplyDelete
  3. yuvaraniFebruary 18, 2019 at 1:58 AM

    This comment has been removed by a blog administrator.

    ReplyDelete
  4. KayalFebruary 20, 2019 at 5:55 AM

    This comment has been removed by a blog administrator.

    ReplyDelete

Post a Comment

Popular posts from this blog

Google Lighthouse Tips: Importance of web page speed

Image
Mobile Focus  75% of global mobile users were on 2G and 3G as of 2016 (Source: GSMA Mobile)  1MB takes minimum of 5 seconds to download on a typical 3G connection. (Source: WebPageTest & DevTools 3D definition)   19 seconds is the average time a mobile web page takes to load on a 3G connection. (Source: Google DoubleClick blog)  70% of mobile pages take nearly 7 seconds for visual content above the fold to display on the screen. (Source: Think with Google)  UX & UI Performance  As the number of elements on a page increases from 400 to 6000 the probability of conversion drops 95%. (Source Think with Google)  Site takes >1 sec to become interactive, users lose attention, and their perception of completing the page task is broken. (Source: Google Developers Blog)  As page load time increases from 1 sec to 7 secs, the probably of mobile site visitor bouncing increased 113%. (Source: Think with Google)  Proven Results  Walmart saw 1% increase in revenue for every 100ms improvemen
Read more

Decision tree for selecting the best cloud hosting option (App service, VM, Containers, Serverless)

Image
While working on a project last year, we were looking at various options for our Microservices hosting strategy. My colleague came across this decision workflow from Microsoft for their Azure hosting service options and I thought of sharing it here. This decision workflow can help in the following scenarios (and others): Hosting options for new build vs migration Overall cloud migration strategy Web & API hosting options IaaS vs PaaS vs serverless Microservices deployment and scaling strategy Feel free to comment on ways in which this may have helped you.
Read more

SOLVED: Sitecore Habitat Home Sync-Unicorn fails with the error: GetResponse" with "0" argument(s): "The remote server returned an error: (403) Forbidden.

Image
When executing  .\build.ps1 or .\build.ps1 -Target "Post-Deploy" commands to deploy Habitat Home build, the PS script fails with the error message; "GetResponse" with "0" argument(s): "The remote server returned an error: (403) Forbidden." ======================================== Sync-Unicorn ======================================== Sync Unicorn items from url: https://sitecore93sc.dev.local//unicorn.aspx Executing: &"C:/Code/HabitatHome/scripts/Unicorn/Sync.ps1" -secret 749CABBC85EAD20CE55E2C6066F1BE375D2115696C8A8B24DB6ED1FD60613086 -url https://sitecore93sc.dev.local//unicorn.aspx Sync-Unicorn: Executing Sync... An error occurred when executing task 'Sync-Unicorn'. Error: One or more errors occurred.         Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (403) Forbidden." The key to solving the issue lies in the following lines of code in Unicorn.p
Read more