Hallo Noties , mal wieder eine Frage : auf unseren Servern (TSE W2K mit Metaframe XP) hängt der Task von Notes (6.01CF)ab und zu mal und der Benutzer kann sich nicht anmelden da der Client nicht startet .
Die EXE liegt im Programmverzeichnis von Notes . Weder über Google noch Lotus läßt sich herrausfinden was der Task macht .
Hat jemand eine Idee oder eventuell eine Lösung ??
Hier habe ich was zu dem Task gefunden.
Vielleicht ist das ja schon ein Hinweis zu deinem Fehler??
Note that all this diagnostic data has the potential to use a lot of space on clients and servers, so Domino gives
administrators the ability to configure how long to keep these diagnostic files (via a policy setting for clients, and the
server configuration document for servers). Every time a client or server starts up, Domino kicks off a second new
executable ([p]fileret) which scans the diagnostic directory for files with the pattern '_<machine name>_' (used by
OSCreateLogFile when creating them) that are over the configured number of days to keep diagnostic files, and
removes them. The default value is 365 days.
What administrators will see
The only real change for administrators will be the location of the diagnostic files they are used to seeing in the data
directory. Here is a list of files that will now be found in the diagnostic directory:
nsd output
memcheck output
core files
memory dump files (created in the format memory_<platform>_<machine name>_<date>@<time>.dmp instead of
memory.dmp)
notes_child_pid (UNIX servers only)
SEMDEBUG.TXT
There is a possibility that the nsd files could be quite large. If very large files are going to be sent to the database,
there is a possibility that the database will grow and the mail.box on the servers will expand greatly. There are also
Notes.INI parameters to turn off either the crash processing piece (DEBUG_DISABLE_DIAGNOSTIC_COLLECTION=1)
or the file retention piece (DEBUG_DISABLE_FILE_RETENTION=1), in case there are any problems with them.
What users will see
The changes should be transparent when running as a server. The [p]senddiag and [p]fileret executables will be
spawned as background processes by the server, waiting until restart recovery is complete and a password (if
specified for the server ID) has been entered. They will then perform their tasks and exit.
When running as a client, if the administrator has turned off prompting for the user it should be transparent as well.
After the user restarts their client, the processes will be loaded, and once they enter their password they will run in the
background and exit.
Hallo Dirk , danke für Deine schnelle Antwort . Ich werde es morgen testen und dann berichten . Es deutet aber auf genau mein Problem hin . Darf ich fragen wo Du den Tip gefunden hast ??
Hallo Dirk , das Problem ist mit dem Eintrag in der Notes.ini behoben !!
Besten Dank für Deine kompetente und sehr schnelle Hilfe !!!
