Client Agent Error Messages

The exceptions to this are:

When running a stand-alone audit
When installing the Client Agent via the email package
When CSetup is run with the /diag switch (show diagnostics)

In the first two cases it is assumed that someone, possibly an end user, actively initiated the activity and will be waiting for some feedback. (The email package can be made silent, see Appendix: CSETUP.INI.) CSetup produces no messages unless the /diag switch is present on its command line. If used the /diag switch should be the first parameter on the CSETUP.EXE command line.
Error number ranges reserved for problem groups:

C000-C049 Reserved
C050-C099 ZipUp problems (ZipUp is used to create ESetup.EXE)
C100-C199 Client Setup problems
C200-C249 Client Agent problems
C250-C299 Client Agent alerts displayed at the Control Center
C300-C399 Reserved
C400-C499 Reserved
C500-C599 Reserved
C600-C699 Reserved
C700-C799 Reserved
C800-C899 Reserved
C900-C999 Generic problems

C200: Incorrect version of <filename>. Please contact your network administrator.
The Client Agent could not load because one of the library files it needed, <filename>, was not present or was the wrong version.

This problem may occur if the installation directory on the server contains an incompatible mix of client files. You should reinstall the client files on the server and force the clients to reinstall (use the /reinstall switch on CSetup.EXE).


C207: Valid INFO.RP0 file not found.

The Client Agent cannot function unless this file is present in either the Shared Folder or the Local Folder. If the file is present it may be that it does not contain valid information.
C208: Local folder not defined in CLIENT.DAT. Please contact your network administrator.

The Client Agent requires a local message folder be defined in CLIENT.DAT (LocalFolder in the [COMMS] section). Depending on the communication mechanism being used the Client Agent may write message files to this folder.


C209: Server shared folder not defined in CLIENT.DAT. Please contact your network administrator.

The Client Agent communicates with the Centennial database via message files. These files are written to a shared folder usually located on a network server. The Client Agent reads the name of this folder from the CLIENT.DAT file (SharedFolder entry in the [COMMS] section).

You should be asked to specify the location of the shared folder when you install the Control Center. The Control Center Setup program writes this to the master CLIENT.DAT file. CSetup.EXE copies this file to each client. One possible cause of this error is that the user has deleted the copy of CLIENT.DAT on his own computer.

This error may also be given by the DOS Client Agent when SharedFolder2 is not defined. SharedFolder2 is used to specify an alternate route to the shared folder via a mapped drive instead of the UNC path specified in SharedFolder.


C210: It was not possible to send a message file to the server shared folder "<folder name>". Please contact your network administrator.

The Client Agent communicates with the Centennial database via message files. These files are written to a shared folder, <folder name>, usually located on a network server. In this case the Client Agent was unable to create one of these message files. This may be because the network connection is not functioning correctly.

The <folder name> should be a UNC path to a directory on the server to which all clients have all file rights (read, write, scan and delete). There should be sufficient disk space available in this directory for all clients to write messages there. As a guide, allow 150 KB per client.


C211: The Centennial Discovery Client is already running on this computer.

This message will be shown if a user tries to use the standalone Client to audit a computer which has Client Agent already installed and running. Only one instance of the Client Agent may be run at a time. The user should either use the installed Client Agent to audit this computer via the Control Center, or terminate the installed Client and retry the standalone audit. (The installed Client may be terminated via the Windows task manager (95/98/NT) or via the Windows Control Panel Services (NT) or by removing CAgent16.EXE from load= entry in WIN.INI (3.x).)


C250: The user cancelled an audit before it was completed.

This alert is displayed at the Control Center: during the audit of a client computer the user clicked the Stop Audit button on the scan progress dialog. Therefore the audit information held for this client computer is incomplete.

You may wish to request a new audit for this computer. You can hide the Stop Audit button on the progress dialog from the User Interaction tab of the File|Options… dialog. You can also choose to hide the entire progress dialog from this tab.

C251: Not enough memory to complete audit.

There was insufficient memory available to audit this client computer. Therefore the audit information held for this client computer is incomplete.

This may have been a temporary problem that will not reoccur. Try requesting a new audit for this computer.
C260: Out-of-date Client Agent failed to automatically upgrade itself.

Every time the Client Agent starts up (when the user restarts his computer) it checks the Build number held in the CLIENT.DAT file in the directory from which the Client Agent was originally installed. If this Build number differs from the number held in the local copy of CLIENT.DAT the Client Agent attempts to launch the CSetup.EXE in the original install directory in order to reinstall itself. If this operation is unsuccessful (e.g. CSetup.EXE is not present in that directory) the Client Agent sends error C260 to the Control Center.


C261: Audit schedule could not be set.

This alert is displayed at the Control Center: the Client Agent received an Audit Schedule message but it was not able to apply the schedule either because the given schedule was invalid (unlikely) or because it was not possible to get a valid current time and date on the client computer (which can happen on older computers).


C290: Registration message successfully written to <file name>.

This is not an error condition. It is simply confirmation that the Client Agent has successfully written the registration message to the given <file name>.


C900: Error <number>. Please contact your network administrator.

Error <number> occurred for which there is no associated message. Under normal circumstances, when the product is correctly installed and configured, you should not see error C900. It may be a transient problem. If it persists you should reinstall the product.

[This is an “internal error occurred” sort of message. It basically means one bit of code has detected that some other bit of code did something it shouldn’t have. E.g. a function that should return 1, 2 or 3 actually returned 4.]