Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog

For Software Delivery 6.1, the leap year bug is back...

Created: 29 Feb 2012 • 7 comments
Ludovic Ferre's picture
+2 2 Votes
Login to vote

I have a couple of customers that reported to me that the leap year bug we had back in... guess what 2008... is right back at it.

In short, you cannot modify any tasks because of the defect documented and fixed previously on KB40682, also documented previously by Marc on his blog:

http://altirisbe.blogspot.com/2008_02_01_archive.html

Apparantly the hotfix doesn't seem to work anymore, most likely due to later changes on the components... more information to come on this throughout the day.

Comments 7 CommentsJump to latest comment

Ludovic Ferre's picture

May be my customer both miss this one fix? Let's see.

I am currently off-net, on a retreat of some kind. I'll be back real soon, and you sure will hear from me then ;-).

Ludovic FERRÉ
Principal Remote Product Specialist
Symantec

0
Login to vote
D-Chad's picture

Is it safe to assume that this will resolve itself tomorrow morning if we cannot run the hotfix?

Thanks

SysMonkey

0
Login to vote
Ludovic Ferre's picture

And given the next leap year will be 2016, I hope nobody will still be on NS 6.0 right then :D.

So don't worry about the pointfix if you can't push it today. That's a day off for new SWD Tasks, or edits.

I am currently off-net, on a retreat of some kind. I'll be back real soon, and you sure will hear from me then ;-).

Ludovic FERRÉ
Principal Remote Product Specialist
Symantec

0
Login to vote
MrSoapsud's picture

I've also just run the hotfix as it seems we're still using the version of SWD that was around 4 years ago!! Problem solved...

Thanks for the info Ludovic

0
Login to vote
Sean.B's picture

I added <validPeriod validDatesAreUTC="true"  after="2012-2-19 00:00:00" before="2012-02-28 23:59:00"/> and imported the task and it worked like a charm. 

I just did this for new tasks. Left the existing tasks alone.

Once you are in the task just change the expiration date to some date after the 29th, i.e. 3/30/2012.

0
Login to vote
Ludovic Ferre's picture

I know it's coming a little late but there are some positive and negative feedback to the fix that was delivered on 2008-02-29.

Some of the positive changes involve the Software Portal, where stored procedures now take an extra argument whcih allows created Portal Request to show under the user account that initiated the request, rather than the Windows Network account.

On the down side some of the stored procedure changes have made the portal pages or Sequeutial Software Delivery Task much slower to load.

Reverting this hotfix (which is a lot more comprehensive than a fix for the leap year bug) is an option that should be considered, should you encounter performance issues.

I am currently off-net, on a retreat of some kind. I'll be back real soon, and you sure will hear from me then ;-).

Ludovic FERRÉ
Principal Remote Product Specialist
Symantec

0
Login to vote