Sathiya's Blog

Cross Domain Error in Dynamic GP 2013 Web Client

The cross domain error would be occurred on Silverlight. Because distinct URL has been configured on session central service, session service and run time service. Severity: Critical Summary: An error occurred while initializing communication with the server. Details: [CrossDomainError] Arguments:

Verifying SMTP SharePoint Outbound mail settings

Once we configured the SharePoint outbound mail server then our responsible to test the setup. Here the small powershell snippet will do!

### The script will return True or False
$toemail = "sathiya@sathiya.io"
$subject = "Test - SharePoint Outbound mail"
$body = "This mail for testing purpose...! Please ignore your action!"
$site = New-Object Microsoft.SharePoint.SPSite "http://sharepoint/"
$web = $site.OpenWeb()
[Microsoft.SharePoint.Utilities.SPUtility]::SendEmail($web,0,0,$toemail,$subject,$body)

### The script will return True or False

$toemail = "sathiya@sathiya.io"

$subject = "Test - SharePoint Outbound mail"

$body = "This mail for testing purpose...! Please ignore your action!"

$site = New-Object Microsoft.SharePoint.SPSite "http://sharepoint/"

$web = $site.OpenWeb()

[Microsoft.SharePoint.Utilities.SPUtility]::SendEmail($web,0,0,$toemail,$subject,$body)

If you get “True” the configuration perfectly alright, else you have to check the ULS log to

Analyse MS-SQL Database Memory Utilization

In most of the development environment or staging server will not be monitored by daily. So the database auto growth can occupy countlessly. Here, we can analyze the memory utilization about the table and we can remove if the database

Create claims-based web application from SharePoint PowerShell

Creating claims-based web application is more flexible with SharePoint PowerShell script than CA. Here, the snippet for http and ssl site.

Add-PSSnapin Microsoft.SharePoint.Powershell
$ap = New-SPAuthenticationProvider
New-SPWebApplication -Name <Name> -ApplicationPool <ApplicationPool> -ApplicationPoolAccount <ApplicationPoolAccount> -URL <URL> -Port <Port> -AuthenticationProvider $ap
# <Name> is the name of the new web application that uses claims-based authentication.
# <ApplicationPool> is the name of the application pool.
# <ApplicationPoolAccount> is the user account that this application pool will run as.
# <URL> is the public URL for this web application.
# <Port> is the port on which the web application will be created in IIS.

# For Non-SSL
New-SPWebApplication -Name "Web Portal - 80" -ApplicationPool "Web Portal Application Pool - 80" -ApplicationPoolAccount (Get-SPManagedAccount "sathiya\sp_appPool") -URL http://webportal.sathiya.com -Port 80 -HostHeader webportal.sathiya.com -DatabaseName WSS_Content_WebPortal_80 -Path "D:\Web_Portal_80" -AuthenticationProvider $ap 

# For SSL 
New-SPWebApplication -Name "Web Portal - 443" -ApplicationPool "Web Portal Application Pool - 443" -ApplicationPoolAccount (Get-SPManagedAccount "sathiya\sp_appPool") -URL https://webportal.sathiya.com -Port 443 -HostHeader webportal.sathiya.com -DatabaseName WSS_Content_WebPortal_443 -Path "D:\Web_Portal_443" -SecureSocketsLayer -AuthenticationProvider $ap

Add-PSSnapin Microsoft.SharePoint.Powershell

$ap = New-SPAuthenticationProvider

New-SPWebApplication -Name <Name> -ApplicationPool <ApplicationPool> -ApplicationPoolAccount <ApplicationPoolAccount> -URL <URL> -Port <Port> -AuthenticationProvider $ap

# <Name> is the name of the new web application that uses claims-based authentication.

# <ApplicationPool> is the name of the application pool.

# <ApplicationPoolAccount> is the user account that this application pool will run as.

# <URL> is the public URL for this web application.

# <Port> is the port on which the web application will be created in IIS.

# For Non-SSL

New-SPWebApplication -Name "Web Portal - 80" -ApplicationPool "Web Portal Application Pool - 80" -ApplicationPoolAccount (Get-SPManagedAccount "sathiya\sp_appPool") -URL http://webportal.sathiya.com -Port 80 -HostHeader webportal.sathiya.com -DatabaseName WSS_Content_WebPortal_80 -Path "D:\Web_Portal_80" -AuthenticationProvider $ap

# For SSL

New-SPWebApplication -Name "Web Portal - 443" -ApplicationPool "Web Portal Application Pool - 443" -ApplicationPoolAccount (Get-SPManagedAccount "sathiya\sp_appPool") -URL https://webportal.sathiya.com -Port 443 -HostHeader webportal.sathiya.com -DatabaseName WSS_Content_WebPortal_443 -Path "D:\Web_Portal_443" -SecureSocketsLayer -AuthenticationProvider $ap

Cheers…!

Delete SharePoint list items from PowerShell

Here the quick solution to clean up/delete SharePoint list items that save a days lot if cleanup required. Manual efforts would take a lot so prefer to go with scripts;

