Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

System-generated Calendar Requests Have the Incorrect Date+Time

Version: 12.7.13

OS: Rocky Linux 8.8

Linux is synced to NTP via timedatectl.

Whenever I've tried to set a Scheduled Date in the Status & Schedule section of a ticket, the calendar request that gets sent from WHD to Outlook always has the incorrect date and time. For example, I set the Scheduled Date of a ticket as 11/24/23 11:00 AM to 11/24/23 12:00 PM but the calendar request sent by WHD has 11/23/2023 11:30 PM to 11/24/2023 12:30 AM. Any ideas why this is incorrect in Outlook?

Find more posts tagged with

Accepted answers

All comments

pabely

This sounds like something I already have with Support and they advised upgrading to the WHD12.8 release.

Avadhut.Deshpande

This issue fixed in WHD 12.8...please check

slips121

I have planned to upgrade to 12.8 this Friday (11/24/2023) and will report back to see if it is resolved. Thanks.

slips121

I upgraded our instance to 12.8.0 (Build #12.8.0.332) and now when I set a Scheduled Date for a ticket, the calendar invite subject is appended with null and the calendar .ics object received is not supported by Outlook (it's literally named "not supported calendar message.ics").

Sent: Monday, November 27, 2023 8:54 AM
Subject: Calendar Request for Ticket#47892, null

This is System generated email. Please do not reply or send meeting response on this mail id.

Avadhut.Deshpande

Hi, Can you raise ticket technicalsupport@soalrwinds.com .Will look into it.

slips121

I've sent an email in with details, thanks.

slips121

Technical support ended up creating two support cases for me, one for the incorrect times and one for broken .ics objects. They replied saying it's currently bugged and that the next release will fix both issues hopefully.