Buildnummer des Servers stimmt nicht

[Colibri]

Hallo Notes Gemeinde,

ich habe unserer Server mit dem FP1 gepatcht. Bei einem Server steht aber im Serverdokument im Feld Buildnummer des Server weiterhin "Release 8.5" statt wie bei den anderen -"Release 8.5FP1".
Der Server ist definitiv gepatcht, was mit sh sever auch bestätigt wird. Wann und wie schreibt der Server dieses Feld im Serverdokument.

Danke und Gruß
Dietmar

[eknori]

Wann und wie schreibt der Server dieses Feld im Serverdokument.

Das wird über den adminp befüllt; WANN: Wie immer im Domino, wenn der Server Zeit und Lust hat

Dazu folgendes aus der KB:

Problem:
You upgrade your IBM Lotus Domino Server and notice that the software build number on the Basics tab of the Server document still reflects the old release.  In some cases, the field is simply blank.  You wish to populate the Server Build number field with the correct Domino server build number.

How To Solve:


The Administration Requests database (admin4.nsf) is created by default on Domino.  This database contains requested actions that the Administration Process (AdminP) must carry out, such as renaming or re-certifying a user, moving mail files, etc.

By default, the database contains one request at creation: to put the Domino Server Build Number in the corresponding field in the Server document.  An administrator might delete this default request from the Administration Requests database, the request may not complete, or AdminP may not be running on the server.

The Domino Server Build Number can be repopulated.  If there is a build number that is incorrect, you can simply make the field editable (the field is not editable by default).  The next time AdminP runs and looks for tasks to process it will check the Server Build Number field and, if it is empty,  will create a request to populate the field.

Windows only:
In order to make this field editable, make the following changes:
NOTE:  Do not make any edits to the Domino Directory without first creating a complete backup of the database.

1.  Open names.nsf in Domino Designer.
2.  Go to Forms and the Server\Server form.
3.  On the form, on the Basics tab, right-click on the ServerBuildNumber text box to open the field properties.
4.  Change the "Computed" field type to "Editable."  Save and close the Server document.
5.  Open the Domino Administrator and go to the Basics tab of the Server document.
6.  Click the 'Edit Server' button.  You should now see the 'Server Build Number' field in edit mode.
7.  Blank out the incorrect build number to leave the field blank.
8.  Save and Close the Server document.
9.  Go back into Domino Designer and open names.nsf again.
10.  Go to Forms and the Server\Server form.
11.  Right-click on the ServerBuildNumber text box again and bring up the field properties.
12.  Change the "Editable" field back to "Computed."
13.  Save and close the Server document.
14.  Open the Admin4.nsf and delete any previous AdminP actions refering to server build number.  Look for the line: Put Server's Notes Build Number into Server Record, and its response: servername performed action on x.
15.  Reboot the Domino server.  When the server comes back up you should be able to see the correct Domino build number in the Server Build Number field.

NOTE:   The AdminP task must be running and set up appropriately on the Domino server for the field to be populated and the above steps to work.  In one customer's case, the "Place server's Notes build number into Server record" request was generated correctly in the ADMIN4.NSF, but this field was not updated until the request was processed on the Administration server.  The customer incorrectly had one-way replication set up so the Administration server had not received the request.

The Domino version is referenced in the Windows Registry as follows:

HKEY_LOCAL_MACHINE/SOFTWARE/Lotus/Domino/Directory#/Version

If the version in the registry is listed incorrectly (example: version 1 rather than 6), the version in the Server Build Number field in the server document may also be incorrect.  As another option the registry can be manually changed to reflect the correct version.

NOTE:  The information above is presented as a guideline for making relevant changes within the Windows Registry.  The Windows Registry is central to the operation of Windows, so any changes should be performed with great care.  As with any major configuration change, it is highly recommended that customers have complete backups of their computer systems before attempting the following procedure, in order to allow recovery from system file corruption or other failures.  If you require instruction about backing up and modifying the Windows system administrator or reference one of the vender guides available for advanced Windows topics.

[DunkelHut]

... 


Gruß
Stefan

[Colibri]

Was macht man nicht alles damits sche ausschaut

@eknori
Danke, hat funktioniert!!!

@DunkelHut
Auch Danke, wer lesen kann ist klar im Vorteil!

[mklumps]

Man kann auch alternativ den Adminp Request in der admin4.nsf suchen und das Häkchen "Perform request again" anwählen.

Dann führt der AdminP die Aufgabe erneut aus. So hat das bei uns funktioniert.

[Tode]

Schöne Ergänzung... für einen 6 Jahre alten Thread...

[Colibri]

Danke, Problem war aber schon gelöst