Thursday, March 5, 2015
How to backup a site collection in Sharepoint using Powershell?
Add-PsSnapin Microsoft.SharePoint.PowerShell
Start-SPAssignment -Global # This cmdlet takes care of the disposable objects to prevent memory leak.
$today=Get-Date -format "MM-dd-yyyy HH.mm.ss" # Get current date and format it to avoid invalid characters such as "/" and ":"
$mySite="http://site" # Replace with your site collection URL
$backupLocation="c:\backup\$today" # Replace with your backup location
$logFile="$backupLocation\BackupLog.log" # Replace with your desired log file location
#check if backup directory exist. if not create them.
if (-not (Test-Path $backuplocation)) {
New-Item $backuplocation -type directory
}
write-Host Start backing up $mySite to $backupLocation
try
{
# Create a new backup file and name it based on current date. If you want to create only 1 backup file and overwrite it each time the backup is run, you can replace "$today.bak" with your desired file name.
Backup-SPSite -Identity $mySite -Path $backupLocation\$today.bak -force -ea Stop
write-Host Backup succeeded.
# Write success message to the log file
write "$today $mySite successfully backed up.">>$logFile
}
catch # If the process failed
{
write-Host Backup failed. See $logFile for more information.
# Write error message to the log file
write "$today Error: $_">>$logFile
}
Stop-SPAssignment -Global
Remove-PsSnapin Microsoft.SharePoint.PowerShell
write-Host "Finished script."
Wednesday, March 4, 2015
How to enable cell storage service in a Sharepoint environment for Office 2007 documents to open in Read/Write mode?
Run the below script to enable back the cell storage service at SP web application level for Office 2007 documents to open in read\write mode.
#-----------------------------------------------------
# Enable cell storage
# This script will enable cell storage on a given
# SharePoint web application
#-----------------------------------------------------
# Set this to the URL of your web application
$webApplicationURL = "http://contoso.com"
#-----------------------------------------------------
# Script body - nothing to change here
#-----------------------------------------------------
if((get-pssnapin 'microsoft.sharepoint.powershell' -ea 0) -eq $null){add-pssnapin microsoft.sharepoint.powershell}
$wa = get-spWebApplication $webApplicationURL -ea 0
cls
if($wa -ne $null)
{
if($wa.cellStorageWebServiceEnabled)
{
write-host "Cell storage is already enabled on the web application $($wa.url)."
}
else
{
$wa.cellStorageWebServiceEnabled = $true
$wa.update()
write-host "Cell storage was successfully enabled on the web application $($wa.url)"
}
}
else
{
write-host "Couldn't find web application $webApplicationURL."
}
#-----------------------------------------------------
# Enable cell storage
# This script will enable cell storage on a given
# SharePoint web application
#-----------------------------------------------------
# Set this to the URL of your web application
$webApplicationURL = "http://contoso.com"
#-----------------------------------------------------
# Script body - nothing to change here
#-----------------------------------------------------
if((get-pssnapin 'microsoft.sharepoint.powershell' -ea 0) -eq $null){add-pssnapin microsoft.sharepoint.powershell}
$wa = get-spWebApplication $webApplicationURL -ea 0
cls
if($wa -ne $null)
{
if($wa.cellStorageWebServiceEnabled)
{
write-host "Cell storage is already enabled on the web application $($wa.url)."
}
else
{
$wa.cellStorageWebServiceEnabled = $true
$wa.update()
write-host "Cell storage was successfully enabled on the web application $($wa.url)"
}
}
else
{
write-host "Couldn't find web application $webApplicationURL."
}
Office 2010 Documents in SharePoint 2010 opening in Read-Only but Office 2007 opening fine in Read/Write
There are some issues when you move to Office 2010 from office 2007 in SharePoint and documents start opening in Read only mode and are not editable.
Please use the below script to run to disable-cellstorage script service for office at SP Web application level.
#-----------------------------------------------------
# Disable cell storage
# This script will disable cell storage on a given
# SharePoint web application
#-----------------------------------------------------
# Set this to the URL of your web application
$webApplicationURL = "http://webapp"
#-----------------------------------------------------
# Script body - nothing to change here
#-----------------------------------------------------
if((get-pssnapin 'microsoft.sharepoint.powershell' -ea 0) -eq $null){add-pssnapin microsoft.sharepoint.powershell}
$wa = get-spWebApplication $webApplicationURL -ea 0
cls
if($wa -ne $null)
{
if($wa.cellStorageWebServiceEnabled)
{
$wa.cellStorageWebServiceEnabled = $false
$wa.update()
write-host "Cell storage successfully disabled on the web application $($wa.url)."
}
else
{
write-host "Cell storage is not currently enabled on the web application $($wa.url)"
}
}
else
{
write-host "Couldn't find web application $($wa.url)"
}
Below is the link to learn more about cellstorage service.
http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2013/01/10/CellStorage.svc-_2D00_-Intelligence-Updating-with-Office-Clients.aspx
Please use the below script to run to disable-cellstorage script service for office at SP Web application level.
#-----------------------------------------------------
# Disable cell storage
# This script will disable cell storage on a given
# SharePoint web application
#-----------------------------------------------------
# Set this to the URL of your web application
$webApplicationURL = "http://webapp"
#-----------------------------------------------------
# Script body - nothing to change here
#-----------------------------------------------------
if((get-pssnapin 'microsoft.sharepoint.powershell' -ea 0) -eq $null){add-pssnapin microsoft.sharepoint.powershell}
$wa = get-spWebApplication $webApplicationURL -ea 0
cls
if($wa -ne $null)
{
if($wa.cellStorageWebServiceEnabled)
{
$wa.cellStorageWebServiceEnabled = $false
$wa.update()
write-host "Cell storage successfully disabled on the web application $($wa.url)."
}
else
{
write-host "Cell storage is not currently enabled on the web application $($wa.url)"
}
}
else
{
write-host "Couldn't find web application $($wa.url)"
}
Below is the link to learn more about cellstorage service.
http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2013/01/10/CellStorage.svc-_2D00_-Intelligence-Updating-with-Office-Clients.aspx
Saturday, December 20, 2014
An error has occurred during report processing. (rsProcessingAborted) Cannot impersonate user for data source 'DataSource1'. (rsErrorImpersonatingUser) This data source is configured to use Windows integrated security. Windows integrated security is either disabled for this report server or your report server is using Trusted Account mode. (rsWindowsIntegratedSecurityDisabled)
We were getting above error when trying to open the reports in Sharepoint where everythign seemed to be configured correctly
SP 2010 integration with Report server in Sharepoint Mode, Authentication was correct, reports were correct as was working fine in other environment and Sql server report server was showing integrated secuirty enabled.
Here is the solution that worked in our case.
1) This is related to permission issue.
SP 2010 integration with Report server in Sharepoint Mode, Authentication was correct, reports were correct as was working fine in other environment and Sql server report server was showing integrated secuirty enabled.
Here is the solution that worked in our case.
1) This is related to permission issue.
Open IIS
manager, click on the site, click authentication and make sure you have
the Windows and ASP.Net impersonation enabled on the site.Try to enabled Anonymous access for few mins and then do the iisreset. Once you do that and after few min, you will see that reports started opening without any errors. Once you conform its working, stop the Anonymous and restart the IIS again.
Once you do that, you will see site reports opening without any issue.
Sometime it is related to access to a folder or some settings that needs to be enabled but hard to find where is that the reports are looking for. Hope it helps people struglling with this isse as i was .:)
Once you do that, you will see site reports opening without any issue.
Sometime it is related to access to a folder or some settings that needs to be enabled but hard to find where is that the reports are looking for. Hope it helps people struglling with this isse as i was .:)
The request failed with HTTP status 401: Unauthorized in Sharepoint logs
Below is one of the solution suggested by microsoft in this types of issue
1) Disable Loopback check on SSRS server (Method 2)
- Click Start, click Run, type regedit, and then click OK.
- In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa - Right-click Lsa, point to New, and then click DWORD Value.
- Type DisableLoopbackCheck, and then press ENTER.
- Right-click DisableLoopbackCheck, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Quit Registry Editor, and then restart your computer.
2) The next thing you want to try to check the authentication level on your IIS. This is related to permission issue. We had the simlar problem in SSRS reporting not opening a custom reporting page containing report viewer webpart in a https site
Open IIS manager, click on the site, click authentication and make sure you have the Windows and ASP.Net impersonation enabled on the site. Check the same for the Default site if you are using it.
How to enable Incoming email on the list/Library in Sharepoint
Below are the steps that we need to perform to enable a library to receive incoming emails.
1) SMTP service has to be installed and enabled on the SP WFE server. This can be added from Windows Server manager under Features and add the SMTP feahttps://www.blogger.com/blogger.g?blogID=122518409722023608#editor/target=post;postID=695350418594854018ture
2) Next step is to open the IIS 6.0 amangement console and make sure that SMTP virtual server is up and running. If you want to ahve your own name, stop the existing one and create a new one with a good name and run it.
3) Now you open the windows serverices and start the SMTP service in WFE server and make sure it is set on Automatic.
4) By default the port assigned to SMTP service is 25. so make sure you have port open and is not blocked to enable the incoming email service.
5) Now open Central admin, configure Incoming email settings,
Select Yes to “Enable site on this server to receive e-mail”
Select “Automatic” for Setting mode or Advanced (Put the system drive inetpub directory for drop folder)
Select “Yes” to use the SharePoint Directory Management Service to create distributions groups and contacts.
Enter your Active Directory container details, i.e. the Organizational Unit container that we created specifically for our SharePoint 2010 contacts.
Ensure that your SMTP server details are correct, this should be the fully qualified domain name of your SMTP service that was installed on your SharePoint Server.
6) Make sure following accounts are added on drop folder with below permissions
WSS_Admin_WPG – Full Control and
WSS_WPG – Read & Execute / List folder Contents / Read
7) Also make sure that application pool account has read permission on the Drop folder as well to carry email over to the site level.
8) Now open the list\library and
Click on Incoming e-mail settings.
Select “Yes” to allow this document library to receive e-mail.
Thats it. now try sending email to the address and you will see email in the library
Below is a very good link with screenshots that can help
http://sharepointgeorge.com/2010/configuring-incoming-email-sharepoint-2010/
1) SMTP service has to be installed and enabled on the SP WFE server. This can be added from Windows Server manager under Features and add the SMTP feahttps://www.blogger.com/blogger.g?blogID=122518409722023608#editor/target=post;postID=695350418594854018ture
2) Next step is to open the IIS 6.0 amangement console and make sure that SMTP virtual server is up and running. If you want to ahve your own name, stop the existing one and create a new one with a good name and run it.
3) Now you open the windows serverices and start the SMTP service in WFE server and make sure it is set on Automatic.
4) By default the port assigned to SMTP service is 25. so make sure you have port open and is not blocked to enable the incoming email service.
5) Now open Central admin, configure Incoming email settings,
Select Yes to “Enable site on this server to receive e-mail”
Select “Automatic” for Setting mode or Advanced (Put the system drive inetpub directory for drop folder)
Select “Yes” to use the SharePoint Directory Management Service to create distributions groups and contacts.
Enter your Active Directory container details, i.e. the Organizational Unit container that we created specifically for our SharePoint 2010 contacts.
Ensure that your SMTP server details are correct, this should be the fully qualified domain name of your SMTP service that was installed on your SharePoint Server.
6) Make sure following accounts are added on drop folder with below permissions
WSS_Admin_WPG – Full Control and
WSS_WPG – Read & Execute / List folder Contents / Read
7) Also make sure that application pool account has read permission on the Drop folder as well to carry email over to the site level.
8) Now open the list\library and
Click on Incoming e-mail settings.
Select “Yes” to allow this document library to receive e-mail.
Thats it. now try sending email to the address and you will see email in the library
Below is a very good link with screenshots that can help
http://sharepointgeorge.com/2010/configuring-incoming-email-sharepoint-2010/
Powershell throwing error the execution of scripts is disabled on this system.
This is the message we get it when try to run any powershell script on the SP server where execution olicy is disabled. It is based on tht 64 and 32 bit tyoe. We have to ensure that the execution policy is enabled on both types of it.
Run the following command:-:- Set-ExecutionPolicy RemoteSignedOnce ran, you can verify using following command:- get-executionpolicy
Subscribe to:
Posts (Atom)