asynchronous reserveFinally failed

[Former Member]

We have implemented an NWDI (NW2004s SP10) server, the problem we experience is caused due to an old test configuration in the begin of the project. The default trace is full of the following errors:

asynchronous reserveFinally failed

I know where this error is comming from and how to solve it. The problem however is that the namereservation list shows four entries on the state FINALIZE_PENDING for a server 'http://FQDN:443'. And that is where our prolem lies... when you try to temporary add this URL to the nameserver list (on the URL https://FQDN/dtr/system-tools/administration/NameServerConfiguration) then you get the error message:

Name Server data is invalid. Error: Precondition invalid-name-reservation-data check failed.: CIM_ERR_FAILED: HTTP error: Invalid begin of response [expected: 'HTTP', found: '(']

So the problem is that it is pointing to an http URL on port 443 :S.....

Does anyone knows if it is possible to delete those namereservation entries? They are absolutely not necessary anymore but need to be removed since we are experiencing problems as long as these name reservations stay open...

Thanks in Advance,

Nico van der Linden

[Former Member]

For People that want to know more on how the name reservation works with regards to the communication of the SLD and the DTR namereservation tables, SAP created an OSS note based on the questions I had. The OSS note is 1113274.

[Former Member]

Well just to give an update (in case other people experience the same problems).

According to the there is an bug in all NWDS versions below SP12 with regards to using an SSL connection to the nameserver. Instead of reserving names for https://<fqdn>; it registers them for http://<fqdn>:443 (so the http protocol instead of the https protocol). This caused all our name reservations to get stuck on the state Finalize_pending.

SAP recommended to use NWDS SP12 instead and confirmed that it was supported to use NWDS SP12 in combination with NWDI and portal on SP10. I downloaded NWDS SP12 and tried to connect to the DTR but I was not able to get an connection at all, no error and no response :S

So I went back to SAP and (again) they confirmed that this is caused due to an bug in NWDS in combination with SSL connections. The Namereservation problem is solved but instead they gave a free bug back with regards to SSL connections to the DTR........

SAP will provide an patch for NWDS SP12 to us, but we decided to stay on NWDS SP10 on the landscapes where the portal and NWDI are also on SP10 and just use HTTP connections for name reservations for a while. We enable https connections for the namereservations on all landscapes that are on SP12 and then we apply the patch that SAP will provided.

I would recommend everyone NOT to turn on SSL connections to the nameserver when you are on NWDS below SP12. All namereservations that were on an incorrect state had to be deleted with an SQL delete statement directly on the database tables since SAP does not provide another way for it. After that we also had to delete all our DC's and recreate them again to make the names reserved again....

Hope that this makes everything clear, otherwise just let me know.

Cheers,

Nico van der Linden

[Former Member]

Excellent info, Nico. Thanks a lot.

[Former Member]

Hi Nico,

You can delete the entries in the SLD via Content Maintenance.

- Pascal

[Former Member]

Hi Pascal,

thank you for the information. When I remove them there it seems that I can re-use the DC name again. However, they are still on the name reservation list on the state 'FINALIZE_PENDING'.... And that is causing loads of errors in the defaultTrace file...

I am wondering where this list is stored... In the SLD or maybe somewhere in the DTR. I doesn't seem that the namereservation list is the same list as the list shown in the DTR application 'Name Reservation List'. Do you know more about this?

Cheers,

Nico...