Archives / 2007 / October
  • DST issue Pt. 2: SharePoint jobs don't immediately propagate

    As of Sunday (Oct 28) it seems that server farms with uneven Windows Server patches are once again seeing issues with deployment jobs. The symptom is that deployment of x takes up to an hour to execute or propagate to all servers in the farm. For example, a web content deployment will be delayed, Forms uploaded to Forms Server aren't marked Ready for an hour, etc.
    As a workaround, this issue can be solved from the command line with the usual:
    stsadm -o execadmsvcjobs
    The fix is to get all servers in the farm up to the same patch levels. Windows Server SP2 solves the issue, it includes the Feb 2007 cumulative time zone update. There is an additional patch for WSS 2.0 and SPS 2003 (previously described here), while O12 products (WSS 3.0 and MOSS) should behave correctly if the server itself is patched.  If you're back in the stone or bronze ages, this is the authoritative article, note that it only addresses SP&T 2001 and 2003:
    [Updated Nov 1 with links to Windows Server SP2 and the SP&T Team Blog article]


  • Error: "Additions to this Web site have been blocked."

    The error is "Additions to this Web site have been blocked." It used to happen occasionally in WSS 2, and now it's confirmed to happen in WSS 3. What am I talking about? MOSS installations where no one monitors the size of database growth.

    Bring up SQL Server Management Studio and check out where the errors are being thrown. It's usually the transaction logs. If you're using log shipping or have a regular database backup strategy (you mean you don't?) the logs will maintain a reasonable size since the operations regularly trim the backlog. If not, then the transaction logs will grow, and grow, and grow. Since you're not doing anything with them, you're just as well to truncate the logs on a routine basis. For SQL 2005, I like comment 14 in this post, it does a great job of describing a way to shrink the logs in the UI, and how to eliminate the log file completely.  

    Best practices? Have separate spindles for your SQL Server OS, databases (.mdf files), and transaction logs. Monitor the growth of your data and transaction logs, and follow a regular backup strategy.


  • Toronto SharePoint Camp: This Saturday!

    Toronto SharePoint Camp

    Volunteer night is Wednesday at Nexient (2 Bloor West, at Yonge). If you'd like to be one of the intelligent, wonderful, sexy people we call our volunteers then click through the picture and get in there!

    Registration is filling up fast, so if you're planning to come out, please get your name and e-mail address in today. Confirmations will go out prior to the event, note that the site does not display a confirmation message. Freebies from our sponsors are available for the first 200 peple through the door who registered on the site. If you're not sure whether you can come Saturday, you're welcome to "just show up" but will not be eligible for the free swag.

    There will be 12 to 15 great sessions through the day from a stellar cast of presenters. You can get details about most of these on the website already, all will be there soon.

    On Saturday, Check-in starts at 8:00am, and the first sessions start at 9:00am. For the last session, we'll wrap up with a Roundtable Panel where you can throw questions at your favourite speakers. Then it's on to the raffle (complete your evaluations!) where you'll have a chance at one of many, many great prizes. Check-out is at 6:00pm, soon after which my Event Receivers will be firing up for beer.

    See you there!