There were two things I changed after which the issue disappeared.
a) Found that an app pool was shared by two web app. Created a new App pool and assigned individual app pool to both web apps. Although one of the web app was not being used.
b) Changed the diagnostic logging for "All" events to Error only to remove excessive log writing.
After above 2 changes the following happened:
a) Error from indexing on Large list (50,000) items disappeared. Were getting same error earlier i.e. Error in data web service...
b) The crawl time reduced from 18 hours to 2 hours.
Long term solution: Migrate to 64 bit environment.
Search This Blog
Thursday, February 25, 2010
Find the # of items in SharePoint lists
SELECT TOP (10) tp_DirName, COUNT(tp_DirName) AS FolderItemsCount FROM AllUserData
GROUP BY tp_DirName
ORDER BY FolderItemsCount DESC
GROUP BY tp_DirName
ORDER BY FolderItemsCount DESC
Friday, February 19, 2010
Get Id from Service Application thru PowerShell
From PowerShell prompt:
Get-SPServiceApplication | select id, name
Pipe i.e. "|" symbol is the same as earlier i.e. send the output of a command as input for one after |
Get-SPServiceApplication | select id, name
Pipe i.e. "|" symbol is the same as earlier i.e. send the output of a command as input for one after |
Thursday, February 18, 2010
Http Request Throttling in SharePoint 2010
HTTP Request throttling basically rejects low priority requests when the server is overloaded - i.e. CPU usage going say 100%. Hence at this time low priority tasks like Search Crawl would be not run.
Having this value off means all low priroty requests will also be processed.
Having this value off means all low priroty requests will also be processed.
Deverloper Dashboard in SharePoint 2010
Issue the following command:
STSADM –o setproperty –pn developer-dashboard –pv on
use -pv off
to set it off.
STSADM –o setproperty –pn developer-dashboard –pv on
use -pv off
to set it off.
Saturday, February 13, 2010
Multilingual Server Pack for MOSS 2007 Link - for Windows 2008 R2 x64
For instructions - use this link:
Deploying Multilingual Interface http://technet.microsoft.com/en-us/library/cc262108.aspxfor SharePoint 2007
Here is the link for operating system language files:
Windows 2008 R2 OS Language Files (All languages - 2+ Gb download)
This is DVD image - hence either burn it on disc or use the any Virtual Image mount software.
If you do not want all the languages and want to download individual files for OS then use the following link,
(select the language from the drop down first..)
Windows 2008 R2 OS language files - Individual Language download
Now go to the regional - language settings of the OS (from control panel) and select the option to install this language. It will look for the path of the file downloaded. Specifiy that where above files were downloaded.
Next comes MOSS 2007 Language packs:
1. WSS 3.0 Language Pack
2. WSS 3.0 Language Pack SP2
3. MOSS 2007 Language Pack
4. MOSS 2007 SP2 Language Pack
Yes that is correct - you need WSS language files also for MOSS 2007.
The above should be installed in the same order and after each of the 4 steps - run the SharePoint configuration wizard. Do not disconnect from the farm if that options shows up.
I hope this becomes easier in future but for now this is what it is for MOSS 2007.
Deploying Multilingual Interface http://technet.microsoft.com/en-us/library/cc262108.aspxfor SharePoint 2007
Here is the link for operating system language files:
Windows 2008 R2 OS Language Files (All languages - 2+ Gb download)
This is DVD image - hence either burn it on disc or use the any Virtual Image mount software.
If you do not want all the languages and want to download individual files for OS then use the following link,
(select the language from the drop down first..)
Windows 2008 R2 OS language files - Individual Language download
Now go to the regional - language settings of the OS (from control panel) and select the option to install this language. It will look for the path of the file downloaded. Specifiy that where above files were downloaded.
Next comes MOSS 2007 Language packs:
1. WSS 3.0 Language Pack
2. WSS 3.0 Language Pack SP2
3. MOSS 2007 Language Pack
4. MOSS 2007 SP2 Language Pack
Yes that is correct - you need WSS language files also for MOSS 2007.
The above should be installed in the same order and after each of the 4 steps - run the SharePoint configuration wizard. Do not disconnect from the farm if that options shows up.
I hope this becomes easier in future but for now this is what it is for MOSS 2007.
Friday, February 12, 2010
New Names in SharePoint 2010
SharePoint 2007 SharePoint 2010
- BDC BCS (allows editing of data now)
- SSP Service Applications. Example: Performance Point SA,Excel SA
- SSO STS (Secured Token Service)
- WSS SPF (SharePoint Foundation Server)
- MOSS SPS (SharePoint Server)
Cancel or other links not working from IE in central admin
Go to server manager in Windows 2008 and disable the enhanced security for Administrator (assuming you are logged in as Administrator)
and try central again... it works...
and try central again... it works...
Thursday, February 11, 2010
Cloning a VM - useful for installing SharePoint with VM for different roles...
Install all the latest service packs
Disconnect from AD if connected.
Use sysprep and shutdown. Sysprep.exe is available in Windows sub folder.
Now you can make copies... Just need the Activation key when you start up... easy...
Disconnect from AD if connected.
Use sysprep and shutdown. Sysprep.exe is available in Windows sub folder.
Now you can make copies... Just need the Activation key when you start up... easy...
MOSS 2007 on Windows 2008 R2 x64
Windows 2008 R2 X64 needs atleast MOSS 2007 with SP2 otherwise you will get "compatibility error" on running setup.exe.
If you have MOSS 2007 or MOSS 2007 SP1: extract the files if they are not already extracted in folder structures. say MOSS2007
Similary extract the MOSS 2007 SP2 in a different folder say MOSS2007SP2
Look for a subfolder Updates in MOSS 2007. Delete any existing files in update folder. Copy all the files from MOSS2007SP2 into the update folder.
Run setup.exe and it works....
If you have MOSS 2007 or MOSS 2007 SP1: extract the files if they are not already extracted in folder structures. say MOSS2007
Similary extract the MOSS 2007 SP2 in a different folder say MOSS2007SP2
Look for a subfolder Updates in MOSS 2007. Delete any existing files in update folder. Copy all the files from MOSS2007SP2 into the update folder.
Run setup.exe and it works....
SharePoint 2010 Event Reciever Debugging
Attach to the SP Timer V4 and not W3P.exe since now event recievers run under SharePoint Timer.
Subscribe to:
Posts (Atom)