Schedule demo

Error Handling


API execution could result in error conditions. In case of an error, the error information would be sent in the response body. The response body will have <error> as the child node along with the appropriate error code.

Error Codes

The list of HTTP error codes are tabulated below:

CodeDescription
4000Operation Completed Successfully.
4000Credential added successfully.
4000Credential updated successfully.
4000Credential deleted successfully.
4002The specified resourceid in request URI should be an integer.
4003The specified resourceid in request URI is wrong.
4004The specified apikey [ "+apiKey+" ] in the request is invalid. Kindly log in to Applications Manager and check for the key in generate key in Admin tab.
4005The specified type in request URI is wrong.
4006The given ResoureID in the URL is wrong or repeated.
4007The specified monitorname in request URI is wrong.
4008The specified request URI is incorrect.
4016The specified method in request URI is incorrect.
4024The given taskid in the URL is wrong.
4025The specified taskname in the URL is already exist or empty.
4032The specified parameter in request URI is incorrect.
4033The taskName cannot be empty.
4034The taskName already exists.
4035The taskStatus should be either enable or disable.
4036The taskType should be either group or monitor.
4037Improper resourceid in the request.
4038The startTime should be of the format (HH:MM).
4039The endTime should be of the format (HH:MM).
4040DestinationAddress DestinationPort GlobalTrap are mandatory for v1 trap
4041The effectFrom should be of the format YYYY-MM-DD HH:MM .
4042Task Method should be any one among Daily,Weekly or Once.
4043The totalNumber should be between 1 to 7 only.
4044The customTaskStartTime should be of the format (YYYY-MM-DD HH:MM).
4045The customTaskEndTime should be a valid date format like (YYYY-MM-DD HH:MM).
4046The startDay,startTime,endDay,endTime for weekly Maintenance are incorrect.
4048The given taskid in the URL is not an integer.
4049The monitor is under maintenance. Try pollnow after maintenance.
4050The monitor cannot be polled when unmanaged.
4055Mail server is not configured (This error occurs when the user tries to create an E-mail action using REST API without configuring mail server.).
4064Kindly buy the License to avail the Applications Manager API's.
4071Smtp Server could not be connected.
4072Proxy Server is not configured
4073Proxy configuration failed
4074Smtp Mail Server Connection Error
4075Modem is not properly connected.
4076Smtp host name/port should not be empty
4080DestinationAddress DestinationPort GlobalTrap are mandatory for v2 trap
4105Unknown Problem occured while calling a Rest API
4128Server Error while processing the request.
4201The pollInterval should be a valid whole number.
4202The type should not be empty.
4203The groupID should be a valid whole number.
4204The WSDLUrl should not be empty.
4205The field emailid should not be empty.
4206The username and password mentioned in the request URL should not be empty.
4207The popHost, smtpUserName and smtpPassword mentioned in the request URL should not be empty.
4208The rbmagentID mentioned in the request URL should not be empty.
4209The rbmagentID mentioned in the request URL is repeated or invalid.
4210The scriptname mentioned in the request URL should not be empty.
4211The displayname mentioned in the request URL should not be empty.
4212Invalid OS type.
4213The mode should be any one among SSH/TELNET/SNMP/WMI
4214The snmptelnetport should be a valid one.
4215The type mentioned in the request URL is not supported.
4216The timeout should be a valid one.
4217The host should not be empty.
4218The port should be a valid one.
4219The username mentioned in the request URL should not be empty.
4220The password mentioned in the request URL should not be empty.
4221The authentication should SQL or Windows.
4222The serverpath should not be empty.
4223The jndiurl should not be empty.
4224The instance should not be empty.
4225The Transaction mentioned in the request URL should be yes or no.
4226The LDAPServer should not be empty.
4227The LDAPServerPort should not be empty.
4228The MatchingAttribute should be anyone of cn, uid, sn, displayname, givenname, objectclass, dc, ou.
4229The FilterCondition should be one of equals, contains or notequals.
4230The IsSecured field should be either a yes or a no.
4231The TargetAddress mentioned in the request URL should not be empty.
4232The DownloadFile mentioned in the request URL should not be empty.
4233The UploadFile should be either yes or no.
4234The SearchField should not be empty.
4235The TargetAddress should not be empty.
4236The LookupAddress should not be empty.
4237The RecordType should not be empty.
4238The version of WEBLOGIC should be anyone of 6.1,7.0,8.1,9.x,10.x.
4238The JNDIPath should not be empty.
4239The version of JBoss server should be one of the following: 3.x, 4.x, 5.x, 6.x, 7.x and newer versions.
4240The version of Tomcat Server should be anyone of 3,4,5,6.
4241The version of Websphere Server should be anyone of 5.x,6.x,7.x
4242The mode of Websphere Server should be BASE or ND.
4243The soapport should be a valid whole number.
4244The version of Oracle Application Server should be anyone of 10.1.2 or 10.1.3.
4245The SSL of OracleEBS should be yes or no.
4246The systemnumber of SAP Server should not be empty.
4247The logonClient of SAP Server should not be empty.
4248The language of SAP Server should not be empty.
4249The specified taskMethod and taskid does not match.
4250The starttime should less than endtime.
4251Check for the date time configuration of weekly.
4252The customTaskStartTime should be less than customTaskEndTime.
4253The method for UrlMonitor should be post or get.
4254The httpcondition for UrlMonitor should be as follows. LT for <, GT for >, EQ for =, NE for !=, LE <= and GE for >=.
4255The url should not be empty.
4256The version of Exchange Server should be any one of 2019, 2016, 2013, 2010, 2007, 2003.
4257The databasetype of QueryMonitor should be any one of MySQL, Oracle, DB2, MsSQL, Sybase, Postgres.
4258The databasetypename of QueryMonitor should not be empty.
4259The showqueryoutput of QueryMonitor should be any one of yes or no.
4260The queries of QueryMonitor should not be empty.
4261The name for adding Monitor Group already exists.
4262The name should not be empty.
4263The grouptype should be either monitorgroup or webappgroup.
4264The userid in the request url is wrong or the values are repeated.
4265The weblogic.jar is missing and is required for monitoring Weblogic server Version 6.
4266The weblogic.jar is missing and is required for monitoring Weblogic server Version 7.
4267The weblogic.jar is missing and is required for monitoring Weblogic server Version 8.
4268The weblogic.jar is missing and is required for monitoring Weblogic server Version 9.
4269The weblogic.jar is missing and is required for monitoring Weblogic server Version 10.
4270The accessKey should not be empty.
4271The SecretAccessKey should not be empty.
4272The apacheurl should not be empty.
4273The serverstatusurl should be either true or false.
4274The listenerport should not be empty.
4275The serverconnectionchannel should not be empty.
4276The jmxurl should not be empty.
4300No EUM agent name configured. Please provide the EUM agent names(eumAgents) or the EUM agent ID(eumAgentsID)
4301Some of the EUM agent names/IDs are invalid
4302Error while fetching data for the EUM agent. Error - {0}
4303The fetchType mentioned in the request URL should be either 1 or 2 - 1 for POP / 2 for IMAP.
4304The fsTLSEnabled mentioned in the request URL should not be empty.
4305The fsHost, fsUserName and fsPassword mentioned in the request URL should not be empty.
4306The fsPort mentioned in the request URL should not be empty.
4307The fetchType mentioned in the request URL should not be empty. Provide fetchType=1 for Pop Server and fetchType=2 for IMAP Server
4308The tlsEnabled mentioned in the request URL should not be empty
4309The fetchEnabled mentioned in the request URL should not be empty
4310The url should not be empty
4310When adding a URL monitor via Rest API, the URL field should not be empty.
4311The urlMethod should be P or G.
4311When adding a URL monitor via Rest API, the urlMethod field should not be empty.
4312The httpValue should be a valid Integer.
4313The httpCondition should be LT or GT or EQ or NE or LE or GE.
4314Some parameter missing for edit URL.For editing URL monitor either one of the following 'type with resourceid' or 'type with url' or 'type with displayname' is needed.
4315The verifyError should be true or false.
4316The url is not created before.
4320Error occurred while editing the monitor.
4321Parameter for Edit Monitor is missing. For editing monitor either the monitor resourceid or displayname is required.
4322Unable to find Monitor with the given resourceid or display name. Verify the details provided.
4323The Record Type mentioned for DNS Monitor is invalid.
4324The Search Field mentioned for DNS Monitor is invalid.
4325The domain name should not be empty.
4326The given EUM monitor details is not for parent monitor. Try to edit again using the parent monitor details.
4340The fsSSLEnabled mentioned in the request URL should not be empty.
4341The sslEnabled mentioned in the request URL should not be empty
4342Agent -{0} mentioned in the URL request not supported for RBM Monitor. RBM monitors support only agents running in Windows
4444Error
4445The Probe Server is Down.
4446The value of datafrequency not equal to 1 or 2 in showpolleddata API.
4447The GetQueryOutput Rest Api Returns an Empty Row Values.
4500The monitor group is not Associated to the Delegated Admin of this API key.
4509Monitor already present in the DB.
4512The specified time in request URI is incorrect. Either it is more than the current time or not a proper time
4522Monitor group name already available.
4523Monitor group name should not be empty.
4524Owner name(s) [own] in the URL is wrong.
4525Given location in the URL is wrong.
4526Problem in editing monitor group.
4540This API is not available for Central Server.
4550The username and password mentioned in the request URL should not be empty when nginxauth is true.
4551The HostController/ServerName should not be empty if LaunchType of JBoss server is 'DOMAIN'. Applicable for version 7.x and above.
4553File/Directory Name should be specified with Absolute Path
4554The content field cannot be empty.
4555The Hostname field cannot be empty.
4556The Username field cannot be empty.
4557Private Key cannot be empty if Key Based Authentication is chosen
4558Script to be Monitored should not be empty
4559Working directory(directory from which the script is executed) should not be empty
4560The value for the parameter table_row (Number of tables) is invalid.
4561The Tablename field cannot be empty.
4562Either String attributes or Numeric Attributes that are present in that table should be given for monitoring
4563Unique column for the table should not be empty.
4564Prompt cannot be empty if the new host is selected
4574VMware Horizon View Connection Broker is supported only when the product is running on a Windows Server
4600Parameters should not be empty.
5001The credential name should not be empty.
5002The type should not be empty.
5003The Credential Name already exists. Choose another name.
5004The given Credential ID is not exist.
5005Credential ID should not be empty.
5006Credential ID should be a valid whole number.
5007am.webclient.credentialManager.adminRestriction
5008The type is null or empty.
5009Something went wrong.
5010Access is denied to perform this operation in Probe Server as SSO is enabled.
5011The trapName should not be empty.
5012The trapStatus is either empty or invalid.
5013The trapVersion is either empty or invalid.
5014The severity is either empty or invalid.
5015The enterpriseOID is either empty or invalid.
5016The trapType is either empty or invalid.
5017The specificType should not be empty.
5018The specificType is either empty or invalid.
5019The trapOID is either empty or invalid.
5020The v3UserName is either empty or invalid.
5021The trapHost is invalid.
5022The associateTrapSeverity is invalid.
5023The filterCondition is invalid.
5024The filterText cannot be empty if the filterCondition is present.
5025The filterText is invalid.
5026The filterCondition cannot be empty if the filterText is present.
5027The criticalCondition and the criticalThreshold should not be empty if the severity is varbindbased.
5028The criticalCondition is invalid.
5029The criticalThreshold cannot be empty if the criticalCondition is present.
5030The criticalThreshold is invalid.
5031The criticalThreshold should not have multiple values if the criticalCondition is WHOLE.
5032The criticalCondition cannot be empty if the criticalThreshold is present.
5033The warningCondition is invalid.
5034The warningThreshold cannot be empty if the warningCondition is present.
5035The warningThreshold is invalid.
5036The warningThreshold should not have multiple values if the warningCondition is WHOLE.
5037The warningCondition cannot be empty if the warningThreshold is present.
5038The clearCondition is invalid.
5039The clearThreshold cannot be empty if the clearCondition is present.
5040The clearThreshold is invalid.
5041The clearThreshold should not have multiple values if the clearCondition is WHOLE.
5042The clearCondition cannot be empty if the clearThreshold is present.
5043The clearCondition and the clearThreshold should not be empty.
5044The warningCondition and the warningThreshold should not be empty.
5045The criticalActions is not required since critical severity is not configured.
5046The warningActions is not required since warning severity is not configured.
5047The clearActions is not required since clear severity is not configured.
5048The action IDs are either invalid or does not exist.
5049The monitor group IDs are either invalid or does not exist.
5050The given trap listener name already exists.
5301Proxy error. This error code is returned when Applications Manager is not able to establish a connection with the host.
5302The JConnect mentioned in the request URL should be yes or no.
5303discoverPDB parameter should be given as yes or no.
5304Socket Read Timeout / Query Execution Timeout value is invalid.
6000Field is mandatory and cannot be empty.
6001Page Load Timeout should be an integer between 1 and 30.
6002Value for the field should be an integer.
6003Wait after load should be an integer between 1 and 10.
6004Value for the field should be true or false.
6005Polling Interval should be greater than 30.
6006Value for discoverOption should be one of the three: [0, 1, 2].
6007The version of Horizon should be '7.x', '7.13', or '8.x'.
6011Provided End time is lesser than the Start time
6022Please provide valid hostname.
6023Please enter a valid instance name.
6024Please provide valid username.
6025Please enter a valid password.
6026Timestamp should be greater than current server time.
6027The request URI must contain StartTime parameter when CustomTime is true.
6028The request URI must contain EndTime parameter when CustomTime is true.
6030The data collection operation is currently in progress. Please wait a few seconds before polling again.
6031The username or password specified is incorrect. Kindly check.
6032Please use the web browser to log into your user account first, and then proceed with using the mobile application.
6033Invalid taskUserGroup or unauthorised access to the taskUserGroup.
6034The taskUserGroup cannot be associated with the Downtime Schedule.
6035The taskUserGroup cannot be edited.
6036Invalid or non-numeric Action ID provided in the Downtime association request.
6037Operator users are not allowed to associate actions with downtime schedules.

Loved by customers all over the world

"Standout Tool With Extensive Monitoring Capabilities"

It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.

Reviewer Role: Research and Development

carlos-rivero
"I like Applications Manager because it helps us to detect issues present in our servers and SQL databases."
Carlos Rivero

Tech Support Manager, Lexmark

Trusted by over 6000+ businesses globally