H3C Technologies H3C Intelligent Management Center - Manual (Page 117)

110
When IMC database is installed on a remote database server (Windows Server 2008 or Windows
Server 2008 R2), how to solve the abnormality occurred during the deployment process?
This is because the user that enabled the SQL Server on the remote database server is not assigned the
write access to the IMCdata folder in the IMC installation path.
To solve the problem, manually change the access right of the IMCdata folder on the remote database
server.
During the component deployment process, an error message “Deployment is stopped with error. For
details, see the log.” appears, and “Execute database script error!” is displayed in the system log. Then
check the specified log file according to the prompt information, and only the error information that the
object dbo.qv.id already exists is displayed. How do I solve the problem?
Log in to the Query Analyzer of SQL Server as an sa user and execute the following commands:
use model
EXEC sp_droptype 'qv_id'
Deploy the component again.
When installing IMC on a PC running Windows Server 2008 R2, the system indicates the Windows
Installer cannot be installed, as shown in the following figure. How do I solve this problem?
On the Windows Installer dialog box, click Browse. On the dialog box for selecting a file, search any
folder whose name contains digits and letters abcdef in the root directory, select file vc_red.msi in the
folder, and click OK. Then, you can continue the installation.
Figure 96 Windows Installer
In Linux, how can I solve the problem that the JavaService is closed when Xwindows is closed?
Use service IMCdmsd start to start the JavaService.
The report cannot work properly when IMC adopts distributed deployment in Linux with the service
components deployed on subordinate servers, and the master server uses Oracle database on a remote
database server. What to do to solve the problem?
1. Check the configuration files in \common\conf\server-addr.xml of the IMC installation path, and
the database names of the components on the subordinate servers.
Take the following environment for example: