Kita · Senior Director · ✭✭✭✭✭

@"jagregorio019" If you have a support case, please share. The current workaround is to use the following option to force the native client: UPDATE WebSettings SET SettingValue='native' WHERE SettingName='ForcedSMTPClient'

More details can be found at: https://support.solarwinds.com/SuccessCenter/s/article/Unable-to-install-stored-procedures-for-driver-UpgradeCompatibilityLevel

This would be the correct approach. All resources (i.e. interfaces, volumes, etc) associated with the node is stored in the collector database. If the number of interfaces change, we would need to discover them via "list resources". Rediscovering the node should work as well, but this is a bit of overkill.

@"Nattapong.ng" We seen this a handful of times and could have multiple reasons. A potential workaround is to run the installer via command line with -notest switch: https://support.solarwinds.com/SuccessCenter/s/article/Orion-Installation-Stuck-on-System-Check

@"elizabeth.wairimu" I believe I found your case. The hostname of the poller has an underscore and the reason why it is being flagged as an invalid hostname. Underscore is not allowed. You'll want to remove the underscore from the hostname.

As long as it is bound to a port, it could be monitored using https://support.solarwinds.com/SuccessCenter/s/article/How-to-Monitor-an-SSL-Certificate-and-Create-an-Alert-in-SolarWinds-SAM-When-There-Are-X-Days-Before-Expiration.

@"GirbanG" We went back to test 2024.1 with an API Poller Credential and received the forbidden message. I am not sure if this worked at some point in time before so we will need to do more testing. The API Poller Credential should only be used for the API poller itself. The SWIS API should be using only the Web Console…

The bug reported with 0158917 was fixed in SolarWinds Platform 2024.2 and included in the release notes. For customers who are not upgrade can utilizing the workaround by using the legacy view documented in the following article.

Agreed. I am seeing the same behavior in my lab. I am using a local admin account that I've created under Manage Accounts with has admin privs. We are working on update the release notes and have a document KCS article to point out the same / similar error message. When using the older port of TCP port 17778, it is…

@"GirbanG" In 2024.2, the SWIS API port was officially moved from 17778 to 17774. If you are script is still utilizing 17778, you want to switch it to 17774 or use the workaround stated in the release…

@"pjd1213" Did the update to SolarWinds Platform 2024.2 resolve the issue? We have updated our 2024.2 release notes to ensure this is properly documented as a "fixed issue". 01559991, 01564082, 01571168, 01571561, 01580158, 01580981, 01600664, 01608819When a node is added to an existing Network Atlas map that is already…

These are all valid points @"ralphpost" . I'll have this discuss internally to see if we can make changes to our documentation to have this clearly stated. For the most part, I am glad that disabling STS has resolved the issue.

If it is related to the following issue, this is resolved in SolarWinds Platform 2024.1.1 and above.

@"stuartd" The upgrade to 2024.1.1 or 2024.2 should fix the issue. We've seen some customer still need to adjust the algorithm order as well. These steps are documented…

@"jroberts77" I am interested in the certificate issue. We did make some changes in the later version to make sure certificate binding are working properly. In the past release, we had issues where the binding would fail and caused a blank certificate bind scenario. This caused other problems. This could be related, but we…

@"jroberts77" There were several problems that appears across the two different set of logs. I'll try and summarize some of the symptoms/problems here, but we will want to open a new case to see if we can really get to the bottom of all of these issues. * SAM logs are flooded with WinRM errors. You'll want to refer to the…

@"jroberts77" If you don't mind, please share the case number. If we still have logs to review, we will try and get to the bottom of it. I have seen several other customers state similar behavior by changing polling engine. 

This issue should be resolved with the latest release. The following documentation on supported algorithm was updated: https://support.solarwinds.com/SuccessCenter/s/article/Supported-algorithms-and-cipher-for-NPM-and-NCM?language=en_US

@"TreyJ" Key all and Encryption list may still need to be manually override in some scenario even after the upgrade. Please refer to the following steps in the following…

@"rodolfomanrique" If you have a support case number, please let us know. Thank you for raising awareness of your experience.

@"pramod.paul.jose" It is updates files specific for the 2024.1. I found the case and asked to fast track to get the help you need.

If you are running 2024.1, buddy drop is available with some additional changes to the encryption and key sig order. Please feel free to open a support ticket and we can help validate the issue and apply the fix. More information is available…

@"pramod.paul.jose" We have a viable workaround with a buddy drop and some additional configuration changes. If you have a support case already open, we are reaching out to customers to help provide the solution. Here is the public documentation that outlines the steps once the the buddy drop has been…

@"adam.beedell" We are aware of the issue and working towards fixing the issue. https://support.solarwinds.com/SuccessCenter/s/article/Alert-Icons-are-broken-after-upgrading-to-2024-1

Starting in 2024.1, this option was added to the Advanced Settings: https://support.solarwinds.com/SuccessCenter/s/article/SAM-Powershell-not-working-after-2022-3-Upgrade?language=en_US

@"sshea" The uninstall will not remove data from the previous database. If data needs to be removed, you'll want to manually delete the database or truncate the specific tables. 

Thank you @"Jugabor" . If you have a case number to share, please let us know. We are reviewing with others if the issue is permanent resolved or not.

@"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