Dhruv Shah's SharePoint Blog

SharePoint 2010 + Powershell + Get Profile Property Values for each ProfileUser

2012-01-25T08:59:00.000-08:00

Scenario: You have thousands of users and hundreds of profile properties in user profile service application. For each user, you want to get the list of profile properties and their associated values then the following scripts can be used.
Part 1: Get the list of profile properties display and internal names:
#######Script Part 1 Start#########
param
(
$siteAddress = "Provide MySite URL"
)
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Server.UserProfiles")

try
{
$site = New-Object Microsoft.SharePoint.SPSite $siteAddress
$context = [Microsoft.SharePoint.SPServiceContext]::GetContext($site)
$configManager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileConfigManager $context
$propertyManager = $configManager.ProfilePropertyManager
set-variable -option constant -name out -value "C:\ProfileProperties.csv"

echo "Display Names"| Out-File $out -append
foreach ($codeProperty in $propertyManager.GetCoreProperties())
{
$codeProperty.DisplayName+","| Out-File $out -append
}
echo "================================================="| Out-File $out -append
echo "Just Names(May be internal)"| Out-File $out -append
foreach ($codeProperty in $propertyManager.GetCoreProperties())
{
$codeProperty.Name+","| Out-File $out -append
}
}
finally
{
if ($site -ne $null)
{
$site.Dispose()
}
}
Echo "Finished!"

This will output the .csv file. Locate the internal names, put them in quotes, and separate them using commas ,.
Part 2: We will provide the list of internal names of properties as an array and the following script needs to be run as scriptname.ps1 | out-file out.txt.
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Server")
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Server.UserProfiles")
[void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
$site =new-object Microsoft.SharePoint.SPSite("Provide Central Admin URL");
$ServiceContext = [Microsoft.SharePoint.SPServiceContext]::GetContext($site);
$ProfileManager = new-object Microsoft.Office.Server.UserProfiles.UserProfileManager($ServiceContext)
$AllProfiles = $ProfileManager.GetEnumerator()
$mySiteUrl = "Provide MySite URL"
//In the following line provide the profile property internal names
$upAttribute = @("UserProfile_GUID","SID","AccountName","FirstName","LastName")
$site1 = Get-SPSite $mySiteUrl
$context = Get-SPServiceContext $site1
$profileManager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($context)
foreach($profile in $AllProfiles)
{
$adaccount = $profile[[Microsoft.Office.Server.UserProfiles.PropertyConstants]::AccountName].Value
if ($profileManager.UserExists($adAccount))
{
$up = $profileManager.GetUserProfile($adAccount)
foreach ($ua in $upAttribute)
{
#if($up[$ua].Value -match "Something") - use this line if you want to get the values which has 'something' in it
#{
$adAccount+" ; "+ $ua +" ; "+$up[$ua].Value + ";"
#}
}
}
else
{
echo "Profile for user"$adAccount "cannot be found"
}

}
#write-host "Finished."
echo Finished
$site.Dispose()
$site1.Dispose()

the output can be easily imported in an excel and utilized for various administrative purpose.
Extras:
To change the profile property value use the following
#Set up default variables
$mySiteUrl = "http://mysite"
$adAccount = "DOMAIN\username"
$upAttribute = "WebSite"
$upAttributeValue = “new value”
#Get site objects and connect to User Profile Manager service
$site = Get-SPSite $mySiteUrl
$context = Get-SPServiceContext $site
$profileManager = New-Object Microsoft.Office.Server.UserProfiles.UserProfileManager($context)
#Check to see if user profile exists
if ($profileManager.UserExists($adAccount))
{
#Get user profile and change the value
$up = $profileManager.GetUserProfile($adAccount)
$up[$upAttribute].Value = $upAttributeValue
$up.Commit()
}
else
{
write-host "Profile for user"$adAccount "cannot be found"
}

#Dispose of site object
$site.Dispose()
References:
http://get-spscripts.com/2010/07/modify-single-value-user-profile.html
http://ghamson.wordpress.com/2010/11/04/updating-user-profile-properties-via-powershell-pictureurlsharepoint-2010-in-sp2010/
Enjoy...

Installing Service Pack 1 and August 2011 CU to Multi Server SharePoint 2010 Farm with Language Packs and Project Server 2010 installed

2012-01-23T08:48:00.000-08:00

With Project Server Installed on SharePoint Server, it is very confusing to determine which packages to download and which installation sequence/order to follow. I hope the following helps SharePoint and/or project server administrators:
Prerequisites:
1. Check Disk space on both WFEs,
2. Check for Pending upgrade status in CA and try to fix those if possible,
3. Check MSSQL disk space
4. Download and locate packages
5. Open Task manager and make sure no other user is logged on
Execution:
*We can concurrently install binaries on both WFEs*
Note:If the installation of packages takes too much time you can change the processor affinity and Priority. Here is how:
1. Open task manager when the installation is in progress
2. Find and select the process under processes tab
3. Right click the process select 'set priority'
4. You can change the priority from 'Normal' to 'Above Normal' or 'High' or 'Realtime'
5. Again select the process under processes tab
6. Right click the process and select 'Set Affinity...'
7. Select all processors
Service Pack 1 [SP farm Build Version upgrade from 14.0.4762.1000/14.0.4763.1000 to 14.0.6029.1000]
1. Login to the boxes using farm admin account
2. Stop the World Wide Web Publishing Service (w3svc) and Microsoft Project Server Queue service 2010 on both WFEs
a. This will prevent any users from accessing the sites when the packages are being installed.
3. Install 'SharePoint Foundation 2010 Service Pack 1' on both WFEs.
a. Package name - sharepointfoundation2010sp1-kb2460058-x64-fullfile-en-us.exe
b. Size - 44236KB
c. After the installation is complete it will ask you to reboot to complete the installation. You can select no and choose to reboot later. In our case, we rebooted the servers.
4. After restart, stop the World Wide Web Publishing Service (w3svc) and Microsoft Project Server Queue service 2010 on both WFEs
5. Install ‘SharePoint Project Server 2010 Service Pack 1’ on both WFEs
a. Project Server 2010 Service Pack 1 also contains Service Pack 1 updates for SharePoint Server 2010, and both are applied automatically during the installation process
b. Package name - officeandprojectserver2010sp1-kb2460047-x64-fullfile-en-us.exe
c. Size - 401415KB
6. After installing the above package,
a. There is no need to install ‘Service Pack 1 for SharePoint Foundation 2010 Language Pack (Package name - spflanguagepack2010sp1-kb2460059-x64-fullfile-en-us.exe)’ When we tried to install the same we got ‘There are no products affected by this package installed on this system’ message.
b. After installing the above package, there is no need to install ‘service Pack 1 for Server Language Pack 2010 (Package name - serverlanguagepack2010sp1-kb2460056-x64-fullfile-en-us.exe)’ When we tried to install the same we got ‘The update is already installed on this system’ message.NOTE:we encountered an environment where we did not get ‘The update is already installed on this system’ message. The package actually got installed and it took 1.5 hours. So, better to have these packages ready and we should check once running it.
7. Run ‘SharePoint Products and Configuration Wizard’ on both WFEs - Run it on the server with Central Administration first
a. In our case we were not able to run the wizard successfully. Some content databases were referencing a feature which was not installed on the farm. And some content databases were complaining about the orphaned sites. You can get this info in upgrade log error in 14/logs folder
b. We detached the databases, did IISRESET and reran the wizard again and it ran successfully. (Sometimes just rerunning the wizard results in success! – withouts even fixing the errors)
c. Make sure to run the wizard successfully on server CA first and then start running it on another WFEs
d. We attached back the databases after running the wizard on both servers.
8. Restart both the servers
9. Testing for successful SP1 deployment
a. Login to CA,
i. Check the configuration database build version
ii. Check the content database schema version
iii. Check the product upgrade status
iv. Check the database upgrade status
v. You can also run stsadm –o localupgradestatus
August 2011 CU [SP farm Build Version upgrade from 14.0.6029.1000 to 14.0.6109.5002]
1. Stop the World Wide Web Publishing Service (w3svc) and Microsoft Project Server Queue service 2010 on both WFEs
2. Install ‘August 2011 CU for Project Server 2010 on both WFEs (CA server first)
a. It will ask to extract files, extract those on same folder
b. Package Name - 438520_intl_x64_zip.exe. After extraction - office2010-kb2553049-fullfile-x64-glb
c. This package includes CU Updates for SharePoint Server, SharePoint Foundation and SharePoint foundation language packs, SharePoint server language packs, Project Server language packs
d. Size - 1114120KB
3. Repeat steps 7, 8(restart is not mandatory), 9 (testing for CU) from SP1 installation steps
4. Manually start the World Wide Web Publishing Service (w3svc) and Project Queue service on both WFEs
5. Check user profile service app. If it is not working as expected restart the same.
References
1. http://technet.microsoft.com/en-us/library/hh272536.aspx#section3
2. http://technet.microsoft.com/en-us/library/dd239177.asp
3. http://blogs.technet.com/b/steve_chen/archive/2010/09/29/build-numbers-cube-sheet-for-sharepoint-2010.aspx
--END--

Before you use Ips with webapplication..

2011-12-20T08:59:00.000-08:00

It will some time just say that the IPs are available. but before you use them with webapplication do the following:
start-network-network and sharing center- click on cluster- on cluster dialog box click on properties-select (tcp/ipv4) and click on properties-on (tcp/ipv4) properties window click on advanced-on advanced tcp/ipv4) settings window under IP Addresses tab click ADD to add IP address. give the subnet mast as 255.255.255.0
After doing this you should be able to associate the IP to the webapp. Make sure to create a DNS entry or host file entry before you access the site.

