New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

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

Free PRTG
Download >>

 

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

 

Top Tags


View all Tags


Share Disk Free sensor fails after upgrade to 18.2.41.1652

Votes:

0

Your Vote:

Up

Down

Dear Paessler

The "Share Disk Free" sensor on the Remote Probes fail quite often after upgrading from 18.1.36.3733 to 18.2.41.1652.

The sensor fail with the message: Cannot access network share: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept(71) (code: PE030)

The bug disappears after restarting the remote probe, but reappears after some time. This can be anything from days to hours.

prtg share-disk-free smb smbdiskspacesensor

Created on Jul 3, 2018 7:20:04 AM by  Kenneth Vindum (0) 1



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hi Kenneth,

What version of PRTG are you currently running? We had some improvements in the last stable that may be worth to try.

However it sounds like an interesting setup with Windows 7 as the Core Server and Windows Embedded as the SQL Server. ^^

Best regards

Created on Aug 6, 2018 12:54:50 PM by  Dariusz Gorka [Paessler Support]



12 Replies

Votes:

0

Your Vote:

Up

Down

Hi there,

Can you check if the correct user credentials to access the share are added to the device settings under "Windows Credentials"? By default the sensor will use "SYSTEM" and then it will try with the Windows Credentials.

Best regards.

Created on Jul 3, 2018 8:03:20 PM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

The correct credentials has indeed been set for the device the sensor is added to. The sensor has been working just fine for several years, but is failing on several remote probes after the upgrade.

Created on Jul 4, 2018 7:19:17 AM by  Kenneth Vindum (0) 1



Votes:

0

Your Vote:

Up

Down

Hi there,

How much share disk free sensors do you have per probe?

The error message indicates that you have about 71 open sessions which exceeds the session limit of Windows itself:

as many connections as the computer can accept(71)



Best regards.

Created on Jul 4, 2018 7:55:28 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi!

The device has 9 sensors which is all set to a 60 seconds interval. Only one is a Share Disk Free.

  • 1. Ping
  • 2. Windows System Uptime
  • 3. Windows CPU Load
  • 4. Share Disk Free <-- Failing
  • 5. WMI Memory
  • 6. WMI UTC Time
  • 7. WMI File
  • 8. WMI Event Log
  • 9. Microsoft SQL v2

Created on Jul 4, 2018 12:53:47 PM by  Kenneth Vindum (0) 1



Votes:

0

Your Vote:

Up

Down

Hi there,

The error message:

No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept(71)

Seem to come from the remote host you are about to monitor. So actually the remote host is limiting the amount of connected users. The following should help you to increase the amount of max logged in users:

  1. Click START -> RUN
  2. Type regedit
  3. Go to \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
  4. Look for cachedlogonscount
  5. Replace its value to your desired number of connection, for example 15.


Best regards.

Created on Jul 4, 2018 6:08:51 PM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Dariusz

The value is currently 10. But this hasn't changed and the device has been monitored for years without any problems. The issue arose after the update of the remote probe, and fixing it by changing the value in on the device seems odd....

Are you sure nothing changed in the Remote Probe that has relation to this?

Created on Jul 5, 2018 7:29:28 AM by  Kenneth Vindum (0) 1



Votes:

0

Your Vote:

Up

Down

Hi Kenneth,

We have altered the sensor yes, but we have no similar cases in the last months that have the same error message.

Is the share used by multiple users? If so, then the session limit might be reached and it is coincidence with the upgrade of PRTG.

Best regards.

Created on Jul 5, 2018 12:47:22 PM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Dariusz

The resource is not shared. The monitored device is a PLC running Windows Enbedded Standard SP3. PRTG is installed on a Windows 7 and the PLC is not being monitored by anyone else, is not being logged onto by anyone and is primarily functioning as a SQL server for two Windows servers.

The issue can be resolved by restarting the PRTG remote probe. It will however reoccur after some time. Usually some hours/days.

We have many other similar installations with the same setup that doesn't have this issue, so it must be a combination of factors causing what we see.

Do you have any ideas to how we can obtain more information on why the restart helps? I'm worried that the remote probe has obtained a lock on some resources that it doesn't release, which causes the error. Restarting the remote probe will however release the lock and resolve the issue...

Created on Aug 6, 2018 9:08:56 AM by  Kenneth Vindum (0) 1



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hi Kenneth,

What version of PRTG are you currently running? We had some improvements in the last stable that may be worth to try.

However it sounds like an interesting setup with Windows 7 as the Core Server and Windows Embedded as the SQL Server. ^^

Best regards

Created on Aug 6, 2018 12:54:50 PM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

PRTG Network Monitor 18.2.41.1652 is the current version. I've initiated an update to the newest version. Let's see if it helps.

And yes, the setup is a bit odd, but this previously didn't cause any issues ;) The Embedded is a Beckhoff CX5020 PLC, and the Windows 7 has in subsequent installations been replaced by a Windows server. But that doesn't really help in this case.

Created on Aug 10, 2018 7:47:51 AM by  Kenneth Vindum (0) 1



Votes:

0

Your Vote:

Up

Down

Hi Kennth,

Let us know if the update solved the issue for you. :)

Best regards.

Created on Aug 10, 2018 9:11:39 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Dariusz

We haven't seen the issue after we updated PRTG, so I'm guessing the update contained a fix. Thanks for your guidance.

Kind regards Kenneth

Created on Aug 22, 2018 5:58:24 AM by  Kenneth Vindum (0) 1



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.