A user server did not start during OpenTP1 startup processing, despite a user service structure definition (usrconf) being specified.

• The date and time when the event occurred
• Any changes made to the OpenTP1 environment immediately before the event occurred

• betran.log on the affected node
  When using Windows, acquire the event logs (application log and system log).
  
• syslog file on the affected node
  Not required when using Windows.
  
• Contents of $DCDIR/conf on the affected node
  If $DCCONFPATH specifies a folder other than $DCDIR/conf, also acquire the contents of the location specified by $DCCONFPATH.
  
• $DCDIR/spool/errlog/errlog***

To start a user server specified in the user service structure definition (usrconf), both of the following conditions must be satisfied:

• uap_conf=Y is specified in the system service structure definition (sysconf)
• OpenTP1's startup mode is set to normal startup

The most likely cause of this problem is that the user server did not start because OpenTP1 was started in restart mode.

Investigate the cause of the error using the flow chart below.

Figure 11-13 Troubleshooting procedure when a user server does not start

A similar problem may occur where certain user servers do not start when OpenTP1 is started in restart mode. In restart mode, OpenTP1 resumes the online status of the previous session. Under normal circumstances, user servers that were active in the previous session are also started when OpenTP1 starts in restart mode; however, this does not include user servers for which node_down_restart=N is specified. If a user server does not start when OpenTP1 starts in restart mode, check the value of the node_down_restart operand for the user server.