UCP Error Messages

Recommended Action Verify that there is enough available memory, the Information Broker is running, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message Could not find symbol %s in library <lib>

Explanation Internal error. A required symbol cannot be found in the dynamic link library.

Error Message Could not start since there is no task creator

Explanation The task creator could not be created.

Recommended Action Verify that there is enough available memory.

Error Message CreateRequester: unknown requester type

Explanation This error occurs if an unknown requester is accessed but has not been correctly created or initialized.

Error Message DHCPPacket::GetCode: Invalid msgType

Explanation The msgType value in a DHCP packet is unrecognizable.

Recommended Action Verify that the DHCP service is properly configured.

Error Message Failed to add server

Explanation A server could not be added to the server table in memory.

Recommended Action Free up additional memory by closing other programs or add additional memory to the system.

Error Message Failed to allocate LibTable

Explanation The system on which the service is running does not have enough memory available for the LibTable.

Recommended Action Free up additional memory by closing other programs or add additional memory to the system.

Error Message Failed to create request task

Explanation An attempt to create a request task failed.

Error Message Failed to get packet creator

Explanation The packet creator could not be created.

Recommended Action Verify that there is enough available memory.

Error Message Failed to initialize the requester

Explanation The service requester could not be initialized.

Error Message Failed to load library: <lib>

Explanation The system on which the service is running does not have enough memory available to load the specified dynamic link library.

Recommended Action Free up additional memory by closing other programs or add additional memory to the system.

Error Message Failed to start the requester

Explanation The service requester could not be started.

Error Message Internal error, current server is NULL

Explanation This error occurs if no Server object (hostname/port number) was created for this requester.

Error Message Internal error, m_pTaskCreator is NULL

Explanation Internal error.

Error Message Internal error, no data sink

Explanation The service cannot communicate with the data sink.

Recommended Action Verify that the service port number and host values are entered in the configuration file correctly.

Error Message Internal error, no data source

Explanation The service cannot communicate with the data source.

Recommended Action Verify that the service port number and host values are entered in the configuration file correctly.

Error Message Internal error, no packet pool

Explanation No Packet Pool memory has been allocated for this requester or task.

Error Message Invalid magic number

Explanation The magic number is invalid, indicating a corrupt packet.

Recommended Action Check network communications.

Error Message Invalid m_op

Explanation The option has a value outside of acceptable range.

Recommended Action Enter the correct value for the option.

Error Message Invalid packet length

Explanation The packet has become corrupt.

Recommended Action Check network communications.

Error Message LibInfo::GetInterface: Authentication type and Interface type are not consistent

Explanation Internal program error.

Error Message LibTable::LoadTable: Could not access file <file>

Explanation The specified file is not accessible.

Recommended Action Verify that the file exists, it is not corrupt, it has proper access rights set, and that the file system on which it exists is accessible.

Error Message No packet pool in TaskCreator

Explanation There are no packets available in the TaskCreator packet pool.

Recommended Action Increase the packet pool size.

Error Message Out of Memory

Explanation The system on which the service is running has run out of available memory.

Recommended Action Free up additional memory by closing other programs or add additional memory to the system.

Server Initialization and Startup Errors

The following errors might occur during server initialization or startup.

Error Message BaseServer::Initialize: Failed to create Service Adapter

Explanation The attempt to initialize the service adapter failed.

Error Message BaseServer::Initialize: Failed to load cfg settings

Explanation The service could not load information from the configuration file.

Recommended Action Verify that the configuration file exists, it is not corrupt, it has proper access rights set, and that the file system on which it exists is accessible by the server.

Error Message BaseServer::Initialize: Failed to startup the socket lib

Explanation The socket library could not be started.

Error Message Configuration file <file> is not accessible

Explanation The server configuration file is not accessible.

Recommended Action Verify that the configuration file exists, it is not corrupt, the proper access rights are set, and that the file system on which it exists is accessible by the server.

Error Message Initialization failed. Exited.

Explanation The attempt to initialize the server failed.

Error Message Invalid or missed port number for <service> in file <file>

Explanation The configuration file for the specified service does not contain a valid port number for the service.

Recommended Action Verify that the port number field has a valid value and that the configuration file is not corrupt.

Error Message No GUID is specified in command line

Explanation The globally unique identifier (GUID) was not specified in the command used to start the server.

Recommended Action Verify the command syntax and re-enter the command.

Error Message No Root Directory is specified in command line

Explanation The root directory was not specified in the command used to start the server.

Recommended Action Verify the command syntax and re-enter the command.

Error Message Parse command line failed. Exited.

Explanation Incorrect syntax was used in the command line to start the server.

Recommended Action Verify the command syntax and re-enter the command.

