NetDeploy01E The time of day must be specified as a four-digit number. (For example: 2330)
Severity: Error
Explanation: A time of day was specified that is not valid.
User Response: Specify the time as a four-digit number based on a 24-hour clock. For example, specify 11:30 p.m. as 2330.
NetDeploy02E The "hours" component of the time must be a number between 00 and 23.
Severity: Error
Explanation: A time was specified where the hours component of the time specification (the first two digits of the four-digit number) was not between 00 and 23.
User Response: Specify a time where the hours component is between 00 and 23.
NetDeploy03E The "minutes" component of the time must be a number between 00 and 59.
Severity: Error
Explanation: A time was specified where the minutes component of the time specification (the final two digits of the four-digit number) was not between 00 and 59.
User Response: Specify a time where the minutes component is between 00 and 59.
NetDeploy04E The host 0 could be not be located.
Severity: Error
Explanation: An error occurred when information was transmitted to or from a Network Deployment server.
User Response: This is an internal error. Make note of the information listed in the message and follow the instructions in the README file to report the problem to IBM.
NetDeploy05E Internal Network Deployment error. Please contact IBM with the following data: 0.
Severity: Error
Explanation: An error occurred when information was transmitted to or from a Network Deployment server.
User Response: This is an internal error. Make note of the information listed in the message and follow the instructions in the README file to report the problem to IBM.
NetDeploy06E The Server name "0" syntax is incorrect. Please specify [//hostname][:port][/servername].
Severity: Error
Explanation: Syntax error in the parameter passed to InitNetDeploy tool.
User Response: For example: To set a WarehouseServer, java InitNetDeploy w //serverhostname:port/servername
NetDeploy07E The install directory "0" is not found.
Severity: Error
Explanation: The install directory does not exist.
User Response: Please specify an existing directory.
NetDeploy09E An error occurred while attempting to communicate with the server "0".
Severity: Error
Explanation: A communication error occurred.
User Response: Make sure that Network is configured with the correct server information. Also, it is possible that a server being contacted is not available. If the server configuration is correct, try again later or possibly configure another server.
NetDeploy2001E Creation of client daemon failed. Registration of client operations disabled
Severity: Error
Explanation: The client agent was unable to create the client daemon process - client registration of operations disabled.
User Response: Report the problem to the client.
NetDeploy2002E User is not authorized to perform stock operation to warehouse
Severity: Error
Explanation: The user was not authorized to perform a stock operation on the warehouse.
User Response: Report the problem to the client.
NetDeploy2004E User is not authorized to perform a restock operation to warehouse for 0
Severity: Error
Explanation: The user was not authorized to perform a restock operation on the warehouse.
User Response: Report the problem to the client.
NetDeploy2005E User is not authorized to perform add operation to catalog
Severity: Error
Explanation: The user was not authorized to perform an add operation on the catalog.
User Response: Report the problem to the client.
NetDeploy2006E User is not authorized to perform a restock operation to catalog for 0
Severity: Error
Explanation: The user was not authorized to perform a restock/update operation on the catalog.
User Response: Report the problem to the client.
NetDeploy2007E User is not authorized to order 0.
Severity: Error
Explanation: The user was not authorized to perform an order (new or update)
User Response: Report the problem to the client.
NetDeploy2008E Creation of remote input stream failed for 0
Severity: Error
Explanation: The client agent was unable to create a remote input stream for the specified pathname.
User Response: Report the problem to the client.
NetDeploy2009E Creation of warehouse item failed
Severity: Error
Explanation: The client agent was unable to create a warehouse item given the user-supplied data.
User Response: Report the problem to the client.
NetDeploy2010E Stock operation on warehouse failed for 0
Severity: Error
Explanation: The client agent was unable to properly perform the stock operation on the warehouse for the specified item.
User Response: Report the problem to the client.
NetDeploy2011E Registration of stock operation within client daemon failed
Severity: Error
Explanation: The client agent was unable to properly register the stock operation within the client daemon process.
User Response: Report the problem to the client.
NetDeploy2012E Order operation on warehouse failed for 0
Severity: Error
Explanation: The client agent was unable to properly perform the order operation on the warehouse for the specified item.
User Response: Report the problem to the client.
NetDeploy2013E Failed to store ordered content in 0
Severity: Error
Explanation: The client agent was unable to properly store the result of the order operation on the client machine.
User Response: Report the problem to the client.
NetDeploy2014E Registration of order operation within client daemon failed
Severity: Error
Explanation: The client agent was unable to properly register the order operation within the client daemon process.
User Response: Report the problem to the client.
NetDeploy2015E Restock operation on warehouse failed for 0
Severity: Error
Explanation: The client agent was unable to properly perform the restock operation on the warehouse for the specified item.
User Response: Report the problem to the client.
NetDeploy2016E Registration of restock operation within client daemon failed
Severity: Error
Explanation: The client agent was unable to properly register the restock operation within the client daemon process.
User Response: Report the problem to the client.
NetDeploy2017E Add operation on catalog failed for 0
Severity: Error
Explanation: The client agent was unable to properly perform the add operation on the catalog for the specified item.
User Response: Report the problem to the client.
NetDeploy2018E Registration of add operation within client daemon failed
Severity: Error
Explanation: The client agent was unable to properly register the add operation within the client daemon process.
User Response: Report the problem to the client.
NetDeploy2019E Order operation on catalog failed for 0
Severity: Error
Explanation: The client agent was unable to properly perform the order operation on the catalog for the specified item.
User Response: Report the problem to the client.
NetDeploy2020E Registration of order operation within client daemon failed
Severity: Error
Explanation: The client agent was unable to properly register the order operation within the client daemon process.
User Response: Report the problem to the client.
NetDeploy2021E Update operation on catalog failed for 0
Severity: Error
Explanation: The client agent was unable to properly perform the update operation on the catalog for the specified item.
User Response: Report the problem to the client.
NetDeploy2022E Registration of update operation within client daemon failed
Severity: Error
Explanation: The client agent was unable to properly register the update operation within the client daemon process.
User Response: Report the problem to the client.
NetDeploy2023E Client registry entry 0 already exists
Severity: Error
Explanation: The specified registry entry already exists.
User Response: This is an internal error. Make note of the information listed in the message and follow the instructions in the README file to report the problem to IBM.
NetDeploy2024E Client registry entry 0 not found.
Severity: Error
Explanation: The specified registry entry already exists.
User Response: This is an internal error. Make note of the information listed in the message and follow the instructions in the README file to report the problem to IBM.
NetDeploy2025E Client registry entry 0 not found.
Severity: Error
Explanation: Unexpected type of ID was submitted to Client Registry.
User Response: A Client Registry user attempted to use an ID type not expected for the request being issued. This is an internal error. Make note of the information listed in the message and follow the instructions in the README file to report the problem to IBM.
NetDeploy2026E Check to see if the home directory is invalid.
Severity: Error
Explanation: InitNetDeploy could not save the configuration information.
User Response: Check to see if the home directory is invalid.
NetDeploy2027E Check to see if the Client daemon is running.
Severity: Error
Explanation: Class locator is unable to contact the Client daemon.
User Response: Check to see if the Client daemon is running or not. You need to start the Client daemon in order to dynamically download the Warehouse items from the Server machine.
NetDeploy2028E Check to see if the install directory exists.
Severity: Error
Explanation: The install directory is not found.
User Response: Check to see if the install directory exists. You can run InitNetDeploy to set the install directory.
NetDeploy2029E Could not extract the content "0" file.
Severity: Error
Explanation: Could not extract the Content file downloaded from the Server.
User Response: Please extract the Content file located in the NetDeployCache directory under install directory.
NetDeploy2030E The class "0" is not found on any of the Warehouses.
Severity: Error
Explanation: The requested class is not found on any of the Warehouses.
User Response: Check whether the pathname of the class is correct. Make sure that this class exists on any of the Warehouses as a secondary key by calling lookup method on the Warehouse.
NetDeploy2031E Required data could not be obtained from the catalog.
Severity: Error
Explanation: Required catalog data could not be read.
User Response: A catalog request probably timed out. Retry the operation.
NetDeploy2032E Order cannot enter completion phase without first being initiated.
Severity: Error
Explanation: An attempt was made to complete an order without first initializing it.
User Response: This is an internal error. Make note of the information listed in the message and follow the instructions in the README file to report the problem to IBM.
NetDeploy2033E Order request used for completion phase must be the same as that used for the initiation phase.
Severity: Error
Explanation: An attempt was made to complete an order without first initializing it.
User Response: This is an internal error. Make note of the information listed in the message and follow the instructions in the README file to report the problem to IBM.
NetDeploy2034E Unable to create a Client. The error that occurred is: 0
Severity: Error
Explanation: An attempt to create an instance of a Client failed. The exception traceback information is displayed on the following lines.
User Response: The BeanExtender code may not be properly configured. Make sure the configuration is correct and retry the operation. Also, if the client is being started with a command line parameter that specifies a data file pathname, the pathname may not be valid.
NetDeploy2035E Unable to bind client to RMI registry. The error that occurred is: 0
Severity: Error
Explanation: An attempt bind the client to the RMI registry failed.
User Response: Make sure the RMI registry is running and that Network Deployment has been properly configured.
NetDeploy2036I Client data file: 0
Severity: Informational
Explanation: Specifies the fully-qualified pathname of the file being used to store client data.
User Response: This message is informational; no action is necessary.
NetDeploy2037I Starting client: 0
Severity: Informational
Explanation: Indicates that the client is being started. The name being registered to the RMI registry is printed with the message.
User Response: This message is informational; no action is necessary.
NetDeploy2038I Client successfully bound in RMI registry.
Severity: Informational
Explanation: Indicates that the client is bound in the RMI registry and client applications that use it can now be run.
User Response: This message is informational; no action is necessary.
NetDeploy2039E Error occurred while reading in client data. The error that that occurred is: 0
Severity: Error
Explanation: Indicates that the client is bound in the RMI registry and client applications that use it can now be run.
User Response: This message is informational; no action is necessary.
NetDeploy2040E Item 0 has already been ordered.
Severity: Error
Explanation: Indicates that the item being ordered has previously been ordered
User Response: This message is informational; no action is necessary.
NetDeploy3001E Received null CatalogItem pointer
Severity: Error
Explanation: A client application passed a null CatalogItem to the Catalog.
User Response: Correct the client application to pass a valid CatalogItem, then retry the application.
NetDeploy3002E Received CatalogItem with no CatalogItemID
Severity: Error
Explanation: A client application passed a CatalogItem to the Catalog which did not contain an identifying CatalogItemID.
User Response: Correct the client application to pass a CatalogItem containing a CatalogItemID, then retry the application.
NetDeploy3003E Received CatalogItem with no Locale
Severity: Error
Explanation: A client application passed a CatalogItem to the Catalog which did not contain a Locale identifying the language being used.
User Response: Correct the client application to pass a CatalogItem containing a Locale, then retry the application.
NetDeploy3004E Attribute query is missing a right parenthesis
Severity: Error
Explanation: A client application passed an AttributeQuery which is missing a right parenthesis needed to balance a corresponding left parenthesis.
User Response: Correct the client application to pass an AttributeQuery containing correctly balanced parentheses, then retry the application.
NetDeploy3005E Attribute query is missing a name or value string
Severity: Error
Explanation: A client application passed an AttributeQuery which is missing an attribute name or value string.
User Response: Correct the client application to pass an AttributeQuery containing the missing attribute name or value string, then retry the application.
NetDeploy3006E A duplicate CatalogItemID was specified
Severity: Error
Explanation: A client application passed a CatalogItem to a Catalog containing a CatalogItemID which is a duplicate of a CatalogItemID for a CatalogItem already contained in the Catalog. Duplicate CatalogItemID's are not allowed in a Catalog.
User Response: Correct the client application to pass a CatalogItem containing a unique CatalogItemID, then retry the application.
NetDeploy3007E CatalogItem does not exist
Severity: Error
Explanation: A client application attempted to update or remove a CatalogItem which does not exist in the Catalog.
User Response: Correct the client application to either add the CatalogItem if it is a new CatalogItem or to verify that the CatalogItem exists in the Catalog before updating or removing it, then retry the application.
NetDeploy3008E Unable to bind to the registry. The error that occurred is:
Severity: Error
Explanation: The Catalog was not able to bind to the remote object registry. The reason for the error is displayed on the next line of the status log.
User Response: The registry may not be running. If so, start the registry and attempt to start the Catalog again. If the registry is already running, verify that the server information at the top of the server status page is correct, then attempt to restart the Catalog again.
NetDeploy3009E Error occurred unbinding from the registry. The error that occurred is:
Severity: Error
Explanation: The Catalog detected an error when attempting to unbind from the remote object registry. The reason for the error is displayed on the next line of the status log.
User Response: The registry may have terminated or encountered an error. The Catalog ignores the error and enters the stopped state.
NetDeploy3010E The Catalog is unavailable for use.
Severity: Error
Explanation: The Catalog is operational, but is not currently available for use.
User Response: The Catalog has been stopped and is not currently responding to requests. Try the request later once the Catalog has been started again.
NetDeploy3011E An error occurred while saving the state of the Catalog to "0". The error that occurred is:
Severity: Error
Explanation: The Catalog encountered an error while attempting to save its state to the specified file.
User Response: The specified file name may be invalid, or there may not be enough available disk space to save the Catalog contents. Verify that the save file name is valid and that there is enough disk space available, then attempt the operation again.
NetDeploy3012E Unable to create a Catalog. The error that occurred is:
Severity: Error
Explanation: An attempt to create an instance of a Catalog failed. The exception traceback information is displayed on the following lines.
User Response: The BeanExtender code may not have been properly installed. Re-install the package, then retry the operation.
NetDeploy3013E Could not define the storage subsystem specified by "0". The error that occurred is:
Severity: Error
Explanation: The currently selected storage subsystem could not be defined.
User Response: Check to make sure that the selected storage subsystem has been installed correctly, then retry the operation.
NetDeploy3014E Error occurred initializing the storage subsystem. The error that occurred is:
Severity: Error
Explanation: The currently selected storage subsystem generated an error while attempting to start the Catalog server.
User Response: Check to make sure that all configuration information for the selected storage subsystem has been correctly specified, then retry the operation.
NetDeploy4001E Catalog content not serializable
Severity: Error
Explanation: The content supplied did not implement the java.io.Serializable interface, and therefore the content cannot be stored on the catalog.
User Response: Only supply content that implements the java.io.Serializable interface.
NetDeploy4002E CatalogItemID is not set
Severity: Error
Explanation: The CatalogItem cannot attempt to retrieve content from the Catalog because the Content's CatalogItemID property has not been set.
User Response: Set the Content's CatalogItemID property and re-try the method.
NetDeploy4002E CatalogItemID is not set
Severity: Error
Explanation: The CatalogItem cannot attempt to retrieve content from the Catalog because the Content's CatalogItemID property has not been set.
User Response: Set the Content's CatalogItemID property and re-try the method.
NetDeploy6001E Could not find file: "0"
Severity: Error
Explanation: The specified file could not be found.
User Response: Check to make sure that the file you specified exists and can be read, then retry the operation.
NetDeploy6002E An error occurred reading file: "0"
Severity: Error
Explanation: The error occurred reading the specified file.
User Response: Check to make sure that the file you specified exists and can be read, then retry the operation.
NetDeploy6003E Unable to add information to catalog. The error that occurred is:
Severity: Error
Explanation: An error occurred while attempting to add the contents of the input file to the Catalog. The error that occurred is described on the following line.
User Response: The Catalog name may have been specified incorrectly or the Catalog server may not be available. Check to make sure that the Catalog name was specified correctly. If the default catalog name was used, check to make sure that the catalog configuration information is correct by running "java com.ibm.beans.netdeploy.Configure" and verifying the information in the "Catalog" page is correct. If the catalog name appears to be correct, make sure that the specified Catalog server is running, then retry the operation.
NetDeploy6004E Unable to create a catalog item identifier. The error that occurred is:
Severity: Error
Explanation: An error occurred attempting to create a catalog item identifier. The error that occurred is described on the following line.
User Response: The Catalog name may have been specified incorrectly or the Catalog server may not be available. Check to make sure that the Catalog name was specified correctly. If the default catalog name was used, check to make sure that the catalog configuration information is correct by running "java com.ibm.beans.netdeploy.Configure" and verifying the information in the "Catalog" page is correct. If the catalog name appears to be correct, make sure that the specified Catalog server is running, then retry the operation.
NetDeploy6005E Could not save catalog item identifier to file: "0"
Severity: Error
Explanation: An error occurred while attempting to save the catalog item identifier used to initialize the Catalog to the specified file. The Catalog was successfully updated however.
User Response: Check to make sure that the specified file name is valid and can be created and written to, then retry the operation.