Could not start the windows sharepoint services timer service on local computer. The service did not start due to a logon failure

I don't know if any of you have come across this, but it cause the Sharepoint wizard to fail during the upgrade process of the service pack. The problem turned out to be very simple. The Timer Job service was running under an account that had expired. To fix it, go to the service, click Log On, and make sure the account it uses is valid and not locked or disabled.

SharePoint and MOSS service pack is out!!!!

SP1 for both MOSS and WSS is out now. Go to microsoft.com and download them. Please install WSS service pack before installing MOSS service pack.

Here is the link for WSS 3.0 SP1:
http://www.microsoft.com/downloads/details.aspx?FamilyId=4191A531-A2E9-45E4-B71E-5B0B17108BD2&displaylang=en

Here is the link for MOSS S1:
http://www.microsoft.com/downloads/details.aspx?FamilyId=AD59175C-AD6A-4027-8C2F-DB25322F791B&displaylang=en

It's a bit tricky to install it on a farm with more than one server, so if you have any questions, simply ask me.

Content Deployment issues and a new wizard

Im not sure if everyone else has had an issue using the SharePoint content deployment, but most of the time it doesn't do what it's meant to do, deploy the content. A very useful tool I've come across is the Content Deployment Wizard (
http://www.codeplex.com/SPDeploymentWizard). Very simple to use. Let me know what you think of it.

Exception from HRESULT: 0x80040E14

If any of you have come across this error "Exception from HRESULT: 0x80040E14" while trying to do a STSADM restore, it's a very simple problem. It means the SQL server has run out of space for either the logs or the data file. Simply delete some un-needed files from the HDD that the SQL server is writting to and it fixes the problem.