I will post helpful "howto's" here
Monday, November 3, 2008
SharePoint DST job timer/definition problems
Not sure how prevalent this problem is, but I have run into this on my "devlab" system.
“One-time timer jobs in Windows SharePoint Services 3.0 or in SharePoint Server 2007 are delayed by at least one hour when the jobs are scheduled to occur during daylight saving time (DST)”
http://support.microsoft.com/kb/938663
I am trying to run a large (23GB) restore job; taking the production stsadm *.bak file and back populate my devlab. In order to do so, you must first create the site and site collection first, and then overwrite with the restore *.bak file. One problem i found in doing this, was that the site did not get created (this worked prior to Wednesday, but then began to "fail", or so i thought.)
I could see a job definition for "Provisioning" the site listed, but unfortunately there is not a choice to "Run now"... (*feature?) and so i deleted the job definition, thinking there was a bug and that it would not run. *btw, "Unprovisioning" is also a one-time job that would get stuck as well, so i had to go old school on the IIS server to release all the files/directories and definitions in IIS to get it to clear; oddly enough the database was deleted as expected, just not the IIS site, as it was waiting for this Unprovisioning job to run.
After finding this KB article, I once again created the site, but then left it alone over the weekend and found it had been created.
Now... we will have to test whether or not, since we are now on Standard Time, if this is a null issue w/o applying the KB. Of course, once i have done my restore (/x-fingers that it works) I will apply the kb!
“One-time timer jobs in Windows SharePoint Services 3.0 or in SharePoint Server 2007 are delayed by at least one hour when the jobs are scheduled to occur during daylight saving time (DST)”
http://support.microsoft.com/kb/938663
I am trying to run a large (23GB) restore job; taking the production stsadm *.bak file and back populate my devlab. In order to do so, you must first create the site and site collection first, and then overwrite with the restore *.bak file. One problem i found in doing this, was that the site did not get created (this worked prior to Wednesday, but then began to "fail", or so i thought.)
I could see a job definition for "Provisioning" the site listed, but unfortunately there is not a choice to "Run now"... (*feature?) and so i deleted the job definition, thinking there was a bug and that it would not run. *btw, "Unprovisioning" is also a one-time job that would get stuck as well, so i had to go old school on the IIS server to release all the files/directories and definitions in IIS to get it to clear; oddly enough the database was deleted as expected, just not the IIS site, as it was waiting for this Unprovisioning job to run.
After finding this KB article, I once again created the site, but then left it alone over the weekend and found it had been created.
Now... we will have to test whether or not, since we are now on Standard Time, if this is a null issue w/o applying the KB. Of course, once i have done my restore (/x-fingers that it works) I will apply the kb!
Welcome to SharePoint (Hit and) Missives
Welcome to, what i hope, will be a useful site for other Enterprise level SharePoint Admins.
Subscribe to:
Posts (Atom)