Error Message Server Object has not created yet. Exited.

Explanation A server object could not be created.

Error Message Start failed. Exited.

Explanation The attempt to start the server failed.

Server Processing Errors

The following errors might occur during server processing.

Error Message BaseServer::AddrRequest: No requester of type <type>

Explanation The service could not communicate with the requester.

Error Message Client table is empty

Explanation The table storing the client data is empty.

Recommended Action Verify that the client table file is not corrupt and that the host on which the service is running can communicate with the Information Broker.

Error Message Could not find handler for protocol

Explanation The handler for the protocol does not exist in memory.

Error Message Failed to add protocol

Explanation The attempt to add a protocol to the internal stack failed.

Error Message Failed to create <section>

Explanation The attempt to create a service failed.

Error Message Invalid port number

Explanation An invalid port number was specified in the configuration file.

Recommended Action Enter the correct port number for the service in the configuration file.

Error Message No memory to load client table

Explanation The system on which the service is running has run out of available memory.

Recommended Action Free up additional memory by closing other programs or add additional memory to the system.

Error Message No memory to load vendor table

Explanation The system on which the service is running has run out of available memory.

Recommended Action Free up additional memory by closing other programs or add additional memory to the system.

Error Message NULL task received

Explanation A packet containing a task that is a null pointer was received.

Recommended Action Verify that the Information Broker is running, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message Primary server is not correctly specified

Explanation The primary server is not specified correctly in the configuration file.

Recommended Action Enter the correct primary server in the configuration.

Error Message Request from invalid client <client> is dropped

Explanation The service received a request from a client that is not specified in the client file.

Recommended Action Verify that the client data is correctly entered in the client file.

Error Message Unknown requester

Explanation This error occurs if an unknown requester is accessed but has not been correctly created or initialized.

Error Message Vendor table is empty

Explanation The table storing the vendor data is empty.

Recommended Action Verify that the vendor table file is not corrupt and that the host on which the service is running can communicate with the Information Broker.

PGS Errors

The following error messages might be issued by the PGS server.

Error Message Critical Error: Could not create Collectable Integer

Explanation The collectable integer could not be created in system memory.

Recommended Action Verify that there is enough available memory.

Error Message Critical Error: Could not create Dictionary CollectableString: <error>

Explanation The dictionary collectable string could not be created in system memory.

Recommended Action Verify that there is enough available memory.

Error Message Critical Error: Could not Insert key and value in dictionary

Explanation A key and its value could not be inserted into the dictionary hash table in memory.

Recommended Action Verify that there is enough available memory.

PGS Protocol Handler Errors

The following error messages might be issued by the Protocol Gateway Service (PGS) protocol handler.

Error Message Could not initialize handler

Explanation The attempt to initialize the handler failed.

Error Message Failed to initialize protocol handler

Explanation The attempt to initialize the protocol handler failed.

PGS RADIUS Initialization Errors

The following errors might occur during PGS Remote Access Dial-In User Service (RADIUS) initialization.

Error Message Failed to create Rad2Rad requester

Explanation The attempt to create the requester failed.

Error Message Failed to load configurations from file <file>

Explanation The service was unable to load the configuration file.

Recommended Action Verify that the configuration file exists, it is not corrupt, that proper access rights are set, and that the file system on which it exists is accessible.

Error Message Incomplete entry for radius server in section <section> of file <file>

Explanation The configuration for the RADIUS service is not complete.

Recommended Action Enter the correct data in the configuration file for the RADIUS service.

Error Message Failed to start request cache table

Explanation The attempt to initialize the service adapter failed.

PGS RADIUS Packet Handler Errors

The following error messages might be issued by the PGS RADIUS packet handler.

Error Message Bad incoming packet, request discarded

Explanation A request was received that contained a corrupt packet.

Recommended Action Verify that the Information Broker is running, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message Internal error, no PGWService or Client in task stack

Explanation A duplicate request was received.

Recommended Action Verify that the Information Broker is running, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message No domain name is specified for user <user> and host <host>

Explanation There is no domain name in a RADIUS packet.

Recommended Action Verify that the domain name was entered correctly during the authorization request, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message No packet in received request

Explanation A request was received that contains no data.

Recommended Action Verify that the Information Broker is running, that the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message No packet in request task

Explanation There is no data in a request.

Recommended Action Verify that the system on which the Information Broker is running is accessible and that the ActiveWeb server is running and accessible.

Error Message No record for user <user>. Request rejected.

Explanation The username in the authorization request is not recognized.

Recommended Action Verify that the username was entered correctly during the authorization request.

Error Message No user name in packet. Request dropped.

Explanation There is no username in a RADIUS packet.

Recommended Action Verify that the username was entered correctly during the authorization request, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message Received NULL request

