Kita · Senior Director · ✭✭✭✭

I am interested to hear if others are having similar problems.Disabling and enabling polling resolved the issue. Within the VIM Collector logs, there were signs of the following error message: https://support.solarwinds.com/SuccessCenter/s/article/Unable-to-poll-server-through-WMI-due-to-DNS-records.

You should have ProgramData as it is a standard Windows director. It is usually a hidden folder by default so you might have to show hidden folder or manually type it in to see it.

It should be in C:\ProgramData\SolarWinds\Logs\Orion\BusinessLayerHost.log. If running the CW fixed the issue, it is likely a bug that we need to identify and fix. Please open a support case so we can analyze the logs. If you are willing to share the case number, please post or DM me. Thank you.

If the license store is inaccessible, then this is a different problem. Here is the article: https://support.solarwinds.com/SuccessCenter/s/article/License-Manager-error-The-License-Store-is-inaccessible-Restore-connectivity-to-Main-Poller-Pollername-in-order-to-view-or-add-Licenses. I would start with reviewing the…

You'll want to confirm if the Menu Failure is due to NotificationItemsGrouped. If the message states a different problematic query, then it is a different problem. From what we've seen from many customers, clearing the NotificationItems table will temporarily resolve the problem.

The latest information about the issue, workaround and planned fix is available at: https://support.solarwinds.com/SuccessCenter/s/article/Menu-Failure-2023

@"hpstech" Within the file, it will contain a string. At the end of the string, it will contain";multisubnetfailover=True". In most cases, switching it to false will "fix" the problem. We are still trying to better understand why in some environment setting this to true is causing problems.

Sorry to hear about the rebuild @"hutcha4113" . If you don't mind sharing the case number, we will dig into the logs to see if we can get to a root cause.

@"wayne1022d" Please provide the case number. We will investigate so we can provide the proper guidance.

The upgrade from 2020.2.6 is usually the most challenging. NTA and LA database are required after 2020.2.6 which was not the case in previous releases. You'll want to make sure you have access to create the database tables (especially if you have a separate DBA that manages the permissions).

Sure. Repair may fix it temporary, but the RunQuery is likely a symptom of a bigger problem. The error is usually signs that SWIS is timing out due to other conditions.

Please share a case number. RunQuery is a generic error so we likely need to review the logs to see the context around the error message

This may be related to the following issue: https://support.solarwinds.com/SuccessCenter/s/article/After-upgrade-to-2024-1-I-can-no-longer-create-Infoblox-BIND-DNS-High-Availability-pool.

Appreciate the feedback @"bmg4357" . We are discussing this internally on how we can help prevent this problem. Hopefully more to share in the future.

@"danbert" The fix in 2024.2.1 is to address the split brain issue. We will dig into why the false positive are occurring

@"danbert" If you can share the case number, we can help validate the issue. There are several customer running into this issue in 2024.2 and uncovered a potential fix for these scenarios in 2024.2.1. This was added to the release notes as well.

@"ctech291" Good question. RequestTimeout is referring to the request sent by the ApiPoller. PollingTimeout is referring to timeout of the jobengine job. I don't think i've had to modified this setting before, but I could see this could be useful if the job itself is taking longer than 60 seconds to complete.

There is a import maps option available in SolarWinds Platform 2024.2 with improvements and fixes: https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/solarwinds_platform_2024-2_release_notes.htm

 @"cristian.bal" I was able to find your case. We will share the clean up script to resolve the immediate problem. This is a bug that we are planning on fixing in the upcoming release.

@"m-milligan" Thank you for the feedback. the 150 limit is stated the following document, but we will add the details about the "filter groups"

@"martian_monster" We are aware of the following issue and working towards a perm fix. You are spot on with the workaround.

@"taylola2010" If you have a support ticket open, please share. We would like to investigate the logs to see if we can get to the bottom of this problem.

Thank you for the feedback @"dmccoy66" and @"MannyC" . We will update the article to share the learning with others. We will continue to work internally to see if we can resolve this without having to apply the workaround.

These are all good points @"paulocruz" . If the Machine Type is incorrect, then the MIB database will not help. If Machine Type are incorrect, please open a support ticket so we can help get this resolved properly.

Agreed with @"brscott" . The grouping is determined by the machine type that is found during discovery phase. This should be properly detected via SNMP. I did a bit of searching and found a few older cases where others were stating the issue was resolved by assigning and unassigning the SAM template. If possible, please…

The following article may help: https://support.solarwinds.com/SuccessCenter/s/article/Configuration-Wizard-Error-Can-not-connect-to-the-SQL-Server-The-original-error-is-The-requested-operation-cannot-be-completed-The-computer-must-be-trusted-for-delegation-and-the-current-user-account-must-be-configured-to-allow-delegation

 @"jameslindsay" Please share the support case so we came see if get this reviewed.

@"Rolfey83" I tried this in the lab and have a different error. In the following path, there should be a log: C:\Program Files (x86)\SolarWinds\NCMSAConnector\NCMSAConnector.log. Does it give more context about the message?

@"MannyC" This is great information. I believe this might be related to the article so the bug is related to original data saved for the node may have the previous certificate details of the PAN device. If/when this does change, the warning state to accept the certificate, but it does not actually save this information…

@"MannyC" This should work in product. If someone is able to provide a case number, we can continue to try get this properly resolved for all.