Messages


Chapter 17. Tivoli Data Protection for Microsoft SQL (ACO0301-5203)



ACO0301EInvalid option found while processing options file.

Explanation: A request was made to the ADSM API. While the API was processing the request, there was an invalid option found in the options file.
System Action: The current request is ended.
User Response: The option in error is written to the DSIERROR.LOG. View this file and modify this option appropriately.



ACO0601EUnable to read from tips file.

Explanation: An attempt was made to read from the "Tips of the Day" file.
System Action: No tip is displayed.
User Response: Be sure that the tips file is installed and had not been corrupted.



ACO0602EError detecting protocols.

Explanation: An attempt was made to detect the protocols that are installed on this machine. The attempt to get this information failed.
System Action: The list box of protocols is displayed with this message.
User Response: Determine if the protocols on your system are functioning. If they are, try to run the command again. If not, fix the protocols in error, and run the command again.



ACO0603ECould not load the resource dll -- %1 Either reinstall or replace the copy of the missing DLL file.

Explanation: An attempt was made to load the DLL listed in the message.
System Action: The agent is not loaded.
User Response: Either reinstall the agent or replace the copy of the DLL listed in the message with the current level of the DLL.



ACO0604ECould not determine the ADSM database agent source path.

Explanation: An attempt was made to read the registry to determine where the agent was installed.
System Action: Processing continues getting the information that it needs from the current directory.
User Response: There are two choices: either cancel the request if the correct files are not in the current directory, or allow the request to complete and take action as to whether the correct results were obtained. This error may indicate that you are not running with the required permissions. Make sure you are running with local administrator permission. This may also indicate that the agent was not installed properly and may require a reinstall.



ACO0609EA TCP/IP address is required.

Explanation: The chosen protocol was TCP/IP. However, there was not a TCP/IP address entered.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor to enter the TCP/IP address. Or, you may choose to cancel from the editor.



ACO0610EA TCP/IP port number is required.

Explanation: The chosen protocol was TCP/IP. However, there was not a TCP/IP port value entered.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor to enter the TCP/IP port value. Or, you may choose to cancel from the editor.



ACO0611ETCP/IP port value must be between 1000 and 32767.

Explanation: The chosen protocol was TCP/IP. The value entered for the TCP/IP port is not valid.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor to enter the TCP/IP port value between 1000 and 32767. Or, you may choose to cancel from the editor.



ACO0612EError obtaining message from resource dll.

Explanation: An attempt was made to get a message from the message DLL. This attempt failed.
System Action: This message is displayed in the protocol box.
User Response: The agent should be reinstalled. This will include the correct version of the message DLL.



ACO0616EA Named pipe name is required.

Explanation: The chosen protocol was Named Pipe. However, there was no value entered for the Named Pipe Name.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor and enter a value for the Named Pipe Name. Or, you may choose to cancel from the editor.



ACO0617EA NetBIOS name is required.

Explanation: The chosen protocol was NetBIOS. However, there was no value entered for the NetBIOS Name.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor and enter a value for the NetBIOS Name. Or, you may choose to cancel from the editor.



ACO0618EA NetBIOS servername is required

Explanation: The chosen protocol was NetBIOS. However, there was no value entered for the NetBIOS Server Name.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor and enter a value for the NetBIOS Server Name. Or, you may choose to cancel from the editor.



ACO0619EAn IPX socket value is required.

Explanation: The chosen protocol was IPX/SPX. However, there was no value entered for the IPX socket.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor and enter a value for the IPX socket. Or, you may choose to cancel from the editor.



ACO0620EAn IPX server address is required.

Explanation: The chosen protocol was IPX/SPX. However, there was no value entered for the IPX Server Address.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor and enter a value for the IPX Server Address. Or, you may choose to cancel from the editor.



ACO1604EUnable to obtain message number %1!u! from %2

Explanation: An error occurred while obtaining a message from the message DLL.
System Action: Processing continues.
User Response: Verify that the correct Agent message DLL is installed. If the error continues contact IBM ADSM support.



ACO2218EUnknown error. RC: %1!u!

Explanation: An attempt was made to get the text of a system error.
System Action: Instead of getting the system error text, this message is used. The Agent code continues.
User Response: Determine if the current level of the system DLL is loaded.



ACO2219EUnable to find system message

Explanation: An attempt was made to get the text of a system error.
System Action: Instead of getting the system error text, the current message is displayed.
User Response: Determine if the current level of the system DLL is loaded.



ACO2504EThe name specified in the Adsm server identifier field cannot include periods ('.'). Please re-enter.

Explanation: The name specified in the ADSM server identifier field contains one or more periods.
System Action: The agent prompts for another server identifier.
User Response: The user should enter a name without a period.



ACO2518EInvalid command line parameter: %1

Explanation: An invalid parameter has been entered on the command line.
System Action: Processing ends.
User Response: Re-enter the command and be sure to enter a valid command line.



ACO2519EOut of Heap Space.

Explanation: An attempt was made to allocate a buffer. However, there is no more heap space for the buffer.
System Action: Processing ends.
User Response: Try stopping other processes, and retry the operation.



ACO2520EIncomplete command line parameter: %1

Explanation: The command you entered was incomplete.
System Action: Processing ends.
User Response: View the line displayed in the message. Determine the error and re-issue the command.



ACO2521EParameter '%1' conflicts with previous parameters.