Explanation A packet containing a request that is a null pointer was received.

Recommended Action Verify that the Information Broker is running, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message Unknown state <state>

Explanation Each PGS handler is given a sequential state value. This error occurs if a handler has a state value that is out of sequence.

Recommended Action Verify that the next state value in the configuration file is correct.

Error Message Unknown request code <code>. Request dropped.

Explanation There is an unrecognized request code in a RADIUS packet.

Recommended Action Verify that the system on which the Information Broker is running is accessible and that the ActiveWeb server is running and accessible.

PGS Authentication Handler Errors

The following error messages might be issued by the PGS authentication handler.

Error Message Authentication failed for user <user>. Request rejected.

Explanation The user cannot be authenticated.

Recommended Action Verify that all data was entered correctly during authentication attempt.

Error Message Internal error, no packet at index 1

Explanation A reply packet has been received and the server cannot match it with the saved packet.

PGS Authorization Handler Errors

The following error messages might be issued by the PGS authorization handler.

Error Message Authorization failed for user <user>. Request rejected.

Explanation The user cannot be authorized.

Recommended Action Verify that all data was entered correctly during the authentication attempt.

Error Message Internal error, no packet at index 1

Explanation A reply packet has been received and the server cannot match it with the saved packet.

PGS DynamicIP Handler Errors

The following error message might be issued by the PGS DynamicIP handler.

Error Message Internal error, no user on task stack

Explanation A reply packet has been received and the server cannot match it with the saved packet.

PGS State Handler Errors

The following error message might be issued by the PGS state handler.

Error Message Invalid next state %d for state %d

Explanation Each PGS handler is given a sequential state value. This error occurs if a handler has a state value that is not in sequence.

Recommended Action Verify that the next state value in the configuration file is correct.

Password Checker Errors

The following error might occur during password checking.

Error Message CheckUnixPassword() failed

Explanation An incorrect password to a UNIX server was entered.

Recommended Action Enter the correct password.

Client/Vendor Table and Dictionary Errors

The following messages are issued as a result of client/vendor table and dictionary errors.

Error Message Could not add value name <name> since it already exists for dictionary attribute <name>

Explanation A parameter with the same name as the one you are adding already exists.

Recommended Action Add the new parameter with a different name.

Error Message Duplicated client <name> specified in file <file> is skipped

Explanation A duplicate client value exists in the file specified.

Recommended Action Remove the duplicate value from the file.

Error Message Failed to create vendor <name>

Explanation The attempt to initialize the service adapter failed.

Error Message Failed to load client from section <section> in file <file>

Explanation The client value in the specified section of the specified file could not be loaded.

Recommended Action Verify that the file is accessible, it is not corrupt, and that the client value was entered correctly in the file.

Error Message Failed to load client table from file <file>

Explanation The client table in the specified file could not be loaded.

Recommended Action Verify that the file is accessible, it is not corrupt, and that there is enough memory.

Error Message Failed to load dictionary from file <file>

Explanation The dictionary could not be loaded from the specified file.

Recommended Action Verify that the file is accessible, it is not corrupt, and that there is enough memory.

Error Message Failed to load vendor from section <section> in file <file>

Explanation The vendor value in the specified section of the specified file could not be loaded.

Recommended Action Verify that the file is accessible, it is not corrupt, and that the vendor value was entered correctly in the file.

Error Message No attributes are specified in the Attributes section in file <file>

Explanation There are no attributes specified in the Attributes section of the specified file.

Recommended Action Verify that the file is accessible, it is not corrupt, and that the attribute values were entered correctly.

Error Message No clients are loaded from file <file>

Explanation The client values in the specified file could not be loaded.

Recommended Action Verify that the file is accessible, it is not corrupt, and that the client values were entered correctly in the file.

Error Message No clients are specified in the Clients section in file <file>

Explanation There are no clients specified in the Clients section of the specified file.

Recommended Action Verify that the file is accessible, it is not corrupt, and that the client values were entered correctly in the file.

Error Message No host is specified in section <section>

Explanation There is no host specified in the specified section of the configuration file.

Recommended Action Verify that the file is accessible, it is not corrupt, and that the host value was entered correctly in the file.

Error Message No vendor name is specified in section <section>

Explanation There is no vendor specified in the specified section of the configuration file.

Recommended Action Verify that the file is accessible, it is not corrupt, and that the vendor value was entered correctly in the file.

Error Message Warning, No dictionary is specified for vendor <vendor>

Explanation There is no dictionary specified for the specified vendor in the configuration file.

Recommended Action Verify that the file is accessible, it is not corrupt, and that the vendor dictionary value was entered correctly in the file.

Proxy Initialization Errors

