|
|
This appendix provides troubleshooting information for Campus Manager (Campus) installation and setup.
This appendix contains:
If the Login Manager dialog box on the CiscoWorks2000 desktop does not appear correctly when you try to log in for the first time after upgrading, clear your browser cache as follows, then reenter the server URL in your browser.
For Microsoft Internet Explorer:
Step 2 Select the General tab.
Step 3 Click Delete Files, then click OK in the Delete Files dialog box.
For Netscape Navigator:
Step 2 Select Advanced>Cache.
Step 3 Click Clear Memory Cache, then click OK in the Memory Cache dialog box.
Step 4 Click Clear Disk Cache, then click OK in the Disk Cache dialog box.
After verifying that the correct files are installed, check the c:\cw2000_in002.log file (or the log file with the highest number, for example cw2000_in003.log) for installation errors.
The following types of installation error messages might appear:
Table A-1 shows error messages that might occur during installation and describes the reasons for the errors.
| Message | Reason for Message | User Action |
|---|---|---|
CiscoWorks2000 installation cannot proceed because you are not logged in as an administrator | You are not logged in to Windows NT with administrator privileges. | Log in with local administrator privileges and try installing again. |
Decompression failed on <file>. The error was for <error code per CompressGet> | If Campus was downloaded, a transmission error occurred, or installation media is damaged. | Retry the download. If you still have errors, contact your technical support representative. |
General file transmission error. Please check your target location and try again. Error number: <error code> | If Campus was downloaded, a transmission error might have occurred. | Retry the download. If you still have errors, contact your technical support representative. |
Unable to write <infoFile> or Unable to create <infoFile> | A file-write operation failed. | Run the file system checking utility, then repeat the installation. |
Cannot stop service <servicename> | The installation (or reinstallation) tried to stop service <servicename> unsuccessfully. | Select Control Panel > Services and try to stop service <servicename> manually, then proceed with (un)installing. |
UseDLL failed for <dll> | <dll> is supposed to be available at any time for any process, but NT failed to load it. | Check permissions on Windows NT System 32. If the <dll> is secure.dll or r_inst.dll, check product installation medium for errors. or Reinstall Windows NT. |
<function> failed: DLL function not found | <dll> is supposed to be available at any time for any process, but NT failed to load it. | Check permissions on Windows NT System 32. If <dll> is secure.dll or r_inst.dll, check product installation media for errors. or Reinstall Windows NT. |
OpenFile failed: <pathname> | A fileopen operation failed. | Run the filesystem checking utility, then repeat installation. |
ProtectFile failed: <file>: error. WWW admin security may be incomplete | Setting file permissions failed because user might not be allowed to change them. | Log in as administrator. |
Launch of isql script failed | The existing database file is broken, or the previous version of Campus is destroyed. (This message might be issued during reinstallation.) | Contact your support representative. |
You have less than 1M free space on <drive name>. Please free up some space and try again. | Insufficient drive space for temporary installation files. | Make more drive space available, then rerun the installation program. |
This program requires to run on Windows NT. | You attempted to install on a system that does not have Windows NT 4.0 installed. | Install Campus on a Windows NT 4.0 Workstation or Windows NT 4.0 Server system that is not configured as a PDC or BDC. |
Unable to determine the type of operating system. Campus can be installed only on NT Workstation or NT Server. | Installation program could not determine which operating system is running. | Install on a Windows NT 4.0 Workstation or Windows NT 4.0 Server system that is not configured as a PDC or BDC. |
Physical memory is <...>M Paging File Size is: File Size is: <...>M(initial), <...>M(maximum). It is recommended that initial paging file size is bigger than physical memory and maximum paging file size is at least twice as big as physical memory. (Maximum paging file size might not appear.) | The paging file size is smaller than recommended. | Finish installation, then increase paging file size. |
There is not enough space available on the disk <drive>: This drive has <...> bytes in a cluster. Total required <...> clusters (<...> bytes), only <...> clusters (<...> bytes) available. Please free up some space or change the target location to a different disk. (Second sentence might be as follows instead of as above: "Please free up some space and rerun installation.") | Insufficient disk space available on drive <drive> to install the product. | Create additional free space on the drive or install on a different drive. |
Cannot determine the local Administrators group | Installation program cannot find one of the built-in Windows NT user groups. This prohibits setup of Campus security. | Check the Windows NT operating system. Reinstall Windows NT if necessary, then rerun installation. |
Cannot determine the local Everyone group | The installation program cannot find one of the built-in Windows NT user groups. This prohibits the setup of Campus security. | Check the Windows NT operating system. Reinstall Windows NT if necessary, then rerun installation. |
Failed to set file permissions. | The installation program is unable to set file permissions. The most likely causes are:
| Fix problem, then rerun installation. |
<...> is already running! Wait for it to finish and press the OK button below | One of the installation subtasks is still running. | Wait for subtask to finish running, then click OK to proceed. |
Unable to create/open log file. | Installation program was unable to create or open installation log file (in the root directory of the drive on which you are installing) named cw2000_inxxx.log, where xxx is a sequential number starting from 001). | Determine why file could not be created or opened, fix problem, then rerun installation. Common causes of this problem are lack of disk space or write protection on the file. |
Error creating user bin <... more info here> Refer To the troubleshooting section in user manual | The installation program could not create the user account bin. | Fix problem, then rerun the installation. |
Can not find script to upgrade database | There was a problem with the database upgrade. | Contact your technical support representative. |
Database upgrade failed | There was a problem with the database upgrade. | Contact your technical support representative. |
Database upgrade result unknown | There was a problem with the database upgrade. |
The CiscoWorks2000 server uses port 1741 by default. If you receive an error message that an alternative port is used instead, verify that you entered the correct URL for the server:
http://server_name:port
where server_name is the name of the machine on which CiscoWorks2000 was installed and port is the port number 1741 or the number supplied during installation.
If you still cannot access the server, enter the following command at a DOS prompt to make sure your server is running:
ping server_name
If you get a message that the server is "alive" and get a proxy error when you try to connect to the server, make sure the proxy is set up correctly. If your server is configured to use a proxy server outside the firewall, you will get proxy errors if you configured the proxy to ignore requests to a certain machine, set of machines, or domain.
You specify a proxy server in Netscape Navigator under Edit>Preferences>Advanced>Proxies and in Internet Explorer under Tools>Internet Options>Connections>LAN Settings.
Your proxy is set up incorrectly if:
To improve system performance for Campus, consider downloading the Client Application Manager, to install Java classes on your local machine. Refer to "Optimizing Performance with CAM (Optional)" section.
Posted: Wed Mar 29 13:32:44 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.