kishore574

Can you change the port number 80 to 443 and test it. Please let me know

Yes, we are also facing the same issue. We enabled the Orion Log Management Syslog after that memory utilization showing 95% huge but it will take time to increase the memory utilization. we raised the case with vendor. they suggested need to improve the RAM size in main server. after that still showing the same. but we…

thank you. we are bale to see the hardware heath in wbemtest correct. Could you please advise on this one. is it reinstalled the wbemagent in client server end. is this helpful

Hi, We faced the same errors in my environment. we did a same processor restarted the services and rebooted all polling engines alsoBut still issue there.we follow the below troubleshooting for deployment health errors . Please test one of the polling engine your environment and test it. > Please stop the all McAfee…

Presently we created the auto discovery profiles manually. I Mean devices assigned manually to Discovery profile. sorry to forget inform to you above script not opening from my end. we tired to given the range also. 

Hi @"familyofcrowes" we are facing the same issue. Solariwnds.orion.logMgmt.trap service causing the memory leakage in All solariwnds servers. is it issue fixed. Please let me know. presently Current Environment is 20202.2.5 version. Regards

Hi Ashwin, we don't have node caption option attribute not available in database query. so we have to given only Entity caption in database. i think Particular device for alert history report not aware. Thanks

Please find the updated query details. Name of alert act as Node Name. select aa.[timestamp] as TriggeredDateTime , aa.message,ac.severity, (CASE aa.eventtype WHEN 0 then 'Triggered' WHEN 1 THEN 'Reset' WHEN 2 THEN 'Acknowledged' WHEN 3 THEN 'Note Added' WHEN 4 THEN 'Added to Incident' WHEN 5 THEN 'Action Failed' WHEN 6…

Looks Like the second error your orion server doesn't communicate with database due to that reason you faced that error . we faced also same error in my environment . Try to follow that. > kindly check the ports opend or not from orion server to database ( if any chance) > kindly check the are you able to login to the…

Create the web based report using the below script. you will get the required report and let me know. select aa.[timestamp] as TriggeredDateTime , aa.message,ac.severity, (CASE aa.eventtype WHEN 0 then 'Triggered' WHEN 1 THEN 'Reset' WHEN 2 THEN 'Acknowledged' WHEN 3 THEN 'Note Added' WHEN 4 THEN 'Added to Incident' WHEN 5…

Are you looking for like this Ashwin. we have time stamp also available for requried alerts report. 

Hi Dc4networks, We have identified the below error in Check database maintain works daily. is this below path file can we copy from C drive to D drive. is this correct way. after that database maintains works properly or not. Please confirm. C:\Program Files (x86)\SolarWinds\Orion\LogAdjuster.exe did not finish…

Thank you @"faizan_123" for you response. do we have any another method for enabling auto discovery with scripting. Could you please help me on this one. 

we used the same component for monitoring the linux devices path. did you provide the permission to credentials in component.

Hey Aswani, I think below query helpful to you. select aa.[timestamp] as TriggeredDateTime , aa.message,ac.severity, (CASE aa.eventtype WHEN 0 then 'Triggered' WHEN 1 THEN 'Reset' WHEN 2 THEN 'Acknowledged' WHEN 3 THEN 'Note Added' WHEN 4 THEN 'Added to Incident' WHEN 5 THEN 'Action Failed' WHEN 6 THEN 'Action Succeeded'…

Yes Correct this job is good. looks like we are able to see the all application credentials in console. Thanks Joeshmoe. 

Hi Joe, We can create a report for which node monitoring with service account. Kindly create a report used the below SQL query. Please find the below details. you can easily identified the service accounts. Select Nodes.IP_Address, Nodes.Caption, Nodes.Domain_name, Nodes.Node_type, Nodes.status, Credential.Name from…

Hi, We have identified the below error in Check database maintain works daily. is this below path file can we copy from C drive to D drive. is this correct method. after that database maitains works properly or not. Please confirm. C:\Program Files (x86)\SolarWinds\Orion\LogAdjuster.exe did not finish successfully....

Yes, your are correct@"Jfrazier" we added the device with SNMP polling method in monitoring tool. if any device having issue with SNMP support team restarted the SNMP or they will remove the old community strings and add the new one. usually we received the node reboot the alert from solariwnds. we faced these type of…

Thank you Mcam actually in that case we have identified the different OID's available in device Browser. Do we have any Single unique OID for network devices Uptime. Please suggested. 

@@"bharris1" No, still error showing in console. we checked with multiple times and finally opend case with vendor they suggested check with Your SQL Team. still i am seeking solution for this one. our database maintenance happend every day 

Thanks For update. we tired with this OID(1.3.6.1.2.1.1.3) but it is showing exact time some of network devices. could you advise on the network devices for Sys uptime OID. Regards, Krish.

Thanks Martain. This video is helpful to me. 

Thanks for update. can we use the old widgets to create Custom dashboard. If yes, Please let me know. if you have any other related documents or KB articles. please provide to me. I will create and update the post here

Hi Ankur, Still issue persistence. not able to see the any performance issues. do you have any solution for this one. please let me know. 

Still these errors are there or vanished. please let me know. 

Actually we have fragmentation scheduler available. it is daily running. Please find the below error message for the check database maintenance. "FileCleaner: An Error has occured during the log files clean proccess. The file is being used..."

Yes, we are monitoring the Cisco Access points. Could you explain the how to work the Wirless controller in Solarwinds. 

Yes, very day database Maintenance executing at 2:15 AM. but still showing the deployment health error. 

i tried with this wbemtest also but Volumes are showing fine in this results but still showing the unknown servers Volumes