The following errors indicate problems in proxy initialization.

Error Message Invalid argument pPacketCreator (NULL)

Explanation Internal error.

Error Message Invalid arguments

Explanation Internal error.

Authentication Server Errors

The following messages might be issued as a result of authentication server errors.

Error Message AuthenticationServer::Handle: Could not extract NAS request from the incoming packet

Explanation The network access server (NAS) request in the incoming packet is corrupt.

Recommended Action Verify that the Information Broker is running, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message AuthenticationServer::Handle: Could not extract user record from the incoming packet

Explanation The user record value in the incoming packet is corrupt.

Error Message SetReplyAttrs(): Could not add attr.

Explanation The server could not add an attribute to the authentication packet.

Recommended Action Verify that the Information Broker is running, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Authorization Server Errors

The following messages might be issued as a result of authorization server errors.

Error Message Authorization failed, since group session count exceeded absolute group session count

Explanation The number of group sessions attempted has exceeded the maximum number allowed.

Recommended Action Close other group sessions or increase the maximum number of group sessions allowed.

Error Message Authorization failed, since session count exceeded absolute session count

Explanation The number of sessions attempted has exceeded the maximum number allowed.

Recommended Action Close other sessions or increase the maximum number of sessions allowed.

Error Message AuthorizationServer::CheckCheckingItems: authorization failed, since check item attr=%d failed

Explanation The server could not recognize the specified attribute.

Recommended Action Verify that the Information Broker is running, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message AuthorizationServer:Handle: Could not extract NAS request from the incoming packet

Explanation The NAS request in the incoming packet is corrupt.

Recommended Action Verify that the Information Broker is running, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Error Message AuthorizationServer::Handle: Could not extract user record from the incoming packet

Explanation The user record value in the incoming packet is corrupt.

Recommended Action Verify that the Information Broker is running, the system on which the Information Broker is running is accessible, and that the ActiveWeb server is running and accessible.

Accounting Server Errors

The following messages might be issued as a result of accounting server errors.

Error Message Cannot read AccountingLogFileName from the config file

Explanation The AccountingLogFileName field in the configuration file cannot be read by the server.

Recommended Action Verify that the AccountingLogFileName field in the configuration file has a valid value, the configuration file is not corrupt, the proper access rights are set, and that the file system on which the file is stored is available to the server.

Error Message Cannot read GUIDTARGET from the config file

Explanation The GUIDTARGET field in the configuration file cannot be read by the server.

Recommended Action Verify that the GUIDTARGET field in the configuration file has a valid value, the configuration file is not corrupt, the proper access rights are set, and that the file system on which the file is stored is available to the server.

Error Message Cannot read TimeInterval from the config file

Explanation The TimeInterval field in the configuration file cannot be read by the server.

Recommended Action Verify that the TimeInterval field in the configuration file has a valid value, the configuration file is not corrupt, the proper access rights are set, and that the file system on which the file is stored is available to the server.

Error Message Cannot set field value for guid source

Explanation The GUID source field value in an ActiveWeb event cannot be set.

Recommended Action Verify that the system on which the Information Broker is running is accessible and that the ActiveWeb server is running and accessible.

Error Message Cannot set field value for guid target

Explanation The GUID target field value in an ActiveWeb event cannot be set.

Recommended Action Verify that the system on which the Information Broker is running is accessible and that the ActiveWeb server is running and accessible.

Error Message Cannot set field value for nas Id

Explanation The nasID field value in an ActiveWeb event cannot be set.

Recommended Action Verify that the system on which the Information Broker is running is accessible and that the ActiveWeb server is running and accessible.

Error Message Cannot start adapter. See log file <file> for information

Explanation The accounting adapter cannot be started.

Recommended Action Verify that there is enough memory and that the ActiveWeb server is running and accessible.

Error Message Cannot start server. See log file <file> for information

Explanation The server cannot be started.

Recommended Action Verify that there is enough memory and that the ActiveWeb server is running and accessible.

Error Message Could not find client: <client>

Explanation Internal error.

Error Message No packet in received request

Explanation There is no data in a request.

Recommended Action Verify that the system on which the Information Broker is running is accessible and that the ActiveWeb server is running and accessible.

Error Message PublishSubnets: Cannot SetFieldValue accountingRec

Explanation The accountingRec field value in an ActiveWeb event cannot be set.

Recommended Action Verify that the system on which the Information Broker is running is accessible and that the ActiveWeb server is running and accessible.

Error Message PublishSubnets: Cannot publish events NCP::Accounting

Explanation The server was unable to publish the NCP::Accounting event.

Recommended Action Verify that the system on which the Information Broker is running is accessible and that the ActiveWeb server is running and accessible.

Table of Contents

UCP Error Messages