Explanation: A parameter has been entered on the command line that conflicts with a previous parameter that was entered.
System Action: Processing ends.
User Response: From the message displayed, the conflicting parameter is identified. View the command line to discover the conflict and re-enter the command correctly.



ACO2522E/ADSMNODE option is not valid when PASSWORDACCESS GENERATE is specified in the options file, %1.

Explanation: The ADSMNODE and PASSWORDACCESS GENERATE may not be specified at the same time.
System Action: Processing ends.
User Response: Re-enter the command with either ADSMNODE or PASSWORDACCESS GENERATE.



ACO2526WThe amount of data exceeds the available buffer space for this query.

Explanation: There was not enough buffer space to receive all of the information regarding the SQL databases.
System Action: Processing continues.
User Response: Re-issue the command to see if the complete list can now be obtained. If the problem persists, contact IBM ADSM support.



ACO2527ENo ADSM servers (options files) were found.

Explanation: An attempt was made to locate all of the ADSM servers. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there are options files defined for your ADSM servers.



ACO2534EMissing TCP/IP address.

Explanation: There is no TCP/IP address defined for the ADSM server.
System Action: Processing continues.
User Response: Before connecting to this ADSM server, a TCP/IP address needs to be defined.



ACO2536EMissing TCP/IP port.

Explanation: There is no TCP/IP port defined for the ADSM server.
System Action: Processing continues.
User Response: Before connecting to this ADSM server, a TCP/IP port value needs to be defined.



ACO2539EMissing IPX/SPX address.

Explanation: There is no IPX/SPX address defined for the ADSM server.
System Action: Processing continues.
User Response: Before connecting to this ADSM server, an IPX/SPX address needs to be defined.



ACO2541EMissing IPX/SPX socket.

Explanation: There is no IPX/SPX socket value defined for the ADSM server.
System Action: Processing continues.
User Response: Before connecting to this ADSM server, an IPX/SPX socket value needs to be defined.



ACO2544EMissing NetBIOS name.

Explanation: There is no NetBIOS name defined for the ADSM server.
System Action: Processing continues.
User Response: Before connecting to this ADSM server, a NetBIOS name will need to be defined.



ACO2546EMissing NetBIOS server name.

Explanation: There is no NetBIOS server name defined for the ADSM server.
System Action: Processing continues.
User Response: Before connecting to this ADSM server, a NetBIOS server name will need to be defined.



ACO2550EMissing Named Pipe name.

Explanation: There is no Named Pipe Name defined for the ADSM server.
System Action: Processing continues.
User Response: Before connecting to this ADSM server, a Named Pipe Name will need to be defined.



ACO2552ECould not open %1.opt.

Explanation: An attempt was made to open the options file defined in the message.
System Action: Processing ends.
User Response: Determine if the options file exists. If it does, try issuing the command again. If it does not, create the file and try issuing the command again.



ACO2553EFile error reading from %1.opt.

Explanation: An attempt was made to read from the options file defined in the message.
System Action: Processing ends.
User Response: Determine if there is an error with the options file. Try running the command again.



ACO2557ELicense file (%1) could not be opened. Reason: %2

Explanation: At attempt was made to read from the license file. This attempt failed.
System Action: Processing ends.
User Response: Reinstall the product. This will ensure that the correct license file is installed.



ACO2558ERead failure on license file (%1).

Explanation: An attempt was made to read from the license file. This attempt failed.
System Action: Processing ends.
User Response: Reinstall the product. This will ensure that the correct license file is installed.



ACO2559EWrite failure on license file (%1).

Explanation: An attempt was made to write to the license file. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there is enough space on the workstation to write the file. If there is, try running the command again.



ACO2560EData in the license file (%1) is not in a valid format.

Explanation: An attempt was made to read information from the license file. This attempt failed.
System Action: Processing ends.
User Response: Reinstall the product.



ACO2561EThe checksum in the license file (%1) does not match the license string text.

Explanation: An attempt was made to read information from the license file. The checksum was not valid so it appears the license file is not at the correct level.
System Action: Processing ends.
User Response: Reinstall the product.



ACO2562EThis is an expired 'Try and Buy'.

Explanation: While reading the license file, it was determined that the Try and Buy license has expired.
System Action: Processing ends.
User Response: This product is no longer valid for use. A valid license must be obtained before running the product.



ACO2563EUnrecognized return code from the ADSM license manager.

Explanation: An attempt was made to read information from the license file. This attempt failed.
System Action: Processing ends.
User Response: Reinstall the product.



ACO2564EUnable to open log file: %1.

Explanation: An attempt was made to open the log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there is enough space on the disk where the log file is being written. Make sure the user has the correct permissions to write to the directory. Re-issue the command.



ACO2565EUnable to open trace file: %1.

Explanation: An attempt was made to open the trace file. This attempt failed.
System Action: Processing ends.
User Response: Re-issue the command. Either specify a different trace file or do not specify a trace file.



ACO2570EYour ADSM password has expired.

Explanation: An attempt was made to connect to the ADSM server. However, the ADSM password has expired.
System Action: Processing ends.
User Response: Reset the ADSM password for the node.



ACO2573EA server name is required.

Explanation: A value was not entered for the server name.
System Action: Processing has focus on the server name.
User Response: Enter a server name.



ACO2574EA computer name is required.

Explanation: A value was not entered for the computer name.
System Action: Processing has focus on the computer name.
User Response: Enter a computer name.



ACO2575EA login ID is required.

Explanation: A value was not entered for the login ID.
System Action: Processing has focus on the login ID.
User Response: Enter a login ID.



