Hello,
we have set up service window on receive ports: 01:00 - 22:45. After
daylight saving switch we noticed that it was shifted to 02:00 - 23:45.

I didnt see anything about it in documentation. Could someone give full
explanation how the daylight saving shift is handled in BizTalk (2004). Or i
f
I missed something could you send a link to this topic? (I would like to kno
w
if the time is changed also for something else, like tracking etc.)

The shift of the service windows caused us problems as we have scheduled
support tasks in maintenance window, when we do not expect any external
messages comming into the system.
Now we rescheduled service windows but I expect another shift on next
dayligth saving.

Thanks,
eXavier

[ Post a follow-up to this message ]

Funny - I am seeing the same behavior with Delay shapes on Beta 1 of BizTalk
2006.

Jon Flanders [MVP]
http://www.masteringbiztalk.com

> Hello,
> we have set up service window on receive ports: 01:00 - 22:45. After
> daylight saving switch we noticed that it was shifted to 02:00 -
> 23:45.
> I didnt see anything about it in documentation. Could someone give
> full explanation how the daylight saving shift is handled in BizTalk
> (2004). Or if I missed something could you send a link to this topic?
> (I would like to know if the time is changed also for something else,
> like tracking etc.)
>
> The shift of the service windows caused us problems as we have
> scheduled
> support tasks in maintenance window, when we do not expect any
> external
> messages comming into the system.
> Now we rescheduled service windows but I expect another shift on next
> dayligth saving.
> Thanks,
> eXavier

[ Post a follow-up to this message ]

Interesting, so am I. Did you find a resolution for it? All my delay shapes
are taking an extra hour now....

Matt

"Jon Flanders" <jon.flanders@gmail.com> wrote in message
news:28a4873811e338c7ae777e7e6d00@news.microsoft.com...
> Funny - I am seeing the same behavior with Delay shapes on Beta 1 of
BizTalk
> 2006.
>
> Jon Flanders [MVP]
> http://www.masteringbiztalk.com
> 
>
>

[ Post a follow-up to this message ]

Hello Matthew,
Yep - i changed my delay shape to take a negative one (-1) for the hour in
creatign the timespan.  LOL - quite the hack.

Seems to me this is a bigger bug than I first thought.  Anyone from MS liste
ning
today?

Jon Flanders [MVP]
http://www.masteringbiztalk.com
[vbcol=seagreen]
> Interesting, so am I. Did you find a resolution for it? All my delay
> shapes are taking an extra hour now....
>
> Matt
>
> "Jon Flanders" <jon.flanders@gmail.com> wrote in message
> news:28a4873811e338c7ae777e7e6d00@news.microsoft.com...
> 
> BizTalk
> 

[ Post a follow-up to this message ]

Hi all,

It seems I haven't been able to reproduce the problem. What is the time
zone you are using?

I set Service Window on a receive location, change system to use Pacific
time and select 'Automatically adjust clock for daylight saving changes'.
Then I set date time to 1:59:55 AM, Oct 30 . After few secs, the clock is
adjusted to 1:0:0 AM. However the time span in Service Window hasn't been
changed at all.

Our BizTalk SDE has ever confirmed they performed many tests on daylight
saving. The time saved in database is in local time, which shouldn't be
affected.

So could you please provide me with detailed info to reproduce the symptom
you met? Thanks.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.

[ Post a follow-up to this message ]

I am in central time zone. While I am not having issues with the service
window, I am having issues with my delay/wait shapes in orchestrations.
Their time span value is being used from a businessobject that is returned
from calling a ruleset. I tried changing the rule that creates the delay by
using a -1 in the hours argument (this is really just a timespan object
right?) and then the orchestrations would complete very quickly, before they
should have. So I then undeployed that policy and put the old one in place
and everything worked like I expected it would.... until this morning. Now
it is back to having longer delays then the wait shape should have. This
seems like a bug of some sort, but I have no idea where to start working on
it.

Any help would be greatly appreciated.

