'AjaxControlToolKit' Undefined.

I was trying to use the DateExtender control from AjaxControlToolKit. I did everything right but there was a javascript error saying that AjaxControlToolKit is undefined. I did a googling and found that it is because of my system date which was pointing to Feb 2, 2002. I changed this to current date Aug 07, 2008 and also the selectedDate property of the DateExtender.
Then this error was not coming and it is working perfectly.

Custom error handling for Microsoft Ajax 1.0 with Javascript

Cause
I was facing problem while handling the exception thrown by ajax 1.0 . I put sometime and find the following way out.
Solution
Understood that i need to add an custom event to the endRequest, this should be done in the body onload.
Sys.WebForms.PageRequestManager.getInstance().add_endRequest(EndRequestHandler);
Then after that we need to check whether the event arguments has an error or not. As follows
function EndRequestHandler(sender, args)
{
if (args.get_error() != undefined && args.get_error().httpStatusCode == '500')
{
//Handle the exception here.
var errorMessage = args.get_error().message
args.set_errorHandled(true);
}
}
This is a simple and very handy way to handle the exception for Ajax 1.0.

STSADM Operations

Cause

I was trying to restore MOSS 2007, in which i was facing lot of problems. These set of STSADM command comes handy to sort out my issues in an hour. So i consolidated the information down below. You can also get the STSADM operations in MOSS 2007 with out SP1 from the following link (Click me). The source of the below is as follows. Source

Complete reference of all STSADM operations (with parameters) in MOSS 2007 SP1

This is an update to my complete reference of all STSADM operations in Microsoft Office SharePoint Server 2007, now including the changes in Service Pack 1. I repeated what I did for MOSS 2007 in MOSS 2007 SP1, using a little scripting to get the list of all commands for STSADM, including the options and parameters for each. Items new in SP1 are underlined. Please note that some defaults might be related to the way my server is configured.

1. stsadm -o activatefeature {-filename <relative path to Feature.xml> -name <feature folder> -id <feature Id>} [-url <url>] [-force]


2. stsadm -o activateformtemplate -url <URL to the site collection> [-formid <form template ID>] [-filename <path to form template file>]


3. stsadm -o addalternatedomain -url <protocol://existing.WebApplication.URLdomain> -incomingurl <protocol://incoming.url.domain> -urlzone <default, extranet, internet, intranet, custom> -resourcename <non-web application resource name>


4. stsadm -o addcontentdb -url <url> -databasename <database name> [-databaseserver <database server name>] [-databaseuser <database username>] [-databasepassword <database password>] [-sitewarning <site warning count>] [-sitemax <site max count>]


5. stsadm -o adddataconnectionfile -filename <path to file to add> [-webaccessible <bool>] [-overwrite <bool>] [-category <bool>]


6. stsadm -o add-ecsfiletrustedlocation -Ssp <SSP name> -Location <URLUNC> -LocationType SharePointUncHttp -IncludeChildren TrueFalse [-SessionTimeout <time in seconds>] [-ShortSessionTimeout <time in seconds>] [-MaxRequestDuration <time in seconds>] [-MaxWorkbookSize <file size in Mbytes>] [-MaxChartSize <size in Mbytes>] [-VolatileFunctionCacheLifetime <time in seconds>] [-DefaultWorkbookCalcMode FileManualAutoAutoDataTables] [-AllowExternalData NoneDclDclAndEmbedded] [-WarnOnDataRefresh TrueFalse] [-StopOpenOnRefreshFailure TrueFalse] [-PeriodicCacheLifetime <time in seconds>] [-ManualCacheLifetime <time in seconds>] [-MaxConcurrentRequestsPerSession <number of requests>] [-AllowUdfs TrueFalse] [-Description <descriptive text>]


7. stsadm -o add-ecssafedataprovider -Ssp <SSP name> -ID <data provider id> -Type OledbOdbcOdbcDsn [-Description <descriptive text>]


8. stsadm -o add-ecstrusteddataconnectionlibrary -Ssp <SSP name> -Location <URL> [-Description <descriptive text>]


9. stsadm -o add-ecsuserdefinedfunction -Ssp <SSP name> -Assembly <strong namefile path> -AssemblyLocation GACFile [-Enable TrueFalse] [-Description <descriptive text>]


10. stsadm -o addexemptuseragent -name <user-agent to receive InfoPath files instead of a Web page>


11. stsadm -o addpath -url <url> -type <explicitinclusion/wildcardinclusion>


12. stsadm -o addpermissionpolicy -url <url> -userlogin <login name> -permissionlevel <permission policy level> [-zone <URL zone>] [-username <display name>]


13. stsadm -o addsolution -filename <Solution filename> [-lcid <language>]


14. stsadm -o addtemplate -filename <template filename> -title <template title> [-description <template description>]


15. stsadm -o adduser -url <url> -userlogin <DOMAIN\user> -useremail <email address> -role <role name> / -group <group name> -username <display name> [-siteadmin]


16. stsadm -o addwppack -filename <Web Part Package filename> [-lcid <language>] [-url <url>] [-globalinstall] [-force] [-nodeploy]


17. stsadm -o addwppack -name <name of Web Part Package> [-lcid <language>] [-url <url>] [-globalinstall] [-force]


18. stsadm -o addzoneurl -url <protocol://existing.WebApplication.URLdomain> -urlzone <default, extranet, internet, intranet, custom> -zonemappedurl <protocol://outgoing.url.domain> -resourcename <non-web application resource name>


19. stsadm -o allowuserformwebserviceproxy -url <Url of the web application> -enable <true to enable, false to disable>


20. stsadm -o allowwebserviceproxy -url <Url of the web application> -enable <true to enable, false to disable>


21. stsadm -o associatewebapp -title <SSP name> [-default -parent] -url <Web application 1 url,Web application 2 url> [-all]


22. stsadm -o authentication -url <url> -type <windows/forms/websso> [-usebasic (valid only in windows authentication mode)] [-usewindowsintegrated (valid only in windows authentication mode)] [-exclusivelyusentlm (valid only in windows authentication mode)] [-membershipprovider <membership provider name>] [-rolemanager <role manager name>] [-enableclientintegration] [-allowanonymous]


23. stsadm -o backup -url <url> -filename <filename> [-overwrite]


