IBM Support

Troubleshooting the Autoprocess Feature in Notes/Domino Calendaring and Scheduling

Product Documentation


Abstract

If the Autoprocess feature is not working properly the typical symptoms are, obviously, that reservations are not being autoprocessed and/or mail delivery failures such as "User <Resource Name> not listed in public Name & Address Book" occur.

Content


The following troubleshooting script can be used to troubleshoot the Autoprocess feature in Notes/Domino. The Autoprocess feature is used to process room and resource reservations in the Resource Reservations database, which is a component of the Calendaring & Scheduling feature of Notes/Domino; it is also used to process meeting invitations in the mail file. If the Autoprocess feature is not working properly the typical symptoms are, obviously, that reservations are not being autoprocessed and/or mail delivery failures such as "User <Resource Name> not listed in public Name & Address Book" occur.

To ensure everything is set up correctly, follow the script below.

I. Check the Server Document:



Basics tab
Are the 'Server Name' field and 'Fully Qualified Internet Host Name' field the same?

When the router sends the acceptance or decline notices to the users, the server needs to be able to resolve its own name. If TCPIP is being used, this cannot happen if the server name is not the same name as the TCPIP host name or the fully qualified internet host name of the PC that is running the Domino Server.



To check if the Domino Server name is the same name as the fully qualified internet host name or TCPIP host name, open the Server document of the Domino Server that the Resource Reservations database was created on. On the Basics tab look at the fields, 'Server Name' and 'Fully Qualified Internet Host Name'. The Domino Server's common name should match the fully qualified internet host name. For example, if the 'Server Name' field lists "ServerA/DomainA", then the Notes common name is "ServerA". The 'Fully Qualified Internet Host Name' field should contain "servera.domainname.com". If the 'Server Name' field and 'Fully Qualified Internet Host Name' field do not match (for example, the Server name is "ServerA/DomainA", but the fully qualified internet host name is "serverb.domainname.com"), then the Domino Server cannot resolve its own name. The host file or DNS table must be modified to include an alias for the fully qualified internet host name or the TCPIP host name. An example host file would look like the following:

IP addressTCPIP Host Name
100.100.100.100 serverb.domainname.com

This host file would need to be modified to look like the following:
IP AddressTCPIP Host NameAlias
100.100.100.100serverb.domainname.comservera


Are the 'Mail Server' field and the 'Server Name' field the same?

The 'Mail Server' field, located in the 'Server Location Information' section of the Server document, should contain the same server name as the 'Server Name' field.



Ports tab
Check the 'Net Address' column located on the 'Notes Network Ports' sub tab

Make sure the address is a valid network address for the server that the Resource Reservations database was created on, and it can be resolved by the Domino Server's common name. For example, if the Domino Server's common name is ServerA, then the net address is usually ServerA or ServerA.domainname.com, as shown below.



PortProtocolNotes NetworkNet AddressEnabled
TCPIPTCPTCPIP Networkservera.domainname.comEnabled

Test if the Net address can be resolved
Can you ping the Domino server name?
To ping the Domino Server name open a command prompt window and type the following: ping ServerA
The output should look similar to the following:

Pinging servera.domainname.com [9.95.52.241] with 32 bytes of data:
Reply from 9.95.52.241: bytes=32 time<10ms TTL=128
Reply from 9.95.52.241: bytes=32 time<10ms TTL=128
Reply from 9.95.52.241: bytes=32 time<10ms TTL=128

Can you connect to the server by performing the 'trace' command on the server console?

At the server console type: trace Servername/Domainname

The output should reveal a successful connect as shown below.

> trace servername/domainname
<date> 06:27:57 PM Network: Determining path to server servername/domainname
<date> 06:27:57 PM Network: Enabled Ports: TCPIP
<date> 06:27:57 PM Network: Checking normal priority connection documents only...
<date> 06:27:57 PM Network: Allowing wild card connection documents...
<date> 06:27:57 PM Network: Enabling name service requests and probes...
<date> 06:27:57 PM Network: Address found in local TCPIP names table for servername/domainname
<date> 06:27:57 PM Network: Connecting to servername/domainname over TCPIP
<date> 06:27:57 PM Network: Using address 'servername.domainname.com' for servername/domainname on TCPIP
<date> 06:27:57 PM Network: Requesting IP Address for servername.domainname.com from DNS
<date> 06:27:57 PM Network: DNS returned address 9.95.52.241 for servername.domainname.com
<date> 06:27:58 PM Network: Connected to server servername/domainname