Matt


""WenJun Zhang[msft]"" <wjzhang@online.microsoft.com> wrote in message
news:hTqzDHU4FHA.1144@TK2MSFTNGXA01.phx.gbl...
> Hi all,
>
> It seems I haven't been able to reproduce the problem. What is the time
> zone you are using?
>
> I set Service Window on a receive location, change system to use Pacific
> time and select 'Automatically adjust clock for daylight saving changes'.
> Then I set date time to 1:59:55 AM, Oct 30 . After few secs, the clock is
> adjusted to 1:0:0 AM. However the time span in Service Window hasn't been
> changed at all.
>
> Our BizTalk SDE has ever confirmed they performed many tests on daylight
> saving. The time saved in database is in local time, which shouldn't be
> affected.
>
> So could you please provide me with detailed info to reproduce the symptom
> you met? Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>

[ Post a follow-up to this message ]

Hi WenJun - I was able to reproduct it with a simple project.  

Here is the string that I sent in  - <string>foo</string>

Here is the string I got out - 
<?xml version="1.0" encoding="utf-8"?>
<string>11/2/2005 9:08:13 PM start:11/2/2005 10:08:45 PM end:</string>

If you notice - the delay was set to 30 seconds in the Orch - but came out t
o an hour and 30 seconds.

This is BizTalk 2006 beta 1 and SQL 2000

Jon Flanders [MVP]
http://www.masteringbiztalk.com

> Hi all,
> 
> It seems I haven't been able to reproduce the problem. What is the
> time zone you are using?
> 
> I set Service Window on a receive location, change system to use
> Pacific time and select 'Automatically adjust clock for daylight
> saving changes'. Then I set date time to 1:59:55 AM, Oct 30 . After
> few secs, the clock is adjusted to 1:0:0 AM. However the time span in
> Service Window hasn't been changed at all.
> 
> Our BizTalk SDE has ever confirmed they performed many tests on
> daylight saving. The time saved in database is in local time, which
> shouldn't be affected.
> 
> So could you please provide me with detailed info to reproduce the
> symptom you met? Thanks.
> 
> Best regards,
> 
> WenJun Zhang
> Microsoft Online Partner Support
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> 

[ Post a follow-up to this message ]

Just to add a little more information - if you look at the BTXTimer message
for the delay (or at least when I did) - it had the correct Timestamp (in
UTC) for the delay.

My computer (from DateTime.UtcNow) reported the correct UTC time.

SQL Server also reported the correct UTC time.

The only thing I can assume is that the code that kicks the BTXTimer back
off to the Orchestration has started doing its date time comparison wrong
after switching back to standard time.


Jon Flanders [MVP]
http://www.masteringbiztalk.com
[vbcol=seagreen]
> Hi WenJun - I was able to reproduct it with a simple project.
>
> Here is the string that I sent in  - <string>foo</string>
>
> Here is the string I got out -
> <?xml version="1.0" encoding="utf-8"?>
> <string>11/2/2005 9:08:13 PM start:11/2/2005 10:08:45 PM end:</string>
> If you notice - the delay was set to 30 seconds in the Orch - but came
> out to an hour and 30 seconds.
>
> This is BizTalk 2006 beta 1 and SQL 2000
>
> Jon Flanders [MVP]
> http://www.masteringbiztalk.com 

[ Post a follow-up to this message ]

Hi Jon,

I've seen the problem, but the result is different than yours. (Maybe the
difference is on time zone. I use Oct 30, 1:59:55 AM Pacific Time to do the
test.)

The behavior I saw is the output file thrown out immediately without 30
secs delay when the timespan is cross the daylight saving. Maybe there is
problem on the timespan calculation.

I'll report this issue to our internal to be discussed. Please wait for my
update.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.

[ Post a follow-up to this message ]

Hi Jon,

I just got update from our SDE. The issue is fixed in the next Beta 2 build.

Thanks very much for reporting this!

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.

[ Post a follow-up to this message ]