whenerver i try to create a new auto discovery group i get this error i did the class c ip range ipv4 and nothing seems to work

Internal Error: Access violation at address 0000000000000000 in module 'PRTG Server.exe'. Execution of address 0000000000000000 Error details
Version: 19.3.51.2725
Server: 127.0.0.1:6120
URL: addgroup2.htm?id=1&name_=Temp&tags_=&discoverytype_=1&devicetemplate_=1&devicetemplate_=1&discoveryschedule_=0&ipselectmethod_=0&ipbase_=192.168.1&iprangebegin_=1&iprangeend_=254&iplist_=&ipsubnet_=&ipoctetrange_=&iplistv6_=&ipou_=&usedns_=0&skipknownips_=1&windowsconnection=0&windowsconnection=1&windowslogindomain_=&windowsloginusername_=&windowsloginpassword_=&linuxconnection=0&linuxconnection=1&linuxloginusername_=&linuxloginmode_=0&linuxloginpassword_=&privatekey_=&wbemprotocol_=https&wbemportmode_=0&wbemport_=5989&sshport_=22&sshelevatedrights_=1&elevationnamesudo_=&elevationnamesu_=&elevationpass_=&sshversion_devicegroup_=2&vmwareconnection=0&vmwareconnection=1&esxuser_=&esxpassword_=&esxprotocol_=0&vmwaresessionpool_=1&snmpversiongroup=0&snmpversiongroup=1&snmpversion_=V2&snmpcommv1_=public&snmpcommv2_=public&snmpauthmode_=authpHMACMD596&snmpuser_=&snmpauthpass_=&snmpencmode_=DESPrivProtocol&snmpencpass_=&snmpcontext_=&snmpport_=161&snmptimeout_=5&dbcredentials=0&dbcredentials=1&usedbcustomport_=0&dbport_=&dbauth_=0&dbuser_=&dbpassword_=&dbtimeout_=60&cloudcredentials=0&cloudcredentials=1&awsak_=&awssk_=&mqttcredentials=0&mqttcredentials=1&mqtt_user_credentials_=0&mqtt_username_=&mqtt_password_=&mqtt_port_=1883&activate_tls_=0&activate_server_auth_=0&ca_certificate_pem_=&activate_client_auth_=0&client_certificate_pem_=&client_key_pem_=&client_key_password_=&httpproxy=0&httpproxy=1&proxy_=&proxyport_=8080&proxyuser_=&proxypassword_=&accessgroup=0&accessgroup=1&accessrights_=1&accessrights_=1&accessrights_201=-1
Time: 15:33:4

Article Comments

Hi there,

I could reproduce it on my end, appears to be a bug with version 19.3.51.2725.

Thank you for bringing this to our attention.

Kind regards,

Erhard


Aug, 2019 - Permalink

Workaround for now:
Instead of Class C base IP with start/end (IPv4), use the IP with octet range (IPv4) as IP Selection Method for the auto-discovery group, then you will get no error message.

Kind regards,

Erhard


Aug, 2019 - Permalink

Update: Issue is fixed now in version 19.3.51.2830.

Kind regards,

Erhard


Sep, 2019 - Permalink