diagtool terminates saying log configurator not initialized

[Former Member]

I have a dev-test-prod NW WAS Java only landscape to run a portal. These have all been installed by an outsourcer and are supposed to be technically identical in release and configuration.

The only configuration difference of which I am aware is that I have two servers under the dispatcher in tst and only one in dev.

In dev I have successfully implemented Windows Integrated Authentication using the spnego wizard.

When I try to follow the same process in test I drop through to password based authentication every time. So, now I want to use the diagtool in test as I did in dev.

The tool runs but instead of waiting for me to reproduce the error it complains that my log configurator is not initialized:

[Error] Aug 20, 2009 9:53:51 AM    Log Configurator is not initialized. TraceCollector test can not start. Use Web Diagtool from SAP Note 1045019.
[Info] Aug 20, 2009 9:53:51 AM    Time: 2009/08/20 09:53:51
[Info] Aug 20, 2009 9:53:51 AM    Diagtool generated the following file:
[Info] Aug 20, 2009 9:53:51 AM    /home/tstadm/diagtool/output/diagtool_090820_095320.zip
[Info] Aug 20, 2009 9:53:51 AM    Send this file for further analysis.

I've looked in the configtool at the property sheet for the log configurator and the log configurator runtime and the properties in dev and tst are the same.

How do I "initialize the log configurator"?

What does it mean when it says the log configurator is not initialized?

(For the record, I have downloaded the Web Diagtool referenced in note 1045019 as well. I am unable to deploy this because the SDM RemoteGui fails to log on. This error is described in another note which has not solved my problem and is the subject of a support message to SAP.)

[Former Member]

Dear Murray,

do you can solve the problem "Log Configurator is not initialized. TraceCollector test can not start. Use Web Diagtool from SAP Note 1045019."?

I have the same problem right now. I can use the web dialog but doesn´t tell me the problem.

[Former Member]

Turns out that this was all tied up with the SDM userid being locked in the Java stack user management engine and the SDM file storage being unable, therefore, to provide a USABLE set of logon credentials.

After the userid was unlocked everything worked a great deal more effectively.