Asynchronous Reserve Finally failed?

Question

Can someone explain to me why I continually see this error in the DTR log file:
asynchronous reserveFinally failed: missing name server configuration, no logon known -> operation will be retried name reservation : name server=http://nwdiserver:55000/,  category=SAP_DevelopmentComponentName, name=example.com/test/test/dc, reservationKey=6505225, state=FINALIZE_PENDING
The SLD has been configured to be a Name Server as well as a SLD.  The Supplier Bridge has been configured, and data has successfully been transferred.
So what does this message really mean?

Answer 1

I know that this may be a bit too late to reply to this thread, but somebody just pointed me out to this query and so I will try to clarify what is happening a bit more in detail.
When you create some objects in the NetWeaver Developer Studio (NWDS) whose names need a reservation (like dictionary files, DC definitions, etc.), the NWDS sets up a special 'name reservation' property on such a file after adding it to DTR.
The property tells DTR that a preliminary name reservation was done by the NWDS on the name server and after check-in, DTR is supposed to finalize the name reservation.  The property also tells DTR on which name server the name has to be reserved - since there could be multiple name servers in a landscape.  DTR records such an entry in its 'name-reservation queue' and marks it as being preliminarily-reserved.
However, the property does not provide the authorization details of the name server to DTR i.e., DTR has no mechanism to connect to the name server until the administrator or CMS configures the name server in DTR with the appropriate credentials.
The finalization itself is an asynchronous operation i.e., after the check-in is complete the name-reservation entry in DTR gets the new status of 'finalize-pending'.  A background task in DTR picks up such pending reservations, tries to see if the name server is registered with DTR and if so, contacts the name server and finalizes the name reservation. If the file was reverted, then the reservation gets the status 'revert-pending' and DTR reverts the preliminary reservation from the name server.
If a developer has checked-in a file with a name reservation pointing to 'old-name-server' and in the meantime if the name server was relocated to 'new-name-server', then DTR does not have a mechanism to contact the old-name-server anymore.  And that is when you get the 'missing name server configuration' error.
As you see in the error message, DTR does not yet give up on the reservation.  So, if you configure the old name server once again, then when the background task runs the next time, it will successfully reserve the name on the old-name server.
Currently, there is no possibility to edit such name reservation entries in DTR's queue and change their URLs to point to the new name server.
In a future release, this mechanism of finalization of reservations via DTR will be completely removed.  The reservations will be handled directly by the NWDS.
Here is what I would suggest before you relocate your name servers:
Use the <a href="http://host:port/dtr/sysconfig/support/NameReservationList">http://host:port/dtr/sysconfig/support/NameReservationList</a>
URL to check if there are any entries in the REVERT_PENDING or FINALIZE_PENDING state.
If so, wait for a few minutes for the background task to process these entries.  But make sure that the name server mentioned in the queue is indeed configured in DTR via the URL:
<a href="http://host:port/dtr/system-tools/administration/NameServerConfiguration">http://host:port/dtr/system-tools/administration/NameServerConfiguration</a>.
You can also check when the background task last ran via the following URL:
<a href="http://host:port/dtr/sysconfig/scheduled_tasks.html">http://host:port/dtr/sysconfig/scheduled_tasks.html</a>
(the task ID is 'ProcessNameReservationsTask').
Only when there are no more reservations pending, then you should reconfigure the nameserver.
If you did not take care for the above steps, then you need to add the name server configuration to DTR as Adrian explained.
- Girish