ACO2576ETCP/IP is not active on this computer.

Explanation: An attempt was made to use the TCP/IP protocol. This attempt failed.
System Action: Processing ends.
User Response: If the protocol wanted is truly TCP/IP, then be sure that TCP/IP is installed and configured correctly. When this is done, re-issue the command.



ACO2577EAn IPX socket value is required.

Explanation: The chosen protocol was IPX/SPX. However, there was no value entered for the IPX socket.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor and enter a value for the IPX socket.



ACO2578EAn IPX server address is required.

Explanation: The chosen protocol was IPX/SPX. However, there was no value entered for the IPX Server Address.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor and enter a value for the IPX Server Address.



ACO2579EA TCP/IP port number is required.

Explanation: The chosen protocol was TCP/IP. However, there was not a TCP/IP port value entered.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor to enter the TCP/IP port value. Or, you can choose to cancel from the editor.



ACO2580EA TCP/IP address is required.

Explanation: The chosen protocol was TCP/IP. However, there was not a TCP/IP address entered.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor to enter the TCP/IP address. Or, you may choose to cancel from the editor.



ACO2581EA NetBIOS name is required.

Explanation: The chosen protocol was NetBIOS. However, there was no value entered for the NetBIOS Name.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor and enter a value for the NetBIOS Name.



ACO2582EA NetBIOS servername is required.

Explanation: The chosen protocol was NetBIOS. However, there was no value entered for the NetBIOS Server Name.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor and enter a value for the NetBIOS Server Name.



ACO2583EA Named pipe name is required.

Explanation: The chosen protocol was Named Pipe. However, there was no value entered for the Named Pipe Name.
System Action: The Options File Editor will be redisplayed.
User Response: Press the Settings button on the Options File Editor and enter a value for the Named Pipe Name.



ACO2584EFailed to delete the specified options file.

Explanation: An attempt was made to delete the options file. This attempt failed.
System Action: Processing ends.
User Response: It is possible that the file is a read-only file, or exists on a volume that you do not have authority to delete from. Determine the problem and re-enter the request.



ACO2585EThe machine ran out of memory while processing the database tree.

Explanation: While preparing the tree of the databases to display, the machine ran out of memory.
System Action: Processing continues.
User Response: Free up some of the system memory and rerun the application.



ACO2589EThe specified database objects are not available on the selected ADSM server (%1).

Explanation: An attempt was made to list the database objects that exist on an ADSM server. However, there are no objects on the ADSM server selected for this database.
System Action: Processing ends.
User Response: Choose a server that has the database object, or backup the database object to this specific server.



ACO2590WThe amount of data exceeds the available buffer space for this query. Click OK to see a partial list of objects.

Explanation: There was not enough buffer space to hold all of the information from the ADSM Server. However, a partial list was obtained.
System Action: Processing will continue showing the partial list.
User Response: Determine if this is okay. If not, free up some buffer space and reissue the request.



ACO2592EADSM server name required

Explanation: A value needs to be entered for the ADSM Server Name.
System Action: Processing has focus on the ADSM Server Identifier.
User Response: Enter an ADSM Server name.



ACO2593EAn ADSM server named %1 is already defined. Enter a new name to continue.

Explanation: A value was entered for the ADSM Server name. However, this server name already exists.
System Action: Processing has focus on the server name.
User Response: Enter a unique ADSM Server name.



ACO2594ECould not find Internet Explorer

Explanation: An attempt was made to read the registry to determine where Microsoft's Internet Explorer was installed. This attempt failed.
System Action: Processing ends.
User Response: Make sure that the registry is set up correctly for Internet Explorer.



ACO2595ECould not find the ADSM HTML books

Explanation: An attempt was made to read the registry to determine where the agent was installed. This attempt failed.
System Action: Processing ends.
User Response: It may be necessary to reinstall the agent code. This will ensure that the registry entries are set up correctly.



ACO2596EFailed to start Web browser

Explanation: An attempt was made to start the web browser to view the ADSM HTML book. This attempt failed.
System Action: Processing ends.
User Response: Start your web browser manually and point it to bookfrm.htm in the agent htm directory.



ACO2597ICould not find the default browser defined. An attempt will be made to use Microsoft's Internet Explorer.

Explanation: An attempt was made to read the registry to determine the default browser. However, there was not one defined. It will be determined where Microsoft Internet Explorer is installed.
System Action: Processing continues.
User Response: It is possible that a default browser is not defined for the system. This is okay. An attempt will be made to use Microsoft's Internet Explorer.



ACO2598EFailed to create RAS process.

Explanation: An attempt was made to start the "Dial-Up Networking" application. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the RASPHONE.EXE file is installed in the appropriate directory.



ACO2599EFailed to create a system diagnostics process.

Explanation: An attempt was made to view the System Diagnostics. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the WINMSD.EXE executable exists in the appropriate directory.



ACO2600ECould not determine the Backup-archive client path.

Explanation: An attempt was made to determine the path of where the ADSM Backup-Archive client is installed. This attempt failed.
System Action: Processing ends.
User Response: It is possible that the ADSM Backup-Archive client was not installed properly. Reinstall the client so that the proper registry entries are written.



ACO2601ECould not determine the Administrative client path.

Explanation: An attempt was made to determine the path where the ADSM Administrative client is installed. This attempt failed.
System Action: Processing ends.
User Response: It is possible that the ADSM Administrative client was not installed properly. Reinstall the client so that the proper registry entries are written.



ACO2602ECould not determine the Server path.

