RnRMgr: Error processing reservation document – Error connecting to server

HCL Domino Domino Forum
1

Our Resource Reservation database works fine, except for the following: when a reservation is made for a room or resource, the chair never receives a confirmation notice that the room/resource reservation has been accepted.

The reservation request is sent to the RR database and the invitation is sent to the invitee. But an invitation confirmation is not sent back from the RR database to the chair. Instead there is the message ‘error connecting to server’ (see below). The RR database as well as the users’ mail files are all on the same server (SERVER1/Sennen/NL), which is a Unix server.

I have removed the complete RR database in an orderly way (remove rooms, wait for adminp, remove site document, etc.) and recreated a new one from template, added the site document and rooms and resources. Then restarted the RnRMgr. But the problem is still there.

Here are the log entries: admin/Sennen/NL is inviting Test Admin/Sennen/NL for a meeting in Conference Room/Sennen:

10/16/2014 13:07:20 Router: Message 003D18A9 delivered to Conference Room/Sennen from admin/Sennen/NL OFB1800B84:329CDA11 ONC1257D73:003D18A9 Size: 1K Time: 00:00:00 Hop Count: 1

10/16/2014 13:07:20 Router: Delivery to local recipient Test Admin/Sennen/NL is ready with 1 messages

10/16/2014 13:07:20 Router: Delivery thread [0000001B] searching for work

10/16/2014 13:07:20 Router: Message 003D087D delivered to Test Admin/Sennen/NL from admin/Sennen/NL OF9ABA6E1C:C995B3A9 ONC1257D73:003D087D Size: 1K Time: 00:00:00 Hop Count: 1

10/16/2014 13:07:29 Error connecting to server SERVER1/Sennen/NL: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.

10/16/2014 13:07:29 RnRMgr: Error processing reservation document (UNID OFB1800B84:329CDA11-ONC1257D73:003D18A9) in database resource.nsf

Thank you.

2

Subject: Error connecting to server message

Hello

Regarding your error

10/16/2014 13:07:29 Error connecting to server SERVER1/Sennen/NL: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.

The error message can result for many different reasons. Review the following to try to resolve the issue : -

1>

Check the Server field in the Server document. If this entry is incorrect the error returned typically is: “Server Not Responding”. This might happen if the server name has been changed and the entry in the Mail Server field has not been updated to match the modified server name. The entry should match the server’s abbreviated hierarchical name.

The Mail Server field can be found by going to the Basics tab of the Server document and expanding the Server Location Information section at the bottom of the document.

2> Server configuration or TCPIP issue. For example, if the Network Address field for a TCPIP port contains either an incorrect host name or an IP address, the errors occur. If the DNS is not working correctly the errors will occur.

The Net Address setting can be found by selecting the Ports tab in the Server document, then selecting the Notes Network Ports sub-tab.

To verify that a server can connect to itself via its Network Address entry you can use the Trace command. To do this launch the Domino Administrator and open a Server Console window, and issue the command: Trace . It should report that it connected to the server.

3 > Use the PING executable to verify IP-level connectivity. If the server is resolvable by IP address but not resolvable by Fully Qualified Host Name (FQHN). Even though the IP address may be listed properly in the Net Address field of the Server document, the DNS servers may need to be updated to point the FQHN to the correct server.

Ping the server from the server itself by its DNS fully qualified domain name (FQDN) to verify that it was added to the network correctly; then ping the server from the Workstation by FQDN.

4> The Domino server may not be listed in its own host table. Update the host file of the server with the FQHN pointing to its own IP or localhost address.

Ping the server by DNS alias name from the server itself to verify it was added to the network correctly. Then ping the server from the workstation. Ideally the server host alias names all should be the same as the Domino server names. Sometimes the server’s FQDN may differ from the Domino server’s. That is when the alias name is used, being the same as the Domino server’s name.

3

Subject: thank you, solution was net address

Sorry for my late reply, but thank you for the solution! It indeed was the net address that was incorrect: a trace resulted in an “unable to find any path to…”. When I updated the net address with the local ip address of the server, and sent a meeting with a resource reservation, I received a confirmation of the room reservation from the R&RMgr. So it works perfect now, thank you!