- SEE ALSO
Ekahau::Response::Error - An error response from Ekahau
Contains information about an error returned by the Ekahau Positioning Engine.
Generally you will not want to construct these objects yourself; they are created by Ekahau::Response, and use its constructor.
Always returns true, to indicate this is an error object. This method can be used on an arbitrary Ekahau::Response object to find out if it represents an error or not.
Returns an integer representing the severity of the error. Errors are ordered from least to most severe, so you can say things like
if ($err-error_level >= EKAHAU_ERR_ERROR). Constants are used to refer to the various levels, which you can refer to as
Ekahau::Response::Error::EKAHAU_ERR_CODE. You can also import these symbols into your program using the
:codes tag, which allows them to be used without the
Ekahau::Response::Error prefix. They can be imported like this:
use Ekahau::Response::Error qw(:codes)
These constants represent the different error levels:
A small problem that should not affect tracking or other operations on the server.
An error that may affect tracking, but may still be recoverable.
A fatal error requires restarting Ekahau.
Returns the code for this error. See Errors for a list of errors.
Returns the exact error response from the Ekahau engine.
Returns a triple containing the error name, description, and explanation for this error.
Returns the name of this error.
Returns a brief description of the error
Returns a longer explanation for this error.
Device Not Tracked. The device is not being tracked
Hardware Failure. Network adapter has an internal error.
Order Product Timeout. The device which you are trying to track might not be responding. Check that the device is still connected to the network and properly running Ekahau Client. Usually you get -1 error first.
Authentication Failed. Password or license is wrong.
Consumer Task Not Started. If this occurs, contact Ekahau support.
Malformed Request. The Ekahau engine expected HELLO and TALK commands but received something else.
Database Version Clash. Internal error, the system could not update the model database. Requires restarting the software
Unknown Product. If this occurs, contact Ekahau support.
Order Reply Timeout. The device which you are trying to track might not be responding. Check that the device is still connected to the network and properly running Ekahau Client. Usually you get a EKAHAU_ERR_DEVICE_NOT_RESPONDING error first.
UDP Send Error. Could not send UDP packet
Authentication timeout. HELLO and TALK commands were not sent quickly enough
Client Device Removed. Network adapter has been removed from the client device.
Unsupported protocol. The requested protocol was not found.
Production Failed. If this occurs, contact Ekahau support.
Client Cannot Measure Data. Ekahau Client can not get signal information from the network adapter.
Location Context Not Found. No location context exists for the requested context ID
License Violation. Too many open sockets for your license.
Producer Not Responding. The device which you are trying to track might not be responding. Check that the device is still connected to the network and properly running Ekahau Client. Usually you get -1 error first.
Device Limit Exceeded. Device limit (how many devices your license allows you to track) is exceeded.
Device Not Found. The device has not been detected by the Positioning Engine
Agent Lookup Failed. If this occurs, contact Ekahau support.
Empty Model. Create a positioning model with Ekahau Manager and save it to the Positioning Engine
Access Denied. Authentication was OK, but the connect was refused either because your IP address is not allowed to connect, or because the server is too busy.
Consumer Not Responding. The device which you are trying to track might not be responding. Check that the device is still connected to the network and properly running Ekahau Client. Usually you get -1 error first.
Device Not Responding. No data (any UDP packets) has been received from the device
Scott Gifford <firstname.lastname@example.org>, <email@example.com>
Copyright (C) 2005 The Regents of the University of Michigan.
See the file LICENSE included with the distribution for license information.