Explanation: An attempt was made to locate where the ADSM Server was installed. This attempt failed.
System Action: Processing ends.
User Response: It is possible that the registry entries are not set up correctly. You may want to reinstall the ADSM server code to ensure that the ADSM Server registry entries are set up appropriately.



ACO2603EFailed to create Backup-archive client process.

Explanation: An attempt was made to start the ADSM Backup-Archive client. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the DSM.EXE executable exists in the appropriate directory. If it is not, you may need to reinstall the Backup-Archive client to ensure the registry entries are set up appropriately.



ACO2604EFailed to create the Administrative client process.

Explanation: An attempt was made to start the Client Administrative GUI. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the DSMADM.EXE file is installed to the appropriate directory. If it is not, you may need to reinstall the ADSM Client Administrative GUI to ensure the registry entries are set up correctly.



ACO2605EFailed to start the event viewer.

Explanation: An attempt was made to start the event viewer. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the EVENTVWR.EXE file is installed in the appropriate directory.



ACO2608EFailed to create ADSM Server process.

Explanation: An attempt was made to start the ADSM Server Console. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the DSMSERV.EXE file is located in the correct directory.



ACO2610ECould not determine the Server Utilities path.

Explanation: An attempt was made to read the registry to get the location of the server utilities. This attempt failed.
System Action: Processing ends.
User Response: Determine whether or not the Server Utilities are installed. If not, you may want to reinstall the Utilities so that the registry entries are set up appropriately.



ACO2611EFailed to create Server Utilities process.

Explanation: An attempt was made to start the server utilities executable. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the ADSM.EXE file is installed to the appropriate directory. If it is not, you may want to reinstall the ADSM Server Utilities to ensure the registry entries are set up correctly.



ACO2615ENo ADSM Servers are selected.

Explanation: A backup of a database was selected, however there was no ADSM server chosen to backup to.
System Action: Processing ends.
User Response: Re-issue the command specifying an ADSM server.



ACO2616ENo ADSM Agents are selected.

Explanation: An attempt was made to either restore a database or delete a database backup on the ADSM server. This attempt failed.
System Action: Processing ends.
User Response: Select an ADSM agent and re-issue the command.



ACO2617EAn ADSM password is required.

Explanation: In order to issue this request, an ADSM password is required.
System Action: Processing ends.
User Response: Re-issue the command specifying an ADSM password.



ACO2618EThe passwords you typed do not match. Type the new password in both text boxes.

Explanation: A check was done between the "New password" and the "Confirm new password" boxes. They were not the same.
System Action: The "Change ADSM Password" box is redisplayed.
User Response: Re-enter the new password or cancel from the task.



ACO2619EAn ADSM servername must be selected.

Explanation: An attempt was made to change the ADSM password for a node. This attempt failed.
System Action: The "Change ADSM Password" box is redisplayed.
User Response: Re-enter the change request and make sure to fill in the "ADSM Server" field. Or, you can cancel the task.



ACO2621EUnable to activate help.

Explanation: An attempt was made to bring up the help panel on how to use help. This attempt failed.
System Action: Processing continues.
User Response: Retry the operation. If it still fails, try reinstalling the Agent.



ACO2622EPlease enter no more than %1!u! characters.

Explanation: The value you entered was more than the number of allowable characters. The maximum number of characters allowed for this field is shown in the message.
System Action: Processing has focus on the field that needs to be updated.
User Response: Enter a new value keeping in mind the maximum number of characters that are allowed.



ACO2623EThe default dsm entry is a requirement of the ADSM API. All parameters except the name can be changed.

Explanation: An attempt was made to rename the default dsm entry. However, the dsm entry is a requirement of the ADSM API and must exist.
System Action: Processing has focus on the ADSM Server name.
User Response: Any other parameter may be changed except for the dsm entry.



ACO2624EADSM client node required.

Explanation: A request was made to update or create a new ADSM Server options file. However, there was no ADSM node defined. This is required.
System Action: Processing has focus on the ADSM client node name.
User Response: Enter an ADSM Client node name.



ACO2625EInternal error detected. Retry the operation.

Explanation: An internal processing error has been detected.
System Action: Unpredictable.
User Response: Retry the operation. If the problem still occurs, report how you obtained this error to IBM ADSM support.



ACO2626EUnresolved command line error, rc = %1!d!. Report how you obtained this error.

Explanation: An internal processing error has been detected.
System Action: Unpredictable.
User Response: Retry the operation. If the problem still occurs, report how you obtained this error to IBM ADSM support.



ACO2627EUnable to write to the system registry: %1

Explanation: An attempt to write a system registry entry failed. The reason for the failure may or may not be provided.
System Action: Processing ends.
User Response: If the reason for the failure is provided, take the appropriate action(s). This may indicate that you are not running with the required permissions. Make sure you are running with local administrator permission. If there is still a problem, contact IBM ADSM support.



ACO2629EError opening log file %1.

Explanation: An attempt was made to open the log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there is enough space on the disk where the log file is being written. Make sure the user has the correct permissions to write to the directory. Re-issue the command.



ACO2630EError reading log file %1.

Explanation: An attempt was made to read the log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: Determine if there is an error with the log file. Try running the command again.



ACO2631EError writing log file %1.

Explanation: An attempt was made to write to the log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there is enough space on the disk where the log file is being written. Make sure the user has the correct permissions to write to the directory. Re-issue the command.



ACO2632EError flushing log file %1.