SharePoint 2010 Document Library Export Import using Powershell

2011-11-21T09:09:00.000-08:00

Export Command:
Export-SPWeb -Identity -Path c:/export.cmp -ItemUrl -IncludeUserSecurity -IncludeVersions 4
Few things before you import:
- import will append the docs on the destination document library (will not overwrite anything on destination)
- I was not able to find na way to change the URL of a document library either thru GUI or thru SPD 2010. Using SPD 2007 i know we can use rename option. However here this option does not seem to be working
- I was not able to find a way to move the exported docs in a seperate folder on the destination doc lib
- I do not think that the import command allows to place the documents in a library with a different name than the source doc library
Import Command:
Import-SPWeb -Identity -Path c:/export.cmp
examples:
Export-SPWeb -Identity "https://Webapp/sitecoll/subsitecoll" -Path c:/exp.cmp -ItemUrl "Shared Documents" -IncludeUserSecurity -IncludeVersions 4
Import-SPWeb -Identity "https://newwebapporsame/sites(or any other managed path)/subweb" -Path c:/exp.cmp
Import-SPWeb -Identity -Path [-Force] [-NoFileCompression] [-Verbose]
NOtes:
The export did not work for mysites user Pictures library.
CA granular backup worked
Import workes for mysites picture library.

list of sitecollection administrators and list of subsite owners

2011-11-09T11:33:00.000-08:00

1. this script drills down to the subsite level
2. this will also provide the email address of the users
3. run it with |out-file c:/owners.txt
4. import the .txt to excel with ; as delimited character
$siteUrls = @("webappurl1","webappurl2")

foreach ($siteUrl in $siteUrls)
{
$rootSite = New-Object Microsoft.SharePoint.SPSite($siteUrl)

$spWebApp = $rootSite.WebApplication

foreach($site in $spWebApp.Sites)

{

foreach($siteAdmin in $site.RootWeb.SiteAdministrators)

{
echo "$($siteAdmin.ParentWeb.Url) ; SiteAdministrators ;$($siteAdmin.DisplayName) ; $($siteAdmin.Email)"

}
foreach($web1 in $site.AllWebs)
{

foreach ($group in $web1.groups)
{

if ($group.name -match "owners")
{

foreach ($member in $group.users)
{

echo "$($web1.Url) ; $($group.name) ; $($member.DisplayName) ; $($member.Email)"
}
}

}

}
$web1.dispose()

$site.Dispose()
}

$rootSite.Dispose()

}

echo "operation Completed"

MOSS 2007 "Ttrial period for this product has expired" error

2011-05-17T13:55:00.000-07:00

Scenario:
You receive this error when you try to edit the page or create a new page.
WorkAround:
Go to All site content page --> click on pages --> check out page --> make changes --> check in --> publish as major version. Most of the times this will work.
Solution:
1) Add App pool accounts to 'Distributed Com Users' Group on all WFEs and APP servers
2) Run the Sharepoint products and technologies wizard on all the three servers
3) Do an IISreset on all the servers
4) 1-3 will fix the issue in most of cases.
5) If not, Download and install the following
Update for 2007 Microsoft Office servers (KB971620), 64-Bit Edition (32 bit for 32 machines)
Reference: http://support.microsoft.com/kb/971620/en-us
6) Reboot the server
This will fix the issue.
--ENJOY--

SharePoint Sites Migration to a new domain. The best way to handle URL redirects

2011-05-13T11:29:00.000-07:00

Scenario: Assume that you have two separate MOSS2007 instances running under inst1.comp.org and inst2.comp.org. You have to decommission inst1 server and hence have to move all the site-collections under http://inst1.comp.org to inst2.comp.org. After the successful migration what if some user tries to access the sites using the old url or what if he bookmarked some document library. I came up with a script (basic Javascript an some html) to handle this situation.
Solution:
Create a default.htm page and paste the following code:
<HTML>
<BODY>
<P>URL Redirect>/P>
<P>You will be redirected to your requested website which has been moved recently. </P>
&;t;P>Please make a note of a new URL and update your bookmarks>/P>

</BODY>
</HTML>
<script language="javascript" type="text/javascript">
document.write("You entered the following URL:");
var str1=document.location.href;
document.write(str1);
document.write(" ");
var str2=str1.replace("inst1.comp.org","inst2.comp.org");
var str3=str2.replace("/sites/one","/somethingelse/one");
var str4=str3.replace("/sites/two","/two");
document.write("The new URL will be:");
document.write(str4);
setTimeout("redirectpageto()", 5000);
function redirectpageto()
{
window.location=str9;
}
</script>
Create a web.config file and paste the following code :
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<httpRedirect enabled="false" destination="" exactDestination="false" />
<httpErrors>
<remove statusCode="404" subStatusCode="-1" />
<error statusCode="404" prefixLanguageFilePath="" path="/default.htm" responseMode="ExecuteURL" />
</httpErrors>
<staticContent>
<mimeMap fileExtension=".aspx" mimeType="text/aspx" />
</staticContent>
</system.webServer>
</configuration>