24. stsadm -o backup -directory <UNC path> -backupmethod <full differential> [-item <created path from tree>] [-percentage <integer between 1 and 100>] [-backupthreads <integer between 1 and 10>] [-showtree] [-quiet]


25. stsadm -o backuphistory -directory <UNC path> [-backup] [-restore]


26. stsadm -o binddrservice -servicename <data retrieval service name> -setting <data retrieval services setting>


27. stsadm -o blockedfilelist -extension <extension> -add [-url <url>]


28. stsadm -o blockedfilelist -extension <extension> -delete [-url <url>]


29. stsadm -o canceldeployment -id <id>


30. stsadm -o changepermissionpolicy -url <url> -userlogin <DOMAIN\name> [-zone <URL zone>] [-username <display name>] [{ -add -delete } -permissionlevel <permission policy level>]


31. stsadm -o copyappbincontent


32. stsadm -o createadminvs [-admapidname <app pool name>] [-admapidtype <configurableid/NetworkService>] [-admapidlogin <DOMAIN\name>] [-admapidpwd <app pool password>]


33. stsadm -o createcmsmigrationprofile -profilename <profile name> [-description <description>] [-connectionstring <connection string>] -databaseserver <server> -databasename <name> -databaseuser <username> [-databasepassword <password>] [-auth windowsauthsqlauth] -destination <url> [-rootchannel <channelname>] [-destinationlocale <LCID>] [-migrateresources onlyusedall] [-migrateacls yesno] [-emailto <address1;address2>] [-emailon successfailurenoneboth] [-keeptemporaryfiles NeverAlwaysFailure] [-enableeventreceivers yesno]


34. stsadm -o creategroup -url <url> -name <group name> -description <description> -ownerlogin <DOMAIN\name or group name> [-type membervisitorowner]


35. stsadm -o createsite -url <url> -owneremail <email address> [-ownerlogin <DOMAIN\name>] [-ownername <display name>] [-secondaryemail <email address>] [-secondarylogin <DOMAIN\name>] [-secondaryname <display name>] [-lcid <language>] [-sitetemplate <site template>] [-title <site title>] [-description <site description>] [-hostheaderwebapplicationurl <web application url>] [-quota <quota template>]


36. stsadm -o createsiteinnewdb -url <url> -owneremail <email address> [-ownerlogin <DOMAIN\name>] [-ownername <display name>] [-secondaryemail <email address>] [-secondarylogin <DOMAIN\name>] [-secondaryname <display name>] [-lcid <language>] [-sitetemplate <site template>] [-title <site title>] [-description <site description>] [-hostheaderwebapplicationurl <web application url>] [-quota <quota template>] [-databaseuser <database username>] [-databasepassword <database password>] [-databaseserver <database server name>] [-databasename <database name>]


37. stsadm -o createssp -title <SSP name> -url <Web application url> -mysiteurl <MySite Web application url> -ssplogin <username> -indexserver <index server> -indexlocation <index file path> [-ssppassword <password>] [-sspdatabaseserver <SSP database server>] [-sspdatabasename <SSP database name>] [-sspsqlauthlogin <SQL username>] [-sspsqlauthpassword <SQL password>] [-searchdatabaseserver <search database server>] [-searchdatabasename <search database name>] [-searchsqlauthlogin <SQL username>] [-searchsqlauthpassword <SQL password>] [-ssl <yesno>]


38. stsadm -o createweb -url <url> [-lcid <language>] [-sitetemplate <site template>] [-title <site title>] [-description <site description>] [-convert] [-unique]


39. stsadm -o databaserepair -url <url> -databasename <database name> [-deletecorruption]


40. stsadm -o deactivatefeature {-filename <relative path to Feature.xml> -name <feature folder> -id <feature Id>} [-url <url>] [-force]


41. stsadm -o deactivateformtemplate -url <URL to the site collection> [-formid <form template ID>] [-filename <path to form template file>]


42. stsadm -o deleteadminvs


43. stsadm -o deletealternatedomain -url <ignored> -incomingurl <protocol://incoming.url.domain>


44. stsadm -o deletecmsmigrationprofile -profilename <profile name>


45. stsadm -o deleteconfigdb


46. stsadm -o deletecontentdb -url <url> -databasename <database name> [-databaseserver <database server name>]


47. stsadm -o deletegroup -url <url> -name <group name>


48. stsadm -o deletepath -url <url>


49. stsadm -o deletepermissionpolicy -url <url> -userlogin <login name> [-zone <URL zone>]


50. stsadm -o deletesite -url <url> -deleteadaccounts <true/false>


51. stsadm -o deletesolution -name <Solution name> [-override] [-lcid <language>]


52. stsadm -o deletessp -title <SSP name> [-deletedatabases]


53. stsadm -o deletessptimerjob -title <SSP Name> -jobid <SSP Timer Job Id>


54. stsadm -o deletetemplate -title <template title> [-lcid <language>]


55. stsadm -o deleteuser -url <url> -userlogin <DOMAIN\name> [-group <group>]


56. stsadm -o deleteweb -url <url>


57. stsadm -o deletewppack -name <name of Web Part Package> [-lcid <language>] [-url <url>]


58. stsadm -o deletezoneurl -url <protocol://existing.WebApplication.URLdomain> -urlzone <default, extranet, internet, intranet, custom> -resourcename <non-web application resource name>


59. stsadm -o deploysolution -name <Solution name> [-url <virtual server url>] [-allcontenturls] [-time <time to deploy at>] [-immediate] [-local] [-allowgacdeployment] [-allowcaspolicies] [-lcid <language>] [-force]


60. stsadm -o deploywppack -name <Web Part Package name> [-url <virtual server url>] [-time <time to deploy at>] [-immediate] [-local] [-lcid <language>] [-globalinstall] [-force]


61. stsadm -o disablessc -url <url>


62. stsadm -o displaysolution -name <Solution name>


63. stsadm -o editcmsmigrationprofile -profilename <profile name> [-description <description>] [-connectionstring <connection string>] [-databaseserver <server>] [-databasename <name>] [-databaseuser <username>] [-databasepassword <password>] [-auth sqlauthwindowsauth] [-emailto <address1;address2>] [-emailon successfailurenoneboth] [-excludeschema ] [-keeptemporaryfiles NeverAlwaysFailure] [-enableeventreceivers yesno]


