Comments
-
OK thank you
-
The TCP 17778 VMAN -> NPM ok In the attached image VM2.png is demonstrated Virtualization tab. Error "status is unknown"
-
Update version Solarwinds
-
Is no problem connecting to the server. It is displayed in the error log of the Mobile Admin server. Socket Connect Exception The handshake failed due to an unexpected packet format It is also presented ssl error in the browser.
-
No firewall. Connection Test made the internal network https: // IP: 4055 and does not open. When I tried to access http: // IP: 4054 functions normally.
-
@harrisa94 By the analysis I did using NPM 12.1 demonstrated by the attached images, I identified in principle that data collected through the Custom Node Poller (UDP) does not provide the information of Last Change in the same way as for information of Nodes. The Last Change information for Custom Node Poller (UDP) is…
-
The system is functioning normally on both servers VMAN and NPM
-
thank you I will test a version below Additional WEB
-
The files listed are not old
-
It worked Thank you
-
<iframe src="http://x.x.x.x:8080/Orion/GoogleMap/GoogleMap.aspx?maptype=TERRAIN&radar=true&state=TX" width="100%" frameborder=0 height=600 scrolling=no align=center></iframe>
-
On the database connection, define IP
-
Erro Custom HTML
-
NPM 11.5 Error: Could not determine the server's DNS address.
-
NPM 11.5 Could not determine the server's DNS address.
-
Port TCP alter. In use. Resolved.
-
-Open Orion Service Manager and stop all services -Click Control Panel > Programs and Features, and uninstall the following: -SolarWinds Job Engine v1 -SolarWinds Job Engine v2 -SolarWinds Collector -SolarWinds Information Service -Navigate to C:\ProgramData\Solarwinds\Installers -Run the following msi files:…
-
Firewall rules
-
NCM migrate
-
VM template in the virtual environment was being presented with the VMAN error logs. Made exclusion of this VM in the virtual environment and reconnection of VMAN.
-
They are being used
-
Atualizando a versão do Orion de 10.7 para 11.5.2 resolveu problema.
-
Quando retira-se um relatório da pasta, o relatório nem abre, é apresentado o erro abaixo ao tentar abri-lo:
-
Ele está na pasta. Pelo acesso web, o relatório funciona normalmente, se executar uma consulta SQL custom também usando a query deste mesmo relatório pelo Report Writer funciona. Apenas pelo Report Writer que todas as fields que eram Custom Properties aparecem agora com *, e a aba Custom Properties mostrada na imagem…
-
I'm not sure of how to create reports. I'm with custom properties of problem disappear in Report Writer, the Custom Properties tab, just do not apacere more.
-
There was no server change and also there was no change in any setting.
-
Download CustomLabels_pt_BR