Sitecore 8 Rebuilding historical path analyzer maps

I thought I would share and issue and resolution I found recently when rebuilding historical path analyser maps in Sitecore.

How to rebuild Path Analyzer maps

We found it in 8.1 update-2 and may have been fixed in a later release but it looks like there is a potential bug.

The code seems to be querying a config database to get a count. The issue we found with this is that that database doesn't exist and the user we are connecting to the Mongo database with doesn't have read permissions on that non existing database.
The error will be along the lines of

Cannot obtain number of chunks from config database Exception: MongoDB.Driver.MongoCommandException Message: Command 'count' failed: not authorized on config to execute command { count: "chunks", query: { ns: "analytics.Interactions" } } (response: { "ok" : 0.0, "errmsg" : "not authorized on config to execute command { count: \"chunks\", query: { ns: \"analytics.Interactions\" } }", "code" : 13 }) Source: MongoDB.Driver at MongoDB.Driver.Operations.CommandOperation`1.Execute(MongoConnection connection)

A workaround/fix to this is to grant your analytics db admin user read permissions on the database. We are using a mlabs cluster so the steps were as follows:
  1. Log into the mongolabs website and navigate to the admin database for your cluster 
  2. Create an admin/cluster user (This will have the root role which we need to grant the cross database permissions, db users only get the dbowner role) 
  3. In a command prompt with administrator privileges, navigate to your mongodb bin folder on your local machine (cd C:\Progra~1\MongoDB\Server\3.0\bin)
  4. Open up the mongo shell in your local machine and connect to the admin database ([clsuterurl]:[port]/admin -u -p 
  5. The run the following commands 
    • use analytics 
    • db.grantRolesToUser( "[existing_database_admin_user]", [ {role:"read", db:"config"} ] ) 
  6. Then you can delete the cluster admin user you created earlier.
Hope this helps.

Comments

Post a Comment

Popular posts from this blog

Sitecore Unicorn standard values field child ID warnings

I thought I'd share this just in case anyone else wonders why they get the following WARN message for every single template that has a standard values set, when performing a Unicorn Sync. To get things started: Unicorn - 4.03 and 4.04 Sitecore - 8.2 Update 6 This happened to us when fully syncing from disk into a blank Sitecore instance, using a gulp script that calls a PowerShell sync, see below. WARN  The standard values field of template /sitecore/templates/User Defined/Foundation/Theming/Theme/Theme Options:{XXX-XXX-XXX-XXX-XXXXXXXXXXXX} does not contain an ID that points to a child The issue (i think) is that when unicorn de-serialises the template item, it has a field for standard values. At the point of creation that items children haven't been created, most importantly the standard values item. Sitecore checks the standard values field value and see that the id doesn't exist at this point, and not as a child of the item, so outputs the WARN message. Un
Read more

Sitecore DMS and Analytics Considerations

Image
Recently I've been tasked with generating some simulated analytics traffic for our Officecore demo solution. I've been using the TrafficGenerator to do this, this is available on marketplace, but get the package from here: https://github.com/JimmieOverby/SitecoreTrafficGenerator The link on marketplace goes to an older version 0.42, 0.43 is available in the packages section. Getting the data in a has come with a few development considerations. On that basis I thought I'd discuss them and share the solutions I found. Caching: The first thing to consider is that the data you see in the engagement analytics dashboard is not real time. There are a couple of levels of caching that can make the results you see not what you expect. These levels are: Browser:  The refresh button needs to be pressed, the graphs will not auto update. The file Silverlight creates will be cached by the browser,  I found a post here,  http://sitecoreblog.alexshyba.com/2009/04/silv
Read more

Sitecore Continuous Integration DMS and the Marketing Centre

Hey all, as you know I'm a big advocate of implementing continuous integration or delivery for your Sitecore projects, in the Sitecore world much is made of the all important final step of the deployment being a Sitecore publish.  We want to get the data from the master to the web database, then we can add steps to do automated web testing such as selenium testing etc, or deploy a package to DEV, UAT, PRD. There are a few options to call a publish, you will probably have seen on many other Sitecore developers blogs,: Use a publish.aspx page that calls the publish code. Web service route, by calling Sitecore ship to initiate the publish and then call a ship endpoint and parse the response to check the late completed date to check for completion. Use Sitecore rocks powercore powersell scripts to do it. Most of the time calling the publish isn't the problem from a CI sense its knowing when its finished, my preference is the Sitecore ship approach, however we use the publis
Read more