64. stsadm -o editcontentdeploymentpath -pathname <path name> [-keeptemporaryfiles NeverAlwaysFailure] [-enableeventreceivers yesno] [-enablecompression yesno]


65. stsadm -o editssp -title <SSP name> [-newtitle <new SSP name>] [-sspadminsite <administration site url>] [-ssplogin <username>] [-ssppassword <password>] [-indexserver <index server>] [-indexlocation <index file path>] [-setaccounts <process accounts (domain\username)>] [-ssl <yesno>]


66. stsadm -o email -outsmtpserver <SMTP server> -fromaddress <email address> -replytoaddress <email address> -codepage <codepage> [-url <url>]


67. stsadm -o enablecmsurlredirect -profilename <profile name> -off


68. stsadm -o enablessc -url <url> [-requiresecondarycontact]


69. stsadm -o enumalternatedomains -url <protocol://existing.WebApplication.URLdomain> -resourcename <non-web application resource name>


70. stsadm -o enumcontentdbs -url <url>


71. stsadm -o enumdataconnectionfiledependants -filename <filename for which to enumerate dependants>


72. stsadm -o enumdataconnectionfiles [-mode <a u all unreferenced>]


73. stsadm -o enumdeployments


74. stsadm -o enumexemptuseragents


75. stsadm -o enumformtemplates


76. stsadm -o enumgroups -url <url>


77. stsadm -o enumroles -url <url>


78. stsadm -o enumservices


79. stsadm -o enumsites -url <virtual server url> -showlocks -redirectedsites


80. stsadm -o enumsolutions


81. stsadm -o enumssp -title <SSP name> [-default -parent -all]


82. stsadm -o enumssptimerjobs -title <SSP Name>


83. stsadm -o enumsubwebs -url <url>


84. stsadm -o enumtemplates [-lcid <language>]


85. stsadm -o enumusers -url <url>


86. stsadm -o enumwppacks [-name <name of Web Part Package>] [-url <virtual server url>] [-farm]


87. stsadm -o enumzoneurls -url <protocol://existing.WebApplication.URLdomain> -resourcename <non-web application resource name>


88. stsadm -o execadmsvcjobs


89. stsadm -o export -url <URL to be exported> -filename <export file name> [-overwrite] [-includeusersecurity] [-haltonwarning] [-haltonfatalerror] [-nologfile] [-versions <1-4> 1= Last major version for files and list items (default), 2= The current version, either the last major or the last minor, 3= Last major and last minor version for files and list items, 4= All versions for files and list items] [-cabsize <integer from 1-1024 megabytes> (default: 25)] [-nofilecompression] [-quiet]


90. stsadm -o extendvs -url <url> -ownerlogin <domain\name> -owneremail <email address> [-exclusivelyusentlm] [-ownername <display name>] [-databaseuser <database user>] [-databaseserver <database server>] [-databasename <database name>] [-databasepassword <database user password>] [-lcid <language>] [-sitetemplate <site template>] [-donotcreatesite] [-description <iis web site name>] [-sethostheader] [-apidname <app pool name>] [-apidtype <configurableid/NetworkService>] [-apidlogin <DOMAIN\name>] [-apidpwd <app pool password>] [-allowanonymous]


91. stsadm -o extendvsinwebfarm -url <url> -vsname <web application name> [-exclusivelyusentlm] [-apidname <app pool name>] [-apidtype <configurableid/NetworkService>] [-apidlogin <DOMAIN\name>] [-apidpwd <app pool password>] [-allowanonymous]


92. stsadm -o forcedeleteweb -url <url>


93. stsadm -o formtemplatequiescestatus [-formid <form template ID>] [-filename <path to form template file>]


94. stsadm -o getadminport


95. stsadm -o getdataconnectionfileproperty -filename <filename of the data connection file> -pn <property name>


96. stsadm -o getformsserviceproperty -pn <option name>


97. stsadm -o getformtemplateproperty [-formid <form template ID>] [-filename <path to form template file>] -pn <property name>


98. stsadm -o getproperty -propertyname <property name> [-url <url>] (SharePoint cluster properties: avallowdownload, avcleaningenabled, avdownloadscanenabled, avnumberofthreads, avtimeout, avuploadscanenabled, command-line-upgrade-running, database-command-timeout, database-connection-timeout, data-retrieval-services-enabled, data-retrieval-services-oledb-providers, data-retrieval-services-response-size, data-retrieval-services-timeout, data-retrieval-services-update, data-source-controls-enabled, dead-site-auto-delete, dead-site-notify-after, dead-site-num-notifications, defaultcontentdb-password, defaultcontentdb-server, defaultcontentdb-user, delete-web-send-email, irmaddinsenabled, irmrmscertserver, irmrmsenabled, irmrmsusead, job-ceip-datacollection, job-config-refresh, job-database-statistics, job-dead-site-delete, job-usage-analysis, job-watson-trigger, large-file-chunk-size, token-timeout, workflow-cpu-throttle, workflow-eventdelivery-batchsize, workflow-eventdelivery-throttle, workflow-eventdelivery-timeout, workflow-timerjob-cpu-throttle, workitem-eventdelivery-batchsize, workitem-eventdelivery-throttle; SharePoint virtual server properties: alerts-enabled, alerts-limited, alerts-maximum, change-log-expiration-enabled, change-log-retention-period, data-retrieval-services-enabled, data-retrieval-services-inherit, data-retrieval-services-oledb-providers, data-retrieval-services-response-size, data-retrieval-services-timeout, data-retrieval-services-update, data-source-controls-enabled, days-to-show-new-icon, dead-site-auto-delete, dead-site-notify-after, dead-site-num-notifications, defaultquotatemplate, defaulttimezone, delete-web-send-email, job-change-log-expiration, job-dead-site-delete, job-diskquota-warning, job-immediate-alerts, job-recycle-bin-cleanup, job-usage-analysis, job-workflow, job-workflow-autoclean, job-workflow-failover, max-file-post-size, peoplepicker-activedirectorysearchtimeout, peoplepicker-distributionlistsearchdomains, peoplepicker-nowindowsaccountsfornonwindowsauthenticationmode, peoplepicker-onlysearchwithinsitecollection, peoplepicker-searchadcustomquery, peoplepicker-searchadforests, presenceenabled, recycle-bin-cleanup-enabled, recycle-bin-enabled, recycle-bin-retention-period, second-stage-recycle-bin-quota, send-ad-email)


