Table Of Contents
Troubleshooting the Installation
Logging In After Upgrading
Understanding Installation Error Messages
Accessing the CiscoWorks2000 Server
Troubleshooting the Installation
This appendix provides troubleshooting information for Campus Manager (Campus) installation and setup.
This appendix contains:
•
Logging In After Upgrading
•Understanding Installation Error Messages
•Accessing the CiscoWorks2000 Server
Logging In After Upgrading
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 1 Select Tools > Internet Options.
The Internet Options dialog box appears.
Step 2 Select the General tab.
Step 3 Click Delete Files, then click OK in the Delete Files dialog box.
For Netscape Navigator:
Step 1 Select Edit > Preferences.
The Preferences dialog box appears.
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.
Understanding Installation Error Messages
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:
•Information messages, which tell you important details
•Warning messages, which tell you that something might be wrong with a particular process, but the process will complete
•Error messages, which tell you that a particular process could not complete
Table A-1 shows error messages that might occur during installation and describes the reasons for the errors.
Table A-1 Installation Error Messages
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 2000 with administrator privileges.
|
Log in with local administrator privileges and try installing again.
|
Campus Manager is not SSL compliant and will not work as SSL is enabled on your server.
Disable SSL and start the installation. You can disable SSL by running the following script from the command line: <perl ConfigSSL.pl -disable> from
<install-location>\lib\web directory.
|
You are trying to install Campus Manager on an SSL (Secure Socket Layer) enabled application suite.
|
Disable SSL on the CiscoWorks2000 server before you install Campus Manager.
You can disable SSL by running the following script from the command line: <perl ConfigSSL.pl -disable> from
<install-location>\lib\web directory.
|
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 installing or uninstalling.
|
UseDLL failed for dll.
|
dll is supposed to be available at any time for any process, but Windows failed to load it.
|
Check permissions on Windows 2000 System32. If the dll is secure.dll or r_inst.dll, check product installation medium for errors.
or
Reinstall Windows 2000.
|
OpenFile failed: pathname
|
A file open operation failed.
|
Run the files system 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 2000.
|
You attempted to install on a system that does not have Windows 2000 with Service Pack 2 installed.
|
Install Campus on a Windows 2000 Professional system that is not configured as a PDC or BDC.
|
Unable to determine the type of operating system. Campus can be installed only on Windows 2000.
|
Installation program could not determine which operating system is running.
|
Install on a Windows 2000 Professional 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 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 2000 user groups. This prevents setup of Campus security.
|
Check the Windows 2000 operating system. Reinstall Windows 2000 if necessary, then rerun installation.
|
Cannot determine the local Everyone group.
|
The installation program cannot find one of the built-in Windows 2000 user groups. This prevents the setup of Campus security.
|
Check the Windows 2000 operating system. Reinstall Windows 2000 if necessary, then rerun installation.
|
Failed to set file permissions.
|
The installation program is unable to set file permissions. The most likely causes are:
•Account you used to log in to the system has insufficient permissions.
•Drive on which you are installing the product has a FAT file system.
|
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.
|
Contact your technical support representative.
|
Accessing the CiscoWorks2000 Server
The CiscoWorks2000 server uses port 1741 by default. If you receive an error message informing you that an alternative port is used instead, verify that you entered the correct URL for the server:
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:
If you get a message informing you 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:
•You receive an error message informing you that you are using a proxy outside the firewall.
•The proxy server recognizes www-int as an internal server, so it does not proxy requests to that server.
•You set up a new internal server, www-nms, but when you make a request to the proxy server, it does not recognize www-nms as an internal server and proxies the request.
•The proxy server outside the firewall tries to request data from a server inside the firewall, and the request is blocked.
•You get a "Connection Refused" error from the proxy server.
