Empty Usage and Health Reports In SharePoint 2013

I was called into Dow Chemical Company Over in St. Louis Park to investigate why they were only seeing empty usage and health reports with their new SharePoint 2013 environment. I was not the person that set it up so I went in this morning to check it out.

If for some reason, you find that the usage and health reports are always showing up as empty, there is a relatively quick fix. This can still happen if you follow the orthodox setup producere in Central Admin -> Monitoring -> Configuring health data collection with both the usage data collection and  health data collection tags checked. The way you can tell if you have this issue is to go into your site collection, get a popularity trend report, and notice the lack of content within it. Follow these setps to execute the repair:

  1. Check whether the Microsoft SharePoint Foundation Usage Data Processing and Microsoft SharePoint Foundation Usage Data Import timer jobs are all running and haven’t farted out.
  2. Because of the merging of search services, make sure that everything is good on that front and that crawling is continuous.
  3. Make sure WSS_Admin_WPG and WSS_WPG have access to the log folder.

At this point, if the above steps have not worked, you have to make sure the logging database isn’t the point of failure.

  1. Create a new login in SQL for logging access
  2. Go back to Central Admin -> Monitoring -> Configuring health data collection
  3. use SQL authentication instead of Windows
Share

Fixing Service running under Network Service account in workgroup environment is not supported Error

This is a tricky error to fix when you are trying to install SharePoint 2013 on a non-domain environment. I have run into this the most when helping clients setting up isolated development areas to for indivudal users to program in.

The exact error is:

Failed to connect to the configuration database.
An exception of type System.Management.Automation.CmdletInvocationException was thrown.  Additional exception information: ErrorCode<NonDomainNWService>:SubStatus<ES0001>:Service running under Network Service account in workgroup environment is not supported.

While this may look like an error of doom for setting up a Sharepoint 2013 in workgroup, you will find it a really easy error to fix! All you have to do is to start PSconfig as so:

[code]

psconfig.exe -cmd Configdb create SkipRegisterAsDistributedCacheHost

[/code]

And the error will go away!

 

Share

Fixing Sorry, we can’t seem to connect to the SharePoint Store Error

You can encounter this error even if you believe that you have the appstore configured correctly. But this is the first thing to check becuase this error will be thrown if this is not configured correctly. You can install and configure it by following the instructions at:

http://msdn.microsoft.com/en-us/library/fp179923(v=office.15).aspx

Following, ensure that the App domain and App prefix  are correct through central administration. At this point, it also makes ense to ensure that the language and currency are correct, since this error can be thrown when hitting a localization error. If at this point, you aren’t having a ton of success and still encountering the error, consider recreating the  Subscription Settings Service Application.

If that doesn’t work, stoke a fire under the WFE.

Share