Comments
-
@"Jugabor" Does the workaround posted by @"bobmarley" help? If not, then it is likely a different problem that we may need to diagnosis. The general feedback has been the workaround has been working. If you have an open case, please feel free to share and we will fast track to make sure the issue is resolved properly.
-
@"dduffy456" If you can share the case number, we can expedite and confirm if it is the same known issue. Currently, the workaround is stated in the release notes and we are working towards a fixed in a future release.
-
Thank you for all of the feedback. The workaround was added to the known issues list until we have a permanent fix: https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/solarwinds_platform_2023-3_release_notes.htm
-
@"Murrphy" If you have a case number, please share so we can help root cause the issue. We are evaluating to ensure this issue is properly resolved.
-
This is great to hear! We will make sure to have this issue added to the Fixed Issues list for 2023.3 release notes.
-
Agreed. This is the default setting from the SolarWinds side. It is possible that Microsoft made a change to no longer accept this type of context-type. There are a few other cases stating same or similar behavior, but we are looking to see if we can make it easier to set this by default when configuring for Microsoft…
-
Check to see what the content type is set to. We had a few customer state that changing the context type to "application/json" resolve the issue. We are still digging into why the change resolves the problem.
-
@"Singh7081" Please PM the case number and we can help fast track the issue.
-
Is the Job Engine log fairly empty? There are a few reported instances where Job Engine services is taking longer than 30 seconds to start. If so, the Windows Service will timeout.
-
This should be addressed in the 2023.3 release, but we can check the logs to make sure the issue is properly identified. If so, there should be a workaround we can apply. Please PM the case number and we can check.
-
If you have a case number, please share. We will look into the log to see if we can find the problem.
-
Thank you to @"sadiqsul" for pointing the the problem javascript. We found the same problem in our lab and confirmed the MapQuest Demo Site was failing as well. It does appear Mapquest did resolve this issue. Here is a mapquest url to test if interested: developer.mapquest.com/.../
-
Running the offline on the main poller should resolve the issue, then you'll have the option to upgrade the other pollers within the UI.
-
We will provide a NTA clean up tool which should help.
-
It is likely a database clean up that is needed to upgraded to 2022.3. If there are older DB tables entries from previous installation that may no longer used, then this cause problems during the upgrade to 2022.3. Can you please provide the case number so we can take a deeper review of the logs you've provided?
-
There are two different scenarios to considered for Azure groups: * Groups created directly in Azure AD * Groups which are synced from On-Premise AD using Azure AD Connect The information is based off of the Microsoft documentation…
-
This should be related to missing the root certificate. I ran the same commands and found it does a generic update of all root certificates (which is good in general). Here is a KB article which specifically points to what certificate authority is being used for the current releases today.…
-
There is a Powershell script issue in 2020.2.5 that is documented in the following KB: support.solarwinds.com/.../Custom-PowerShell-monitors-in-SAM-stop-working-after-upgrading-to-SAM-2020-2-5
