This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Does anyone use Windows server 2022 as a monitoring server for SQL Sentry without any problems?

Getting always following error.

Windows]: SQL?????.CCREK.BE
[Message]: Error synchronizing history for event source: SQL?????.CCREK.BE: Windows Event Log An error has occurred:
Message: We do not have 18 variants given for the UnsafeNativeMethods.EvtRenderFlags.EvtRenderEventValues flag. (System Properties)

System.InvalidOperationException: We do not have 18 variants given for the UnsafeNativeMethods.EvtRenderFlags.EvtRenderEventValues flag. (System Properties)
at System.Diagnostics.Eventing.Reader.NativeWrapper.EvtRenderBufferWithContextSystem(EventLogHandle contextHandle, EventLogHandle eventHandle, EvtRenderFlags flag, SystemProperties systemProperties, Int32 SYSTEM_PROPERTY_COUNT)
at System.Diagnostics.Eventing.Reader.EventLogRecord.PrepareSystemData()
at System.Diagnostics.Eventing.Reader.EventLogRecord.get_RecordId()
at Intercerve.SqlSentry.Providers.WindowsEventLogEventSourceTypeSynchronizer.TranslateHistoryDataMasterInternal(Object sourceObject, EventSourceAccessor eventSource, EventSourceConnectionAccessor eventSourceConnection)
at Intercerve.SqlSentry.Providers.WindowsEventLogHistorySynchronizer.ProcessDataRow(EventRecord eventRecord, Func`2 cutoffPredicate, EventSourceAccessor eventSource, EventSourceConnectionAccessor eventSourceConnection, TimeSpanOffsets serverTimeSpanOffsets, ICriteriaOperator criteriaOperator, RemoteSequenceOffset remoteSequenceOffset)
at Intercerve.SqlSentry.Providers.WindowsEventLogHistorySynchronizer.SynchronizeHistory(EventSourceConnectionBase eventSourceConnection, EventSourceAccessor eventSource)
at Intercerve.SqlSentry.Providers.EventSourceSynchronizer.SynchronizeHistory(Nullable`1 managementEngineID, EventManagerWatchTask eventManagerWatchTask)
at SqlSentry.Server.EventHistoryMonitor.SynchronizeHistory(WorkQueueItem`1 workQueueItem)
----------------------------------------------------------------------
[Timestamp (Local)]: 20/04/2022 15:24:33 [Timestamp (UTC)]: 20/04/2022 13:24:33 [Generated By]: SolarWinds SQL Sentry 2021.18 Server [????21]
[Version]: 2021.18.8.31174
[Monitor Type]: EventHistoryMonitor
[Condition]: Event History Monitor: Error [Response Ruleset]: Notify Every Time (default) Debugging Information:
[Response Ruleset Definition]:
Start Sending Notifications After 1 occurrence within 00:00:01 [First Occurrence (UTC)]: 20/04/2022 13:24:33 [Last Occurrence (UTC)]: 20/04/2022 13:24:33 [Total Count]: 1 [First Message Sent Count]: 0 [First Message Sent (UTC)]: 20/04/2022 13:24:33 [Last Message Sent Count]: 0 [Last Message Sent (UTC)]: 20/04/2022 13:24:33 [Configured Object Name]: Global [Configured Object Type]: Global

Parents
  • I just deployed SQL Sentry and am constantly getting bombarded with this. It does not look like the Failsafe Condition is working since this error is still getting logged in the database. My monitoring service is on Windows Server 2022 while the SQL instance I'm monitoring is on 2016. This is a fresh Windows Server installation and is up to date. Any guidance would be appreciated.

Reply
  • I just deployed SQL Sentry and am constantly getting bombarded with this. It does not look like the Failsafe Condition is working since this error is still getting logged in the database. My monitoring service is on Windows Server 2022 while the SQL instance I'm monitoring is on 2016. This is a fresh Windows Server installation and is up to date. Any guidance would be appreciated.

Children
No Data