Explanation: An attempt was made to write the log file from buffers to disk. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there is enough space on the disk where the log file is being written. Make sure the user has the correct permissions to write to the directory. Re-issue the command.



ACO2633EError closing log file %1.

Explanation: An attempt was made to close the log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there is enough space on the disk where the log file is being written. Make sure the user has the correct permissions to write to the directory. Re-issue the command.



ACO2634EError deleting log file %1.

Explanation: An attempt was made to delete the log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: It is possible that the file is a read-only file or exists on a volume that you are do not have authority to delete from. Determine the problem and re-enter the request.



ACO2635EError opening temporary log file while pruning %1.

Explanation: An attempt was made to open the temporary log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there is enough space on the disk where the log file is being written. Make sure the user has the correct permissions to write to the directory. Re-issue the command.



ACO2636EError writing temporary log file while pruning %1.

Explanation: An attempt was made to write to the temporary log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there is enough space on the disk where the log file is being written. Make sure the user has the correct permissions to write to the directory. Re-issue the command.



ACO2637EError flushing temporary log file while pruning %1.

Explanation: An attempt was made to flush the temporary log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there is enough space on the disk where the log file is being written. Make sure the user has the correct permissions to write to the directory. Re-issue the command.



ACO2638EError closing temporary log file while pruning %1.

Explanation: An attempt was made to close the temporary log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: Be sure that there is enough space on the disk where the log file is being written. Make sure the user has the correct permissions to write to the directory. Re-issue the command.



ACO2639EError renaming temporary log file while pruning %1.

Explanation: An attempt was made to rename the temporary log file specified in the message. This attempt failed.
System Action: Processing ends.
User Response: Determine if there is an error with the temporary log file. Try running the command again.



ACO2640ILog file %1 successfully pruned.

Explanation: The log file has been successfully pruned as requested.
System Action: None.
User Response: None.



ACO2641ILog file %1 already meets the log prune specifications: no action taken

Explanation: The log file is unchanged by the prune process.
System Action: None.
User Response: None.



ACO3001ENo SQL servers are available.

Explanation: A check was done to determine if a SQL Server was installed on this machine. A SQL Server does not exist on this workstation.
System Action: Processing ends.
User Response: Install the SQL Server and re-issue the command.



ACO3006EThe specified object(s) were not found.

Explanation: A request was made to get a list of SQL databases. This request returned no databases.
System Action: Processing ends.
User Response: Determine if there is a problem with SQL. Re-enter the command.



ACO3009EERROR - /NOTRUNCATE cannot be used with a full database backup.

Explanation: A request was made to do a full backup of a database using the /NOTRUNCATE option. This is not valid.
System Action: Processing ends.
User Response: Re-enter the command. Do not specify the /NOTRUNCATE option.



ACO3010EERROR - /TRUNCAFTER cannot be used with an incremental backup.

Explanation: A request was made to do an incremental backup of a database using the /TRUNCAFTER option.
System Action: Processing ends.
User Response: Re-enter the command. Do not specify the /TRUNCAFTER option.



ACO3019EAn error was encountered.

Explanation: While processing the request, there was an error encountered.
System Action: Processing ends.
User Response: Review the other messages regarding this error to get more information about the problem.



ACO3024EUnable to obtain ADSM error message.

Explanation: An ADSM error has occurred.
System Action: Processing ends.
User Response: Retry the operation. If the same error persists, call IBM ADSM support and report how the error occurred.



ACO3026EError:

Explanation: An error has occurred processing the request.
System Action: Processing ends.
User Response: Review the other messages regarding this error to get more information about the problem.



ACO3027EError: ADSM server errors encountered.

Explanation: While processing the request, there were ADSM server errors.
System Action: Processing ends.
User Response: Review the other messages regarding this error to get more information about the problem.



ACO3028EError: SQL server errors encountered.

Explanation: While processing the request, there were SQL server errors.
System Action: Processing ends.
User Response: Review the other messages regarding this error to get more information about the problem.



ACO3030ETruncation failure:

Explanation: An error occurred trying to truncate the transaction log.
System Action: Processing ends.
User Response: Review the other messages regarding this error to get more information about the problem.



ACO3036EError: %1

Explanation: An error has occurred reading the options file.
System Action: Processing ends.
User Response: Review the other messages regarding this error to get more information about the problem.



ACO3055EError: An invalid ADSM database information record was detected and ignored.

Explanation: This is an internal error with the format of an ADSM database information record.
System Action: The invalid database information record is ignored.
User Response: Retry the operation. If this error persists, contact IBM ADSM support.



ACO3057EERROR - The /IFOLDer option is required for this operation.

Explanation: This option needs te be entered for the /ADSMAUTODELete command.
System Action: Processing ends.
User Response: Re-enter the command specifying the /IFOLDer option.



ACO3505EFailed write to SQL server. Check SQL server error log.

Explanation: An attempt was made to restore a SQL database. This attempt failed to write to the SQL server.
System Action: Processing ends.
User Response: Refer to the SQL server log for a better understanding of the problem.



ACO3801EA SQL server name or * must be entered.

Explanation: A request was made that requires a SQL server name or an asterisk (*) to be specified.
System Action: Processing ends.
User Response: Re-enter the request specifying a valid SQL server name.



ACO3802EA database name or * must be entered.

Explanation: A request was made that requires a database name or an asterisk (*) to be specified.
System Action: Processing ends.
User Response: Re-enter the request specifying a valid database name.



ACO3803EUnable to obtain ADSM error message. Please report how you got here.