Once this two files are ready placed them in c:/newsite folder
then add this folder as a website in IIS(with dedicated IP address of old (inst1)server->if it is SSL make sure to select port 443-> then select the host header (or a DNS entry will work)
Add it as a website on all WFEs on inst2 farm.
Note:if the dedicated ip is not available you can test it using host file entries
Advanced Scenario:
You do not have to manually download you can copy or move the server certificate from the old server's IIS, using the following steps you can copy or move the certificate from one server to another
Click on website-> properties->click on directory security tab->click on server certificate ->click on next->select last option ‘copy or move current certificate’->click next->select copy and then click next
==END==

Install Powershell 2.0 on Windows server 2008

2011-01-24T10:49:00.000-08:00

System requirements:
Windows server 2008 enterprise SP1 x64
What version of powershell you have?
-Click start-> type 'Power' in the search text box,
-Click on the 'Windows Powershell' icon to open powershell
-Type $PSVersionTable to get the version of the installed powershell
the above command did not work for me, so I ran the following command:
Get-host and it gave me the version number
-After confirming that you are running v1 of powershell, browse to the following URL:
http://www.microsoft.com/downloads/en/details.aspx?FamilyId=d37e25cf-db05-4b23-a852-cdf865d81b82&displaylang=en
-If you want to install it on any other OS with x86 or x64 get the appropriate resource from the following page:
http://support.microsoft.com/kb/968930
Key notes:
-There is no upgrade package which will let you upgrade from powershell v1 to 2
-No need to uninstall the existing poweshell with v1
-You must have to download windows update in order to install v2 of powershell.
this installer will automatically upgrate the powrshell from v1 to v2.
-Once you download the installer double click on it
-Read the license agreement and follow the steps to complete installation.
-Reboot is required
Testing for successful upgrade:
-Open windows powershell and type the command 'Get-host' and now it will show version : 2.0
Enjoy...

E-mail notification - Server has less Disk Space - Powershell Script

2010-11-05T13:06:00.000-07:00

Specifications/What does this script do?
1. Checks the server's disk space continuously
2. If the diskspace is lessthan 2GB on any disk on any server it will send an email and goes in sleep mode for 60 minutes, e site

Schedule it:
1. Create a batch file and schedule it to run on one time bases as this script runs continuously and automatically goes to start and sleep mode depending on whether it is able to ping the site.
THE SCRIPT:
do
{
# specify the server names in the following array
$strComputers = @("**","**","**")

$msg1=""
$flag=1

foreach ($server in $strcomputers)
{
try
{
$dsk= Get-WmiObject -computername $server Win32_LogicalDisk
foreach ( $drive in $dsk )
{
if(($drive.Name -ieq "C:") -or ($drive.Name -ieq "D:"))
{
$freespace=[int]($drive.FreeSpace/1073741824)
if ($freespace -ilt 2)
{
$msg1=$msg1+"Server: "+$server+" Drive: "+$drive.Name+" has less than 2 GB disk space!"+"`n"+"`n"
$flag=$flag+1
}
else
{
$msg1=$msg1
}
}
else
{
#nothing
}

}

}
catch
{
$msg1=$msg1+"Failure Getting "+ $server+ " DiskSpace Info"+"`n"+"Details:"+"`n"+$($_.Exception)+"`n"+"`n"
$flag=$flag+1
}
}

$smtpServer = "********"
$msg = new-object Net.Mail.MailMessage
$smtp = new-object Net.Mail.SmtpClient($smtpServer)
$msg.From = "*********"
$msg.To.Add("***************")
$msg.To.Add("***********")
$msg.Body = $msg1
if ($flag -igt 1)
{
$today=get-date
$msg.Subject = "Sharepoint Disk Space Alert " + $today
$smtp.Send($msg)
Start-Sleep -s 3600
}
else
{
$msg.Subject = "The server has enough DiskSpace"
echo SUCCESS
Start-Sleep -s 1800
}
$response = "Y"
} #end of DO
while ($response -eq "Y")
--End--
Enjoy

E-mail notification when the site is down - Powershell Script

2010-11-05T13:00:00.000-07:00

Specifications/What does this script do?
1. Pings the site specified
2. If the site is up it will rerun after 10 seconds
3. if the site is down, sends an email to the specified recipients with the error message, and the disk space and log reports from the associated servers specified.
4. After sending an email it will not run for next 60 minutes, giving administrators the chance to recover the site

Prerequisites:
1. On the server where you want to run this PowerShell script needs to have PowerShell 1.0 or later installed.
2. The execution policy needs to be set as ‘remote signed’
• Right click on the ‘PowerShell’ and select “Run it as an administrator’
5.
• To check the existing execution policy run ‘get-executionpolicy’ command as shown below in the PowerShell console:
• If you do not get the result ‘RemoteSigned’ run the following command to set the execution policy to ‘RemoteSigned’
4. The account under which you have logged in to the remote server, needs to be the member of the following groups on the servers which you want to query:
Wss_wpg, Rdp, Users

Schedule it:
1. Create a batch file and schedule it to run on one time bases as this script runs continuously and automatically goes to start and sleep mode depending on whether it is able to ping teh site.
THE SCRIPT:
do {
function Test-Site {
param($URL)
Start-Sleep -s 15
trap{
"Failed. Details: $($_.Exception)"
# specify the server names in the following array
$strComputers = @("*********","*******","********")

# specify the log names in the following array
$logList = @("application","security","system")

# following lines determine the new file name to be created
$today=get-date -format D
$combined=""
foreach ($server in $strcomputers)
{
$combined=$combined+$server+"_"
}
$filename1="******_Prod_Down_Summary_"+$combined+$today
$filename2="******_Prod_Down_Details_"+$combined+$today

#the following lines will remove the file if it already exists
#Sounds like the Add-Content cmdlet isn't disposing of the file object after it
#is done with it. If it doesn't then the garbage collector will eventually
#catch it and finalize it (dispose/close it) whenever it gets around to
#running which is non-deterministic. The following line will force the garbage collector to run.
Start-Sleep -s 3
[GC]::Collect()
Start-Sleep -s 3
Remove-Item D:\scripts\$filename1.txt -force
Remove-Item D:\scripts\$filename2.txt -force

# the following line gets the current system date and writes it to the file
get-date | Add-Content D:\scripts\$filename1.txt
get-date | Add-Content D:\scripts\$filename2.txt

echo "+++++Servers' Summary+++++"| Add-Content D:\scripts\$filename1.txt
echo "**********************************Disk Space Report***************************************"| Add-Content D:\scripts\$filename1.txt

foreach ($server in $strcomputers)
{
echo $server| Add-Content D:\scripts\$filename1.txt
echo ~~~~~~~| Add-Content D:\scripts\$filename1.txt
try
{
$dsk= Get-WmiObject -computername $server Win32_LogicalDisk
$data=foreach ( $drive in $dsk )
{
if(($drive.Name -ieq "C:") -or ($drive.Name -ieq "D:"))
{
"Drive = " + $drive.Name +" Size(GB) = " + [int]($drive.Size/1073741824) + " Free Space(GB) = " + [int]($drive.FreeSpace/1073741824)
}
else
{
#nothing
}

}
$data | Add-Content D:\scripts\$filename1.txt
}
catch
{
"Failure Getting "+ $server+ " DiskSpace Info"| Add-Content D:\scripts\$filename1.txt
"Details:"| Add-Content D:\scripts\$filename1.txt
$($_.Exception)| Add-Content D:\scripts\$filename1.txt
}
}

echo "********************************Log Summary******************************************"| Add-Content D:\scripts\$filename1.txt
foreach ($logname in $logList)
{
echo $logname" log Summary" | Add-Content D:\scripts\$filename1.txt
echo ~~~~~~~~~~~~~~~~~~~~~~ | Add-Content D:\scripts\$filename1.txt
$newest = 100
if ($logname.compareto("application"))
#if the comparison is true it will go to else block, that is how powershell comparison works
{
$newest = 10
}
else
{
$newest = 100
}

foreach ($server in $strcomputers)
{
echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" | Add-Content D:\scripts\$filename1.txt
try
{
$Lap = Get-EventLog -computername $server -LogName $logname –newest $newest
$Lap|where {$_.entryType -match "Error"}|Sort-Object eventid|group-object eventid|Format-Table Name, Count -auto|fl|out-string|Add-Content D:\scripts\$filename1.txt
}
catch
{
"Details:"| Add-Content D:\scripts\$filename1.txt
$($_.Exception)| Add-Content D:\scripts\$filename1.txt
}
}
}
echo "************************************Log Details********************************"| Add-Content D:\scripts\$filename2.txt
foreach ($logname in $logList)
{
echo $logname | Add-Content D:\scripts\$filename2.txt
echo ======== | Add-Content D:\scripts\$filename2.txt
$newest1 = 100
if ($logname.compareto("application"))
#if the comparison is true it will go to else block, that is how powershell comparison works
{
$newest1 = 10
}
else
{
$newest1 = 100
}
foreach ($server in $strcomputers)
{
echo "$server ~ $newest1 entries were checked" | Add-Content D:\scripts\$filename2.txt
echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" | Add-Content D:\scripts\$filename2.txt
try
{
$LapD = Get-EventLog -computername $server -LogName $logname –newest $newest1
$LapD | where {$_.entryType -match "Error"} | Sort-Object eventid | fl | out-string | Add-Content D:\scripts\$filename2.txt
}
catch
{
"Details:"| Add-Content D:\scripts\$filename2.txt
$($_.Exception)| Add-Content D:\scripts\$filename2.txt
}
}
}
echo "Please check the other attachment for log details" | Add-Content D:\scripts\$filename1.txt
echo "********************END of Summary*******************************" | Add-Content D:\scripts\$filename1.txt
echo "********************END of Details*******************************" | Add-Content D:\scripts\$filename2.txt
$filename1 = "D:\scripts\$filename1.txt"
$filename2 = "D:\scripts\$filename2.txt"
$smtpServer = "*********"
$msg = new-object Net.Mail.MailMessage
$att1 = new-object Net.Mail.Attachment($filename1)
$att2 = new-object Net.Mail.Attachment($filename2)
$smtp = new-object Net.Mail.SmtpClient($smtpServer)
$msg.From = "************"
$msg.To.Add("************")
# You can add multiple recipients
$msg.To.Add("*************")
# $msg.To.Add("**********")
$msg.Subject = "********* Production is Down"
$msg.Body = "Details: $($_.Exception). For more information see the attached report."
$msg.Attachments.Add($att1)
$msg.Attachments.Add($att2)
$smtp.Send($msg)
# if the ping is UNsuccessful the following line will pause the script for n seconds, so that we donot get multiple emails
Start-Sleep -s 3600
}

$webclient = New-Object Net.WebClient
# The next 5 lines are required as our network has a proxy server
$webclient.Credentials = [System.Net.CredentialCache]::DefaultCredentials
if($webclient.Proxy -ne $null) {
$webclient.Proxy.Credentials = `
[System.Net.CredentialCache]::DefaultNetworkCredentials
}
# This is the main call
$webclient.DownloadString($URL) | Out-Null
}

Test-Site "http://************/Pages/default.aspx"
$response = "Y"
}

while ($response -eq "Y")

--End--

Enjoy

Windows Logs + Errors Within last 24 Hours + Powershell + Schedule a Powershell Script + Send an email using Powershell

2010-10-19T13:14:00.000-07:00

Make sure you run the following command:
Set-executionpolicy remotesigned on powershell before dive further into this blog.
Here is the Powershell script. I call it pshell_FINAL.ps1
#=====================Start==============
#remotely checks the diskpace and event log errors for the specified servers and sends the report
#The account which runs this script needs to be the member of the following groups on the specified servers:
#Wss_wpg, Rdp, Users
#The script does not stop running if it encounnters any issue for any server, it writes the exception message in the report

# specify the server names in the following array
$strComputers = @("********","********","*******")

# specify the log names in the following array
$logList = @("application","security","system")

# following lines determines the new file name to be created and the old file name to be deleted
$today=get-date -Format D
$todaysubject=get-date
$combined=""
foreach ($server in $strcomputers)
{
$combined=$combined+$server+"_"
}
$yesterday=get-date (get-date).adddays(-1) -Format D
$oldfilename1="SP_Morning_Report_Summary_"+$combined+$yesterday
$oldfilename2="SP_Morning_Report_Details_"+$combined+$yesterday
Remove-Item D:\scripts\$oldfilename1.txt
Remove-Item D:\scripts\$oldfilename2.txt
$filename1="SP_Morning_Report_Summary_"+$combined+$today
$filename2="SP_Morning_Report_Details_"+$combined+$today

# the following line gets the current system date and writes it to the file
get-date | Add-Content D:\scripts\$filename1.txt
get-date | Add-Content D:\scripts\$filename2.txt

echo "+++++Servers' Summary+++++"| Add-Content D:\scripts\$filename1.txt
echo "**********************************Disk Space Report***************************************"| Add-Content D:\scripts\$filename1.txt

foreach ($server in $strcomputers)
{
echo $server| Add-Content D:\scripts\$filename1.txt
echo ~~~~~~~| Add-Content D:\scripts\$filename1.txt
try
{
$dsk= Get-WmiObject -computername $server Win32_LogicalDisk
$data=foreach ( $drive in $dsk )
{
if(($drive.Name -ieq "C:") -or ($drive.Name -ieq "D:"))
{
"Drive = " + $drive.Name +" Free Space(GB) = " + [int]($drive.FreeSpace/1073741824) +" /Total Size(GB) = " + [int]($drive.Size/1073741824)
}
else
{
#nothing
}
}
$data | Add-Content D:\scripts\$filename1.txt
}
catch
{
"Failure Getting "+ $server+ " DiskSpace Info"| Add-Content D:\scripts\$filename1.txt
"Details:"| Add-Content D:\scripts\$filename1.txt
$($_.Exception)| Add-Content D:\scripts\$filename1.txt
}
}

echo "********************************Log Summary******************************************"| Add-Content D:\scripts\$filename1.txt
foreach ($logname in $logList)
{
echo $logname" log Summary" | Add-Content D:\scripts\$filename1.txt
echo ~~~~~~~~~~~~~~~~~~~~~~ | Add-Content D:\scripts\$filename1.txt
$newest = 100
if ($logname.compareto("application"))
#if the comparison is true it will go to else block, that is how powershell comparison works
{
$newest = 100
}
else
{
$newest = 1000
}
foreach ($server in $strcomputers)
{
echo $server | Add-Content D:\scripts\$filename1.txt
echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" | Add-Content D:\scripts\$filename1.txt
try
{
$Lap = Get-EventLog -computername $server -LogName $logname –newest $newest
$Lap|where {$_.entryType -match "Error"}|Sort-Object eventid|group-object eventid|Format-Table Name, Count -auto|fl|out-string|Add-Content D:\scripts\$filename1.txt
}
catch
{
"Details:"| Add-Content D:\scripts\$filename1.txt
$($_.Exception)| Add-Content D:\scripts\$filename1.txt
}
}
}
echo "************************************Log Details********************************"| Add-Content D:\scripts\$filename2.txt
foreach ($logname in $logList)
{
echo $logname | Add-Content D:\scripts\$filename2.txt
echo ======== | Add-Content D:\scripts\$filename2.txt
$newest1 = 100
if ($logname.compareto("application"))
#if the comparison is true it will go to else block, that is how powershell comparison works
{
$newest1 = 100
}
else
{
$newest1 = 1000
}
foreach ($server in $strcomputers)
{
echo "$server ~ $newest1 entries were checked" | Add-Content D:\scripts\$filename2.txt
echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" | Add-Content D:\scripts\$filename2.txt
try
{
$LapD = Get-EventLog -computername $server -LogName $logname –newest $newest1
$LapD | where {$_.entryType -match "Error"} | Sort-Object eventid | fl | out-string | Add-Content D:\scripts\$filename2.txt
}
catch
{
"Details:"| Add-Content D:\scripts\$filename2.txt
$($_.Exception)| Add-Content D:\scripts\$filename2.txt
}
}
}
echo "Please check another attachment for log details." | Add-Content D:\scripts\$filename1.txt
echo "********************END of Summary*******************************" | Add-Content D:\scripts\$filename1.txt
echo "********************END of Details*******************************" | Add-Content D:\scripts\$filename2.txt
$filenameatt1 = "D:\scripts\$filename1.txt"
$filenameatt2 = "D:\scripts\$filename2.txt"
$smtpServer = "**********"
$msg = new-object Net.Mail.MailMessage
$att1 = new-object Net.Mail.Attachment($filenameatt1)
$att2 = new-object Net.Mail.Attachment($filenameatt2)
$smtp = new-object Net.Mail.SmtpClient($smtpServer)
$msg.From = "************"
$msg.To.Add("************")
# You can add multiple recipients
$msg.To.Add("*************")
# $msg.To.Add("*****************")
$msg.Subject = "Sharepoint Morning Report "+$todaysubject
$msg.Body = "Please see the attached report."
$msg.Attachments.Add($att1)
$msg.Attachments.Add($att2)
$smtp.Send($msg)

=============================END==================
Modifications:
Report on any other server:
1. Search for the comment ‘# specify the server names in the following array’
3. Change the server names
Other modifications:
All the lines in the script have been explained in the comment line above the script. It is easy to modify: servers’ names, log names, number of logs to check, sender and receivers’ email addresses.

Enjoy...

Preupgradecheck FeatureInfo...Failed

2010-10-07T11:42:00.000-07:00

If you run the ‘stsadm –o preupgradecheck’ on SP07 environment you may encounter the following message:

FeatureInfo… Failed

What you should do in this case?

1) Get the list of missing features and related content databases

a) Get the list of missing features from preupgradecheck.htm file.

b) Open preupgradecheck.log from 12/logs. Search for the feature IDs which are missing according to report. Doing so will give the content database name which references to these missing feature.

Example:

[FeatureInfo] [DEBUG] [10/6/2010 10:52:18 AM]: Found 2 webs using missing feature definition e2660694-9026-460b-8515-69ca06ecd4d8 in content database WSS_Content.

So now you have the list of missing features and the names of the content databases referring to these features.

2) Install standard/recommended/third-party features

a) Check the standard features list at following two locations:

http://www.thorprojects.com/blog/archive/2007/05/16/list-of-features-with-guids.aspx and

http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d-183c-4fc2-8320-ba5369008acb&ID=238

If any features belong to that list, install it.

2. 1 Features already exists on the server

To install we need to have the path for the feature.xml file > we already have the ids of the features so we need to search the features folder with the help of Ids and this search will be ‘text within the file’ search > on windows server 2008 we need to use the advanced search so that we can search the text from a file > on windows server 2008 box click on search tools >click on search tab >select the option to search the content of the file > then search for specific id and it should return the feature.xml file> Our Windows 08 boxes did not returned the search result so what I did is copied the features folder to my desk which is running windows Xp and then did search feature.xml file which has the feature ids à now we do have the name of the feature and its location so we need to install this feature using the following command:

stsadm -o installfeature -filename "Featurename\feature.xml

" –force > make sure you provide the relative path or else you will get an error

2.2 Features do not exist on the server

There can be few feature ids for which you do not find the folder or the feature.xml file > If these features belongs to the standard list of MOSS07 features, get them from web> place them in features folder of your moss servers and using the above stated command install it. (Make sure you run IIS reset after running each of the command mentioned.)

3) WSSANALYZER

-we need to find out that which webapp is referencing the missing features for that use this tool: wssanalyzer

-you need to download this tool to the server. Let's say you place it in C: and give the folder name to wssanalyzer. On command prompt first u need to navigate to the C:/wssanalyzer in order to run wssanalyzefeatures command. Run the command foreach webapp, make sure you specify the correct url which displays in webapplist in CA or else you will run into errors. Once you run this it will give you 0 errors report if not it will return a text doc which mentions the feature references which are missing -> once you have 0 references to this feature for all the webapps we ned to deactivate and then uninstall feature with particular Id using following commands:

stsadm -o deactivatefeature -id ******** -url http://webappurl:port/ -force

-run the above command for each webapp

after that, uninstall it from the farm using the following command:

stsadm -o uninstallfeature -id ****** –force

4) Remove unnecessary webapps and their content databases which will also help to reduce no of reference counts toward the missing features

Run the preupgardecheck you should not rcv the feature info/…. Failed

References:

http://code.msdn.microsoft.com/WssAnalyzeFeatures

http://code.msdn.microsoft.com/WssRemoveFeatureFrom

http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d-183c-4fc2-8320-ba5369008acb&ID=371

http://www.gilham.org/Blog/Lists/Posts/Post.aspx?ID=229

http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d-183c-4fc2-8320-ba5369008acb&ID=238

http://www.thorprojects.com/blog/archive/2007/05/16/list-of-features-with-guids.aspx

--END--

Installing a CU to Multi Server MOSS 2007 Farm, (Best Practice Sequence)

2010-09-23T07:53:00.001-07:00

Scenario: You have 2 Webfront end and 1 application server. App server hosts CA.
Remember:
moss patches and CUs need to be applied only on WFEs and APp servers and not on DB servers. However the cu will change the Db to a newer version of a Db.
Procedure:
1. DBA – to take the backup of a DB (335GBs), name it as 'olderversion.Db'
2. DBA – to defragment SP databases
3. Devel – to take the backup of all customized files
4. Take both servers off from NLB make sure they are not accessible
5. Loginto all servers one by one and stop w3svc
6. Make all software update files available on all servers in your server farm.
7. Make sure no update related timer jobs are running on any of the servers
8. Make sure there is enough disk space on all the servers
9. AppServer: Extract wss package with correct password and install it, Do not run Sp products and technology wizard
10. WFE1: Extract wss package with correct password and install it, Do not run Sp products and technology wizard
11. WFE2: Extract wss package with correct password and install it, Do not run Sp products and technology wizard
12. AppServer: Extract MOSS package with correct password and install it, Do not run Sp products and technology wizard
13. WFE1: Extract MOSS package with correct password and install it, Do not run Sp products and technology wizard
14. WFE2: Extract MOSS package with correct password and install it, Do not run Sp products and technology wizard
15. AppServer: Start product and technologies wizard.
If the wizard does not start automatically, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.
• On the SharePoint Products and Technologies Configuration Wizard Welcome page, click Next.
• In the dialog box that notifies you that some services might have to be restarted during configuration, click Yes.
• On the Completing the SharePoint Products and Technologies Configuration Wizard page, click Next.
• When the dialog box about installation in a server farm opens, do not click OK. Instead, leave server with the following dialog box displayed:
• "You must run Setup to install new binary files for every server in your server farm." (Ref: http://technet.microsoft.com/en-us/library/cc263467%28office.12%29.aspx)
16. WFE1: repeat step 15
17. WFE2: repeat step 15
18. AppServer: click Ok on-the message:
"You must run Setup to install new binary files for every server in your server farm."
and let the installation finish
19. WFE1: repeat step 18
20. WFE2: repeat step 18
21. reboot the servers if prompted
22. Search for upgrade.log file and search for success, warnings and error words.
23. Note down the new version Number
24. Copy the upgradefile rename it and save it to some other location
25. Start w3svc services on servers
26. DBA - Take the backup of the DB
27. Devel - restore customizations
28. Make the servers available thru NLB
I hope this helps someone to determine the correct sequence and correct order of installation.
Enjoy.......!!!!

unable to run security reort using MBSA for MOSS Farm

2010-09-20T08:00:00.000-07:00

In MOSSRAP I mentioned about the MBSA (Microsoft Baseline Security Analyzer)which can give us the report regarding our moss farm. This report contains the scorecard and shows high risk, medium risk and low risk items, However recently I was unable to run the report if I check mark any of the following options:
-Check for security updates
-Configure computers for Microsoft Update and scanning prerequisites
-Advanced Update Services options:
-Scan using assigned Windows Server Update Services(WSUS) servers only
-Scan using Microsoft Update only
I used to get the following error message:
Unable to scan all computers
The catalog file is damaged or an invalid catalog.
I found out that the automatic updates for the servers were turned off by the sysadmins. In order to run the security reports through MBSA this automatic updates should be turned on and the boxes must be connected with the internet. It is necessary for MBSA to connect to internet world and get to know the latest updates released by the Microsoft and then compare what it finds on the box and let us know about the missing ones.
It is really very useful tool and I recommend Admins to use it once a month at-least to asses the health of the Moss farm
Enjoy....

Email Distribution Group in SharePoint

2010-09-20T07:37:00.000-07:00

Requirement: need to have a group in sharepoint with the email address group@domain.com. This group will have multiple users and their email addresses are u1@domain.com, u2@domain.com etc. When any one send an email to group@domain.com the users of this group will get an email. Also, the emails should be archived in a list.
Solution:
1. create an OU in AD and delegate full control to SP service account. If you already have the incoming and outgoing mail setup for your moss server you may already have the OU created. make sure you have the OU name ready.
2. Configure Incoming Email settings:
CA>operations>Incoming E-Mail Settings>Enable sites on this server to receive e-mail? yes>Settings mode: Automatic >Use the SharePoint Directory Management Service to create distribution groups and contacts? yes >Active Directory container where new distribution groups and contacts will be created: For example, OU=ContainerName, DC=domain, DC=com >SMTP mail server for incoming mail: domain.com > Accept messages from authenticated users only? NO > Allow creation of distribution groups from SharePoint sites? yes>Distribution group request approval settings : check mark all 4 options> E-mail server display address: "mylist@" domain.com > select 'Accept mail from all e-mail servers ' > OK
3. on SP site create a new group with full control permission
on SP site>SA>SS>PNG>new>new group>Create an e-mail distribution group for this group? yes>Distribution list e-mail address: listname@domain.com>under 'Archive mail sent to this group:' select 'Archive mail to a new list'> List name : "Give a listname as you like"
navigate to the list page and you will see:
Group E-Mail Address: GroupName@domain.com
Group E-Mail Archive: ListName (0 Item(s))
4. on group page>settings>group settings>incoming email settings>accept emails from any sender
5. Approve the distribution group in CA
CA>OP>Approve/reject distribution groups > change the view to Create Requests>you will see your distribution group name and the associated email address>approve that group> this will create an entry in OU in AD. To check that on the computer click on start>administrative tools>active directory users and computers> check and see the email address will be there. If its is not there then you may not have the write permission on AD.
Now, send an email to the group email address and it will forward the same to the group members.
*CA - Central Admin
SA - Site Actions
SS - Site Settings
PnG - People and Groups
OP - operations
SP - SharePoint

Setup the Audit Logs on MOSS'07 Site - Solutions and Workarounds to Issues and Errors

2010-08-25T05:30:00.000-07:00

For any of the following errors:
The specified web does not contain a reporting metadata list. or
The template could not be found for the specified report
Do the following:
1)Go to command prompt and type the following command:
"cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN"
2)and than
"stsadm -o activatefeature -name Reporting -url http://servername:port/sitecollection/ -force"
3)you will receive the following message:
Operation completed Successfully
4)do "IISreset"
5)open sitecollection-->siteactions-->modify all site settings-->site collection features-->deactivate reporting feature
6)you will receive the warning message
7)click on deactivate.
**8)repeat steps 1) to 4) very very imp step if u miss it the error will still persist**
everything will works fine now...
if you click on the report and you receive the following error:
"Report contains no data."
do the following:
site actions-> site settings->site collection administration->site collection audit log setting->
enable all options which are required for you.
One more error:
when you click on the audit log report it will give 'HTTP 403 forbidden error: website can not display this webpage'
solution: add the user to the site collection's administration group.
[to add the user as a site collection administrator:7. Site actions->site settings->Modify all site settings->site collection administrators->add users here. You can add any user windows based, forms based etc, if they are site collection admin, they will be able to access the audit log]
** For all the reports you want to see make sure you do some activity in order to get the report since you have implemented the audit log, otherwise you will strill be getting "report contains no data" error.
------------------------
when you try to open ‘Expiration and disposition’ & ‘Policy modifications’ from 'Information management policy reports' section you will receive the same error:"Report contains no data."
Reason:
because, we did not created any custom policy for any document or report library. Expiration and disposition is also a part of the policy.
solution: Open any document or report library. Settings-->modify list settings-->Information Management Policies-->create anew policy--> give name: 'Policy 1'-->select 'enable auditing'-->select 'expiration'--> select appropriate options for both the above options.
Now, try to open both the above stated reports again, they will open.
** Audit log reports are being opened as XML files in IE instead of XLS or XLSX
When you run any reports of audit logs from site settings-->modify all site settings-->site collection administration , a pop up will open which asks for Open or save options. Depending on the IE settings on the client machine no pop up appears sometimes and the XML file is opened in browser itself rather than asking for saving that file.
*Workaround: When the file opens as XML in browser click on file--> save as and save the file with default name and extension. After saving the file, double click on it and it will open in excel.
Enjoy....!!!!
Enjoy......

Useful Third Party Tools for SharePoint

2010-08-05T10:53:00.000-07:00

1)SharePrep - Sharepoint by default will not allow you to upload any files which has special characters in it [~~!@#$%^{}-] etc., This utility helps to correct the file names (replaces it with _) for successful upload.
SharePrep Utility Home
2)Control point from Axceler
3)Metalogix Migration Manager

Pie Chart for SP list : NO code solution

2010-06-24T07:33:00.000-07:00

scenario: you have the Issue list with on hold, active and waiting status. You want to display it using the pie chart.
solution:
1) go to the list page--> modify this view-->expand group by-->under 'First group by the column:' select 'Issue Status' -->ok-->come back to the list page-->edit page-->add a new webpart-->content editor webpart-->click on source editor-->type the following code:
=========
<div id="jLoadMe" class="content"><strong>Pie Chart Using Google Charting API</strong></div>
<script type="text/javascript">
if(typeof jQuery=="undefined"){
var jQPath="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/";
document.write("<script src='",jQPath,"jquery.js' type='text/javascript'><\/script>");
}
</script>

<script
type="text/javascript">
$("document").ready(function(){
var arrayList=$("td.ms-gb:contains(':')");
var coord= new Array();
var labels= new Array();
$.each(arrayList, function(i,e)
{
var MyIf= $(e).text();
var txt= MyIf.substring(MyIf.indexOf('(')+1,MyIf.length-1); // Extract the 'Y' coordinates
coord[i]=txt;
var txt1= MyIf.substring(MyIf.indexOf(':')+2,MyIf.indexOf("(")-1); // Extract the labels
labels[i]=txt1+"("+txt+")"; //add also coordinates for better read
});
var txt= coord.join(",");
var txt1= labels.join("|");
// Adjust Chart Properties below - See Google Charts API for reference
var vinc= "<IMG src='http://chart.apis.google.com/chart?cht=p3&chs=750x200&chd=t:"+txt+"&chl="+txt1+"'/>";
$("#jLoadMe").append("<p>"+vinc+"</p>")
});

</script>

=========
-->apply ok and you will have the foloowing pie chart ready for you.

you can do the same for any list you want.
References:
1) Google-->for google APIs
2) Claudio Cabaleyro -->http://www.endusersharepoint.com/2009/04/20/finally-dynamic-charting-in-wss-no-code-required/
*** If your manager says that the Google APIs are not secure there is an alternate approach to do the same:
Multiple Secure Pie Charts for SharePoint by Bryon Wyly

Do the same and make your managers happy!!! how easy it is I love MY job.
Enjoy...

**CODE DOES NOT WORK FOR HTTPS

Attach/Add an existing Content Database to a sharepoint Webapplication

2010-06-09T12:53:00.000-07:00

Scenario: you have the content database from the same server or from your production MSSQL server. Now you want to attach this content database and use it. There are few ways to do that:
1) database attach using SP CA
let's assume that the content database you want to attach has the name 'WSS_Content_New'. You already have a webapplication. Open SP CA-->application management-->content databases-->select the right webapplication --> see the attached content database-->select it-->from drop down select 'offline'--> also check mark-->remove content database--> click ok on the pop-up warning message. [Do not be scared with the pop-up message as the database will still remain in the SQL-DB and can be used in future if needed]-->now come back to manage content databases page and you will see that no more databases are associated with this webapplication-->click on the add a new content database--> in content database text box there will be wss_content_somerandomGUID remove that and type wss_content_new-->ok and now the database is attached. and you should be able to navigate to the webapplication and it will show you the site which resides in the attached content database.
** the above process is easy but I encountered the following error:
"The attach operation cannot continue because another object in this farm already contains the same ID. Each object in a farm must have a unique ID. In order to proceed with the attach operation you must assign a new ID to this database. To attach this database with a new ID, use the "stsadm.exe -o addcontentdb" operation with the -assignnewdatabaseid parameter. Note that if this new database and an existing database contain the same site collections, attaching this database will likely result in orphaned site collections due to conflicts between the two databases. "
**As the error mentions you can use the stsadm command which we will discuss later
**The possible cause for this error is - it's already being used by another webapplication. Check for every webapplication and its associated content database to make sure that this content database is not already being used by any other webapplication and try again.
2) using stsadm command:
stsadm -o addcontentdb -url http://server:port/ -databasename WSS_Content_New -assignnewdatabaseid
(If you happen to get the above stated error then only u need to use -assignnewdatabaseid parameter)
3) creating a new webbapp
open SPCA-->create or extend a webapplication-->create a new webapplication--> in content database text box there will be wss_content_somerandomGUID remove that and type wss_content_new-->fill-out other details-->click ok
**After performing all the above stated steps correctly, if you still get 404 webpage not found error, it may be possible that the content database does not have any sites. To check that navigate to the manage content database page-->select the appropriate webapp and see the content database' sites column if it says 0 you cannot see the site when you try to navigate. You can of-course create the new site in the new content database.
how to check?
navigate to the site and you will see the site.
BENEFIT: This is a part of the SharePoint backup and recovery using database attach and detach method. You can use this method to attach a moss 2007 content database to the MOSS 2010 webapplication and have a new look and feel!!!
Love SharePoint.

Zip and/or remove old Sharepoint and IIS Log files

2010-06-09T06:41:00.000-07:00

Scenario: By default SharePoint saves it logs to 12/logs folder. the logs can increase in size without any warning. Having the log files on the system drive can potentially cause the performance issues.
proposed solution: Move the SharePoint log away from the c:/ let's say on D:/. on D:/ the log folder name is SharePointLogs. A script should run everyday at night which compresses the files older than 1 day, remove the original files which we are compressing, remove all the previous zip files which are older than 30 days
working on a solution:
prerequisites:
- we are going to use forfiles and 7zip.
- forefiles are already there in windows server at C:\Windows\System32 (look for forfiles.exe)
- download and install '7-zip' - open source utility which helps you to run the command to zip the file. (http://www.7-zip.org/ and download the appropriate file)
- the installer will install it to following location on windows:C:\Program Files\7-Zip
- I like the idea of 'Roni Schuetz' to add the installation paths of both these utilities into environment path variable for scripting convenience. (so to run 7zip's 7z command you do not need to navigate to C:\Program Files\7-Zip location on the command prompt)
- start--> control panel-->make sure yoy are in classic view-->click on System --> on the LHS click on 'Advanced system settings'-->on the 'system properties' window under Advanced tab click on 'Environment Variables'--> on 'environment variables' window under 'system variables' section select 'Path' and then click on 'edit..'-->on 'edit system variable window' besides 'variable value' you will see that there will already some paths added, go to the end of the line and add ";C:\Windows\System32;C:\Program Files\7-Zip"--> click ok --> ok
-navigate to D:/ and create an empty folder named 'SharePointLogs'
- to move the SharePointLogs to a different drive: open SP CA--> operations--> under 'Logging and reporting' click on 'Diagnostic logging' --> under 'Trace Log' section under 'Path' remove 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS' and add 'D:\SharePointLogs' (you can also control the logs using two options 'Number of log files' and 'Number of minutes to use a log file')AGAIN- operations-->'Usage analysis and processing'-->change the log file location to 'D:\SharePointLogs'-->click ok
- now it's time to write the batch file (see my previous blogs for the info about how to create one and how to schedule one using the Windows Task Scheduler)
===V1=====================================================================
@echo START - %TIME%
forfiles -p "D:\SharePointLogs" -s -m *.* -d -1 -c "Cmd /C 7z a @FILE.zip @FILE"
forfiles -p "D:\SharePointLogs" -s -m *.* -d -1 -c "cmd /c del @file"
forfiles -p "D:\SharePointLogs" -s -m *.zip -d -30 -c "cmd /c del @file"

forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.* -d -1 -c "Cmd /C 7z a @FILE.zip @FILE"
forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.* -d -1 -c "cmd /c del @file"
forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.zip -d -30 -c "cmd /c del @file"

@echo DONE - %TIME%
========================================================================
*remember if you have multi server farm - The new location you specify for logs must exist on all servers in the farm.
*** If you want to copy files from folders and their sub-folders based on their age on windows box use the following command:
robocopy "source path" "Destination path" *.* /minage:2 /s
(Explanation: *.* - any files with any extension,
/minage:2 - files older then 2 days
/s - Also look into the subfolders )
***Error while accessing 'Diagnostic Logging Page'***
I moved the default diagnostic logging location from 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS' to D:/SPLOGS. Then I deleted everything from 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS', then I went to CA>OP>Diagnostic Logging and encountered an error 'something.runtime is missing' (I apologize that right now I am unable to reproduce the exact error message).
Solution:even if you remove the log location never remove the content which is already there in 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS' this will cause the error above.
all set.
======V2 modified script==========
===v2 changes:
1. Added one more command to remove all files older than 180 days from logs' default location. If we compress them, the modified date will be changed to today's date and hence the script does not remove it immediately and will wait for 180 days to remove them.
2. Removed /minage from robocopy, as we decided not to keep any .zip files at logs' default locations irrespective of their age.
===script v2
@echo START - %TIME%
forfiles -p "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" -s -m *.* -d -180 -c "cmd /c del @file"
forfiles -p "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" -s -m *.log -d -1 -c "Cmd /C 7z a @FILE.zip @FILE"
forfiles -p "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" -s -m *.log -d -1 -c "cmd /c del @file"
robocopy "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" "D:\SPLogArchieve\SP" *.zip /s
forfiles -p "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" -s -m *.zip -c "cmd /c del @file"
forfiles -p "D:\SPLogArchieve\SP" -s -m *.zip -d -180 -c "cmd /c del @file"

forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.* -d -180 -c "cmd /c del @file"
forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.log -d -1 -c "Cmd /C 7z a @FILE.zip @FILE"
forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.log -d -1 -c "cmd /c del @file"
robocopy "C:\inetpub\logs\LogFiles" "D:\SPLogArchieve\IIS" *.zip /s
forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.zip -d -1 -c "cmd /c del @file"
forfiles -p "D:\SPLogArchieve\IIS" -s -m *.zip -d -180 -c "cmd /c del @file"
@echo DONE - %TIME%
=========
================================Modified V3====================
Requirement Specifications:
1. Compress log files older than 1 day from SharePoint and IIS’ default log locations
2. Remove the log files older than 1 day from SharePoint and IIS’ default log locations
3. Copy compressed files from SharePoint and IIS’ default log locations to D: /
4. Remove all compressed files from SharePoint and IIS’ default log locations
5. Remove all compressed files from D:/ older than 180 days"
6. Remove all empty folders and subfolders from SharePoint and IIS’ default log locations
===part 1
REM *****************************************************
REM this batch file will remove the files older than 180 days from Sharepoint and IIS' defaul log locations
REM *****************************************************
@echo START - %TIME%
forfiles -p "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" -s -m *.* -d -180 -c "cmd /c del @file"
forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.* -d -180 -c "cmd /c del @file"
@echo DONE - %TIME%
====part 2
REM *****************************************************
REM Version 4-10/18/2010 -Dhruv Shah
REM 1. Spelling correction: SPLogArcheive to SPLogArchive
REM 2. Removed 'forfiles -p "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" -s -m *.* -d -180 -c "cmd /c del @file"'
REM 3. Removed 'forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.* -d -180 -c "cmd /c del @file"'
REM 4. Added ''
REM 'cd\'
REM 'set dir = "***"'
REM 'for /f "usebackq" %%d in (`"dir /ad/b/s | sort /R"`) do rd "%%d"'
REM 5. If you want to play with this command from the command prompt, then undouble the percent signs.
REM 6. SP log location 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS'
REM 7. IIS log location 'C:\inetpub\logs\LogFiles'
REM *****************************************************

@echo START - %TIME%
REM ****Sp Logs *************************************************
forfiles -p "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" -s -m *.log -d -1 -c "Cmd /C 7z a @FILE.zip @FILE"
REM "The above command will compress log files older than 1 day from path -p"

forfiles -p "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" -s -m *.log -d -1 -c "cmd /c del @file"
REM "The above command will remove the log files older than 1 day from path -p"

robocopy "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" "D:\SPLogArchive\SP" *.zip /s
REM "The above command will copy all compressed files from source to destination"

forfiles -p "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS" -s -m *.zip -c "cmd /c del @file"
REM "The above command will remove all compressed files from path -p"

forfiles -p "D:\SPLogArchive\SP" -s -m *.zip -d -180 -c "cmd /c del @file"
REM "The above command will remove all compressed files from path -p older than 180 days"

cd\
REM "The above command will take the command prompt to directory's home, which is necessary inorder to run the following command"

set dir = "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS"
REM "The above command sets the target directory to perform the following command on"

for /f "usebackq" %%d in (`"dir /ad/b/s | sort /R"`) do rd "%%d"
REM "The above command will remove empty folders. It will start from child nodes to parent directory"
REM "Command promt will be on hold for about a minute before executing this command. Please do not close the command prompt window"

REM ****IIS Logs *************************************************
forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.log -d -1 -c "Cmd /C 7z a @FILE.zip @FILE"
forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.log -d -1 -c "cmd /c del @file"
robocopy "C:\inetpub\logs\LogFiles" "D:\SPLogArchive\IIS" *.zip /s
forfiles -p "C:\inetpub\logs\LogFiles" -s -m *.zip -c "cmd /c del @file"
forfiles -p "D:\SPLogArchive\IIS" -s -m *.zip -d -180 -c "cmd /c del @file"
cd\
set dir = "C:\inetpub\logs\LogFiles"
for /f "usebackq" %%d in (`"dir /ad/b/s | sort /R"`) do rd "%%d"
REM Command promt will be on hold for about a minute before executing this command. Please do not close the command prompt window

@echo DONE - %TIME%

References:
1) http://netrsc.blogspot.com/2010/05/zip-zipper-and-7zip-log-files.html
2) http://www.codejacked.com/zip-up-files-from-the-command-line/
Enjoy.....

You receive a "Service Unavailable" error message when you browse your sharepoint website. error code: 505/503

2010-06-03T12:28:00.000-07:00

This is how we resolved the error:
-Go to IIS manager-->click on application pools--> on the 'application pools' main window right click on the webapplication which gives the above stated error-->stop-->start.
-do the iis reset
you are all set.
this error is related to the application pool account of a ShareoPoint website.
You may have to do some extra R&D, depending on what you did last before you encountered this error.
There are enough help available on Google for this.
-> we got the same error after few days to a new server which rendered the same error when we tried to access central admin site. The above method solved the problem.

MetaLogix Migration Issue

2010-06-02T12:48:00.000-07:00

Scenario: On one site collection we had the document library with default content type 'document'. In this content type few more columns are added. some of these columns had the special characters in their names. for example 'new/column', 'case number(s)' etc., On the target site collection we want to migrate this doc lib in such a way so that the columns are mapped to the new content type called 'NewCT'. This content type must be a site content type. All the documents must be mapped to the same columns but here the columns must be the site columns and not the list columns.
solution:
--prepare the source site collection
-create a new site collection with blank site template
-create a custom columns without the special characters **
and create a new content type 'NewCT' docs and include all these columns which you just created. So now you have the site content type with all the site columns
open Metalogix site migration manager
open type source
open the destination
and follow these procedure:
attached in gmail:
Document name: "Final Procedure Metalogix Solution"
[sometime I will upload the procedure here the only thing which is stopping me to do so right now is screen-shots!!]

copy the one column value to another of a sharepoint document library using Object model and C#.Net

2010-06-02T12:27:00.000-07:00

Scenario: We have a document library which needs to have a title field same as their name filed for all the documents. Currently for all the documents the Title field is empty. So we need to copy Name field to Title field.
Workaround : Open the list or library in the IE-->actions-->edit in datasheet--> in the datasheet view, copy the Name column and paste it to the Title column. Problem: it pastes the entire url.
Solution with code:
1. open VS
2. file-> new-> project-->visual c#->console application-> give it a meaningful name
3. right click references-->add reference--> add 'Windows Sharepoint Services'(this will add 'microsoft.sharepoint' reference) and 'system.web' reference
4. the program.cs file should look like this :
using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Administration;

using System.Web;
using System.Web.Mail;

using System.IO;
namespace ConsoleApplication1
{
class Program
{
static void Main(string[] args)
{

SPSite spSite = new SPSite("URL of a parent site collection");
SPWeb web = spSite.AllWebs["Name of a sub site collection"];
SPDocumentLibrary docLib = (SPDocumentLibrary)web.Lists["Name of a document library"];
SPListItemCollection items = docLib.Items;
foreach (SPListItem item in items)
{
item["Name"] = item["Title"];
item.Update();
}
Console.WriteLine("done");
Console.ReadLine();
}
}
}
Run the program and you are all set!!

============update: running the above stated program copies the .pdf also so to remove that we used split string here is the code:
static void Main(string[] args)
{

//copying the column value from Name to Title New for dcouments
SPSite spSite = new SPSite("http://sitename/");
SPWeb web = spSite.AllWebs["Law_Dept"];
SPDocumentLibrary docLib = (SPDocumentLibrary)web.Lists["Active1"];
SPListItemCollection items = docLib.Items;

string s = null;
string[] s1 = null;
foreach (SPListItem item in items)
{
s = item["Name"].ToString();
s1 = s.Split('.');
Console.WriteLine(s1[0]);
item["NEWNAME"] = s1[0];
item["Title_New"] = s1[0];
item.Update();
s = null;
s1 = null;
}

Console.WriteLine("done");
Console.ReadLine();
}
enjoy!!!!

Find the Largest File in your SharePoint Portal using C#.Net and Sharepoint Object Model

2010-06-02T11:49:00.000-07:00

Scenario: The default maximum upload size limit in MOSS is 50MBs. During the MS MOSSRAP we got notified that some one has changed it to 500 MBs. I was asked to find-out if there are any large files in the portal. We have more than 100 thousand files. So the best way to achieve this is using the code.
Solution:
1. open VS
2. file-> new-> project-->visual c#->console application-> give it a meaningful name
3. right click references-->add reference--> add 'Windows Sharepoint Services' reference ->this will add 'microsoft.sharepoint' reference.
4. the program.cs file should look like this :
using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Utilities;
using Microsoft.SharePoint.Administration;

namespace GetFileSize
{
class Program
{
static void Main(string[] args)
{
SPSite spSite = new SPSite("http://Yourwebsitename/");
SPWebCollection webs = spSite.AllWebs;
long b = 0;
string s = null;
foreach (SPWeb web in webs)
{
Console.WriteLine(web.Title);

SPListCollection doclibcol = web.Lists;

foreach (SPList list in doclibcol)
{
if (list.BaseType.ToString() == "DocumentLibrary")
{
SPListItemCollection items = list.Items;

foreach (SPListItem item in items)
{

if (item.File.Length > b)
{
b = item.File.Length;
s = item.File.Url;
}
else
{
b = b;
s = s;
}

}

}
}

}
Console.WriteLine("The largest file url is : " + s);
Console.WriteLine("The Value of b is: " + b);

Console.WriteLine("done");
Console.ReadLine();
}
}
}
Click run and you will get the url and the size of the biggest file in your portal.

Error: The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired.

2010-05-25T09:39:00.000-07:00

I got this error when I tried to open the 'User Profile and Properties' page from SharePoint Central Admin.
Resolution:
- navigate to this page:
http://support.microsoft.com/kb/971620/en-us
-click on the following url to download the fix:
Download the Update for 2007 Microsoft Office Servers (KB971620), 64-Bit Edition package now.
-Install it on the SharePoint server and reboot the server.
** If you have the multi server farm you need to install this patch on all the WFEs and an App server and reboot all of them in-order to complete the installation.
(Scenario:We had multi server farm and CA was runing on one WFE, so I installed this patch on that WFEs only. Doing so corrected the error of acceesing SSP pages like 'Profile pages' and 'Mysite pages' but I noticed one more error when I tried to 'search' : 'Your licence for Office Server Search has expired. at Microsoft.Office.Server.Search.Query.FullTextSqlQuery.Execute() ' so, I installed this patch on the other WFE on the farm and rebooted it. Issue solved.. happy Friday... yeaa....)
Problem Solved.

Solutions which did not workout for me:
1) Joel Olson's blog:
http://blogs.msdn.com/b/joelo/archive/2008/01/02/evaluation-version-expired-but-not-really.aspx
- Permissions for the groups WSS_WPG, WSS_ADMIN_WPG to the Registry were correct in our case
- I could not figure out how to 'add -application pool Account- ("dcomcnfg.exe") to the Distributed users group.
2)other workaround:
open the web.config of ssp --> make a small change-->undo your change-->save-->iis reset: this also did not workout

**Note: I installed this package only on the server running the CA and it fixed the issue even if we had 5 servers in the farm. (I guess we just have to install it on the server running CA)