Enumssptimerjobs: STSADM operation (Office SharePoint Server)

The primary purpose of this operation is for an administrator to list all timer jobs in the SSP especially if a computer had Microsoft Project Server installed, and then was uninstalled. In this scenario, the Project Server SSP timer jobs still exist in the SSP database even though Project Server is not installed on the computer. To delete these orphan timer jobs, use the Deletessptimerjob operation. For more information about timer jobs, see the Remarks section of this article.

Syntax

stsadm -o enumssptimerjobs

-title

'stsadm -o canceldeployment' when a solution deployment is already under way

If a SharePoint solution deployment fails, yet the timer job is created and not running, you will be unable to redeploy or retract the solution. The retract / deploy buttons will not be present in Central Admin and stsadm will declare that a "deployment or retraction is already under way for the solution". You can find yourself in this state if the “Windows SharePoint Services Administration” service is stopped when you first attempt to deploy, but even after you realise your mistake and start that service, the solution deployment is still stuck.
The answer is hidden in that long list of stsadm operations:

stsadm –o canceldeployment –id

This command will cancel the timer job that is meant to deploy the solution. Once it has been cleared, you can deploy successfully. Obtain the id parameter from the url to the appropriate deployment timer job in the Operations -> Timer Job Definitions page

Create Page Access Denied

Users need to be in the Readers group for the Master Page Gallery in order to create pages in the portal.

Deploying Web Parts using CAB files

1. For ease of deployment, copy the .cab file to the following location, where Office SharePoint Server 2007 is installed:
   

   C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin

   This should be the same as the location of Stsadm.exe. Ensure that you update the path on your computer if it does not match the default location.
   


2. Click Start, click Run, and then type cmd.
   


3. Type cd "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin"
   


4. Run the following command to deploy your Web Part accross the entire farm:
   
   stsadm.exe -o addwppack -filename yourcabfilename.cab -globalinstall -force
   


5. Run the following command to deploy your Web Part to a specific website:
   
   stsadm.exe -o addwppack -filename yourcabfilename.cab -url http://teleport -globalinstall -force
   


6. After the command returns with "Operation completed successfully," run the following command:
   
   iisreset /timeout:0
   


7. Check central administration / solution management to see where the solutions are registered as deployed by SharePoint.
   

MOSS Site Usage report error (and crash)

This happened today;

The symptom of the problem is that when trying to access the site usage reporting in MOSS the user (who does have access) is prompted to authenticate, upon failing to authenticate the worker process falls over.

The app event reports the following error: .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error

The SSP1 & Portal application pools both stopped running.

The resolution is the application of a non-public hotfix to ASP.net 2.0: http://support.microsoft.com/kb/913384