
50 Novell eDirectory 8.8 SP7 Troubleshooting Guide
7.3 iMonitor Report Does Not Save the Records for Each Hour
The custom reports feature in iMonitor is designed to place the URL specified by the user into the
saved report (the saved HTML file) when the custom report is created. That means that when you
open a saved custom report that has been run, you see the live (current) data instead of the data
captured by the URL at the time the custom report is run. This issue will be resolved in a future
release of iMonitor.
7.4 Creation and Modification Time Stamps
Because UNIX platforms do not maintain the creation time of a file, iMonitor shows both the creation
and modification times to be the same.
7.5 iMonitor Issues in Older Versions of Mozilla
If you access iMonitor using Mozilla versions earlier than 1.5, iMonitor might have problems during
DSTrace Flag selection. Mozilla might not support all the operations.
7.6 Run Report Screen Layout Not Aligned on iMonitor
The navigation and assistant frames appear twice on Linux and Solaris.
To work around this problem, refresh the page.
7.7 iMonitor Displays Error -672
A few operations fail and display error -672, when some debug tool is running in parallel with
iMonitor.
On UNIX
iMonitor displays error -672 if dsdump tool is running in parallel with iMonitor.
To resolve this issue, exit the dsdump tool, before starting iMonitor.
On Windows
iMonitor displays error -672 if the dsbrowse or dsedit tool is running in parallel with iMonitor.
To resolve this issue, exit the dsbrowse and dsedit tool before starting iMonitor.
7.8 Time Stamps Displayed in Hexadecimal Format
If you set a Time syntax attribute with a value prior to January 1, 1970, iMonitor displays the time
stamp for the attribute in hexadecimal format instead of in standard date/time format. iMonitor
displays all attributes with values after January 1, 1970, in date/time format.
Comentarios a estos manuales