Main causes of Web browser errors and actions to be taken

In the event of an error, check the execution environment for the Web browser used by Asset Information Manager Subset for any errors.

This subsection describes the main causes and actions to be taken for each Web browser error.

Organization of this subsection: (1) Web browser might have frozen or terminated abnormally; (2) A communication error has occurred; (3) GUI is not displayed correctly; (4) Login window cannot be displayed; (5) Login fails; (6) File download processing fails; (7) Graphs cannot be displayed

(1) Web browser might have frozen or terminated abnormally

There might be an error in the execution environment for the Web browser, or the registry and required DLL might have been corrupted.
Restore the correct environment, or re-install the Web browser.
There might be a problem with the Web browser version.
Use Microsoft Internet Explorer 6 SP1 or later, Windows Internet Explorer 7, or Windows Internet Explorer 8.
A plug-in might have failed, or there might be a problem with a plug-in.
If an updated version has been released, install that version of the Web browser.
A control contained in the contents might have failed, or there might be a problem in a control contained in the contents.
If an updated version has been released, install that version of the Web browser.
A script might have failed or there might be a problem in a script.
Check the operating status. If an updated version has been released, install that version of the Web browser.
There might be a problem in the Web browser.
If an updated version has been released, install that version of the Web browser.

(2) A communication error has occurred

The routing table might have been corrupted, or a network failure might have occurred due to contention with other software for a communication port.
Restore the correct routing table, or set up the communication port again so that contention will not occur with other software.
Microsoft Internet Information Services or the proxy server might not be running or an error might have occurred.
Make sure that operation is normal.

(3) GUI is not displayed correctly

The Asset Information Manager Subset database might have been corrupted because of a change made to information by unauthorized access or due to corruption of the database's logical structure.
If you have a backup, use it to restore the Asset Information Manager Subset database.
If you do not have a backup, initialize the Asset Information Manager Subset database and re-create it.
Active scripting might be set to Disable.
In Microsoft Internet Explorer, in the Security Settings dialog box (which is displayed by clicking the Custom Level button on the Security page in the Internet Options dialog box), enable the Active scripting option.
The Binary and script behaviors option might be set to Disable (in Windows Server 2003 SP1 or later or Windows XP SP2 or later).
In Microsoft Internet Explorer, in the Security Settings dialog box (which is displayed by clicking the Custom Level button on the Security page in the Internet Options dialog box), enable the Binary and script behaviors option.

(4) Login window cannot be displayed

World Wide Web Publishing Service might not be running.
Make sure that World Wide Web Publishing Service is running.
Active scripting might be set to Disable.
In Microsoft Internet Explorer, in the Security Settings dialog box (which is displayed by clicking the Custom Level button on the Security page in the Internet Options dialog box), enable the Active scripting option.

(5) Login fails

Allow per-session cookies might be set to Disable.
Enable the Allow per-session cookies option.
Submit nonencrypted form data might be set to Disable.
Enable the Submit nonencrypted form data option.
Allow META REFRESH might have been set to Disable (in Windows Server 2003).
Enable Allow META REFRESH.
The Asset Information Manager Subset server might not be connected to the Asset Information Manager Subset database.
Make sure that the Asset Information Manager Subset server is connected to the Asset Information Manager Subset database.

(6) File download processing fails

The extension of the file to be downloaded might not have been registered as MIME type (in Windows Server 2012, Windows Server 2008 or Windows Server 2003).
Register the extension of the file to be downloaded as MIME type.
In the Microsoft Internet Explorer settings, File download might be set to Disable.
Enable File download.

(7) Graphs cannot be displayed

The Microsoft Office Web component might not have been installed. Install the Microsoft Office Web component on the PC where graphs are to be displayed.
To install the Microsoft Office Web component, either install Microsoft Office 2003 or earlier, or download the component from the Microsoft home page.
ActiveX controls and plug-ins might be set to Disable. Enable ActiveX controls and plug-ins.

All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.