99. stsadm -o getsitedirectoryscanschedule


100. stsadm -o getsitelock -url <url>


101. stsadm -o getsiteuseraccountdirectorypath -url <url>


102. stsadm -o geturlzone -url <protocol://incoming.url.domain>


103. stsadm -o grantiis7permission


104. stsadm -o import -url <URL to import to> -filename <import file name> [-includeusersecurity] [-haltonwarning] [-haltonfatalerror] [-nologfile] [-updateversions <1-3> 1= Add new versions to the current file (default), 2= Overwrite the file and all its versions (delete then insert),3= Ignore the file if it exists on the destination] [-nofilecompression] [-quiet]


105. stsadm -o installfeature {-filename <relative path to Feature.xml from system feature directory> -name <feature folder>} [-force]


106. stsadm -o listlogginglevels [-showhidden]


107. stsadm -o listregisteredsecuritytrimmers -ssp <ssp name>


108. stsadm -o localupgradestatus


109. stsadm -o managepermissionpolicylevel -url <url> -name <permission policy level name> [{ -add -delete }] [-description <description>] [-siteadmin <true false>] [-siteauditor <true false>] [-grantpermissions <comma-separated list of permissions>] [-denypermissions <comma-separated list of permissions>]


110. stsadm -o mergecontentdbs -url <url> -sourcedatabasename <source database name> -destinationdatabasename <destination datbabase name> [-operation <1-3> 1 - Analyze (default) 2 - Full Database Merge 3 - Read from file] [-filename <file generated from stsadm -o enumsites>]


111. stsadm -o migrateuser -oldlogin <DOMAIN\name> -newlogin <DOMAIN\name> [-ignoresidhistory]


112. stsadm -o osearch [-action <liststartstop>] required parameters for 'start' (if not already set): role, farmcontactemail, service credentials [-f (suppress prompts)] [-role <IndexQueryIndexQuery>] [-farmcontactemail <email>] [-farmperformancelevel <ReducedPartlyReducedMaximum>] [-farmserviceaccount <DOMAIN\name> (service credentials)] [-farmservicepassword <password>] [-defaultindexlocation <directory>] [-propagationlocation <directory>] [-cleansearchdatabase <truefalse>] [-ssp <ssp name>] required parameter for 'cleansearchdatabase'


113. stsadm -o osearchdiacriticsensitive -ssp <ssp name> [-setstatus <TrueFalse>] [-noreset] [-force]


114. stsadm -o preparetomove {-ContentDB <DatabaseServer:DatabaseName> -Site <URL>} [-OldContentDB <uniqueidentifier>] [-undo]


115. stsadm -o profilechangelog -title <SSP Name> -daysofhistory <number of days> -generateanniversaries


116. stsadm -o profiledeletehandler -type <Full Assembly Path>


117. stsadm -o provisionservice -action <start/stop> -servicetype <servicetype (namespace or assembly qualified name if not SharePoint service)> [-servicename <servicename>]


118. stsadm -o quiescefarm -maxduration <duration in minutes>


119. stsadm -o quiescefarmstatus


120. stsadm -o quiesceformtemplate [-formid <form template ID>] [-filename <path to form template file>] -maxduration <time in minutes>


121. stsadm -o reconvertallformtemplates


122. stsadm -o refreshdms -url <url>


123. stsadm -o refreshsitedms -url <url>


124. stsadm -o registersecuritytrimmer -ssp <ssp name> -id <0 - 2147483647> -typename <assembly qualified TypeName of ISecurityTrimmer implementation> -rulepath <crawl rule URL> [-configprops <name value pairs delimited by '~'>]


125. stsadm -o registerwsswriter


126. stsadm -o removedataconnectionfile -filename <filename to remove>


127. stsadm -o removedrservice -servicename <data retrieval service name> -setting <data retrieval services setting>


128. stsadm -o remove-ecsfiletrustedlocation -Ssp <SSP name> -Location <URLUNC> -LocationType SharePointUncHttp


129. stsadm -o remove-ecssafedataprovider -Ssp <SSP name> -ID <data provider id> -Type OledbOdbcOdbcDsn


130. stsadm -o remove-ecstrusteddataconnectionlibrary -Ssp <SSP name> -Location <URL>


131. stsadm -o remove-ecsuserdefinedfunction -Ssp <SSP name> -Assembly <strong namefile path> -AssemblyLocation GACFile


132. stsadm -o removeexemptuseragent -name <user-agent to receive InfoPath files instead of a Web page>


133. stsadm -o removeformtemplate [-formid <form template ID>] [-filename <path to form template file>]


