What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

PRTG Billing Tooll

Votes:

0

Your Vote:

Up

Down

I've installed PRTG Billing Tool on the server with the main PRTG installation and configured connection details under PRTG Server Connection details yet when I try to create a report i get an unhanded exception, i can continue though but no sensors are available in the drop down menu.

Has anyone had any experience of this? Have an explanation to the root cause?

billing-tool connection prtg

Created on Aug 19, 2016 2:15:00 PM by  Michael Wing (0) 1



4 Replies

Votes:

0

Your Vote:

Up

Down

Dear Michael

I am sorry, the Billing Tool comes without technical support. I recommend to check the log files, for example PRTG Core Server logs and PRTG web server logs. You find the Core Server logs in "C:\ProgramData\Paessler\PRTG Network Monitor\Logs (System)" (one or two big files, please open the more recent and scroll to the bottom) and the web server logs in "C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Web Server)", containing one log file per day.

Are you getting any useful information out of those logs, which could relate to the Billing Tool?

Created on Aug 22, 2016 11:05:55 AM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Nothing in the server logs.

This is quite an annoying problem, The problem only exists for me within the corporate environment, the billing tool runs fine on my home network. On the corporate environment i get :

The underlying connection was closed: The connection was closed unexpectedly

when launching the application and

unhanded exception has occurred in your application. if you click continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Object reference not set to an instance of an object:

See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.

** Exception Text ** System.NullReferenceException: Object reference not set to an instance of an object. at Paessler.Billingtool.ReportDialog.CreateSensorTree() at Paessler.Billingtool.ReportDialog.ReportDialog_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

** Loaded Assemblies ** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:/C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- Paessler.Billingtool Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:/C:/Program%20Files%20(x86)/Paessler%20Billingtool/Paessler.Billingtool.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34251 built by: FX452RTMGDR CodeBase: file:/C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR CodeBase: file:/C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34270 built by: FX452RTMGDR CodeBase: file:/C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:/C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR CodeBase: file:/C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Microsoft.GeneratedCode Assembly Version: 1.0.0.0 Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR CodeBase: file:/C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Web Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34280 built by: FX452RTMGDR CodeBase: file:/C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:/C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ----------------------------------------

** JIT Debugging ** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled.

For example:

<configuration> <system.windows.forms jitDebugging="true" /> </configuration>

When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

Created on Aug 23, 2016 9:57:57 AM by  Michael Wing (0) 1



Votes:

0

Your Vote:

Up

Down

Dear Michael

The error occuring first at "Paessler.Billingtool.ReportDialog.CreateSensorTree()" is consistent with "The connection was closed unexpectedly". This unspecific error message indicates that the connection issue is outside of the tool's control. With no connection and no data, the sensor tree cannot be created.

Please check if any application or the firewall on that computer could interfere with the connection.

Created on Aug 23, 2016 6:11:44 PM by  Arne Seifert [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello, I have the same problem and would like to know if they managed to fix it.

Kind regards.

Created on Mar 22, 2021 2:15:59 PM by  drodriguezc (0)



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.