I have several receive locations of type schedule in a BizTalk 2016 server. All except one work fine. This one has been getting triggered as defined in the schedule daily at 04:00 am, however it suddenly began to start at 05:00 pm and one day it didn´t run.
There is no Error Log in the Application Logs or the SQL Logs. The Receive Location is enabled. The Server Time is correct.
Does anyone has a hint, what this behavior might be caused by?
BTS 2016
Scheduled Task Adapter 6.0.0.6
The current version is 7.0.2. and that includes some fixes
e.g.
In certain cases task won't trigger in set time with Timespan with Biztalk 2016
Timly Schedule Start Time (and Date) doest not work correct
So I would suggest downloading and installing 7.0.2.
I experienced a similar behavior when the Host Instance is shared and sometimes overloaded. Try to dedicate a HI for scheduling only. And as suggested by #Dijkgraaf, you can use the last version of this Adapter
Related
I currently have two custom tasks in my Task Scheduler which have nearly the same trigger configured except one is executing 15 minutes after the other one
As you can see in the image above, one of the Tasks, was executed 1 DAY earlier than it should have.
In the history I can see that it says that its executed due to scheduler, but that's actually not true because there is only one trigger configured like this:
as you see below, it executes also on the first as it is in the scheduler, last month i also had the problem that it was executed one day earlier, i reconfigured everything and now i have the same problem again, probably its going to execute tomorrow also.
these are my other settings:
the tasks are running on a 2016 Server 1607
Does anybody know about any issues with monthly schedules?
i saw that in the 2019 Server there is a problem that on monthly tasks the tasks probably wont execute at all.
so this seems to be an issue inside Windows 2016 Build 1607.
I changed the time so it does not execute on 02:00 to 02:05AM and the task executed correctly.
I don't know why this is an issue or if only 02:00 is bugged but we opend an issue at microsoft for this.
I have multiple scheduled jobs on a windows Server that run every night starting at 9 PM till midnight.
Is there any programmatic way (C#) to read (export) the Logs/History of each scheduled task and save it to SQL Server or as a text file within the server.
We are tying to show that data on a dashboard.
Thank You
I have researched on this issue and found a solution that worked for me. Created a sample project and is on GitHub.
Please check it out GetTaskSchedulerHistory
Thank You
Following problem:
I have a Yesod web app that is connected to a Postgres database (everything is hosted on AWS Elastic Beanstalk).
My customer wants to define a schedule (day, hour, ...) for things to happen automatically (e.g. sending out a message). E.g.: "every wednesday message A will be sent at 02:00 PM, but does not get sent after 03:00 PM if the server was down in that period". The definition could be saved to a text file on S3 for example.
One lib I found was https://hackage.haskell.org/package/cron which could be used as a basis for my needs with a caveat: if the server is shut down in that particular minute in which a job would be triggered, the message would not be sent when the server is back.
I used DelayedJob (Ruby) in the past and there the scheduled jobs were stored in a database to circumvent this issue. But in Haskell I could only find solutions without database persistence.
Is there anything to look into for Haskell or do I have to build that on my own e.g. use something like http://jdabbs.com/resquing-yesod/ as a starting point)?
I provide support for a large application across multiple servers. System has been running live for 6+ months.
8th December: total system failure. iisreset across each of the servers sorted it out. Everything back to normal.
Post failure investigation showed various processes not able to get a response from a particular server which hosts an instance of Dynamics CRM (2011 R11). Specifically it seems the SOAP service was not responding (Organization.svc). 503 - Server Unavailable (really it was just the web service). I suspect it died.
Having the exact time of the error I checked the event logs on the server but these did not have anything of use. The last error prior to the failure was a report rendering error which was 9 minutes before the system actually went down. Surely if web service crashed this would be reflected in the event log?
Fast forward to today, 8th January and the system fails again. The 8th of the month again! iisreset fixes it... again!
Again, completely useless event logs showings no errors prior to failure.
Entertained the idea of Dynamics CRM trace logging but this is out of the question due to the performance hit.
Apart from the event logs where else to look? Are there possible external factors or causes? I'm trying to find the root cause but have run out of ideas!
While this may not address the source of your problem, maybe it can help minimize the symptoms. May I suggest that you configure the IIS server to recycle the application pool at a scheduled interval within your production environment.
http://technet.microsoft.com/en-us/library/cc753179%28v=ws.10%29.aspx
I'm using a Raspberry Pi, and upon startup it's sending an e-mail with the time and an IP address. The problem is that the time is not correct, it's the time from last time the system was shut down. When I log in through ssh and do a date command, I get the correct time. In other words, the e-mail is sent before the system has updated its time.
I was thinking of automatically running ntpdate on boot, but after reading up on it it seems like a bad idea due to the many risks of error.
So, can I somehow wait until the time has been uppdated before continuing in a script?
There is a tool included in the ntp reference implementation for this very purpose. The utility has a rather cryptic name: ntp-wait. Five minutes with the man page and you will be all set.