DateTime issue about pswindocumentation.o365healthservice

[PrzemyslawKlys]

Ok, it seems MS guys changed the date format. It's like they type this stuff manually. I have some working concept. will publish soon after few more tests on the date format.

[Raipel]

It worked after the module Update ! Thanks a lot!

[PrzemyslawKlys]

Can you let me know which tenant location you have? I've tested on Europe one.

[harleykin]

I'm in United States and am seeing this.

[PrzemyslawKlys]

Ok figures. Most likely dates behave differently in US then those I have in my tenant. I'll make a test with two other tenants. I believe I have at least one in the US.

[Raipel]

I'm in Europe and see it, too.

[PrzemyslawKlys]

Right, Ok, guys. Hold on. Will test this with 3 other tenants I have.

[PrzemyslawKlys]

Please try:

Update-Module PSWinDocumentation.O365HealthService

Run it and let me know the results. I've added a warning so that if the format of date will be wrong, or DateTime conversion fails it will show it like:

 Write-Warning "ConvertFrom-UTCTime - couldn't convert time. Please report on GitHub - $Time. Skipping conversion..."

If that happens please give me information what does it says, so I can address this. It shouldn't crash thou so data should be readable.

[PookyBeer]

We are seeing this issue in Australia:
WARNING: ConvertFrom-UTCTime - couldn't convert time. Please report on GitHub - 9/29/2021 6:00:00 AM. Skipping conversion...
WARNING: ConvertFrom-UTCTime - couldn't convert time. Please report on GitHub - Tuesday, May 25, 2021, at 7:00 PM UTC unless our continued investigation identifies additional information. Skipping conversion...
WARNING: ConvertFrom-UTCTime - couldn't convert time. Please report on GitHub - Friday, May 14th, 2021, at 12:00 AM UTC.. Skipping conversion...
WARNING: ConvertFrom-UTCTime - couldn't convert time. Please report on GitHub - Friday, May 14th, 2021, at 12:00 AM UTC.. Skipping conversion...
WARNING: ConvertFrom-UTCTime - couldn't convert time. Please report on GitHub - Friday, May 14th, 2021, at 12:00 AM UTC.. Skipping conversion...
WARNING: ConvertFrom-UTCTime - couldn't convert time. Please report on GitHub - Friday, May 14th, 2021, at 12:00 AM UTC.. Skipping conversion...
WARNING: ConvertFrom-UTCTime - couldn't convert time. Please report on GitHub - Friday, May 14th, 2021, at 12:00 AM UTC. Skipping conversion...
WARNING: ConvertFrom-UTCTime - couldn't convert time. Please report on GitHub - Friday, May 14th, 2021, at 12:00 AM UTC. Skipping conversion...
WARNING: ConvertFrom-UTCTime - couldn't convert time. Please report on GitHub - Friday, May 14th, 2021, at 12:00 AM UTC. Skipping conversion...

[PookyBeer]

FWIW, I updated my copy of ConvertFrom-UTCTime to have this:
$NewTime = ($Time -replace ", at" -replace "UTC.*" -replace "at" -replace "(^.+?,)" -replace "th" -replace "st" -replace "nd").Trim()
If ($NewTime -match "/")
{
Try {[DateTime]$ConvertedTime = {[DateTime]::Parse($NewTime,([Globalization.CultureInfo]::CreateSpecificCulture('en-US')))}}

Of course, MS will undoubtedly keep putting in all manner of stupid dates, but....

[PookyBeer]

Just another note. Replace also needed -replace "Augu","August" at the end. I'm sure it could be done cleaner & smarter with a regex, but just did a quick and dirty.

[PrzemyslawKlys]

Does this affect everyone or just Australia?

[PookyBeer]

No idea, but I would suspect everyone. If you plug in the dates that popped up in my original error, you'll be able to check them against your time zone. The first one (that has the date in US format), would affect anyone not in the US I imagine. _Wendy_ 19 Oct 2021 5:37:48 pm Przemysław Kłys ***@***.***>:

…

Does this affect everyone or just Australia? — You are receiving this because you commented. Reply to this email directly, view it on GitHub[#2 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AQ2XRGI4L3HZWS25K62PHXLUHUG3VANCNFSM4HJ2SA6Q]. Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub]. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAD8AAAA/CAYAAABXXxDfAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAmSURBVGiB7cEBDQAAAMKg909tDwcUAAAAAAAAAAAAAAAAAAAAJwY+QwABivJx1AAAAABJRU5ErkJggg==###24x24:true###][Tracking image][https://github.com/notifications/beacon/AQ2XRGMYYPOQ2K2ZOJADHA3UHUG3VA5CNFSM4HJ2SA62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHBURALQ.gif]

[PrzemyslawKlys]

Ye, I guess that's what you get when you push dates manually as you enter them.

[PrzemyslawKlys]

Not a big deal anymore. Rewritten using graph, where most of the dates should be correct with only a problem on when parsing incident post messages - as this is still text parsing.