Explanation: There was an error with the task for ADSM to backup the database.
System Action: Processing ends.
User Response: Please report how you obtained this error to ADSM service.



ACO3809ETruncation failed

Explanation: An attempt was made to truncate the transaction log. This attempt failed.
System Action: Processing ends.
User Response: Check the SQL Server error log for more details. Correct the problem and retry.



ACO3810EAn error was encountered

Explanation: An attempt was made to issue a backup request. An unknown error was encountered while trying to do the backup.
System Action: Processing ends.
User Response: Check the SQL Server error log for more details. Correct the problem and retry.



ACO3812IPlease enter a password for the ADSM node.

Explanation: This is a prompt message.
System Action: Processing waits for a password to be entered.
User Response: Enter a password for the ADSM node.



ACO3813EPlease enter a log file name.

Explanation: An attempt was made to update the log file for the agent.
System Action: The "Activity Logging" tab on the "SQL Agent Settings" panel is redisplayed.
User Response: Enter a log file name.



ACO3815EFailed to start the SQL Enterprise Manager.

Explanation: An attempt was made to start the SQL Enterprise Manager. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the SQLEW.EXE file is installed in the appropriate directory.



ACO3816EFailed to create an Editor process.

Explanation: An attempt was made to open an edit session using the notepad utility of the dsm.opt file. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the notepad utility is installed in the appropriate directory. Also, be sure that the DSM.OPT file exists in the ADSM directory of either the ADSM Backup Client or the ADSM Administrative client, whichever you are trying to edit.



ACO3817ECould not set new image for SQL server tree item.

Explanation: The state icon may not reflect the current state of the SQL Server.
System Action: Processing continues.
User Response: Retry the operation.



ACO3818ECould not set new label for SQL server tree item.

Explanation: The label for the SQL Server tree item may not be up to date.
System Action: Processing continues.
User Response: Retry the operation.



ACO3823EThe ADSM API DLLs are at a lower version than the application. Install the current ADSM API DLLs to ensure correct operation.

Explanation: The current ADSM API DLL that is running is a lower version than what the SQL Agent needs. The SQL Agent is expecting the ADSM API DLL to be at least Version 3.
System Action: The SQL Agent command is terminated.
User Response: Install the Version 3 ADSM API.



ACO3825EThe ADSM API DLLs are at a lower release than the application. Install the current ADSM API DLLs to ensure correct operation.

Explanation: The current ADSM API DLL that is running is a lower release than what the SQL Agent needs. The SQL Agent is expecting the ADSM API DLL to be at least Release 1.
System Action: The SQL Agent command is terminated.
User Response: Install the Version 3, Release 1 ADSM API.



ACO3830INo SQL Servers are available.

Explanation: There are no SQL servers available to display in the tree.
System Action: Processing ends.
User Response: Check to make sure that SQL is installed properly.



ACO3831ECould not set new label for SQL Agent tree item.

Explanation: The label for the SQL Agent tree item may not contain the most current label.
System Action: Processing continues.
User Response: Retry the operation.



ACO3832ECould not set new image for SQL Agent tree item.

Explanation: The image for the SQL Agent tree item may not contain the most current image.
System Action: Processing continues.
User Response: Retry the operation.



ACO3833EThe SQL Server path cannot be found.

Explanation: An attempt was made to read the registry to determine where the SQL Server was installed. This attempt failed.
System Action: Processing ends.
User Response: Make sure you are running with the required permissions (local administrator). If it still fails, try reinstalling the product.



ACO3834ECould not initialize OLE.

Explanation: An attempt was made to initialize the OLE DLLs. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the correct version of the OLE system DLL's are installed.



ACO3835EThe ADSMConnect Agent is not properly installed. The ADSMConnect Agent for Microsoft SQL Server registry key could not be located. Please reinstall the agent.

Explanation: An attempt was made to read the registry to determine where the ADSMConnect Agent for Microsoft SQL Server was installed. This attempt failed.
System Action: Processing ends.
User Response: Reinstall the SQL Agent to ensure that the registry is set up properly.



ACO3836EThe ADSMConnect Agent for Microsoft SQL Server is not properly installed. %1 is a required file and could not be located. Please reinstall the agent.

Explanation: An attempt was made to start the SQL Agent. This attempt failed because one of the required files is missing. The missing part is identified in the message.
System Action: Processing ends.
User Response: Reinstall the SQL Agent to ensure that the registry is set up properly.



ACO3856EA password must be entered.

Explanation: There was a prompt to enter a password for the ADSM node. However, the password was not given.
System Action: Processing continues on the panel to enter the password for the ADSM node.
User Response: Reenter the password for the ADSM node.



ACO3857EA confirm password must be entered.

Explanation: On the password prompt panel, you must enter a confirm password.
System Action: Processing is brought back to the password panel for entry of a confirm password.
User Response: Enter a password to be used for confirmation.



ACO3858EA confirm password does not match password. Please retry.

Explanation: A confirm password was entered that does not match the new password.
System Action: Processing is brought back to the password panel for reentry of the confirm password.
User Response: Reenter the confirm password and make sure that the confirm password is the same as the new password.



ACO3862WThe ADSMConnect Agent for Microsoft SQL Server is not properly installed. Some functions may not work properly. The product should be reinstalled.

Explanation: An attempt was made to read the registry to determine where the SQL Agent was installed. This attempt failed.
System Action: Processing ends.
User Response: Reinstall the SQL Agent.



