Follow

HTTP 500.100 - Internal Server Error - ASP Error encountered while trying to Add SNMP Object

KB#:  KKB000721

QUESTION

An HTTP 500.100 - Internal Server Error - ASP Error is encountered while trying to upload a device MIB under Monitor > Monitoring > Add SNMP Object.

The error message is similar to:

Error Type:
ADODB.Steam (0x-7ff5f446)
File could not be opened.
/monitortab/loadMIB.asp, line 86

or

* Error Type:
Microsoft JScript runtime (0x-7ff5ec6f)
'strEnterprise' is undefined
/monitortab/loadMIB.asp, line 339
* Browser Type:
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR
2.0.50727) 
* Time:
Wednesday, June 27, 2007 2:15:43 PM

 

This is caused by one of three possible issues:

a) The MIB exceeds the size we can upload into an ASP page or access permissions or another technical issue prevent it from being uploaded.

b) The MIB has a dependency on another MIB that you have not yet uploaded.

c) The MIB is either a slightly non-standard format or has features that Kaseya does not yet support.

 

ANSWER

The following steps are required to diagnose the issue:

a) Manually copying the MIB file to the server to the directory C:\Kaseya\WebPages\ManagedFiles\VSAMonSetFiles\usr\share\snmp\mibs? Add a .txt extension to the MIB file if it does not have one already.

If the MIB Objects then appear in the MIB Tree, it was an upload error or permissions error on the directory. Try reapplying the schema (Under System > Server Management > Configure), or manually reapplying inherited permissions to the above directory to allow the MIB uploads.

b) Reload the Kaseya Server hotfixes (System > Server Management > Configure) to ensure that you have the hotfixes correctly applied. SNMP compatibility is improved through the use of hotfixes.

c) Raise a support call with Kaseya (System > Server Mangement > Request Support). Attach a zipped version of the MIB files you are attempting to add. Also import the following script, and run an SNMP walk of the device you wish to monitor from the machine you intend to monitor it from. Zip and attach the generated etherStatsPkts1.txt, etherStatsEntryWalk.txt and ifEntryWalk.txt files.

Script Name: Execute SNMPWalk
Script Description: This script will run a SNMPWalk command on the MIB 2 tables: etherStat and ifEntry. The user can alter the deviceipaddress and communityname variables to get the basic interface information on a SNMP Device; aiding them in creation or modification of SNMP Monitor sets.


IF True 
THEN
Get Variable
Parameter 1 : 2
Parameter 2 : public
Parameter 3 : communityName
OS Type : 0
Get Variable
Parameter 1 : 2
Parameter 2 : 192.168.0.4
Parameter 3 : deviceIpAddress
OS Type : 0
Execute Shell Command
Parameter 1 : "C:\temp\usr\bin\snmpget.exe" -c #communityName# -v 1 -t 2 -O Qstab -M "C:\temp\usr\share\snmp\mibs" #deviceIpAddress# .iso.org.dod.internet.mgmt.mib-2.rmon.statistics.etherStatsTable.etherStatsEntry.etherStatsPkts.1 >> c:\temp\out.txt
Parameter 2 : 1
OS Type : 0
Get File
Parameter 1 : c:\temp\out.txt
Parameter 2 : etherStatsPkts1.txt
Parameter 3 : 0
OS Type : 0
Delete File - (Continue on Fail)
Parameter 1 : c:\temp\out.txt
OS Type : 0
Execute Shell Command
Parameter 1 : "C:\temp\usr\bin\snmpwalk.exe" -c #communityName# -v 1 -M "C:\temp\usr\share\snmp\mibs" #deviceIpAddress# .iso.org.dod.internet.mgmt.mib-2.rmon.statistics.etherStatsTable.etherStatsEntry >> c:\temp\out.txt
Parameter 2 : 1
OS Type : 0
Get File
Parameter 1 : c:\temp\out.txt
Parameter 2 : etherStatsEntryWalk.txt
Parameter 3 : 0
OS Type : 0
Delete File - (Continue on Fail)
Parameter 1 : c:\temp\out.txt
OS Type : 0
Execute Shell Command
Parameter 1 : "C:\temp\usr\bin\snmpwalk.exe" -c #communityName# -v 1 -M "C:\temp\usr\share\snmp\mibs" #deviceIpAddress# .iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry >> c:\temp\out.txt
Parameter 2 : 1
OS Type : 0
Get File
Parameter 1 : c:\temp\out.txt
Parameter 2 : ifEntryWalk.txt
Parameter 3 : 0
OS Type : 0
Delete File
Parameter 1 : c:\temp\out.txt
OS Type : 0
ELSE


The information you provide may be used to develop a hotfix for improved MIB support. Please ensure that you have permission from the device vendor before doing so.

 

APPLIES TO
Kaseya Monitor Tab
Add SNMP Object
MIB

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.