APM script datediff returning different results from time to time

Hi,

I have opened case#260905 as one of our custom script monitors keeps failing, it has been closed already as solarwinds does not offer support for customizations.

I have pinned down the problem to a comparison of dates:

tDiff = DateDiff("n", CDate(Month(Yesterday)&"/1"&"/"&Year(Yesterday)), CDate(Month(Yesterday)+1&"/1"&"/"&Year(Yesterday)))

This sometimes converts to the difference in minutes for one day and sometimes for the whole month (which is what we want).

If I let this run in a loop in a script on the server, this error never appears.

I am assuming, that for some reason the date sometimes gets evaluated as MM/DD/YYYY and sometimes as DD/MM/YYYY.

I have already modified language/regional settings to US even for system accounts but that does not seem to work either.

Does anyone have an idea what could be causing this issue or how to fix it?

Find more posts tagged with

script_monitor

regional

time

datediff

date

vbscript

language

settings

Accepted answers

FormerMember

Why not use YYYY-MM-DD to avoid all confusion?

tDiff = DateDiff("n", CDate(Year(Yesterday) & "-" & Month(Yesterday) & "-01"), CDate(Year(Yesterday) & "-" & Month(Yesterday)+1 & "-01"))

Works out as 44640 for this month when I run it.

Edit: On a side note, wouldn't you run into issues when Month = 12? It'd try and convert the 13th Month

All comments

FormerMember

Why not use YYYY-MM-DD to avoid all confusion?

tDiff = DateDiff("n", CDate(Year(Yesterday) & "-" & Month(Yesterday) & "-01"), CDate(Year(Yesterday) & "-" & Month(Yesterday)+1 & "-01"))

Works out as 44640 for this month when I run it.

Edit: On a side note, wouldn't you run into issues when Month = 12? It'd try and convert the 13th Month

Bronx

Will investigate.

Questionario

this seemed to have solved the issue occurring at 12AM/PM :-)

PS: I have a If then else implemented, if month = 12 then year+1 and month =1, the script hasnt passed a year-turnover yet though

Thanks, lets hope APM 4.2 is better (isnt it always? ) and will come out soon.

Questionario

Hi Bronx,

you first wrote:

There is a known issue in APM 4.0.2 that dates do not follow regional settings consistently; however, this issue has been corrected in the upcoming APM 4.2 release.

what has changed your mind and what exactly do you plan to investigate? :-)

Bronx

I think I was wrong with the information I posted earlier. That's what I need to verify.

Questionario

looking forward to it

if it will take a while to verify would you mind telling which part you will verify?

that there is a known issue in apm4.0.2 or that this has been corrected in apm 4.2?