ACO3863EThere are no ADSM servers selected.

Explanation: A request has been made, but there was no ADSM server selected.
System Action: Processing ends.
User Response: Select an ADSM server and reissue the request.



ACO3866IThe default dsm entry is a requirement of the ADSM API and cannot be deleted.

Explanation: An attempt was made to delete the dsm entry from the list of ADSM servers. The dsm entry must exist as a result of a requirement by the ADSM API.
System Action: Processing ends. The GUI is displayed for further requests.
User Response: None.



ACO3869EA SQL server account name must be entered.

Explanation: Before you can login to the SQL server, a SQL server account name must be entered. This account name is not known.
System Action: Processing waits on the "SQL Server Login Information" panel.
User Response: Enter the SQL server account name.



ACO3870ICould not log on to SQL server. Please enter your SQL server connection information and try again.

Explanation: An attempt was made to connect to the SQL server. This attempt failed as a result of not knowing all of the SQL Server login information.
System Action: Process waits on the "SQL Server Login Information" panel.
User Response: Enter the correct information on the "SQL Server Login Information" panel and try again.



ACO3878IMore than one version of a database (%1) is selected for restore. This will cause a redundant restore operation. Are you sure you want to continue?

Explanation: An attempt was made to do a restore of the database in the message. However, more than one version was selected for restore.
System Action: Processing waits for a "Yes" or "No" answer.
User Response: Choose either "Yes", and the restore of the redundant databases choices will occur, or "No" to cancel the operation.



ACO3891ICannot determine if the original database object (%1) has a separate transaction log. Would you like to display the list of potential target databases anyway?

Explanation: An attempt was made to determine if the database object has an integrated log or not. This attempt failed.
System Action: Processing waits until a "Yes" or "No" response is chosen.
User Response: Choose either "Yes" or "No".



ACO3892INo database information is available. Please expand the tree view so that you see the list of individual databases.

Explanation: This is an internal error with a database structure not being filled in correctly.
System Action: Processing ends.
User Response: Try to stop and restart the GUI and retry the operation.



ACO3893IThere are no existing databases with integrated transaction logs that are large enough to hold the data from %1. A database object that matches the original type and size must be created before a restore can be completed.

Explanation: There are no databases with integrated transaction logs large enough to hold the data.
System Action: Processing ends.
User Response: A database object that matches the original type and size must be created before a restore can be completed.



ACO3894IThere are no existing databases without integrated transaction logs that are large enough to hold the data from %1. A database object that matches the original type and size must be created before a restore can be completed.

Explanation: There are no databases without integrated transaction logs large enough to hold the data.
System Action: Processing ends.
User Response: A database object that matches the original type and size must be created before a restore can be completed.



ACO3898IThe date entered was not valid and has been modified, please verify.

Explanation: The user entered an invalid 'Point in Time' date that was automatically updated to be a valid date.
System Action: Processing continues.
User Response: Verify that the new 'Point in Time' date is correct and continue processing accordingly.



ACO3899EAn internal error has occurred. The point in time restore date cannot be set.

Explanation: An internal error has occurred that prevents the setting of the point in time restore "stop at" date. The point in time restore cannot be performed.
System Action: Normal (non-point in time) restore processing continues.
User Response: Attempt the point in time restore using the command line agent. If this problem still occurs contact IBM ADSM support.



ACO3901EBase path cannot be located.

Explanation: An attempt was made to start the ADSM help program for the SQL Connect Agent. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the SQLDSM.HLP file exists in the appropriate directory. If it does not, you may want to reinstall the ADSMConnect Agent for Microsoft SQL Server.



ACO3902EFailed to create winhelp process.

Explanation: An attempt was made to show the SQLDSM.HLP file. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the SQLDSM.HLP file is installed to the appropriate directory. If not, it may be necessary to reinstall the agent code so that the registry is set up correctly.



ACO4201ERemote error type detected in local error handler

Explanation: An error was encountered with the ADSM API.
System Action: Processing ends.
User Response: Review the other messages regarding this error to get more information about the problem.



ACO4202EService error encountered, rc = %1!lu!

Explanation: An attempt was made to either stop or open a Microsoft NT Service. This attempt has failed.
System Action: Processing ends.
User Response: Identify the problem further by checking the circumstances that generated this message and retry the operation.



ACO4203ETimed out while attempting to logon to the ADSM server.

Explanation: An attempt was made to logon to the ADSM Server. However, the connection was not made in the allowable time.
System Action: Processing ends.
User Response: Determine if the ADSM Server is up and running. If it is, try again. Otherwise, wait for the needed ADSM Server to be running.



ACO4204WAvailable data exceeds the amount of available memory. Try reducing the amount of stored data.

Explanation: There is more information than that which is shown. However, there is no available memory to receive the information.
System Action: Processing continues with the incomplete information.
User Response: Try to obtain more memory and retry the command.



ACO4205ETimed out while attempting to logon to the SQL server.

Explanation: An attempt was made to logon to the SQL Server. However, the connection was not made in the allowable time, which is 60 seconds.
System Action: Processing ends.
User Response: Determine if the SQL Server is up and running. If it is, try again. Otherwise, wait for the needed SQL Server to be running.



ACO4206ECaught exception while issuing dsminit.

Explanation: An attempt was made to run an initialization routine. This attempt failed.
System Action: Processing ends.
User Response: Retry the operation. If the problem persists, please contact IBM ADSM support and indicate how this message was received.



ACO4207ENo matching objects were found.

