Anyone bitten by Daylight Saving Time yet?

I have.

For some reason, my clock didn't "spring forward" today, so I set it manually.

When I tried to make a call to a Web Service that's protected by UserNameToken's which we're using Microsoft.Web.Services2 to access, and getting this error:

-----
Type  = SecurityFault
Message = Message Expired

InnerException
Type = Exception
Message = At least one timestamp has expired.

-----

And when I set my clock back an hour, everything works just fine. Weird?

(whoops shoulda posted to TechOff)

So far everything is smooth here.  I do have one machine that doesn't get patches pushed to it that I use for VB6 coding that keeps changing back 1 hour when I set its clock. 

My web server runs a daily task of which it sends me a summary mail, and I noticed I get that an hour early now since I'm not in DST yet while the server is.

I was bitten by Godaddy's outage yesterday, but other than that, fine (I've got everything in UTC)

How much you wanna bet that the US government decides it wasn't worth it to change the date and goes back to the old DST, requiring all the patched computers to be unpatched?

I couldn't work out. The work-out room has a time based lock, and doesn't open till 6:00 AM. No one reset it, so I was screwed. I've got two calls into the homeowners association, but no response yet.

And yes, I LIKE working out, so it was a bummer!

I'll take you up on that one   Since the US Gov't voted for this in the first place, it'll take years to get it changed.

I did hear an interesting point over the weekend on NPR:  At this point in time, we are at 8 months of 'non-standard' time and 4 months of 'standard' time.  So if we spend twice as much time in the non-standard time, why not just flip them around and make DST the standard time.

Of course, the best idea would be to eliminate it altogether.  There are plenty of economic reasons to allow people to come home in daylight, so why not do it year round?

Minh wrote:

I have.

For some reason, my clock didn't "spring forward" today, so I set it manually.

When I tried to make a call to a Web Service that's protected by UserNameToken's which we're using Microsoft.Web.Services2 to access, and getting this error:

-----
Type  = SecurityFault
Message = Message Expired

InnerException
Type = Exception
Message = At least one timestamp has expired.

-----

And when I set my clock back an hour, everything works just fine. Weird?

(whoops shoulda posted to TechOff)

My blackberry did not get set and I was really scared.

I did some research, and I think this is the cause....

Because of company policy, I can't simply run Windows Update to get the March-11 DST patch... and apparently, I didn't get it through the company patching process either... Fine, no big deal right?

I'm using WSE to access a Web Service, which sends along w/ the request, an expiration date, in Universal Coordinated Time (UTC) format.

A couple of days ago, for most people in my time zone, UTC is local time + 5, but today, it's actually local time + 4.

The other big problem is that my web server IS actually updated, so when it gets my "correct" time (local + 5) it must've fallen outside the allowable range. But giving me back a Message _Expired_ still isn't cool, since in reality, my message is too early.

Every clock was reset except the alarm clock.

I woke an hour before it was set to go off anyway...