134. stsadm -o removesolutiondeploymentlock [-server <server> [-allservers]


135. stsadm -o renameserver -oldservername <oldServerName> -newservername <newServerName>


136. stsadm -o renamesite -oldurl <oldUrl> -newurl <newUrl>


137. stsadm -o renameweb -url <url> -newname <new subsite name>


138. stsadm -o restore -url <url> -filename <filename> [-hostheaderwebapplicationurl <web application url>] [-overwrite]


139. stsadm -o restore -directory <UNC path> -restoremethod <overwrite new> [-backupid <Id from backuphistory, see stsadm -help backuphistory>] [-item <created path from tree>] [-percentage <integer between 1 and 100>] [-showtree] [-suppressprompt] [-username <username>] [-password <password>] [-newdatabaseserver <new database server name>] [-quiet]


140. stsadm -o restoressp -title <SSP name> -url <Web application url> -ssplogin <username> -mysiteurl <MySite Web application url> -indexserver <index server> -indexlocation <index file path> [-keepindex] -sspdatabaseserver <SSP database server> -sspdatabasename <SSP database name> [-ssppassword <password>] [-sspsqlauthlogin <SQL username>] [-sspsqlauthpassword <SQL password>] [-searchdatabaseserver <search database server>] [-searchdatabasename <search database name>] [-searchsqlauthlogin <SQL username>] [-searchsqlauthpassword <SQL password>] [-ssl <yesno>]


141. stsadm -o retractsolution -name <Solution name> [-url <virtual server url>] [-allcontenturls] [-time <time to remove at>] [-immediate] [-local] [-lcid <language>]


142. stsadm -o retractwppack -name <Web Part Package name> [-url <virtual server url>] [-time <time to retract at>] [-immediate] [-local] [-lcid <language>]


143. stsadm -o runcmsmigrationprofile -profilename <profile name> [-skipanalyzer ] [-onlyanalyzer ] [-startover ] [-migratesincetime <DateTime string>] [-migrationfolder <path>] [-exportonly ] [-importonly ] [-htmldiff <path>]


144. stsadm -o runcontentdeploymentjob -jobname <name> [-wait yesno] [-deploysincetime <datetime>] (<datetime> as "MM/DD/YY HH:MM:SS")


145. stsadm -o scanforfeatures [-solutionid <Id of Solution>] [-displayonly]


146. stsadm -o setadminport -port <port> [-ssl] [-admapcreatenew] [-admapidname <app pool name>]


147. stsadm -o setapppassword -password <password>


148. stsadm -o setbulkworkflowtaskprocessingschedule -schedule <recurrence string>


149. stsadm -o setconfigdb [-connect] -databaseserver <database server> [-databaseuser <database user>] [-databasepassword <database user password>] [-databasename <database name>] [-exclusivelyusentlm] [-farmuser] [-farmpassword] [-adcreation] [-addomain <Active Directory domain>] [-adou <Active Directory OU>]


150. stsadm -o setcontentdeploymentjobschedule -jobname <name> -schedule <schedule> (Schedule Parameter Examples: "every 5 minutes between 0 and 59", "hourly between 0 and 59", "daily at 15:00:00", "weekly between Fri 22:00:00 and Sun 06:00:00", "monthly at 15 15:00:00", "yearly at Jan 1 15:00:00")


151. stsadm -o setdataconnectionfileproperty -filename <filename of the data connection file> -pn <property name> -pv <property value>


152. stsadm -o setdefaultssp -title <SSP name>


153. stsadm -o set-ecsexternaldata -Ssp <SSP name> [-ConnectionLifetime <time in seconds>] [-UnattendedServiceAccountName <account name>] [-UnattendedServiceAccountPassword <account password>]


154. stsadm -o set-ecsloadbalancing -Ssp <SSP name> [-Scheme WorkbookUrlRoundRobinLocal] [-RetryInterval <time in seconds>]


155. stsadm -o set-ecsmemoryutilization -Ssp <SSP name> [-MaxPrivateBytes <memory in MBytes>] [-MemoryCacheThreshold <percentage>] [-MaxUnusedObjectAge <time in minutes>]


156. stsadm -o set-ecssecurity -Ssp <SSP name> [-FileAccessMethod UseImpersonationUseFileAccessAccount] [-AccessModel DelegationTrustedSubsystem] [-RequireEncryptedUserConnection FalseTrue] [-AllowCrossDomainAccess TrueFalse]


157. stsadm -o set-ecssessionmanagement -Ssp <SSP name> [-MaxSessionsPerUser <number of sessions>]


158. stsadm -o set-ecsworkbookcache -Ssp <SSP name> [-Location <local or UNC path>] [-MaxCacheSize <storage in Mbytes>] [-EnableCachingOfUnusedFiles TrueFalse]


159. stsadm -o setformsserviceproperty -pn <option name> -pv <option value>


160. stsadm -o setformtemplateproperty [-formid <form template ID>] [-filename <path to form template file>] -pn <property name> -pv <property value>


161. stsadm -o setholdschedule -schedule <recurrence string>


162. stsadm -o setlogginglevel [-category < [CategoryName Manager:CategoryName [;...]] >] {-default -tracelevel < None; Unexpected; Monitorable; High; Medium; Verbose> [-windowslogginglevel < None; ErrorServiceUnavailable; ErrorSecurityBreach; ErrorCritical; Error; Warning; FailureAudit; SuccessAudit; Information; Success>] }


163. stsadm -o setpolicyschedule -schedule <recurrence string>


164. stsadm -o setproperty -propertyname <property name> -propertyvalue <property value> [-url <url>] (SharePoint cluster properties:, avallowdownload, avcleaningenabled, avdownloadscanenabled, avnumberofthreads, avtimeout, avuploadscanenabled, command-line-upgrade-running, database-command-timeout, database-connection-timeout, data-retrieval-services-enabled, data-retrieval-services-oledb-providers, data-retrieval-services-response-size, data-retrieval-services-timeout, data-retrieval-services-update, data-source-controls-enabled, dead-site-auto-delete, dead-site-notify-after, dead-site-num-notifications, defaultcontentdb-password, defaultcontentdb-server, defaultcontentdb-user, delete-web-send-email, irmaddinsenabled, irmrmscertserver, irmrmsenabled, irmrmsusead, job-ceip-datacollection, job-config-refresh, job-database-statistics, job-dead-site-delete, job-usage-analysis, job-watson-trigger, large-file-chunk-size, token-timeout, workflow-cpu-throttle, workflow-eventdelivery-batchsize, workflow-eventdelivery-throttle, workflow-eventdelivery-timeout, workflow-timerjob-cpu-throttle, workitem-eventdelivery-batchsize, workitem-eventdelivery-throttle; SharePoint virtual server properties:, alerts-enabled, alerts-limited, alerts-maximum, change-log-expiration-enabled, change-log-retention-period, data-retrieval-services-enabled, data-retrieval-services-inherit, data-retrieval-services-oledb-providers, data-retrieval-services-response-size, data-retrieval-services-timeout, data-retrieval-services-update, data-source-controls-enabled, days-to-show-new-icon, dead-site-auto-delete, dead-site-notify-after, dead-site-num-notifications, defaultquotatemplate, defaulttimezone, delete-web-send-email, job-change-log-expiration, job-dead-site-delete, job-diskquota-warning, job-immediate-alerts, job-recycle-bin-cleanup, job-usage-analysis, job-workflow, job-workflow-autoclean, job-workflow-failover, max-file-post-size, peoplepicker-activedirectorysearchtimeout, peoplepicker-distributionlistsearchdomains, peoplepicker-nowindowsaccountsfornonwindowsauthenticationmode, peoplepicker-onlysearchwithinsitecollection, peoplepicker-searchadcustomquery, peoplepicker-searchadforests, presenceenabled, recycle-bin-cleanup-enabled, recycle-bin-enabled, recycle-bin-retention-period, second-stage-recycle-bin-quota, send-ad-email)


165. stsadm -o setrecordsrepositoryschedule -schedule <recurrence string>


166. stsadm -o setsearchandprocessschedule -schedule <recurrence string>


167. stsadm -o setsharedwebserviceauthn -ntlm -negotiate


168. stsadm -o setsitedirectoryscanschedule -schedule <recurrence string> (Schedule parameter examples: "every 5 minutes between 0 and 59", "hourly between 0 and 59", "daily at 15:00:00", "weekly between Fri 22:00:00 and Sun 06:00:00", "monthly at 15 15:00:00", "yearly at Jan 1 15:00:00")


169. stsadm -o setsitelock -url <url> -lock <none noadditions readonly noaccess>


170. stsadm -o setsiteuseraccountdirectorypath -url <url> [-path <path>]


171. stsadm -o setsspport -httpport <HTTP port number> -httpsport <HTTPS port number>


172. stsadm -o setworkflowconfig -url <url> {-emailtonopermissionparticipants <enabledisable> -externalparticipants <enabledisable> -userdefinedworkflows <enabledisable>}


173. stsadm -o siteowner -url <url> [-ownerlogin <DOMAIN\name>] [-secondarylogin <DOMAIN\name>]


174. stsadm -o spsearch [-action <list start stop attachcontentdatabase detachcontentdatabase fullcrawlstart fullcrawlstop>] [-f (suppress prompts)] [-farmperformancelevel <Reduced PartlyReduced Maximum>] [-farmserviceaccount <DOMAIN\name> (service credentials)] [-farmservicepassword <password>] [-farmcontentaccessaccount <DOMAIN\name>] [-farmcontentaccesspassword <password>] [-indexlocation <new index location>] [-databaseserver <server\instance> (default: josebda-moss)] [-databasename <database name> (default: SharePoint_WSS_Search)] [-sqlauthlogin <SQL authenticated database user>] [-sqlauthpassword <password>] -action list -action stop [-f (suppress prompts)] -action start -farmserviceaccount <DOMAIN\name> (service credentials) [-farmservicepassword <password>] -action attachcontentdatabase [-databaseserver <server\instance> (default: josebda-moss)] -databasename <content database name> [-searchserver <search server name> (default: josebda-moss)] -action detachcontentdatabase [-databaseserver <server\instance> (default: josebda-moss)] -databasename <content database name> [-f (suppress prompts)] -action fullcrawlstart -action fullcrawlstop


175. stsadm -o spsearchdiacriticsensitive [-setstatus <TrueFalse>] [-noreset] [-force]


176. stsadm -o sync {-ExcludeWebApps <web applications> -SyncTiming <schedule(M/H/D:value)> -SweepTiming <schedule(M/H/D:value)> -ListOldDatabases <days> -DeleteOldDatabases <days>}


177. stsadm -o syncsolution -name <Solution name>] [-lcid <language>] [-alllcids]