# Enter the site URL instead http://sathiya.io
$weburl = "http://sathiya.io"
$site = new-object Microsoft.SharePoint.SPSite ($weburl)
$web = $site.OpenWeb()
Write-Host "The Web application is : "$web.Title
# Enter name of the List below insted of ProjectList
$oList = $web.Lists["ProjectList"];
$collListItems = $oList.Items;
$count = $collListItems.Count - 1
$itemCount = $contents.Count;
$currentItem = 1;
Write-Output -NoNewline "Are you sure you want to permanently delete the '$oList.ItemCount' item from the list '$oList.Title' (y/n)? " -NoNewline;
$con = Read-Host;
if ($con -eq "y") {
    for($intIndex = $count; $intIndex -gt -1; $intIndex--)
    {
        #Deleting the item from list
        "Deleting record: " + $intIndex
        $collListItems.Delete($intIndex);
    }
    Write-Host $itemCount "item has been deleted from the list '"$oList.Title "'...!" -ForegroundColor Yellow;
}
else {
    Write-Host "No changes are happened in the list'"$oList.Title "'...!" -ForegroundColor Black -BackgroundColor Green;
}
#Close the connection
$web.Dispose()

# Enter the site URL instead http://sathiya.io

$weburl = "http://sathiya.io"

$site = new-object Microsoft.SharePoint.SPSite ($weburl)

$web = $site.OpenWeb()

Write-Host "The Web application is : "$web.Title

# Enter name of the List below insted of ProjectList

$oList = $web.Lists["ProjectList"];

$collListItems = $oList.Items;

$count = $collListItems.Count - 1

$itemCount = $contents.Count;

$currentItem = 1;

Write-Output -NoNewline "Are you sure you want to permanently delete the '$oList.ItemCount' item from the list '$oList.Title' (y/n)? " -NoNewline;

$con = Read-Host;

if ($con -eq "y") {

for($intIndex = $count; $intIndex -gt -1; $intIndex--)

{

#Deleting the item from list

"Deleting record: " + $intIndex

$collListItems.Delete($intIndex);

}

Write-Host $itemCount "item has been deleted from the list '"$oList.Title "'...!" -ForegroundColor Yellow;

}

else {

Write-Host "No changes are happened in the list'"$oList.Title "'...!" -ForegroundColor Black -BackgroundColor Green;

}

#Close the connection

$web.Dispose()

Cheers…!

Export Windows Service to Excel with Filter

Another sample Powershell script to exporting “Running” and “Stopped” windows service to excel by using Powershell Array.

$location = "C:\sathiya.io";
$service = @("Running", "Stopped");
for ($i=0;$i -ne 2;$i++)
{
	$text = $service[$i];
	#Exporting the result to the text file
	# Append - This keyword is to update the file in the loop
	# Select - To export the field that you want to export
	Get-Service |?{$_.Status -eq "running"} | Select ServiceName, Status | Out-File $location\text1.txt -Append
	#Exporting the result to CSV
	Get-Service |?{$_.Status -eq $text} |  Select ServiceName, Status | export-csv $location\file2.csv -Append
}

$location = "C:\sathiya.io";

$service = @("Running", "Stopped");

for ($i=0;$i -ne 2;$i++)

{

$text = $service[$i];

#Exporting the result to the text file

# Append - This keyword is to update the file in the loop

# Select - To export the field that you want to export

Get-Service |?{$_.Status -eq "running"} | Select ServiceName, Status | Out-File $location\text1.txt -Append

#Exporting the result to CSV

Get-Service |?{$_.Status -eq $text} | Select ServiceName, Status | export-csv $location\file2.csv -Append

}

Cheers!

Creating Managed Metadata Service Application by Powershell Script

As we are all knows, the SharePoint Powershell can be fast and simple. Here the sample script for creating Managed Metadata Service Application;

New-SPServiceApplicationPool -Name "Managed Metadata Service App Pool" -Account sathiya\SPAppPool
New-SPMetadataServiceApplication -Name "Managed Metadata Service Application" -ApplicationPool "Managed Metadata Service App Pool" -DatabaseName "MMD"
New-SPMetadataServiceApplicationProxy -Name "Managed Metadata Service App Pool" -ServiceApplication "Managed Metadata Service Application"

New-SPServiceApplicationPool -Name "Managed Metadata Service App Pool" -Account sathiya\SPAppPool

New-SPMetadataServiceApplication -Name "Managed Metadata Service Application" -ApplicationPool "Managed Metadata Service App Pool" -DatabaseName "MMD"

New-SPMetadataServiceApplicationProxy -Name "Managed Metadata Service App Pool" -ServiceApplication "Managed Metadata Service Application"

Cheers!

SharePoint continuous user login prompting with custom host header site

SharePoint site with custom host header will prompting the user login screen on local machine but either you can login or view the site from your local network machines. Because the loop back is enabled by default on each and

Import Users in Active Directory Using PowerShell

Today, we are going to discuss about importing bulk users in Active Directory using PowerShell. We are all knows that we can do anything in PowerShell. You can check the required parameter for adding AD user. But I’m going to

Application error when access “/_layouts/15/workflow.aspx”

After, I installed and configured the workflow for SharePoint 2013 and register to the web application, it was getting an error while starting the workflow as; Error: Message: Application error when access /_layouts/15/workflow.aspx, Error=The pipe endpoint ‘net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc’ could not be