'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

Is Rendered Item Valid XHtml Document Could not find schema information warnings during publish item Sitecore 7.2

Image
Note: Since we now live in the HTML5 world, the simple resolution to any XHtml validation errors is to remove the XHtml validation rules on  System->Settings->Validation Rules->Global Rules item. Sitecore should update it's validation rules to be relevant to HTML5. This make the rest of this post obsolete :). I created a simple approval workflow in Sitecore 7.5 and tried to approve an item for publishing and found a bunch of validation errors in the Validation Results. Most of them were related to the "Is Rendered Item Valid XHtml Document" section which looked like this: The problems were related to violations of the W3C HTML5 recommendation An important note here is: The element containing the character encoding declaration must be serialized completely within the first 1024 bytes of the document. Adding the following xmlns attribute to the Html tag fixed most of the errors: <html lang="en" xmlns="http://www.w3.org/1999/
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