SSRS 2012 installation in SharePoint 2013 integration mode , sometimes failed. It may be the due to the SharePoint web applications web.config file may contains
< ! - - comments - - > lines (this is one of the reason for the failure)
Try to remove the comments
< ! - - comments - - > lines lines and try to install.
It’s better to install SSRS in SharePoint 2013 server at initial stage so that before customizing the web.config (with comments lines) to avoid this problem.
Hope this may helpful for someone.
Some time we may need to generate a GUID in SQL Server, and there is a function provided in SQL Server called NewID()
Say for e.g the following query will insert a record into a table named Employee with GUID
SELECT NEWID() as ‘UniqueID’ , ‘Kumar’, as ‘EMPNAME’ INTO #TmpEmp
SELECT * FROM #TmpEmp
In SharePoint 2010, with administrators account (not the default Sharepoint System account) users getting the object reference not set to an instance of an object.
To solve the issue, we need to give shell access permission in the SQL Server for that particular user in SharePoint_config database.
Go to SQL Management Studio -> Login using sa account/admin login -> Select Security ->expand login -> select the user (if its not there add the user and select) -> properties
Please check the below screen for the permission
I hope this may helpful for who are always using System account to deploy the solution, even if you have another account which has admin rights.
In SharePoint if we are not taking backup periodically the log db of content database will grow very large, We can shrink the log db using the following command in SQL Server.
BACKUP LOG db_name WITH TRUNCATE_ONLY
Also check this link for script to shrink the log db.