Using TFS 2017 Update 2, we notice that we sometimes get some email notification double, with a lot of time (30 minutes) between them.
We are not using distributions lists, users are added to TFS Teams directly.
When checking the View link in the bottom, its shows the same ID for all duplicate emails, so its the same alert triggering it.
A concrete example
Build completed at 11:18 AM. We received an identical notification at 11:37, 11:53 and 12:09.
First issue is already that there is 20 minutes between the completion of the build and the sent of the first message.
What part of TFS should i troubleshoot here, we have noticed before that email alerts are received later then expected.
So we have 2 issues, which might be related
1. Emails arrive up to 30 minutes later than expected
2. Identical Emails sometimes are received 2/3 times.
Update, issue came back.
Technical Details:
Build Ran for 15.3 minutes (Default), completed at Fri 12/01/2017 01:48 PM
1st email header:
Received: from TFSAPPSERVER (ip) by smtphost.domain.com
(ip address) with Microsoft SMTP Server id 14.3.319.2; Fri, 1 Dec 2017
07:50:34 -0600 ( 01:50 PM tranlated to same time above)
2nd email header:
Received: from TFSAPPSERVER (ip) by smtphost.domain.com
(ip address) with Microsoft SMTP Server id 14.3.319.2; Fri, 1 Dec 2017
08:26:37 -0600 ( 02:26 PM tranlated to same time above)
In this thread there is a solution from Microsoft:
The root of our issue was that the SMTP server was not responding to TFS to indicate that the mail was sent within the timeout period. Thus the fix in our case was simply to increase the timeout that TFS waits before re-sending emails.
To do this, we ran the following in the TFS Configuration database to change the timeout from 10 seconds (the default) to 90 seconds:
exec prc_SetRegistryValue 1, '#\Service\Integration\Settings\SendTimeout\', 90000
Related
I am trying to do a remote tachograph authentication by sending a RemoteCompanyCardReady cantp message to a VDO tachograph on connector C.
The reply message I get is a nack 7f 31 7f which seems to suggest there is no open session. I can't seem to find anywhere how to open the diagnostic session to the tachograph. Also the can id I am using for sending the messages is 18DAEEFB, is that correct? Can anyone give me the byte sequence on the can bus for that?
If you are receiving a response from the device (7F 31 7F in your case), then the CAN ID seems to be correct.
The service which you are trying to send (0x31) seems to be a Routine Control service. Those services usually work in the Diagnostic Session.
According to the ISO, Session Control service is 0x10. So, try to send the request (10 03) to the device. If you receive a positive response (50 01 XX..) then send your required service immediately (within 5 seconds of receiving 50 01).
How would we do this with Twilio
We need to add code that allows messages / calls only to be sent from 9 am New York time to 9 pm New York time
message can be sent from 9:00am - 8:45 pm. (this will give a 15 minute buffer to clear out the queue
Message can not be sent from 8:46 pm til 8:59 am New York time
There are past blogs that take advantage of JavaScript libraries to help with routing based on date/time of day. You can also apply this to SMS response behavior.
Using Twilio Functions to Add Custom JavaScript Code in Studio Flows
I was writing a script to create and fill playlists on my channel yesterday ( using playlist.insert and playlistItems.insert) when i received a 403 response with this message:
"The request cannot be completed because you have exceeded your
\u003ca
href=\"/youtube/v3/getting-started#quota\"\u003equota\u003c/a\u003e"
I think this is really strange because when i check my quota at https://console.developers.google.com/apis/api/youtube.googleapis.com/quotas i'm way below my daily quota with only 32.554 queries (1 million is the daily limit). I decided to wait until midnight PST for my quota to reset but i still can't make requests.
Is there anything i can do to reset my quota?
I am using document db with my console application. I am able to access document db with my project running without any issue. But when I am running my console application with docker locally on windows as windows container its not able to access document db.
I am getting following error :
The authorization token is not valid at the current time. Please create
another token and retry (token start time: Mon, 12 Mar 2018 20:54:57 GMT,
token expiry time: Mon, 12 Mar 2018 21:09:57 GMT,
current server time: Mon, 12 Mar 2018 08:24:47 GMT).
ActivityId: a3e015e6-a4bb-47dc-bf24-c7ceacad317c,
Microsoft.Azure.Documents.Common/1.21.0.0, Windows/10.0.16299 documentdb-
netcore-sdk/1.8.1
It seems issue with time sync problem.
Please let me know if you need more details.
I faced the similar issue, and here is the reply from Microsoft
Cosmosdb authorization token is generated for a time period between Now – 1 minute to Now + 15 minutes. The -1 was to account for clock drift between client machines and servers (which are synchronized).
The fact that you’re seeing this error clearly shows that we should have allowed for a longer time window to account for real world clock drifts, and we will increase this to -5 minutes in an upcoming service release.
Meanwhile, a workaround that might help you is to adjust your machines time back by 2 minutes.
Adjusting my machine time back by 2 minutes fixed the problem and allowed me to access my Costmosdb account. Hopefully the permanent fix will be deployed soon.
Related Issue
I registered a local notification which will occur every day .But in my application we have a setting called out of office where the user can select his out of office period for a period .(example: From Nov 4 to Nov 10).In between these days i should not get the reminder.Is there any way to do this?