Understanding the Logging Database
How to Query the WSS_Logging Database
How to Reduce the Size of the Logging Database
SEO in SharePoint Server 2013
SharePoint 2013 Analytics a Big Step Backward
How to Query the WSS_Logging Database
Install SSRS in SharePoint Mode
New-SPUsageApplication
Demystifying SharePoint Performance Management
Capturing Performance Counters for SharePoint
Enabling Usage Reports
SharePoint Usage Reports are Empty
Empty Usage Reports
View Popularity Trends and Most Popular Items
Planning for monitoring in SharePoint 2013
Microsoft Troubleshooting Methodology
Split-Half Troubleshooting
Deductive Reasoning vs. Inductive Reasoning
SharePoint Farm Documentation Scripts at Codeplex.com
Acceleratio Documentation Toolkit for SharePoint
TechNet SharePoint Updates Center
Stefan Goßner's Blog
Difference between CU, PU, and service packs
How to find your SharePoint version with PowerShell
Software Updates Overview for SharePoint 2013
Farm Patching Explained
Be careful-some patches are on Windows Update
Communications Protocol (Wikipedia)
SharePoint Ports and Protocols
Using IIS Request Tracing
Enable the Developer Dashboard
SharePoint 2013 Troubleshooting Guide
SharePoint 2013 Administration Inside Out
Microsoft Message Analyzer
Microsoft Message Analyzer Operating Guide
Wireshark
Fiddler
Decrypting SSL Traffic with Wireshark
Webalizer
SharePoint Manager 2013
FeatureAdmin for SharePoint 2013
How to Use Kerbtray
Wednesday, December 10, 2014
Monday, December 8, 2014
SharePoint 2013 Distributed Cache service update!
Introduction
Maybe most of you want to update / updated or don't know that you could update SharePoint 2013 Distributed Cache Service.
First of all I need to say that you have to be very careful with Distributed Cache Service in SharePoint 2013!!!
I strongly recommend to read the Wictor Wilen SharePoint Blog carefully!!
I used the aforementioned procedure for several production environments and I could say it is working.
BUT there is only one exception when you are trying to update Distributed Cache in Cache cluster scenario!
Exception
There is a little exception I would like to share with you. When you gracefully stop Distributed cache.
You will need to wait some time, so cached items are transferred to the another active node in Distributed cache cluster.
For example we have 2 servers in our Cache cluster: server1 and server2. Before we stop distributed cache service on server1 we could check the health of the cluster. Normally it should look like this:
Afeter
You have to execute several time Get-CacheClusterHealth until Unallocated named cache fractions "disappear"
When you get the following:
You are ready to patch/update you distributed cache service.
In case you follow these additional steps you would be able to update your Distributed Cache Service without any issues/problems.
Feel free to contact me in case you need more help / information.
Enjoy!
Maybe most of you want to update / updated or don't know that you could update SharePoint 2013 Distributed Cache Service.
First of all I need to say that you have to be very careful with Distributed Cache Service in SharePoint 2013!!!
I strongly recommend to read the Wictor Wilen SharePoint Blog carefully!!
I used the aforementioned procedure for several production environments and I could say it is working.
BUT there is only one exception when you are trying to update Distributed Cache in Cache cluster scenario!
Exception
There is a little exception I would like to share with you. When you gracefully stop Distributed cache.
Stop-SPDistributedCacheServiceInstance -Graceful
You will need to wait some time, so cached items are transferred to the another active node in Distributed cache cluster.Stop-SPDistributedCacheServiceInstance -GracefulFor example we have 2 servers in our Cache cluster: server1 and server2. Before we stop distributed cache service on server1 we could check the health of the cluster. Normally it should look like this:
- use-cachecluster
- get-cacheclusterhealth
Afeter
Stop-SPDistributedCacheServiceInstance -Graceful you need to wait until "Unallocated named cache fractions" are transferred to server2, in our case.You have to execute several time Get-CacheClusterHealth until Unallocated named cache fractions "disappear"
When you get the following:
You are ready to patch/update you distributed cache service.
In case you follow these additional steps you would be able to update your Distributed Cache Service without any issues/problems.
Feel free to contact me in case you need more help / information.
Enjoy!
Friday, November 28, 2014
How to install Symantec Protection for SharePoint
Hello all,
yesterday I mange to fix another mystery with Symantec Protection for SharePoint Servers (SPSS), latest version - 7.0.5.8.
Environment - SharePoint 2013 September 2014 CU.
According to Symantec the service account should have the following permissions:
BUT when I checked the SPSS service I was surprised - the service was NOT RUNNING. If you try to start it I got the following error:
My first impression was that it should be something wrong with the account ... but it wasn't.
If you try to reinstall SPSS the result will be the same.
Fortunately inside the security log I found the following Audit Failure:
Fortunately this is easy to fix - just add the used account to the local GPO in log on as a service
And I thought finally it should start ... unfortunately no, it was not able to start ... grrrrrrrrr
The next error was:
Log Name: Application
Source: Symantec Protection for SharePoint Servers Service
Date: 27.11.2014 11:39:04
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: XXXX
Description:
Module=DirectorThread | Exception message=Requested value 'SPVERSION' was not found. | Stack= at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
at Symantec.Sharepoint.Utility.FarmManager.IsSharePointFarm()
at Symantec.Sharepoint.Service.DataAccess.SPSSDal. ()
at Symantec.Sharepoint.Service.DataAccess.SPSSDal..ctor()
at Symantec.Sharepoint.SPSSService.Code.DirectorThread.ThreadProc()
Symantec suggested the following:
The solution is to lower the User Account Control level during the install, or if needed turning off User Account Control for the account Symantec Protection for SharePoint Servers 6.0 will run as. To do this go to Control Panel -> User Accounts -> click on Change User Account settings. Lower the level to Never notify, and click OK. Attempt to install Symantec Protection for SharePoint Servers 6.0 again, this time the install should work without throwing the mentioned exception above. After SPSS 6.0 is installed the User Account Control Level can be returned to its previous level.
Sounds good, sounds really good ... BUT no, this solution is not going to fix the problem.
The real solution is to disable the UAC through the registry - turn off UAC via registry by changing the DWORD "EnableLUA" from 1 to 0 in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system"
Reboot of the server is required and when I reinstall the SPSS everything was working just fine.
Hope you will find this article useful!
Enjoy and comment!
yesterday I mange to fix another mystery with Symantec Protection for SharePoint Servers (SPSS), latest version - 7.0.5.8.
Environment - SharePoint 2013 September 2014 CU.
According to Symantec the service account should have the following permissions:
- Local Administrator - the server where SPSS will run
- SharePoint Farm administrator
- 'db_creator' Server Role on SQL
- 'db_owner' permission for SharePoint Config and Content DBs
BUT when I checked the SPSS service I was surprised - the service was NOT RUNNING. If you try to start it I got the following error:
My first impression was that it should be something wrong with the account ... but it wasn't. If you try to reinstall SPSS the result will be the same.
Fortunately inside the security log I found the following Audit Failure:
Fortunately this is easy to fix - just add the used account to the local GPO in log on as a service
And I thought finally it should start ... unfortunately no, it was not able to start ... grrrrrrrrr
The next error was:
Log Name: Application
Source: Symantec Protection for SharePoint Servers Service
Date: 27.11.2014 11:39:04
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: XXXX
Description:
Module=DirectorThread | Exception message=Requested value 'SPVERSION' was not found. | Stack= at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
at Symantec.Sharepoint.Utility.FarmManager.IsSharePointFarm()
at Symantec.Sharepoint.Service.DataAccess.SPSSDal. ()
at Symantec.Sharepoint.Service.DataAccess.SPSSDal..ctor()
at Symantec.Sharepoint.SPSSService.Code.DirectorThread.ThreadProc()
Symantec suggested the following:
The solution is to lower the User Account Control level during the install, or if needed turning off User Account Control for the account Symantec Protection for SharePoint Servers 6.0 will run as. To do this go to Control Panel -> User Accounts -> click on Change User Account settings. Lower the level to Never notify, and click OK. Attempt to install Symantec Protection for SharePoint Servers 6.0 again, this time the install should work without throwing the mentioned exception above. After SPSS 6.0 is installed the User Account Control Level can be returned to its previous level.
Sounds good, sounds really good ... BUT no, this solution is not going to fix the problem.
The real solution is to disable the UAC through the registry - turn off UAC via registry by changing the DWORD "EnableLUA" from 1 to 0 in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system"
Reboot of the server is required and when I reinstall the SPSS everything was working just fine.
Hope you will find this article useful!
Enjoy and comment!
Subscribe to:
Posts (Atom)