178. stsadm -o syncsolution -allsolutions


179. stsadm -o unextendvs -url <url> [-deletecontent] [-deleteiissites]


180. stsadm -o uninstallfeature {-filename <relative path to Feature.xml> -name <feature folder> -id <feature Id>} [-force]


181. stsadm -o unquiescefarm


182. stsadm -o unquiesceformtemplate [-formid <form template ID>] [-filename <path to form template file>]


183. stsadm -o unregistersecuritytrimmer -ssp <ssp name> -id <0 - 2147483647>


184. stsadm -o unregisterwsswriter


185. stsadm -o updateaccountpassword -userlogin <DOMAIN\name> -password <password> [-noadmin]


186. stsadm -o updatealerttemplates -url <url> [-filename <filename>] [-lcid <language>


187. stsadm -o updatefarmcredentials [-identitytype <configurableid/NetworkService>] [-userlogin <DOMAIN\name>] [-password <password>] [-local [-keyonly]]


188. stsadm -o upgrade {-inplace -sidebyside} [-url <url>] [-forceupgrade] [-quiet] [-farmuser <farm user>] [-farmpassword <farm user password>] [-reghost] [-sitelistpath <sites xml file>]


189. stsadm -o upgradeformtemplate -filename <path to form template file> [-upgradetype <upgrade type>]


190. stsadm -o upgradesolution -name <Solution name> -filename <upgrade filename> [-time <time to upgrade at>] [-immediate] [-local] [-allowgacdeployment] [-allowcaspolicies] [-lcid <language>]


191. stsadm -o upgradetargetwebapplication -url <URL to upgrade> -relocationurl <new URL for non-upgraded content> -apidname <new app pool name> [-apidtype <configurableid/NetworkService>] [-apidlogin <DOMAIN\name>] [-apidpwd <app pool password>] [-exclusivelyusentlm]


192. stsadm -o uploadformtemplate -filename <path to form template file>


193. stsadm -o userrole -url <url> -userlogin <DOMAIN\name> -role <role name> [-add] [-delete]


194. stsadm -o verifyformtemplate -filename <path to form template file>

VS 2003 to VS 2005 asp.net not working with ajax 1.0.

A migrated asp.net application from 1.1 to 2.0 with ajax 1.0 is found that the ajax part is not working. I did some research and found that the culprit is
tag in the web.config
Background:
ASP.NET 1.0 and 1.1 didn't emit XHTML compliant markup from many of its server controls. ASP.NET 2.0 changed this and by default emits XHTML compliant markup from all controls.
One of the things we noticed in the early ASP.NET 2.0 betas, though, was that when upgrading customer applications a lot of the applications had assumptions that the page output was not XHTML compliant. By changing our default output of the server controls to be XHTML, it sometimes modified the visual rendering of a page. For backwards compatibility purposes the switch above that allows developers to render controls in "Legacy" mode (non-XHTML markup the same as ASP.NET 1.1) as well as Transitional mode (XHTML Transitional) as well as Strict mode (XHTML Strict).
By default when you use the VS 2003->VS 2005 Web Project Migration wizard (for both web sites and web application projects), your web.config file will have the legacy switch added.
Solution:
Unless you know of known issues that your site has when running in XHTML mode (and which you don't have time yet to fix), It is recommend removing the section from your web.config file (or you can explicitly set it to "Transitional" or "Strict").
This will make your HTML output standards compliant. Among other things, this will cause the HTML from your server controls to be "well formed" - meaning open and close tag elements always match. This is particularly important when you are using AJAX techniques to dynamically replace the contents of certain HTML elements on your page (otherwise the client-side JavaScript sometimes gets confused about container elements and can lead to errors). It will also ensure that ASP.NET AJAX works fine with your site.
Source

Best Practices to improve ASP.Net Web Application Performance

Introduction
Performance tuning can be tricky. It's especially tough in Internet-related projects with lots of components running around, like HTML client, HTTP network, Web server, middle-tier components, database components, resource-management components, TCP/IP networks, and database servers. Performance tuning depends on a lot of parameters and sometimes, by changing a single parameter, performance can increase drastically.

1) Turn off Tracing unless until required
Tracing is one of the wonderful features which enable us to track the application's trace and the sequences. However, again it is useful only for developers and you can set this to "false" unless you require to monitor the trace logging.

How it affects performance:

Enabling tracing adds performance overhead and might expose private information, so it should be enabled only while an application is being actively analyzed.

Solution:

When not needed, tracing can be turned off using

2) Turn off Session State, if not required