Explanation: An attempt was made to query a database object. This attempt failed as there were no objects found matching the input.
System Action: Processing ends.
User Response: Reenter the command indicating a database object that exists.



ACO4208EA database name is required.

Explanation: A database name is required to do the function requested.
System Action: Processing ends.
User Response: Reenter the command making sure that a database is specified.



ACO4209EA named pipe name is required.

Explanation: An attempt was made to do the requested function. However, the pipename to the SQL server is not set.
System Action: Processing ends.
User Response: Retry the operation. If the problem still occurs, contact IBM ADSM support and let them know how this error was obtained.



ACO4210EFailed to connect to SQL server.

Explanation: An attempt was made to connect to a SQL server. This attempt failed.
System Action: Processing ends.
User Response: There are several reasons why a connection could not be made to the SQL server:

Check which of these items caused the failure, and correct the problem.



ACO4211ESQL EXEC failed.

Explanation: An attempt was made to either use a SQL database or to send a command to the SQL server. This attempt failed.
System Action: Processing ends.
User Response: There could be a problem with the SQL Server permissions. Determine if this is the case. Retry the operation. If the problem still occurs contact IBM ADSM support and report how this error was obtained.



ACO4212EAn incremental backup cannot be performed because the named database does not have a separate transaction log.

Explanation: An incremental backup was requested however the database does not have a separate transaction log.
System Action: Processing ends.
User Response: Only a full backup is allowed for this particular database.



ACO4213ECould not build a SQL command.

Explanation: An attempt was made to build a command to send to the SQL server. This attempt failed.
System Action: Processing ends.
User Response: Retry the operation. If the failure persists, contact IBM ADSM support and report how the error occurred.



ACO4214EThe input buffer was not large enough to hold the complete list of databases.

Explanation: An attempt was made to get a list of the databases. This attempt failed as a result of a buffer being defined that was not large enough.
System Action: Processing ends.
User Response: Retry the operation. If the problem still occurs, contact IBM ADSM support and report how the error occurred.



ACO4215EUnable to obtain attributes for the specified SQL database.

Explanation: An attempt was made to get the attributes for a SQL database. This attempt failed.
System Action: Processing ends.
User Response: Stop and restart the SQL Server. Retry the operation. If the problem persists, contact IBM ADSM support and report how the error occurred.



ACO4216ECould not connect to SQL Server. SQL server (%1) was not found on this machine.

Explanation: An attempt was made to start the SQL Server listed in the message. This attempt failed.
System Action: Processing ends.
User Response: Be sure that the SQL server exists. Also, be sure that the SQLSERVR.EXE file exists.



ACO4217EUnable to obtain the name of the local SQL server.

Explanation: An attempt was made to get the name of the local SQL server. The attempt failed.
System Action: Processing ends.
User Response: Retry the operation. If the problem persists, contact IBM ADSM support and report how the error occurred.



ACO4218ECould not open the ADSM client message file (dscameng.txt). Ensure that this file is installed in the correct location.

Explanation: An attempt was made to send a command to the ADSM API. However, the API code could not find the dscameng.txt file.
System Action: Processing ends.
User Response: Make sure that the dscameng.txt file exists. If it does not, try reinstalling the product.



ACO4219EYour ADSM password has expired. You can update your ADSM password from the Server | ADSM Server | Change password menu item.

Explanation: An attempt was made to connect to the ADSM server. However, the attempt failed because the client node password has expired.
System Action: Processing ends.
User Response: The client node password needs to be changed. The message lists a method that can be used to update the password.



ACO4227ENo matching SQL databases were found.

Explanation: An attempt was made to get a list of SQL databases. However, there were none found.
System Action: Processing ends.
User Response: Reenter the database name to one that exists.



ACO4228EError retrieving agent error code.

Explanation: An error code was sent to the error handler that currently does not exist in the error handler routine.
System Action: Processing ends.
User Response: Retry the operation. If the error persists, contact IBM ADSM support and let them know how the error occurred.



ACO4229EUnable to find system message.

Explanation: An attempt was made to determine what the last system message was. This attempt failed.
System Action: Processing ends.
User Response: It is possible that the system dll is not current. Check and make certain that it is current.



ACO4230EThe start of the SQL server failed.

Explanation: An attempt was made to start the SQL Server. This attempt failed.
System Action: Processing ends.
User Response: View the other messages for an indication as to the problem. Also, view the SQL Server Error Log as to an indication of what the problem may be.



ACO4231EAn incremental restore cannot be performed because the named database does not have a separate transaction log.

Explanation: An incremental restore was requested however the database does not have a separate transaction log.
System Action: Processing ends.
User Response: Only a full restore is allowed for this particular database.



ACO5201ECould not open file %1.

Explanation: An attempt was made to open the file listed in the message. This attempt failed.
System Action: Processing ends.
User Response: Determine if this file exists. Be sure that there is enough room for this file if it is being created.



ACO5202EThere is a syntax error on line %1!d! of the options file: %2 Line Contents: %3 You will need to correct the error before continuing.

Explanation: While reading the options file, it was discovered that there was a syntax error. This error is listed in the message.
System Action: Processing ends.
User Response: Update the options file with the correct syntax.



ACO5203EError reading file: %1. Processing will not continue.

Explanation: There was an attempt to read the file listed in the message. This attempt failed.
System Action: Processing ends.
User Response: Determine if the file is read-only. Determine if the file still exists.


[ Top of Page | Previous Page | Next Page | Table of Contents ]