SQL Standard OR Enterprise Version of RS (Reporting services) for SharePoint 2013

I got a nice finding about using either a MSSQL Standard OR Enterprise version of RS for SharePoint 2013.

1- if you use the SQL Standard 2012 for RS in SharePoint 2013, you will not be able to activate the SQL Server Reporting Services on more than one application Servers of SharePoint.

2- If you use Enterprise version of SQL 2012, the SQL Server Reporting Service can be started on multiple application servers.

Here is more details about it.

http://netwovenblogs.com/2013/08/04/reporting-services-in-sharepoint-2013-integrated-mode-cannot-support-scale-out-mode/

SQL Server Reporting Services Scale-out mode is supported by following SQL Server editions: Enterprise, Business Intelligence. (Refer MSDN: Features Supported by the Editions of SQL Server 2012)
With your SQL Server 2012 Enterprise or Business Intelligence editions, under your SharePoint 2013 (2010) you could always scale out to more than one SharePoint server. (Refer MSDN Add an Additional Report Server to a Farm (SSRS Scale-out) )
While you have SQL Server 2012 Standard edition, under the SharePoint 2013 Farm, you can have only one instance of SQL Server Reporting Services in the SharePoint Integrated mode. While you try to start another instance of Reporting Service in the farm on different server within the Farm, you will receive the above message.
If you intend to start the SQL Server Reporting Services on a different server than the service is currently running, you should first stop the service on the current running service and then start on your desired server. But also be aware other installation and configuration requirements for hosting the SSRS Service on the Server before you try to start the SSRS Service on a new server

Configure Custom Access Denied Page - SP 2013

I found a really nice article for creating custom access denied page from Danish.

http://a2zdinesh.blogspot.in/2014/05/configure-custom-access-denied-page-bug.html


Danish also explained the step by step configuration (Development and deployment) for creating custom access denied page.

Running Powershell for SharePoint Online from local machine

1- download SharePoint Online Management Shell  on your local machine.

Download SharePoint Online Management Shell

2- once this is installed, you will find an icon for Powershell Online.

3- click on that icon.

4- before you execute any command for SharePoint online. run the below command

Import-Module Microsoft.Online.SharePoint.PowerShell -DisableNameChecking

5- With SharePoint 2013 online you need to connect to your tenant administration site to be able to do anything.

Connect-SPOService –url  $siteCollectionUrl –Credential $O365Credential

6-Note: I was facing an error while executing the above command. i took the help from microsoft office 356 community. see the link below.

Help from office 365 community


7- Finally i got it run. after executing the step 4. i ran the below command.
$cred = [System.Net.CredentialCache]::DefaultCredentials
[System.Net.WebRequest]::DefaultWebProxy.Credentials = $cred

8- then i ran the command in step 5 and i was able to connect to SharePoint Online powershell.




PowerShell script to Take a backup of Service application in SP 2013

 
Below is the Power Shell script to Take a backup of Service application in SP 2013

 
$currentDateTime = (Get-Date -Format yyyy-MM-dd-HH-mm)
$SrvAppFolder = Test-Path "\\$env:computername\SPServiceApplicationBackup\"


#add sharepoint snapin
Add-PSSnapin microsoft.sharepoint.powershell 
    
#Backup Service Applications
#Excel Services Application
Backup-SPFarm -Directory $backupSAFolder -BackupMethod Full -Item "Farm\Shared Services\Shared Services Applications\Excel Services Application"
        
#Secure Store Service 

Backup-SPFarm -Directory $backupSAFolder -BackupMethod Full -Item "Farm\Shared Services\Shared Services Applications\Secure Store Service"
Backup-SPFarm -Directory $backupSAFolder -BackupMethod Full -Item "Farm\Shared Services\Shared Services Proxies\Secure Store Service"

Re-ghost Items presented in Master page gallery

I found a nice article about re-ghost items (specially for master pages and page layouts)

http://mosshowto.blogspot.nl/2008/10/re-ghost-master-pages-sharepoint.html

Error While Creating Web Application in SharePoint 2013

Error : While creating a new web application in SharePoint 2013 using central administration, I was getting the below error every time. "Internet Explorer cannot display the webpage".















Solution :
1- Go to IIS Manager.
2- Look for the application pool "DefaultAppPool"
3- Change the following 3 Process Model time settings
3a.Ping Maximum Response Time --> set to 400
3b.Shutdown Time Limit --> set to 400
3c.Startup Time Limit --> set to 400
4. reset the IIS. Try to create the web application once again.



Once the web application is created, you can revert the settings to 90 and finally do the IISRest Once again. I got the above information from the below post.
http://blogs.ibs.com/Duane.Odum/Lists/Posts/Post.aspx?ID=33

Find List details if you know the List IDs

if you only know the list id and want to know the other details of the list, below is the code to get that
protected void Page_Load(object sender, EventArgs e)
{
string[] _listArray = {"List ID 1", "List ID 2", "List ID 3"};
using (SPSite oSite = new SPSite("MySiteURL"))
{
SPWeb oWeb = oSite.OpenWeb();
SPListCollection allLists = oWeb.Lists;
foreach (SPList list in allLists)
{
foreach (string singleArraylist in _listArray)
{
if (list.ID.ToString().ToUpper() == singleArraylist.ToString().ToUpper())
{
Response.Write("List Name :\t" + list.Title + " List ID :" + list.ID + "");
}
}
}
}
}

Know the site template used for the SharePoint site

Using STSADM.EXE: It needs high level permissions. Means the user should be an administrator on the server. Below is the command we need to use for knowing the site template. stsadm.exe -o enumallwebs -database [content database name] for more details see the below link http://praveenbattula.blogspot.nl/2010/08/know-site-template-used-for-sharepoint.html

SharePoint 2003 to MOSS 2007 Upgrade: Database migration

I found a really nice article about database migration from SharePoint 2003 to MOSS 2007.

the blog post describe, how to take a backup of SP 2003 content database and migrate the same in MOSS 2007 with step by step instruction

http://farhanfaiz.wordpress.com/2008/05/23/sharepoint-upgrade-database-migration/

Decompile .net assembly ildasm

if you want to de compile a .net assembly (dll), you can use a visual studio option to de-complie it.

if you have visual studio installed in the machine. 

1- Go to Visual Studio Tools --> Visual Studio command prompt.
2- write ILDASM

it will open an interface where you can open your dotnet assembly and de-compile it. the best option to decompile any .net dll is .Net Reflector by red-gate. Please visit the below link to download the .Net reflector. It allows you to export the entire source code with in the assembly.

http://www.red-gate.com/products/dotnet-development/reflector/