One extremely powerful feature of ASP.NET is its ability to store session state for users, such as a shopping cart on an e-commerce site or a browser history.

How it affects performance:

Since ASP.NET Manages session state by default, you pay the cost in memory even if you don't use it. I.e. whether you store your data in in-process or on state server or in a Sql Database, session state requires memory and it's also time consuming when you store or retrieve data from it.

Solution:

You may not require session state when your pages are static or when you do not need to store information captured in the page. In such cases where you need not use session state, disable it on your web form using the directive,

<@%Page EnableSessionState="false"%>

In case you use the session state only to retrieve data from it and not to update it, make the session state read only by using the directive,

<@%Page EnableSessionState ="ReadOnly"%>

3) Disable View State of a Page if possible

View state is a fancy name for ASP.NET storing some state data in a hidden input field inside the generated page. When the page is posted back to the server, the server can parse, validate, and apply this view state data back to the page's tree of controls. View state is a very powerful capability since it allows state to be persisted with the client and it requires no cookies or server memory to save this state. Many ASP.NET server controls use view state to persist settings made during interactions with elements on the page, for example, saving the current page that is being displayed when paging through data.

How it affects performance:

There are a number of drawbacks to the use of view state, however. It increases the total payload of the page both when served and when requested. There is also an additional overhead incurred when serializing or deserializing view state data that is posted back to the server. View state increases the memory allocations on the server. Several server controls, the most well known of which is the DataGrid, tend to make excessive use of view state, even in cases where it is not needed.

Solution:

Pages that do not have any server postback events can have the view state turned off. The default behavior of the ViewState property is enabled, but if you don't need it, you can turn it off at the control or page level. Within a control, simply set the EnableViewState property to false, or set it globally within the page using this setting:

<%@ Page EnableViewState="false" %>

If you turn view state off for a page or control, make sure you thoroughly test your pages to verify that they continue to function correctly.

4) Set debug=false in web.config

When you create the application, by default this attribute is set to "true" which is very useful while developing. However, when you are deploying your application, always set it to "false".

How it affects performance:

Setting it to "true" requires the pdb information to be inserted into the file and this results in a comparatively larger file and hence processing will be slow.

Solution:

Therefore, always set debug="false" before deployment.

5) Avoid Response.Redirect

Response.Redirect () method simply tells the browser to visit another page.

How it affects performance:

Redirects are also very chatty. They should only be used when you are transferring people to another physical web server.

Solution:

For any transfers within your server, use .transfer! You will save a lot of needless HTTP requests. Instead of telling the browser to redirect, it simply changes the "focus" on the Web server and transfers the request. This means you don't get quite as many HTTP requests coming through, which therefore eases the pressure on your Web server and makes your applications run faster.

Tradeoffs:

1. ".transfer" process can work on only those sites running on the server. Only Response.Redirect can do that.

2. Server.Transfer maintains the original URL in the browser. This can really help streamline data entry techniques, although it may make for confusion when debugging

5. A) To reduce CLR Exceptions count, Use Response.Redirect (".aspx", false) instead of response.redirect (".aspx").

6) Use the String builder to concatenate string

How it affects performance:

String is Evil when you want to append and concatenate text to your string. All the activities you do to the string are stored in the memory as separate references and it must be avoided as much as possible. i.e. When a string is modified, the run time will create a new string and return it, leaving the original to be garbage collected. Most of the time this is a fast and simple way to do it, but when a string is being modified repeatedly it begins to be a burden on performance: all of those allocations eventually get expensive.

Solution:

Use String Builder when ever string concatenation is needed so that it only stores the value in the original string and no additional reference is created.

7) Avoid throwing exceptions

How it affects performance:

Exceptions are probably one of the heaviest resource hogs and causes of slowdowns you will ever see in web applications, as well as windows applications.

Solution:

You can use as many try/catch blocks as you want. Using exceptions gratuitously is where you lose performance. For example, you should stay away from things like using exceptions for control flow.

8) Use Finally Method to kill resources

The finally method gets executed independent of the outcome of the Block. Always use§ the finally block to kill resources like closing database connection, closing files and other resources such that they get executed independent of whether the code worked in Try or went to Catch.

9) Use Client Side Scripts for validations

User Input is Evil and it must be thoroughly validated before processing to avoid overhead and possible injections to your applications. How It improves performance: Client site validation can help reduce round trips that are required to process user's request. In ASP.NET you can also use client side controls to validate user input. However, do a check at the Server side too to avoid the infamous Javascript disabled scenarios.

10) Avoid unnecessary round trips to the server

How it affects performance:

Round trips significantly affect performance. They are subject to network latency and to downstream server latency. Many data-driven Web sites heavily access the database for every user request. While connection pooling helps, the increased network traffic and processing load on the database server can adversely affect performance.

Solution:

Keep round trips to an absolute minimum§ § Implement Ajax UI whenever possible. The idea is to avoid full page refresh and only update the portion of the page that needs to be changed