If you cannot connect to the server via trace refer to the Admin Help topic, Troubleshooting TCP/IP problems for NRPC.


Security tab
Check the 'Server Access' heading

By default, the 'Only Allow Server Access to Users Listed in this Address Book' field is set to "No". If it is set to "Yes", proceed to the 'Access Server' field.



Check the 'Access Server' field

By default this field is blank. If you set the 'Only Allow Server Access to Users Listed in this Address Book' field to "Yes", make sure that the servers are listed in this field. You can place each server name in this field or use the public group, "Local Domain Servers". Omitting the server in the Access Server field means that the server cannot access itself.



Check the 'Not Access Server' field

Check the log file. You will see an error message such as the following:



<date> 03:59:45 PM Opened session for Servername/OrgName (Release 5)
<date> 03:59:45 PM ATTEMPT TO ACCESS SERVER by Servername/OrgName was denied
<date> 03:59:45 PM Closed session for Servername/OrgName

Make sure the server is not in any of the groups or nested groups that are listed in this field.

II. Check the Access Control List

Check the Access Control List (ACL) of the Resource Reservations database.



The server that the database was created on should be listed as the Administration Server of this database. To verify the Administration Server perform the following:

1. Select File, Database, Access Control.
2. Select the Advanced icon.
3. At the top, for Administration Server select the Server radio button.
4. Type in the name of the server that the Resource Reservations database was created on.

III. Is SMTP Selected for Local Intranet Domain? (NOTE: This section applies only to Domino 5.x.)

In Notes/Domino 5.x Calendaring & Scheduling iCalendar is not supported. When configuring Calendaring & Scheduling, make sure that the mail servers and the server that the Resource Reservations database was created on are not configured to use SMTP in the local internet Domain. This is specified in the Server Configurations view of the Domino Directory.

1. Open the Configuration document for the server that the Resource Reservations database is created or the mail server that is sending reservations requests.
2. Click the Router/SMTP tab.
3. In the Basics tab check to see if the field, 'SMTP Allowed Within the Local Internet Domain' is set to "All Messages". If it is, change it to "Disabled".
4. Ensure that the Routing Task field in the Server document is set to "Mail Routing". In Domino R5 you need only "Mail Routing" selected in the Routing Tasks. The Domino R5 Router handles both Notes Remote Procedure Call (NRPC) mail and Simple Mail Transfer Protocol (SMTP) mail.
5. Check to see if there are any SMTP Connection documents to the server that the Resource Reservations database is on. If so, delete them; however, if the servers are in different Notes Named Networks (NNN) then create a Mail Routing connection document to the server that the Resource Reservations database is on.

IV. Try Creating a Connection Document to the Server Itself

If all of the above has checked out, try creating a Server Connection record to the server itself. In this manner the Domino Server will check local connection records first in the Domino Directory before resolving the address over the network. If creating a Server Connection to the Domino Server itself resolves the Autoprocess issue, then the problem is related to the network because Domino is no longer using the network to resolve the address of the Domino Server.


V. Check the Router task for modifications
    If the the priority of certain jobs (tasks) on the server has been altered, there may be autoprocess problems. If the Router task priority is not 30, change it back to 30.

Internal Use Only

Contributors: Marc Vecchio

Domino 4.5x/4.6x

Domino 4.5x/4.6x

I. Check the Server Document
  • Basics section

Are the 'Server Name' field and 'Fully Qualified Internet Host Name' field the same?

When the Agent Manager runs the Autoprocess Meeting Notice or Autoprocess Reservations agent, the router sends the acceptance or decline notices to the users. In order to do this the server needs to be able to resolve its own name. If TCPIP is being used, this cannot happen if the server name is not the same as that of the TCPIP host name or the fully qualified internet host name of the computer that is running the Domino Server.



To check if the Domino Server name is the same name as the fully qualified internet host name or TCPIP host name, open the Server document of the Domino server that the Resource Reservations database was created on. In the 'Basics' section look at the 'Server Name' field and compare it to the 'Fully Qualified Internet Host Name' field in the 'Internet Message Transfer Agent (SMTP MTA)' section. The Domino Server common name should match the fully qualified internet host name. For example, if the 'Server Name' field lists "ServerA/DomainA", then the Notes common name is "ServerA". The fully qualified Internet host name should be "servera.domainname.com". If the 'Server Name' field and 'Fully Qualified Internet Host Name' field do not match (for example, the Server name is "ServerA/DomainA" but the 'Fully Qualified Internet Host Name' is "serverb.domainname.com"), then the Domino Server cannot resolve its own name. The host file or DNS table must be modified to include an alias for the fully qualified internet host name or the TCPIP host name. An example host file would look like the following:

