Topics | How To | Tasks | Troubleshoot
Cell Registration
How do I register a Cell which is already registered in another CommNet Server
I have registered my Cell(s) and I do not see any data on my reports and summaries
Cell Updates
Some of the Cells do not get updated at the specified hour
Remote Administration
Cannot open the CommCell Console using the Remote Administration option in the CommNet Browser
Cannot open the QSMCell Console using the Remote Administration option in the CommNet Browser
Cannot open the CommNet Browser Remotely
Cell Synchronization
My synchronization with a QSMCell fails
Required Capability: See Capabilities and Permitted Actions
Click OK. The newly registered Cell is displayed in the Cell Registration dialog box.
|
You have not run any jobs in within the Cell
Once the Cells are synchronized with the CommNet Server, the data from the jobs should be visible in the appropriate reports and summaries.
The latest Service Pack may not be installed on the CommServe computer
If necessary, install the latest Service Pack on the CommServe computer.
Synchronize the CommCell as described in Synchronize Cells.
Necessary Services may not be running on the CommServe or QSM Server computer
The services used are described in CommNet Services.
For a CommServe computer, check the Bull Calypso Client Event Manager Service and if necessary restart the service. (For information on starting this service, see the CommServe documentation.)
For a QSM Server, launch Service Control Manager and verify that services are running; if necessary, restart QSM Services.
If necessary, synchronize the Cell(s) as described in Synchronize Cells.
|
A different Data Collection time may be setup for the Cell
Automatic updates from a Cell are based on the time established for the Cell in the Cell Data Collection Policy. Check the Data Collection Policy dialog box to verify the data collection periods established for the Cell. To update the information from the Cell(s) immediately, see Synchronize Cells.
CommCell Update time is based on the time in the CommCell computer
The CommCell update time is based on the CommCell's time. If the time in the CommCell computer is not exactly the same as the CommNet Server, the update process may take place before or after the general update time setup for the other computers.
The QSM Server update time is based on the data collection time of the QSM Server computer
If the CommNet Server synchronizes with a QSMCell that has not run data collection since the last time that Cell was synchronized, the CommNet Server may not be updated with new information from the QSMCell. Try setting the data collection policy to coincide with the QSM data collection schedule.
The Remote Administration option in the CommNet Browser opens the CommCell Console as a Remote Web-Based Application.
The following components are required to open the CommCell Console remotely:
If one or more of these components are not available, use the following procedure to access the CommCell Console from the CommNet Browser:
HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\ Galaxy\Platform Information\<MachineName>\CommServe
Create the following entry as a String value: SGalaxyAlias
Assign the following value: /galaxy
The CommCell does not have the correct URL, or a URL does not exist
Change the URL of the CommCell Cell by following the procedure Change the URL for Launching the CommCell Console for Remote Administration or contact your software administrator.
Your version of Internet Explorer blocks pop-ups
Make sure that your version of Internet Explorer does not block pop-ups.
You don't have the latest service packs installed
Make sure you have the latest service packs installed for the CommServe you are trying to launch.
The Remote Administration option in the CommNet Browser opens the QSMCell Console as a Remote Web-Based Application.
The following components are required to open the QSMCell Console as a Remote Web-Based Application:
The QSMCell does not have the correct URL, or a URL does not exist
Change the URL of the QSMCell by following the procedure Change the URL for Launching the QSM Console for Remote Administration or contact your software administrator.
Your version of Internet Explorer blocks pop-ups
Make sure that your version of Internet Explorer does not block pop-ups.
You are not using the correct version of JRE (Java Run Time Environment)
Make sure that the appropriate version of JRE is installed on the computer. Verify that you have the correct version from the Add or Remove Programs window on your computer. Also, make sure that you do not have multiple versions of the JRE software on your computer. If you need to install JRE, make sure that you have the proper administrative rights on the computer you are using to install the JRE.
The CommNet Server does not have the correct URL, or a URL does not exist
Change the URL of the CommNet Server by following the procedure Change the URL Used for Launching the CommNet Browser as an Applet or contact your software administrator.
You do not have a valid user name and password to open the CommNet Browser
Contact your software administrator.
The CommNet Browser is not installed on the CommNet Server
The CommNet Browser must be installed on the CommNet Server. If the CommNet Browser is installed after the CommNet Server is installed, you must manually create a web alias for the CommNet Server. This can be done by creating a virtual directory pointing to the browser location on the CommNet Server.
Your version of Internet Explorer does not allow you to launch the Java applet
Try using a different version of Internet Explorer or use another computer to launch the Java applet.
You installed the CommNet Server on a virtual server and configured IIS for web administration, but the CommNet Browser Applet will not start
This applies to Windows Server 2003 cluster installations of the CommNet Server only. In this case, some IIS properties need to be modified in the Windows Internet Information Service Manager.
This will enable the CommNet Browser to be launched as an applet from the virtual server.
The QSM Server is busy updating its database
One of the most likely reasons is that the CommNet Server is attempting to push billable entities and cost categories to the QSM Server, and the QSM Server must clean up its own billing entities and cost categories, and insert the new billing and costing data into its database. If the Cell synchronization fails as a result of this, try waiting a while, and then synchronize with the QSMCell again by following the procedure Synchronize Cells.