11) Use Page.ISPostBack

Make sure you don't execute code needlessly. Use Page.ISPostBack property to ensure that you only perform page initialization logic when a page is first time loaded and not in response to client postbacks.

12) Include Return Statements with in the Function/Method

How it improves performance

Explicitly using return allows the JIT to perform slightly more optimizations. Without a return statement, each function/method is given several local variables on stack to transparently support returning values without the keyword. Keeping these around makes it harder for the JIT to optimize, and can impact the performance of your code. Look through your functions/methods and insert return as needed. It doesn't change the semantics of the code at all, and it can help you get more speed from your application.

13) Use Foreach loop instead of For loop for String Iteration

Foreach is far more readable, and in the future it will become as fast as a For loop for special cases like strings. Unless string manipulation is a real performance hog for you, the slightly messier code may not be worth it.

14) Avoid Unnecessary Indirection

How it affects performance:

When you use byRef, you pass pointers instead of the actual object. Many times this makes sense (side-effecting functions, for example), but you don't always need it. Passing pointers results in more indirection, which is slower than accessing a value that is on the stack.

Solution:

When you don't need to go through the heap, it is best to avoid it there by avoiding indirection.

15) Use "ArrayLists" in place of arrays

How it improves performance

An ArrayList as everything that is good about an array PLUS automatic sizing, Add, Insert, Remove, Sort, Binary Search. All these great helper methods are added when implementing the IList interface.

Tradeoffs:

The downside of an ArrayList is the need to cast objects upon retrieval.

16) Always check Page.IsValid

when using Validator Controls Always make sure you check Page.IsValid before processing your forms when using Validator Controls.

17) Use Paging

Take advantage of paging's simplicity in .net. Only show small subsets of data at a time, allowing the page to load faster.

Tradeoffs:

Just be careful when you mix in caching. Don't cache all the data in the grid.

18) Store your content by using caching

How it improves performance:

ASP.NET allows you to cache entire pages, fragment of pages or controls. You can cache also variable data by specifying the parameters that the data depends. By using caching you help ASP.NET engine to return data for repeated request for the same page much faster.

When and Why Use Caching:

A Proper use and fine tune of caching approach of caching will result on better performance and scalability of your site. However improper use of caching will actually slow down and consume lots of your server performance and memory usage. Good candidate to use caching is if you have infrequent chance of data or static content of web page.

19) Use low cost authentication

Authentication can also have an impact over the performance of your application. For example passport authentication is slower than form-base authentication which in here turn is slower than Windows authentication.

20) Minimize the number of web server controls

How it affects performance:

The use of web server controls increases the response time of your application because they need time to be processed on the server side before they are rendered on the client side.

Solution:

One way to minimize the number of web server controls is to taking into consideration, the usage of HTML elements where they are suited, for example if you want to display static text.

21) Avoid using unmanaged code

How it affects performance:

Calls to unmanaged code are a costly marshaling operation.

Solution:

Try to reduce the number calls between the managed and unmanaged code. Consider to do more work in each call rather than making frequent calls to do small tasks.

22) Avoid making frequent calls across processes

If you are working with distributed applications, this involves additional overhead negotiating network and application level protocols. In this case network speed can also be a bottleneck. Try to do as much work as possible in fewer calls over the network.

23) Cleaning Up Style Sheets and Script Files

A quick and easy way to improve your§ web application's performance is by going back and cleaning up your CSS Style Sheets and Script Files of unnecessary code or old styles and functions. It is common for old styles and functions to still exist in your style sheets and script files during development cycles and when improvements are made to a website.

Many websites use a single CSS Style Sheet or Script File for the§ entire website. Sometimes, just going through these files and cleaning them up can improve the performance of your site by reducing the page size. If you are referencing images in your style sheet that are no longer used on your website, it's a waste of performance to leave them in there and have them loaded each time the style sheet is loaded.

Run a web page analyzer against pages in§ your website so that you can see exactly what is being loaded and what takes the most time to load.

24) Design with ValueTypes

Use simple structs when you can, and when you don't do a lot of boxing and unboxing.

Tradeoffs:

ValueTypes are far less flexible than Objects, and end up hurting performance if used incorrectly. You need to be very careful about when you treat them like objects. This adds extra boxing and unboxing overhead to your program, and can end up costing you more than it would if you had stuck with objects.

25) Minimize assemblies

Minimize the number of assemblies you use to keep your working set small. If you load an entire assembly just to use one method, you're paying a tremendous cost for very little benefit. See if you can duplicate that method's functionality using code that you already have loaded.

26) Encode Using ASCII When You Don't Need UTF

By default, ASP.NET comes configured to encode requests and responses as UTF-8. If ASCII is all your application needs, eliminated the UTF overhead can give you back a few cycles. Note that this can only be done on a per-application basis.

27) Avoid Recursive Functions / Nested Loops

These are general things to adopt in any programming language, which consume lot of memory. Always avoid Nested Loops, Recursive functions, to improve performance.

28) Minimize the Use of Format ()

When you can, use toString () instead of format (). In most cases, it will provide you with the functionality you need, with much less overhead.

29) Place StyleSheets into the Header

Web developers who care about performance want browser to load whatever content it has as soon as possible. This fact is especially important for pages with a lot of content and for users with slow Internet connections. When the browser loads the page progressively the header, the logo, the navigation components serve as visual feedback for the user. When we place style sheets near the bottom part of the html, most browsers stop rendering to avoid redrawing elements of the page if their styles change thus decreasing the performance of the page. So, always place StyleSheets into the Header

30) Put Scripts to the end of Document

Unlike StyleSheets, it is better to place scripts to the end of the document. Progressive rendering is blocked until all StyleSheets have been downloaded. Scripts cause progressive rendering to stop for all content below the script until it is fully loaded. Moreover, while downloading a script, browser does not start any other component downloads, even on different hostnames. So,always have scripts at the end of the document.

31) Make JavaScript and CSS External

Using external files generally produces faster pages because the JavaScript and CSS files are cached by the browser. Inline JavaScript and CSS increases the HTML document size but reduces the number of HTTP requests. With cached external files, the size of the HTML is kept small without increasing the number of HTTP requests thus improving the performance.

Source