Table Of Contents
System Error Messages
This chapter gives some of the IP Solution Center (ISC) error messages with explanations and in some cases recommended actions. If there is no Recommended Action(s) or you still have questions, contact the Technical Assistance Center (TAC), as explained in the "Obtaining Technical Assistance" section.
For ease of reaching a specific error message for which you want to find more information, the messages are broken into the following categories:
•
Messages Starting with + (RBAC messages)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Note
Messages Starting with +
Error Message
+ Change did not succeed, possible reason: old password is not correct.
Explanation Password change failed, due to incorrect old password.
Recommended Action Enter the right old password.
Error Message
+ FATAL: AuthorizationManager.init() failed! Please check if your db server is up-running, or listening at the right port, by comparing your running dbsrv instance with `DataAccess.url.1' in etc/spe/cns.properties.
Explanation Possible problems could be: database server connection problem, JAVA classpath not set correctly, database missing entries, or wrong database.
Recommended Action Make sure vpnenv.sh or vpnenv.csh has been sourced; installation has been done properly; database server is up, running, and listening at the port expected by ISC, by checking the property repository.persistence.url in vpnsc.properties and the property DataAccess.url.1 in etc/spe/cns.properties. The two property values should be the same.
Error Message
+ FATAL: Cannot load ClassDescriptors. Please check JAVA CLASSPATH setting.
Explanation Running environment is set properly.
Recommended Action Make sure to run vpnenv.sh or vpnenv.csh.
Error Message
+ FATAL: Failed to get key for user, group or role container. Please report this to the Repository team. Your repository may not have RBAC tables populated properly.
Explanation Wrong database, missing RBAC database tables, or database connection problem.
Recommended Action Have the database administrator examine the database. Make sure the database server is up, running, and listening at the port expected by ISC, by checking the property repository,persistence.url in vpnsc.properties and the property DataAccess.url.1 in etc/spe/cns.properties. The two property values should be the same.
Error Message
+ FATAL: Failed to load service token. Please report this to the Repository team. Your repository may not have RBAC tables populated properly.
Explanation Possible problems could be: database server connection problem, JAVA classpath not set correctly, database missing entries, or wrong database.
Recommended Action Make sure vpnenv.sh or vpnenv.csh has been sourced; installation has been done properly; database server is up, running, and listening at the port expected by ISC, by checking the property repository.persistence.url in vpnsc.properties and the property DataAccess.url.1 in etc/spe/cns.properties. The two property values should be the same.
Error Message
+ RbacManager.setTokenContext: Cannot find user for the token.
Explanation User may have been deleted.
Recommended Action Log in as a user with SysAdminRole, to check if the user specified exists.
Error Message
+ setSecurityContext: failed to load service token.
Explanation Missing entries in database, incorrect database, or database is corrupted.
Recommended Action Report the problem or have the database administrator diagnose the database.
Messages 0-99
Error Message
0: Attribute {2} does not exist
Explanation The value for the attribute is not specified.
Recommended Action Set the attribute value.
Error Message
0 (from RbacExceptionMsg_en.properties)
Explanation The user specified does not have Create, Modify, Delete, or View (denoted by "C", "M", "D", "V", respectively) permission to the object specified.
Recommended Action Check the roles assigned to the user. Add the missing permissions.
Error Message
1: Attribute not found for Column {2}
Explanation A dependent attribute for a column is not specified.
Recommended Action Set the attribute value.
Error Message
1 (from RbacExceptionMsg_en.properties)Explanation Failed to login, due to invalid username or password provided.
Explanation Failed to login, due to invalid username or password provided.
Recommended Action Enter the correct username and password.
Error Message
2: Unable to get the Connection to the Database. {2}
Explanation Database Connection is not available.
Recommended Action Check whether the database is running. Also make sure it is running at the right port specified in the DB_PORT variable.
Error Message
2 (from RbacExceptionMsg_en.properties)
Explanation This indicates an ISC internal bug.
Recommended Action Report the problem with the complete stack shown.
Error Message
3: Cannot instantiate abstract class {2}
Explanation This error message is thrown while trying to instantiate an abstract class.
Recommended Action Abstract class can not be instantiated.
Error Message
3 (from RbacExceptionMsg_en.properties)
Explanation The user who created the object disallows other users to perform the operation on the object shown, even if the current user does possess the permissions on the object type.
Recommended Action Check the object's creator user's Permissions For Others field in the user editor. Check the box needed to allow others to perform the operation. Creator's permission checking is the last line of defense.
Error Message
4: ClassDictionary for class ==> {2} Not Found
Explanation Class information is not found for a class in ISC.
Recommended Action Internal error.
Error Message
5: Cant load {2} for {3}
Explanation An internal programmatic software error has occurred.
Error Message
6: Class Map not update because {2}
Explanation The error message thrown explains the detail.
Recommended Action Internal Error.
Error Message
7: Class ==> {2} Not Found
Explanation The specified class is not found.
Recommended Action Make sure you have sourced vpnenv.(c)sh. It could be an internal error too.
Error Message
8: Column not found for Attribute {2}
Explanation The specified column is missing in the database.
Recommended Action Internal Error.
Error Message
9: Database driver not available
Explanation The JDBC driver for the database is not found.
Recommended Action Make sure your database driver is installed properly. If your database is Sybase from ISC, it could be an internal error.
Error Message
10: Database URL not available
Explanation Database URL is not specified.
Recommended Action Make sure your database URL is specified.
Error Message
11: Database Not Accessible ==> {2}
Explanation The database is not accessible by ISC.
Recommended Action Make sure your database is up and running.
Error Message
12: DCPL Property ==> {2} Not Found
Explanation The specified DCPL property is not set.
Recommended Action Specify the property value. It could be Internal error.
Error Message
13: Field type {2} not implemented
Explanation The field type given in the error message is not implemented/supported.
Recommended Action Internal Error.
Error Message
14: File {2} not found
Explanation The specified file is not found in the ISC path.
Recommended Action Make sure the file is under ISC path. If this is an ISC file, then it could be an internal error.
Error Message
15: Incorrect Class Name; Expected {2}, Got {3}
Explanation Wrong class name found for a class.
Recommended Action Internal Error.
Error Message
16: Incorrect Object type; Expected {2}, got {3}
Explanation Object type is incorrect.
Recommended Action Internal Error.
Error Message
17: IO Exception while accessing {2}
Explanation The exception message thrown explain the error in detail.
Error Message
18: No attributes found for class {2}
Explanation Attributes are missing for a class.
Recommended Action Internal Error.
Error Message
19: Attribute {0} is null
Explanation Attribute value is not specified. Null value found for the attribute.
Recommended Action Set a valid value to the specified attribute.
Error Message
20: Password not available
Explanation The password for a user is not available in the database.
Recommended Action Set the password.
Error Message
21: Could not update {2} to database, the object could have been updated already by another user
Explanation The object is already modified by another user. This could occur if multiple persons are trying to modify the same object.
Recommended Action Make sure not more than one person is working on the same connection object.
Error Message
22: SQL Exception {2}
Explanation The exception message explains the error in detail.
Error Message
23: SQL Type {2} not implemented
Explanation This SQL type is not implemented in ISC.
Recommended Action Internal Error.
Error Message
24: SQL Type Unknown for {2}
Explanation An unknown type was found for an object.
Recommended Action Internal Error.
Error Message
25: Table --> {2} Not Found
Explanation The specified table is missing in the database.
Recommended Action Internal Error.
Error Message
26: User Name not available
Explanation A specified user name is not available in the database.
Recommended Action Make sure the user is stored in the database.
Error Message
27: This method ({2})should never have been called
Explanation The method given in the error message should not be invoked.
Recommended Action Internal Error.
Error Message
28: Class {2} could not be instantiated
Explanation The specified class can not be instantiated.
Recommended Action Avoid instantiating the class. It could be an internal error.
Error Message
29: Cannot delete Object
Explanation This object can not be deleted because some other objects may be dependent on it.
Recommended Action First try deleting the dependencies.
Error Message
30: Could not rollback transaction
Explanation Rollback on this commit is failed.
Recommended Action Internal Error.
Error Message
31: General Exception
Explanation The given error message will have the details.
Error Message
32: Null Transaction
Explanation Invalid transaction.
Recommended Action Internal Error.
Error Message
33: Unable to load file "{2}"
Explanation The specified file is not loaded in the JVM.
Recommended Action The file might be missing or it may not be in the correct path.
Error Message
34: The size of data in the attribute, {2} of {3} object
Explanation The given error message will have details
Recommended Action Internal error.
Error Message
35: Unable to Clone the object. {0}
Explanation The specified object can not be cloned.
Recommended Action Internal Error.
Error Message
36: Unable to set default value. {0}
Explanation Error while setting default value for the specified attribute.
Recommended Action Internal Error.
Error Message
37: Unable to set attribute value. {0}
Explanation Error occurred while setting a value for the specified attribute.
Recommended Action Internal Error.
Error Message
38: Invalid value, {0} detected for the argument
Explanation Wrong value set for the argument.
Recommended Action Set valid value for the argument.
Messages 100-199
Error Message
133: {0}::{1}: ResourcePool == Value {2} already exists.
Explanation Value specified by variable {2} already exists in the repository.
Recommended Action Do not allocate the same resource multiple times.
Error Message
134: {0}::{1}: ResourcePool == Block overflows into previous block.
Explanation Internal resource pool error when the resource pools overflow into the previous block.
Recommended Action Check the resource pools.
Error Message
135: {0}::{1}: ResourcePool == Block overflows into next block.
Explanation Internal resource pool error when the resource pool overflows into the next block.
Recommended Action Check the resource pools.
Error Message
136: {0}::{1}: Cannot Allocate Resource, Pool is empty.
Explanation Cannot allocate resource because the pool is empty.
Recommended Action Create new resource pool.
Error Message
137: {0}::{1}: ResourcePool == Pool contains insufficient blocks.
Explanation Resource pool does not contain enough resource.
Recommended Action Check new resource pools.
Error Message
138: {0}::{1}: ResourcePool == Pool already contains block starting with {2} of size {3} with name {4}.
Explanation Resource pool overlaps with the new resource pool being created.
Recommended Action Check the resource pool and create a new one. {2} Starting value of the block; {3} Size of the block; {4} Name given to the pool.
Error Message
139: {0}::{1}: ResourcePool == Block starting with {2} of size {3} has already been allocated.
Explanation Resource pool overlaps with the allocated pool already existing.
Recommended Action Check the resource pool and create a new one that does not overlap with the allocated pool. {2} Starting value of the block; {3} Size of the block.
Error Message
140: {0}::{1}: ResourcePool == Could not recover from aged pool, ip addresses have not aged yet.
Explanation Could not recover addresses from the aged pool.
Recommended Action Adjust the aged timer if you want the IP addresses to be recovered in DCPL.
Error Message
141: {0}::{1}: PoolWithSeed == {2} is a malformed string, should be of the form sss:nnn.
Explanation The value being allocated is malformed.
Recommended Action Make sure the value to be manually allocated follows the valid format.
Error Message
142: {0}::{1}: PoolWithSeed == {2} has null value part
Explanation Pool with seed to be allocated is not valid.
Recommended Action Either the seed value or the allocated value is null. Make sure that the value to be manually allocated follows the valid format.
Error Message
143: {0}::{1}: PoolWithSeed == Release cannot be called for Pools with seed (Route Target and Route Distinguisher)
Explanation Pool with seed value once allocated cannot be released.
Recommended Action Route Target, Route Distinguisher, and SOO values cannot be released once allocated.
Error Message
144: {0}::{1}: Vlan == add cannot be called for Vlan. The values are added automatically when an instance is created
Explanation The Resource Pool API cannot be invoked with this function.
Recommended Action Avoid using the Resource Pool API that results in the exception.
Error Message
145: {0}::{1}: ResourcePool == Associated Object of class {2} does not exist in the database
Explanation The Associated Class to which the pool belongs does not exist in the database.
Recommended Action Check the reason for deletion of the associated object. This exception should not occur.
Error Message
146: {0}::{1}: IPAddressPool == IP Address {2} has no mask specified
Explanation The IP address being allocated does not have any mask specified.
Recommended Action Specify an IP address with a valid mask (8-29).
Error Message
147: {0}::{1}: IPAddressPool == Expected Mask to be <= 32, but got {2}
Explanation The IP address being allocated has an incorrect mask specified.
Recommended Action Specify an IP address with a valid mask (8-29).
Error Message
148: {0}::{1}: Vlan == Vlan Range {2}, {3} out of range (must be between 1 and 4094 inclusive)
Explanation The VLAN pools being allocated are out of range. The valid ranges are between 1 and 4094.
Recommended Action Specify the valid VLAN range (1-4096).
Error Message
149: {0}::{1}: Vlan == Vlan Range {2}, {3} overlaps existing values
Explanation The VLAN pool being created overlaps with the pools already existing.
Recommended Action Do not create the VLAN pool with a range overlapping with existing VLAN pools.
Error Message
150: {0}::{1}: Vlan == Vlan Range {2}, {3} has some values already allocated
Explanation The VLAN pool with the starting value {2} and the ending value {3} has some values already allocated.
Recommended Action Do not allocate values that have already been allocated.
Error Message
151: {0}::{1}: ResourcePool == {2}, {3} overlaps allocated data
Explanation The resource pool being created overlaps the allocated data.
Recommended Action Do not allocate values that have already been allocated.
Error Message
152: {0}::{1}: ResourcePool == {2}, {3} not available for allocation
Explanation The resource pool values are not available for allocation because they have already been allocated.
Recommended Action Do not allocate values that have already been allocated.
Error Message
153: {0}::{1}: ResourcePool == Cannot Delete Allocated Pools
Explanation The allocated pools cannot be deleted.
Recommended Action Do not try to delete allocated pools.
Error Message
154: {0}::{1}: VCID == add cannot be called for Vcid. The values are added automatically when an instance is created
Explanation This is an internal exception that prevents the user from calling an incorrect function for adding a VCID Pool.
Recommended Action Do not call the specific function for the VCID pool. This exception is not visible in the GUI.
Error Message
155: {0}::{1}: VCID == VCID Range {2}, {3} overlaps existing values
Explanation The VCID pool being created overlaps with the pools already existing.
Recommended Action Do not create the VCID pool with a range overlapping with existing VCID pools.
Error Message
156: {0}::{1}: VCID == VCID Range {2}, {3} has some values already allocated
Explanation The VCID pool with the starting value {2} and the ending value {3} already has some values allocated.
Recommended Action Do not allocate values that have already been allocated.
Error Message
157: Unable to delete the associated resource pools of the PersistentObject of type, {0} with ID = {1}
Explanation The resource pool associated with a particular PersistentObject cannot be deleted.
Recommended Action Check whether there are allocated resources associated with a PersistentObject with the class name specified with {0} and identifier specified by {1}.
Error Message
158: Unable to allocate IP Address from the {0} IP Address Pool
Explanation Unable to allocate a particular IP address from the pool.
Recommended Action Check whether there an IP address being allocated {0} is already allocated.
Error Message
159: IP address {0} overlaps with the available /30 IP address pool for Provider {1} and Region {2}
Explanation IP address being allocated from /30 pool for a particular region overlaps with the available pool for a different region belonging to the provider.
Recommended Action Do not allocate IP Address {0} which belongs to Provider {1} and Region {2}.
Error Message
160: IP address {0} overlaps with the available /32 IP address pool for Provider {1} and Region {2}
Explanation IP address being allocated from /32 pool for a particular region overlaps with the available pool for a different region belonging to the provider.
Recommended Action Do not allocate IP address {0} which belongs to Provider {1} and Region {2}.
Error Message
161: IP address {0} overlaps with the allocated /30 IP address pool for Provider {1} and Region {2}
Explanation IP address being allocated from /30 pool for a particular region overlaps with the available pool for a different region belonging to the provider.
Recommended Action Do not allocate IP address {0} which belongs to Provider {1} and Region {2}.
Error Message
162: IP address {0} overlaps with the allocated /32 IP address pool for Provider {1} and Region {2}
Explanation IP address being allocated from /32 pool for a particular region overlaps with the available pool for a different region belonging to the provider.
Recommended Action Do not allocate IP address {0} which belongs to Provider {1} and Region {2}.
Error Message
163: Trying to Add out of bound IP address {0} for poolname {1}
Explanation Trying to add an out of bound IP address for a particular pool.
Recommended Action Do not add an out of bound /30 or /32 pool.
Error Message
164: Invalid Mask {0} ISC supports mask between 8 and 29
Explanation Invalid mask. Not in the range 8-29 supported by ISC.
Recommended Action Enter a valid mask in the range 8-29.
Error Message
165: Invalid Range for VCID Pools
Explanation Invalid range for the VCID pools being created.
Recommended Action Make sure that the VCID pools being created are within the integer range.
Error Message
166: Out Of Bound Pool Size for Pool with seed with class {0}
Explanation Invalid size of the new PoolWithSeed pool being created.
Recommended Action Check that the new PoolWithSeed resource pool being created associated with class {0} has a valid size.
Error Message
167: Incorrect Size for poolname {0}
Explanation Invalid size of the new resource pool being created.
Recommended Action Check that the new resource pool being created associated with name {0} has a valid size.
Error Message
168: Persistent Object with which the resource pool is to be associated does not exist in the database
Explanation Internal resource pool error specifying the PersistentObject associated with datablocks is not in the database.
Recommended Action Check why the PersistentObject associated with the datablocks has been deleted.
Messages 200-299
Error Message
200: {0}::{1}: FirewallRepository ==> CPE (id = {2}, {3}) must exists in repository before being added into Firewall Service Request. Try save CPE first, then adding it into SR.
Explanation To be added into a Firewall service request, the CPE must be saved in the repository.
Recommended Action Save the CPE first, and then add that CPE into the service request.
Error Message
201: {0}::{1}: FirewallRepository ==> CPE {2} is already associated with this Firewall SR.
Explanation A CPE can only be associated with a Firewall service request once. ISC issues this error message if a user tries to add a CPE to a service request that is already associated with that service request.
Recommended Action Abort this action, because a CPE has already been associated with this service request.
Error Message
202: {0}::{1}: FirewallRepository ==> CPE {2}, {3} is already added into other Firewall SR, id = {4}.
Explanation A CPE can only be associated with one Firewall service request. ISC issues this error message if a user tries to add a CPE that is already associated with another service request.
Recommended Action Find the service request that a CPE was originally associated with, remove the CPE from that service request, and add the CPE to a new service request again.
Error Message
203: {0}::{1}: FirewallRepository ==> Can not modify an existing SR in repository, id = {2}. Please create a new subsuming SR and modify that SR.
Explanation A service request that exists in a repository can no longer be modified. Only a new service request in memory can be modified.
Recommended Action Create a subsuming service request, and modify it instead.
Error Message
204: {0}::{1}: FirewallRepository ==> Create a MODIFY CPE for a root SR (id = {2})is not allowed, only ADD and DELETE is valid operation.
Explanation A modified CPE can only be added into a service request that is not at the bottom of a service request stack.
Recommended Action Add the modified CPE into the service request that is at the top of the stack.
Error Message
205: {0}::{1}: FirewallRepository ==> Create a MODIFY CPE in SR(id = {2}) for a DELETED CPE on is not allowed.
Explanation If a CPE is a Delete type in the service request, it can only be added in a subsuming service request. Modify is not allowed for a Delete type.
Recommended Action Create an Add type CPE to a service request.
Error Message
206: {0}::{1}: FirewallRepository ==> Set this policy {1} as parent policy for policy {2} will cause a loop.
Explanation This policy hierarchy has a loop, meaning that some policy is a parent of itself. This is invalid in ISC.
Recommended Action Abort this attempt. This is not a valid action.
Error Message
207: {0}::{1}: FirewallRepository ==> The CPE (id = {2}, {3}) is missing definitions needed by the firewall policy {4}:
Explanation The CPE is missing attributes that are required in the policy. ISC does not allow the CPE to be added into the service request that is using the policy.
Recommended Action Find out which attributes are missing. Add them into the CPE and retry this action again.
Error Message
208: {0}::{1}: FirewallRepository ==> FirewallSR (id = {2}) must be in CLOSED state in order to be deleted.
Explanation Only a Closed service request can be safely deleted.
Recommended Action Decommission the service request into the Closed state or use the Force Purge option.
Error Message
209: {0}::{1}: FirewallRepository ==> Can not add a CPE into a DELETE SR. Please create an ADD SR instead.
Explanation A CPE cannot be added into a decommissioned service request.
Recommended Action Abort this action.
Error Message
210: {0}::{1}: FirewallRepository ==> CPE already deleted in parent SRs.
Explanation If a CPE is already deleted in a parent service request, it cannot be deleted again.
Recommended Action Abort this action, because the CPE is already the Delete type.
Error Message
211: Parent object {0} is missing or null
Explanation The required parent object is null.
Recommended Action Find out which object is missing and provide it.
Error Message
212: AAServer with ID {0} doesn't support TACACS+ or RADIUS protocol.
Explanation A Firewall policy requires an AA server with TACACS+ or RADIUS.
Recommended Action Create a new AA server object which TACACS+ or RADIUS protocol support, and use that new AA server in a policy.
Error Message
213: can not set the same parameter, {0}
Explanation The same parameter has been set.
Recommended Action Find out which parameter causes the problem and try to provide a different value.
Error Message
214: can not determine whether service is protocol or protocol bundle
Explanation From the service name, ISC can not decide whether the service is a protocol or a protocol bundle.
Recommended Action Go to the Access Rule that uses that service and reset the service.
Messages 300-399
Error Message
300: Could not set isolation level back to {2}.
Explanation An internal programmatic software error has occurred.
Error Message
301: Cannot delete MASTER VPNSC Host.
Explanation An internal programmatic software error has occurred.
Error Message
302: Invalid interface encapsulation type.
Explanation An internal programmatic software error has occurred.
Error Message
303: Unable to execute query using QueryManager. {0}
Explanation An internal programmatic software error has occurred.
Error Message
304: Unable to delete persistent object, {0} - {1}
Explanation An internal programmatic software error has occurred.
Error Message
305: Unable to instantiate object - {0} - {1}
Explanation An internal programmatic software error has occurred.
Error Message
305: Object does not exist. - {0} - {1}
Explanation An internal programmatic software error has occurred.
Error Message
310: CPE {0} must exists in repository before being added into NAT Service Request. Try save CPE first, then adding it into SR.
Explanation User tried to add a non-existing CPE into a NAT service request.
Recommended Action Save CPE and then create NAT service request.
Error Message
311: CPE {0} is already associated with this NAT SR.
Explanation This CPE is included in this service request.
Recommended Action Remove the CPE from the service request and save the service request again.
Error Message
312: CPE {0} is already in another NAT SR and it had been configured, Job id = {1}.
Explanation This CPE had been included with another NAT service request.
Recommended Action Remove the CPE from the service request and save the service request again.
Error Message
318: NAT SR (id = {0}) must be in CLOSED state in order to be deleted.
Explanation User tried to purge a service request that was not in Close state.
Recommended Action Decommission the service request first, and then purge or delete the service request.
Error Message
321: This Nat SR id {0} is in processing state and cannot be modify.
Explanation User tried to modify a service request that is being deployed by ISC.
Recommended Action Wait until the deployment completes and then modify the service request.
Error Message
322: This Nat SR already been subsumed by {0}, fail to commit.
Explanation The NAT service request had been changed by another service request. Unable to commit.
Recommended Action Cancel the NAT service request save operation.
Messages 400-499
Error Message
400: {0}::{1}: Tibco ==> Could not register {2} with Tibco.
Explanation An internal programmatic software error has occurred.
Messages 500-599
Error Message
500: IPSecSR:=> Cannot create new IPSecSR. Attribute {0} not defined or missing
Explanation A new IPsec SR can not be created because the attribute given in the error message is not defined.
Error Message
501: IPSecSR:=> Query {0} with {1} found more than 1 matching row
Explanation A single row was expected, but the query returned many rows.
Recommended Action Internal error
Error Message
502: IPSecSR:=> Encountered error getting/processing {0}
Explanation Error while processing the IPsec SR.
Recommended Action The error message will have the details.
Error Message
503: IPSecSR:=> Cannot do query {0}. Reason : {1}
Explanation Query can not be done, details given in the error message
Error Message
504: IPSecSR:=> IPSEC SR Validation error. Validation Type : {1}. Reason : {2}
Explanation Validation error, reason given in the error message.
Error Message
505: IPSecSR:=> IPSEC SR Validation error. Logical device for : {0} is either not enbaled for IPSec or does not have a Secure interface
Explanation Validation error for the logical device given in the error message.
Recommended Action Make sure the particular logical device is IPsec enabled and has a secured interface.
Error Message
506: IPSecSR:=> The following Logical device pairs already have tunnels associated
between each other {0}
Explanation The pair of logical devices given already have tunnels created between them.
Error Message
507: IPSecSR:=> Invalid topology detected : {0}
Explanation Invalid topology found.
Error Message
508: IPSecSR:=> Topology has no hub specified
Explanation There is no hub specified for the topology.
Error Message
509: IPSecSR:=> Invalid or incomplete information in this CpeTopoRole instance. Logical Device represented : {0}, field : {1}, value : {2}
Explanation An internal programmatic software error has occurred.
Error Message
510: IPSecSR:=> Duplicate Logical Device {0} detected in SR {1}
Explanation The logical device is duplicated for the SR specified in the error message.
Recommended Action Make sure you are not adding the same device more than once to an SR.
Error Message
511: {0}::{1}: IPSecPolicy:=> IPSecPolicy {2} is associated with the following SRs:{3}. It cannot be deleted
Explanation A policy cannot be deleted because it is associated with some SRs.
Recommended Action A policy can be deleted only if there are no SRs associated with it.
Error Message
512: {0}::{1}: IPSecProposal:=> IPSecProposal is not associated with a IPSec Policy
Explanation The IPsec proposal is not associated with any IPsec policy.
Recommended Action Associate the IPsec proposal with an IPsec policy object.
Error Message
513: {0}::{1}: IPSecProposal:=> Expected one IPSec Policy for policy ID {2}. Got {3}.
Explanation Expecting only one IPsec policy for an IPsec proposal, but more than one is returned.
Error Message
514: {0}::{1}: IPSecProposal:=> IPSecProposal with ID {2} has IPSecPolicies associated with the following SRs: {3}. It cannot be deleted
Explanation An IPsec proposal can not be deleted when its parent IPsec policy is associated with SRs.
Recommended Action To delete the IPsec proposal object, there should not be any IPsec SRs associated with the parent object IPsec policy.
Error Message
515: {0}::{1}: IKEProposal:=> IKEProposal is not associated with a IPSec Policy
Explanation The IKE proposal is not associated with any IPsec policy.
Recommended Action Associate the IKE proposal with an IPsec policy object.
Error Message
516: {0}::{1}: IKEProposal:=> Expected one IPSec Policy for policy ID {2}. Got {3}.
Explanation Expecting only one IPsec policy for an IKE proposal, but more than one is returned.
Recommended Action
Error Message
517: {0}::{1}: IKEProposal:=> IKEProposal with ID {2} has IPSecPolicies associated with the following SRs: {3}. It cannot be deleted
Explanation IKE proposal can not be deleted when its parent IPsec policy is associated with SRs.
Recommended Action There should not be any IPsec SRs associated with the parent object IPsec policy to delete the IKE proposal object.
Error Message
518: User ==> User is not associated with a Group
Explanation User is not associated with a Group.
Recommended Action Associate the User with a Group.
Error Message
519: User ==> Expected one Group for group ID {2}. Got {3}.
Explanation Expected one Group for the user, but more than one is returned.
Error Message
520: User ==> User with ID {2} has Groups associated with the following SRs: {3}. It cannot be deleted.
Explanation User can not be deleted because its Group is associated with some SRs.
Recommended Action User can be deleted only if its Group is not associated with any SR.
Error Message
521: AAServer ==> AAServer is not associated with a customer
Explanation AAServer is not associated with a customer
Recommended Action AAServer needs to be associated with a customer.
Error Message
522: AAServer ==> Expected one customer for customer ID {2}. Got {3}
Explanation Expected one customer, but more than one is returned.
Error Message
523: AAServer ==> AAServer {2} is associated with the following SRs: {3}. It cannot be deleted
Explanation AAServer is associated with some SRs.
Recommended Action AAServer can not be deleted if it is associated with an SR.
Error Message
524: AddressPool ==> AddressPool does not have a {2} association
Explanation Address Pool is not associated with any Persistent Object.
Error Message
525: AddressPool ==> Expected one {2} for ID "{3}". Got "{4}".
Explanation The error message will have the details.
Recommended Action Internal error
Error Message
526: AddressPool ==> Returned object ({2}) is not of type {3}.
Explanation The error message will have the details.
Recommended Action Internal error
Error Message
527: AddressPool ==> Parent {2} has not been defined.
Explanation An internal programmatic software error has occurred.
Recommended Action Associate the Address Pool with the parent.
Error Message
528: RepXXXMapping ==> Mapping object "{2}" is null. This object cannot be persisted in the DB.
Explanation This object can not be persisted in the database.
Error Message
529: RepGroup ==> List elements must each be of type {2}.
Explanation The error message will have the details
Error Message
530: GROUP RepGroup ==> The device-specific group attributes object has not been associated with this Group. Use method "createDeviceSpecificAttributes" to create or "getDeviceSpecificAttributes" to retrieve and activate the device-specific group object.
Explanation The error message will have all the details.
Error Message
531: RepGroup ==> Remote Access Group "{2}" is not defined
Explanation The object given in the error message is not defined for the Remote Access Group.
Error Message
532: Remote Access ==> Expected one {2} for ID {3}. Got {4}.
Explanation Expected one object of type {2} and many were returned.
Error Message
533: Remote Access ==> Unexpected object type ({2}). Expected {3}.
Explanation Query returns unexpected object type.
Recommended Action Internal error
Error Message
534: Remote Access ==> Expected one device-specific group object. Got {2}.
Explanation Expected one device-specific group object.
Error Message
535: User ==> Returned object ({2}) is not of type Group
Explanation Object retuned is not of type Group.
Error Message
536: User ==> Parent Group has not been defined.
Explanation Parent Group has not been defined
Error Message
537: AAServer ==> Returned object ({2}) is not of type Customer.
Explanation Returned object ({2}) is not of type Customer.
Recommended Action Internal error
Error Message
538: IPSecPolicy ==> Parent Customer has not been defined
Explanation Parent Customer has not been defined.
Recommended Action Customer should be assigned to IPsec polic.y
Error Message
539: IPSecProposal ==> Returned object ({2}) is not of type IPSecPolicy
Explanation Returned object ({2}) is not of type IPsec policy.
Error Message
540: IPSecProposal ==> Parent IPSecPolicy has not been defined.
Explanation Parent IPsec policy has not been defined.
Recommended Action IPsec policy should be assigned to IPsec proposal.
Error Message
541: IKEProposal ==> Returned object ({2}) is not of type IPSecPolicy
Explanation Returned object ({2}) is not of type IPsec policy.
Error Message
542: IKEProposal ==> Parent IPSecPolicy has not been defined
Explanation Parent IPsec policy has not been defined
Recommended Action IPsec policy should be assigned to IKE proposal.
Error Message
543: RepGroup3K ==> method call order error: addChildAttributesToTable must be called prior to setChildAttributes.
Explanation Method call order error.
Recommended Action addChildAttributesToTable must be called prior to setChildAttributes.
Error Message
544: RepGroup3K ==> the child attribute tables list is not associated with any Persistent Objects created via method RepGroup::createDeviceSpecificAttributes
Explanation The child attribute tables list is not associated with any Persistent Objects created via method RepGroup::createDeviceSpecificAttributes.
Error Message
545: RemoteAccess ==> No {2} association exists for this object
Explanation No {2} association exists for this object.
Error Message
546: {0}::{1}: RemoteAccess :: Expected one {2} for ID "{3}". Got "{4}".
Explanation Expected one object, but query returns more than one.
Error Message
547: {0}::{1}: RemoteAccess :: Returned object ({2}) is not of type {3}.
Explanation Returned object ({2}) is not of type {3}.
Error Message
548: {0}::{1}: RemoteAccess :: Parent {2} is not defined.
Explanation A parent object is not defined for the given Remote Access object.
Recommended Action Associate this Remote Access object with the parent object.
Messages 600-699
Error Message
600: Invalid String: String {0} has invalid size {1}. The valid range is [{2}, {3}].
Explanation The given string is invalid.
Recommended Action Input string of length within the specified range.
Error Message
601: Invalid String: String {0} has incorrect format
Explanation String has incorrect format.
Recommended Action Give string given in the error message in correct format.
Error Message
602: Invalid Integer: value {0} is not within valid range [{1}, {2}]
Explanation Invalid integer. The value is not within the specified valid range.
Recommended Action Give the integer given in the error message a correct value.
Error Message
603: Invalid Enumeration: value {0} is not valid for enum of type {1}
Explanation Invalid enumeration. The value is not valid for the given enum type.
Recommended Action Give the correct enum type.
Error Message
604: Invalid IP Address: {0} is in incorrect format
Explanation The specified IP address is not in the correct format.
Recommended Action Enter a valid IP address.
Error Message
605: Invalid IP Address: {0} has an invalid mask
Explanation The specified IP address does not have a valid mask.
Recommended Action Enter a valid IP address with a valid mask value.
Error Message
606: Invalid IP Address: {0} is not a correct host address
Explanation The specified IP address is not a correct host address.
Recommended Action Enter the valid IP address of the host.
Error Message
607: Invalid Object: The object {0} with id {1} is of invalid type {2}
Explanation The specified object is not of the correct or required type.
Recommended Action Internal error.
Error Message
608: Invalid Object: The object {0} with id {1} is invalid since its attribute {2} has invalid value {3}
Explanation An object is invalid because one of its attributes does not have a valid value.
Recommended Action Internal error.
Error Message
609: The Object {0} with id {1} does not exist in the database
Explanation The persistent object with the ID given in the error message is not persisted in the database.
Error Message
610: The Object {0} with id {1} cannot be deleted since Object {2} with id {3} is associated with it
Explanation The Object {0: Class Name of Object} with ID {1} cannot be deleted because Object {2} with ID {3 : ID/IDS} is associated with it.
Recommended Action Find the objects of the given type and with the given IDS or ID and either delete or disassociate these from the concerned object. Only then can the concerned object be deleted.
Error Message
611: The Object {0} with id {1} cannot be modified since Object {2} : {3} are associated with it
Explanation The Object {0: Class Name of Object} with ID {1} cannot be modified because object {2: ObjectType} : {3 :parameter} are associated with it.
Recommended Action Find the objects of the given type and with the given parameter and either delete or disassociate these from the concerned object. Only then can the concerned object be modified.
Error Message
612: The Object {0} with id {1} cannot be modified
Explanation The specified object can not be modified due to other dependent objects.
Recommended Action Find the objects of the given type and with the given IDs or ID and either delete or disassociate these from the concerned object. Only then can the concerned object be modified.
Error Message
613: The Object {0} with id {1} cannot be modified since it is already modified
Explanation Another instance of the connection modified the object.
Error Message
614: The Object {0} cannot be persisted since its parent Object {1} is not in the database
Explanation The parent object is not committed. Thus, the specified object can not be committed.
Recommended Action Set the parent object before committing the specified object.
Error Message
615: The Object {0} with id {1} cannot be persisted since its parent Object {2} with id {3} is not in the database
Explanation The parent object is not committed. Thus, the specified object can not be committed.
Recommended Action Set the parent object before committing the specified object.
Error Message
616: The Object {0} with id {1} cannot be associated with Object {2} with id {3} since attribute {4} has value {5}
Explanation An invalid association of objects occurred because their parent attribute has an invalid value.
Recommended Action Set the parent object with valid attribute values.
Error Message
617: The Object {0} with id {1} is a duplicate since attribute {2} has value {3}
Explanation A duplicate object is being committed, and thus an exception is thrown.
Recommended Action Make sure you do not commit duplicate objects, that is, objects having the same attribute values.
Error Message
618: null {0} Object has been obtained
Explanation A query returned a null object.
Error Message
619: Invalid Api Usage: The method {0} on Object {1} is not valid for attribute {2} with value {3}
Explanation This API can not be called with an invalid value set for an attribute.
Recommended Action Call this API with a valid attribute value.
Error Message
620: The {2} Service Request with Job id {3} and id {4} cannot be subsumed since its not on top of the stack
Explanation An SR on the bottom of the stack can not be subsumed.
Recommended Action Avoid subsuming an SR that is the bottom SR of the stack and there are one or more SRs on top of it.
Error Message
621: The {0} Service Request with Job id {1} and id {2} cannot be subsumed since it is decommissioned
Explanation A decommissioned SR can not be subsumed.
Recommended Action Avoid subsuming a decommissioned SR.
Error Message
622: The {0} Service Request with Job id {1} and id {2} cannot be purged since it is not in CLOSED state
Explanation The {Service Request type - MPLS, L2VPN, and so on} Service Request with the given Job ID and ID cannot be purged because it is not in the CLOSED state.
Recommended Action First decommission the SR and then purge it or use Force Purge.
Error Message
623: The {0} Service Request with Job id {1} and id {2} cannot be purged since its not on top of the stack
Explanation The {Service Request type - MPLS, L2VPN, and so on} Service Request with the given Job ID and ID cannot be purged because it is not on the top of the stack.
Recommended Action Do not try to purge an SR that is not on the top of the stack. Purging the topmost SR purges the entire stack.
Error Message
624: Cannot add Service Element {0} with id {1} to Service Request with Job id {2} and id {3} since the Service Request is decommissioned
Explanation Cannot add the Service Element with the ID mentioned in the error message to the Service Request with the given Job ID, because the Service Request is decommissioned.
Recommended Action Avoid adding any service elements to an SR that is already decommissioned.
Error Message
625: Data integrity error. Found {0} entries of Object {1} while only {2} was expected.
Explanation Data integrity error.
Recommended Action Internal error.
Error Message
626: Interface {0} is not a Loopback interface
Explanation The Interface is not a Loopback interface when a loopback interface is expected.
Error Message
627: Object {0} with attribute {1} of value {2} could not be found on parent device with id {0}
Explanation Object {Class Name of Object} with attribute {1} of value {2} could not be found on parent device with ID {0}.
Error Message
628: Attribute cache has not been enabled.
Explanation Attribute cache has not been enabled.
Error Message
629: The Object {0} with attribute {1} = {2} does not exist in the database.
Explanation The Object {Class Name of Object} with attribute {1} = {2} does not exist in the database.
Error Message
630: The Object {0} cannot be persisted since its not associated with Object {1}
Explanation The Object {Class Name of Object} cannot be persisted since its not associated with Object {1}
Recommended Action Read the error message details about why it can not be persisted.
Error Message
631: The Object {0} cannot be removed from the Object {1}
Explanation The Object {Class Name of Object} cannot be removed from the Object {1}
Recommended Action Read the error message details about why it can not be removed.
Error Message
632: The {0} Service Request with Job id {1} and id {2} cannot be subsumed since its already subsumed
Explanation The {Service Request type - MPLS, L2VPN, and so on} Service Request with Job ID {1} and ID {2} cannot be subsumed because it is already subsumed.
Recommended Action Subsume the SR which is on the top of the stack.
Error Message
633: the {0} Service Request with Job id {1} and id {2} cannot be closed because one of the SRs in the subsumption stack is not at REQUESTED state. You need to decommission the SR then config audit succeeds before you can close it.
Explanation The {Service Request type - MPLS, L2VPN, and so on} Service Request concerned cannot be closed because one of the SRs in the subsumption stack is not at REQUESTED state.
Recommended Action You need to decommission the SR and then config audit should succeed before you can close it.
Error Message
634: the state transition from {0} to {1} is not allowed for Service Request with Job id {2} and id {3}
Explanation The state transition from {initial State} to {intended state} is not allowed for Service Request with Job ID {2} and ID {3}.
Error Message
635: The Service Request with Job id {0} and id {1} cannot be deleted since it is not on top of the subsumption stack OR it is not in CLOSED state
Explanation This SR cannot be deleted because it is not on the top of the subsumption stack or it is not in CLOSED state
Recommended Action Do not try to purge an SR that is not on top of the stack or is not in the closed state. Purging the topmost SR will purge the whole stack or first decommission the SR and then purge it or use Force Purge.
Error Message
636: VPN cannot be created as there is no sufficient license!
Explanation VPN cannot be created because there are not sufficient licenses.
Recommended Action Install proper or sufficient licenses.
Error Message
637: Cannot compare states {0} and {1}
Explanation The states cannot be compared.
Error Message
640: {0}:{1}: Migration ==> Target with id {2} does not exist
Explanation The target with a given ID (specified in the variable {2}) does not exist in the database.
Recommended Action The target ID referenced in this object did not get exported from the VPNSC 1.x/2.x repository for migration. Please verify the VPNSC 1.x/2.x repository and retry the export.
Error Message
641: {0}:{1}: Migration ==> String {2} is a malformed number
Explanation The value exported from VPNSC 1.x/2.x is not in a valid number format.
Recommended Action Verify and fix the source data and retry the export.
Messages 700-799
Error Message
700: {0}::{1}: Customer ==> Customer with ID {2} is associated with the following SRs: {3}. It cannot be deleted.
Explanation Customer can not be deleted because it has been associated with an SR.
Recommended Action Do not delete this customer or purge those SRs associated with it.
Error Message
710: {0}::{1}: Site ==> Site is not associated with a customer.
Explanation Site did not have any customer associated with it.
Recommended Action Reassign a customer to that site.
Error Message
711: {0}::{1}: Site ==> Expected one customer for customer ID {2}. Got {3}.
Explanation One site can only be associated with one customer. The current site is associated with more than one customers.
Recommended Action Make sure this site is associated with only one customer.
Error Message
712: {0}::{1}: Site ==> Site with ID {2} has CPEs associated with the following SRs: {3}. It cannot be deleted.
Explanation Site can not be deleted because it is associated with SRs.
Recommended Action Do not delete this site or purge the associated SRs.
Error Message
713: {0}::{1}: VPN ==> VPN is not associated with a customer
Explanation VPN did not have any customer associated with it.
Recommended Action Reassign a customer to that VPN.
Error Message
714: {0}::{1}: VPN ==> Expected one customer for customer ID {2}. Got {3}.
Explanation One VPN can only be associated with one customer. The current VPN is associated with more than one customer.
Recommended Action Make sure that this VPN is associated with only one customer.
Error Message
715: {0}::{1}: VPN ==> VPN with ID {2} is associated with the following SRs: {3}. It cannot be deleted
Explanation VPN can not be deleted because it has been associated with an SR.
Recommended Action Do not delete this VPN or purge those SRs associated with it.
Error Message
716: {0}::{1}: CustomerNetworkPrefix ==> CustomerNetworkPrefix is not associated with a Cpe
Explanation An internal programmatic software error has occurred.
Error Message
717: {0}::{1}: CustomerNetworkPrefix ==> Expected one Cpe for cpe ID {2}. Got {3}.
Explanation An internal programmatic software error has occurred.
Error Message
718: {0}::{1}: CustomerNetworkPrefix ==> CustomerNetworkPrefix with ID {2} has CPE associated with the following SRs: {3}. It cannot be deleted
Explanation An internal programmatic software error has occurred.
Error Message
725: {0}::{1}: RepManager ==> {2} "{3}" is not a PersistentObject.
Explanation An internal programmatic software error has occurred.
Error Message
726: {0}::{1}: RepManager ==> Element "{2}" ({3}) is not of type DbAccess.
Explanation An internal programmatic software error has occurred.
Error Message
727: {0}::{1}: RepManager ==> Could not find a public constructor for instantiation: "public {2}({3})".
Explanation An internal programmatic software error has occurred.
Error Message
728: {0}::{1}: RepManager ==> A runtime exception occurred during the creation of an object of type {2}. Either the object's constructor failed or the Persistent Object constructor failed. This is likely due to the database being out of sync with the Repository object (the table attributes do not match the Repository object attributes).
Explanation An internal programmatic software error has occurred.
Error Message
731: {0}::{1}: RepQueryManager ==> called getNextObjectsList before calling getObjectsList for query "{2}".
Explanation An internal programmatic software error has occurred.
Error Message
732: {0}::{1}: RepQueryManager ==> The first filter expression should not define a connector ({2}).
Explanation An internal programmatic software error has occurred.
Error Message
733: {0}::{1}: RepQueryManager ==> Filter consists of predefined operands only.
Explanation An internal programmatic software error has occurred.
Error Message
734: {0}::{1}: RepQueryManager ==> No matching query found for query "{2}".
<