IP addressTCPIP Host Name
100.100.100.100 serverb.domainname.com

This host file would need to be modified to look like the following:
IP AddressTCPIP Host NameAlias
100.100.100.100serverb.domainname.comservera

  • Network Configuration section

Check the Net Address column

Make sure the address is a valid network address for the server that the Resource Reservations/Mail File database is created on and it can be resolved by the Domino Server's common name. For example, if the Domino Server's common name is ServerA, then the net address is usually ServerA or ServerA.domainname.com as shown below.



PortProtocolNotes NetworkNet AddressEnabled
TCPIPTCPTCPIP Networkservera.domainname.comEnabled


Test if the Net address can be resolved
Can you ping the Domino server name?
To ping the Domino Server name open a command prompt window and type: ping ServerA
The output should look similar to the following:

Pinging servera.domainname.com [9.95.52.241] with 32 bytes of data:
Reply from 9.95.52.241: bytes=32 time<10ms TTL=128
Reply from 9.95.52.241: bytes=32 time<10ms TTL=128
Reply from 9.95.52.241: bytes=32 time<10ms TTL=128

For more information on TCPIP refer to sections I and II the document, "Troubleshooting Script: How to Diagnose Notes and Domino TCP/IP Issues" (#144302).
  • Server Location Information section

Is the 'Mail Server' field the same as the 'Server Name' field?

The Mail Server field, located in the 'Server Location Information' section, is not the same name as the Server name field.


  • Agent Manager section

Check the 'Run Restricted LotusScript Agents' field

The person who enabled the agent should be listed in this field. It's best to put an "*" to allow all users.


  • Check the AutoprocessReservations agent (for the Resource Reservations database) or AutoprocessMeetings agent (for the mail file)

Make sure that the AutoprocessReservations agent or AutoprocessMeetings agent in the Resource Reservation database/Mail file is enabled.

Open the agent document; in the Run only on "servername field" in the "Schedule" dialog box, check that the server name is listed. With the administrator's ID make any fake modification to the agent and save it to make sure that this ID (with the administration privileges) is the last to modify the agent.

Try running the AutoprocessReservations agent (for the Resource Reservations database) or AutoprocessMeetings agent (for the Mail File) manually by selecting Actions, Run. If it runs, ensure minimum delay in agent execution:

By default, Agent Manager polls for new requests every 30 minutes (this is controlled by the INI parameter AMgr_DocUpdateAgentMinInterval, which defaults to 30). Use the Notes.ini parameters below to have Agent Manager poll for new agent requests at a higher frequency. For example, to poll every 1 minute, add the parameters to the Notes.ini as follows:

AMgr_DocUpdateEventDelay=1
AMgr_DocUpdateAgentMinInterval=1
AMgr_NewMailEventDelay=1
Amgr_NewMailAgentMinInterval=1

Note: Extreme caution should be used when using this parameter on a server that has a heavy load. Using the parameters above will result in an approximate 3 minute delay before the agent actually runs to completion.

  • Restrictions Section

Server Access
Check the 'Only Allow Server Access to Users Listed in this Address Book': By default this field is set to "No". If it is set to "Yes", proceed to the "Access Server" field.

Access Server Field
By default this field is blank. If you set the 'Only Allow Server Access to Users Listed in this Address Book' field to 'Yes', make sure that the servers are listed in this field. You can place each server name in this field or use the public group, Local Domain Servers.


II. Check the Access Control List of the:

a. Resource Reservations Database
The server and the administrator names should be listed as managers in the Access Control List (ACL) of the Resource Reservations database. The Server that the database is created on should be listed as the Administration Server

b. Mail File
The owner of the mail file should be listed as Manager of the database. The Server that the database is created on should be listed as the Administration Server.

III. Try Creating a Connection Document to the Server Itself

If all of the above has checked out, try creating a Server Connection record to the server itself. In this manner the Domino Server will check local connection records in the Public Name and Address Book (NAB) first before resolving the address over the network. If creating a Server Connection to the Domino Server itself resolves the Autoprocess issue, then the problem is related to the network because Domino is no longer using the network to resolve the address of the Domino Server.

[{"Product":{"code":"SSKTWP","label":"IBM Notes"},"Business Unit":{"code":"BU003","label":"Collaboration Solutions"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"8.5;8.0;6.5;6.0","Edition":""}]

Document Information

Modified date:
23 June 2018

UID

swg27003646