List of Task result codes and what they mean.
Why not just put the info in the task scheduler MS?
SCHED_S_TASK_READY
0x00041300
The task is ready to run at its next scheduled time.
SCHED_S_TASK_RUNNING
0x00041301
The task is currently running.
SCHED_S_TASK_DISABLED
0x00041302
The task will not run at the scheduled times because it has been disabled.
SCHED_S_TASK_HAS_NOT_RUN
0x00041303
The task has not yet run.
SCHED_S_TASK_NO_MORE_RUNS
0x00041304
There are no more runs scheduled for this task.
SCHED_S_TASK_NOT_SCHEDULED
0x00041305
One or more of the properties that are needed to run this task on a schedule have not been set.
SCHED_S_TASK_TERMINATED
0x00041306
The last run of the task was terminated by the user.
Complete List here :
Task Scheduler Error and Success Constants
http://msdn.microsoft.com/en-us/library/aa383604%28VS.85%29.aspx
Showing posts with label windows server 2008 R2. Show all posts
Showing posts with label windows server 2008 R2. Show all posts
Tuesday, 20 March 2012
Monday, 19 March 2012
SharePoint Website Warm up options
There are many warm up scripts and exe's that can run against your SharePoint environments to speed up the first time access to any site. These options have worked the best for our infrastructure. personally the first works well and has useful options.
Setup a scheduled windows task which launches your selection, running under an account that has relevant access, every morning before start of business. The web application is hit and every page iterated in the site.
SPWakeup : http://spwakeup.codeplex.com/
A simple application that touches each site and site collection on a Sharepoint or WSS server to rebuild the IIS cache.
This is compatible with Win 2008 R2 and SharePoint 2010, nice touch is the email letting you know it's been run.
Powershell Script : http://www.jonthenerd.com/2011/04/19/easy-sharepoint-2010-warmup-script-using-powershell/
The script loads the SharePoint plugin, enumerates the zones, and sends a request to each one.
MS Application Warm-up : http://forums.iis.net/t/1176740.aspx
The MS IIS team had a nice warm up optiont that i've used before, but this has been removed at present (19/03/2012)
Keep an eye on any new developments as it was a good option.
SP George had a good how to : http://sharepointgeorge.com/2010/warm-sharepoint-web-applications-windows-2008-r2-iis-75-application-warmup-module/
For reasons on why we get IIS resets and reasons to use Warm up scripts check out this link : http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/8547eaed-5420-4cca-af29-206d71898322/
Setup a scheduled windows task which launches your selection, running under an account that has relevant access, every morning before start of business. The web application is hit and every page iterated in the site.
SPWakeup : http://spwakeup.codeplex.com/
A simple application that touches each site and site collection on a Sharepoint or WSS server to rebuild the IIS cache.
This is compatible with Win 2008 R2 and SharePoint 2010, nice touch is the email letting you know it's been run.
Powershell Script : http://www.jonthenerd.com/2011/04/19/easy-sharepoint-2010-warmup-script-using-powershell/
The script loads the SharePoint plugin, enumerates the zones, and sends a request to each one.
MS Application Warm-up : http://forums.iis.net/t/1176740.aspx
The MS IIS team had a nice warm up optiont that i've used before, but this has been removed at present (19/03/2012)
Keep an eye on any new developments as it was a good option.
SP George had a good how to : http://sharepointgeorge.com/2010/warm-sharepoint-web-applications-windows-2008-r2-iis-75-application-warmup-module/
For reasons on why we get IIS resets and reasons to use Warm up scripts check out this link : http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/8547eaed-5420-4cca-af29-206d71898322/
Wednesday, 14 March 2012
Developer Dashboard
The Developer Dashboard helps diagnose issues with custom code, load times and heaps more.
There are a few ways to enable/disable/ondemand it.
Note : you may need an IIS reset to see the developer dash appear / disappear
1. Powershell
PS commands in blue
onDemand Mode (makes the icon available to expand the info window on each relevant page)
$service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$addsetting =$service.DeveloperDashboardSettings
$addsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand
$addsetting.Update()
Enable for all
$service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$addsetting =$service.DeveloperDashboardSettings
$addsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::On
$addsetting.Update()
Remember to Turn Off
$service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$addsetting =$service.DeveloperDashboardSettings
$addsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::Off
$addsetting.Update()
2. STSADM
Run stsadm from command prompt in the hive\bin dir unless you have it as a path in windows.
hive = C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\
onDemand Mode
stsadm –o setproperty –pn developer-dashboard –pv “OnDemand”
Enable for all
stsadm –o setproperty –pn developer-dashboard –pv “On”
Remember to Turn Off
stsadm –o setproperty –pn developer-dashboard –pv “Off”
There are a few ways to enable/disable/ondemand it.
Note : you may need an IIS reset to see the developer dash appear / disappear
1. Powershell
PS commands in blue
onDemand Mode (makes the icon available to expand the info window on each relevant page)
$service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$addsetting =$service.DeveloperDashboardSettings
$addsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand
$addsetting.Update()
Enable for all
$service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$addsetting =$service.DeveloperDashboardSettings
$addsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::On
$addsetting.Update()
Remember to Turn Off
$service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$addsetting =$service.DeveloperDashboardSettings
$addsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::Off
$addsetting.Update()
2. STSADM
Run stsadm from command prompt in the hive\bin dir unless you have it as a path in windows.
hive = C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\
onDemand Mode
stsadm –o setproperty –pn developer-dashboard –pv “OnDemand”
Enable for all
stsadm –o setproperty –pn developer-dashboard –pv “On”
Remember to Turn Off
stsadm –o setproperty –pn developer-dashboard –pv “Off”
Sunday, 11 March 2012
Windows TIFF iFilter
Built-in Windows TIFF iFilter, simple to install and comes with Windows Server 2008 R2.
permits you to index Tiff Files in SharePoint 2010
Install instructions :
Open Server manager > Features > Add Features > Windows TIFF iFilter > Next > Install.
Next, check the Group policy to ensure OCR filter is enabled.
Open mmc > add group policy object snapin > Local computer policy > administrative templates > OCR > Force TIFF iFilter to perform OCR for every page in a document > edit > Enable.
Install on your SharePoint Servers doing the indexing the Farm.
In the case of a multi tier farm, if you have no compatibility concerns or security issues, install on all servers in the Farm in case you move the indexing role around.
Lastly, upload a .TIFF with some text, run an indexing job and check the search results.
Thanks to Mr Liu : http://johnliu.net/blog/2010/8/13/sharepoint-enable-ifilter-for-tiff-ocr.html
permits you to index Tiff Files in SharePoint 2010
Install instructions :
Open Server manager > Features > Add Features > Windows TIFF iFilter > Next > Install.
Next, check the Group policy to ensure OCR filter is enabled.
Open mmc > add group policy object snapin > Local computer policy > administrative templates > OCR > Force TIFF iFilter to perform OCR for every page in a document > edit > Enable.
Install on your SharePoint Servers doing the indexing the Farm.
In the case of a multi tier farm, if you have no compatibility concerns or security issues, install on all servers in the Farm in case you move the indexing role around.
Lastly, upload a .TIFF with some text, run an indexing job and check the search results.
Thanks to Mr Liu : http://johnliu.net/blog/2010/8/13/sharepoint-enable-ifilter-for-tiff-ocr.html
Subscribe to:
Posts (Atom)