No response from booked rooms/resources

HCL Domino Domino Forum
1

Hi All

We have a 6 domino servers in our domain and each of them have a resource reservation DB. This means that all users can book rooms and/or resources via their calendar on all servers if needed - which is exactly what we want and this has been working for a few years perfectly.

Since last month, just one of the servers has stopped accepting any reservation done by users via calendar (direct reservations in this DB are fine). For example, I create a new invitation, book a room and/or a resouce from this location, check that it is available (using check availabiliy action on new inviation) and save the invite. Normally, this invitation/reservation should be visible on the calendar of that Resource Reservation database. But it is not. Also, there is no decline notice sent either.

I have tried restarting the server, stopping the server, deleting BUSYTIME.nsf DB and restarting the server - but nothing has helped.

It is as if the invitations sent from users’ calendars to resources/rooms in this DB are not even arriving in this DB.

Any ideas anyone?

TIA

Alpna

2

Subject: No response from booked rooms/resources

You can check that last idea (“as if the invitations are not even arriving in this db”) by creating a view in the reservations db that shows all documents that have “Notice” as Form.If they don’t show, they indeed don’t arrive in the db and you must check mail routing (do the mail-in docs still exist ?).

If they do show, then it’s a processing problem and you must check why the router doesn’t trigger the processing when depositing the invitation.

3

Subject: RE: No response from booked rooms/resources

Check the signing of agents and script libraries in the db. Make sure that user has been granted all rights on the server to execute the agent.

4

Subject: RE: No response from booked rooms/resources

Also check the Server document - Ports - Notes …and make sure that the address is correct. If it isn’t you will see a message in the log-file stating something like ‘unable to open server…’

Weird, but a fact…