Table Of Contents
Troubleshooting the Installation
Logging In After Upgrading
Understanding Installation Messages
Accessing the CiscoWorks Server
FAQs On Service Packs
Troubleshooting the Installation
This appendix provides troubleshooting information for Campus Manager 4.0.6 installation and setup.
This appendix contains:
•
Logging In After Upgrading
•Understanding Installation Messages
•Accessing the CiscoWorks Server
•FAQs On Service Packs
Logging In After Upgrading
If the Login window on the CiscoWorks Home page does not appear correctly when you try to log in for the first time after upgrading, clear your browser cache and re-enter the server URL in your browser.
To clear the browser cache in Microsoft Internet Explorer:
Step 1 Select Tools > Internet Options.
The Internet Options dialog box appears.
Step 2 Click the General tab.
Step 3 Click Delete Files and click OK in the Delete Files dialog box.
To clear the browser cache in Netscape Navigator:
Step 1 Select Edit > Preferences.
The Preferences dialog box opens.
Step 2 Select Advanced > Cache.
Step 3 Click Clear Cache and click OK.
Understanding Installation Messages
After verifying that the correct files are installed, check the C:\Ciscoworks_setup002.log file (or the log file with the highest number, for example Ciscoworks_setup003.log) for installation errors.
The following types of installation messages might appear:
•Information messages—Display important details
•Warning messages—Inform you that something might be wrong with a particular process, but the process will complete
•Error messages—Inform 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
|
CiscoWorks installation cannot proceed because you are not logged in as an administrator.
|
You are not logged in to Windows 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 Manager 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 Manager 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.
|
1. Run the file system checking utility.
2. Repeat the installation.
|
Cannot stop service servicename.
|
The installation (or reinstallation) tried to stop service servicename unsuccessfully.
|
1. Select Control Panel > Services and try to stop service servicename manually,
2. Continue installing or uninstalling.
|
UseDLL failed for dll.
|
dll is supposed to be available at any time for any process, but Windows could not load it.
|
•Check permissions on Windows System32. If the dll is secure.dll or r_inst.dll, check product installation medium for errors.
Or
•Reinstall Windows.
|
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 you may 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 Manager is destroyed.
This message might appear during reinstallation.
|
Contact your support representative.
|
You have less than 1M free space on drive name. Free up some space and try again.
|
Insufficient drive space for temporary installation files.
|
1. Make more drive space available.
2. Rerun the installation program.
|
This program requires to run on Windows.
|
You attempted to install on a system that does not have Windows with Service Pack 3 installed.
|
Install Campus on a Windows Professional system that is not configured as a PDC or BDC.
|
Could not determine the type of operating system. Campus Manager can be installed only on Windows with SP3.
|
Installation program could not determine which operating system is running.
|
Install on a Windows 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).
We recommend 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.
(The second sentence might also appear as "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 user groups. This prevents setup of Campus Manager security.
|
1. Check the Windows operating system. Reinstall Windows if necessary.
2. Rerun installation.
|
Cannot determine the local Everyone group.
|
The installation program cannot find one of the built-in Windows user groups.
|
1. Check the Windows operating system. Reinstall Windows if necessary.
2. Rerun installation.
|
Failed to set file permissions.
|
The installation program cannot set file permissions. The most likely causes are:
•The account you used to log in to the system has insufficient permissions.
•The drive on which you are installing the product has a FAT file system.
|
1. Fix problem.
2. Rerun installation.
|
<...> is already running! Wait for it to finish and press the OK button.
|
One of the installation subtasks is still running.
|
1. Wait for subtask to finish running.
2. Click OK to proceed.
|
Unable to create/open log file.
|
The installation program could not create or open installation log file (in the root directory of the drive on which you are installing) named Ciscoworks_setupxxx.log, where xxx is a sequential number starting from 001).
|
This may have occurred because of lack of disk space or write protection on the file.
1. Determine why file could not be created or opened and correct the problem.
2. Rerun installation.
|
Error creating user bin <... more info here> See troubleshooting section in the User Manual
|
The installation program could not create the user account bin.
|
1. Fix problem.
2. Rerun installation.
|
Cannot 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 CiscoWorks Server
The CiscoWorks server uses port 1741 by default (443 if SSL is enabled). 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 CiscoWorks 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:
•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 send 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.
FAQs On Service Packs
The following are the Frequently Asked Questions (FAQs) on Service Packs.
Q. What is an SP? Why should I install the latest SP?
A. SP (Service Pack) for Campus Manager is a downloadable package containing a collection of updated files to provide you with support for new devices. In addition, the SP contains fixes to certain known problems, as well as fixes to newly discovered problems. SPs are available for downloading from Cisco.com.
Q. From where can I download a Service Pack?
A. To retain support for new devices, we recommend that you download and install the latest SP for Campus Manager from:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-campus
Q. How do I know which version of SP I have installed?
Q. To check the version of SP installed on your system, from the CiscoWorks Homepage, go to Software Center > Software Update > Campus Manager.
