ETERNUS SF Disk Space Monitor User's Guide - Microsoft(R) Windows Server(TM) 2003/Solaris(TM) Operating System/Linux - 13.0

6.4 Other Supplementary and Important Information

6.4.1 syslog settings 

Error messages are output to syslog using two syslog facilities.

In order to log messages, /etc/syslog.conf must be set up so that daemon.log and user.log are collected.

Refer to the syslog.conf(4) and syslogd(1M) manuals for details on syslogd and how to set up syslog.conf.

facility.level	Process
deamon.err	dcmd
user.err	dsa_*

A settings example for syslog.conf is shown below.

daemon.err /var/adm/messages

user.err /var/adm/messages

6.4.2 Content display errors 

The following problems sometimes occur when users try to display the desired contents (graphs or tables) in the Monitor, Drill Down or Report view in the Console window using the Display or Generate button.

• The operation terminates with error code 1572864.
• The graph image drops out (only the graph is not displayed).

These problems may occur because the desktop heap on the operation management client is not large enough. In this case, increase the size of the desktop heap using the following method.

6.4.2.1 How to increase the size of the desktop heap

Making errors in editing the registry can lead to problems such as Windows not starting. Be very careful while editing the registry.

1. Start the registry editor. (REGEDT32.EXE)
2. Display the following key from the HKEY_LOCAL_MACHINE sub-tree.

   \System\CurrentControlSet\Control\Session Manager\SubSystems

   
   
3. Modify the SharedSection parameter settings (shown in bold in the example below) in the Windows values.
   Increase the third value (separated by commas) in multiples of 256 or 512 to somewhere between 1024 and 2048.

Depending on the system, an error message (such as "abnormal program termination") may be displayed when the Console is started if the value specified is too large, and the window may not open. In this case, adjust the specified value within the range indicated.

Depending on the system, there may be three or four values separated by commas. In both cases, increase the third value.

• Before

  %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 erverDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

  
  
• After

  %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,1024 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

1. Restart the machine.

6.4.2.2 Other content display errors 

In addition, the following error codes may occur when an attempt is made to display content.

In such cases, perform the checks and actions indicated:

Error code	Check item	Action
536870912	Has Microsoft Internet Information Server been set up correctly?	If Internet Information Server has not been set up correctly, set it up again by referring to Section 16.2.1, "For Microsoft Internet Information Server".
	Has the target data been collected?	If not even one item of the target data has been collected, make settings so that the data is collected.
1074003968	Is the Manager service running?	Start the Manager service if it is not running already.
	Can the name of the Manager be resolved from the operation management client?	If the name cannot be resolved, add the name and IP address of the Manager to the hosts file on the operation management client.
1074266112	Has the power to the Manager been turned off?	Turn the power to the Manager on if it has been turned off.
	Has the IP address of the Manager been set up incorrectly on the operation management client?	The IP address of the Manager is specified in the following registry key. Check if the content of this key is correct. \\HKEY_LOCAL_MACHINE\SOFTWARE\Fujitsu\SQC-C\CurrentVersion\Settings\ManagerIP-Address If the wrong IP address has been specified, specify the correct IP address using the method described in Section 17.4.2, "Changing the IP address of the Manager recognized by the operation management client".

6.4.3 Application errors with tclsh84  

The tcl84.exe application may produce the following kind of application error on a Manager or an Agent.

• "The application failed to initialize properly (0xc0000142)."

This problem may occur because the desktop heap on the Manager or Agent is not large enough. In this case, increase the size of the desktop heap using the method explained in Section 6.4.2.1, "How to increase the size of the desktop heap".

6.4.4 Event ID 2003  

For Microsoft Windows 2000 Server and Microsoft Windows 2000 Advanced Server, a warning message with event ID 2003 may be displayed in the application event log.

This is a problem with Windows, and Microsoft has announced a workaround. Refer to the following URL for details.

http://support.microsoft.com/kb/267831/EN-US/

6.4.5 Failure to collect server performance information  

Server performance information may not be displayed (may not be collected) for the various display functions in the Console window. This is a problem with Windows, and Microsoft has announced a workaround. Refer to the following URL for details.

http://support.microsoft.com/kb/248993/EN-US/

6.4.6 PDB maintenance processing 

Data in the PDB for which the retention period (described in Section 2.4, "Manager") has elapsed is deleted from the PDB by the PDB maintenance processing that is executed everyday at 2:00 am.

While PDB maintenance processing is in progress, access to the PDB (such as executing PDB commands or displaying the Monitor, Drill Down or Report views in the Console window) may become temporarily impossible.

In this case, repeat the operation after the PDB maintenance processing has completed.