"Restart DSfW Services" provisioning task fails if January 2013 patch for OES11SP1 is installed

"Restart DSfW Services" provisioning task fails if the January 2013 Scheduled Maintenance patch for OES11SP1 is installed prior to installing and provisioning DSfW and /var is a file system partition.
The same applies if any sub directories below /var are created as separate file system partitions.

During the execution of the "Restart DSfW Services" provisioning task the following error message is displayed in Provisioning wizard:

Post-check of DSFW services status Failed:[Service xadsd is down]
 at /opt/novell/xad/lib64/perl/Logger.pm line 120
        Logger::_err('Post-check of DSFW services status Failed:[Service xadsd
is d...') called at /opt/novell/xad/lib64/perl/Logger.pm line 211
        Logger::Log(0, 'Post-check of DSFW services status Failed:[Service
xadsd is d...') called at
/opt/novell/xad/share/dcinit/provision/provision_restart_dsfw.pl line 47
2013-01-23 17:23:58,099 INFO  - Restart dsfw:Finished restarting dsfw.

Execute the steps as outlined below to address the issue:

- Identify the value for the setting NcalRpcDir in the  /etc/opt/novell/xad/xad.ini configuration file.
  Execute:
 # grep -i NcalRpcDir /etc/opt/novell/xad/xad.ini

- The directory structure PIPE/np/ has to be created manually in the directory specified for the NcalRpcDir setting in the
  configuration file /etc/opt/novell/xad/xad.ini.
  Example: If /etc/opt/novell/xad/xad.ini file contains the followig setting: NcalRpcDir = /var/newxad/rpc
  then execute the command below to create the directory structure PIPE/np
 # mkdir -p /var/newxad/rpc/PIPE/np

Once the above directory structure has been created, retry "Restart DSfW Services" provisioning task.

In order to pro-actively prevent the issue from occurring when the DSfW packages from the January 2013 Scheduled Maintenance patch for OES11SP1 are installed but the DSfW provisioning wizard has not yet been executed, it is only required to create the directory structure as outlined in the above steps.

This issue is only seen when the January 2013 Scheduled Maintenance for OES11SP1 patch is installed during the installation of DSfW and /var is a separate file system partition.
The same applies if any sub directories below /var are created as separate file system partitions.

The following messages are seen in /var/log/messages:

Jan 23 17:30:04 blr8-119-97 xadsd: [RPC] Could not create named pipe lsarpc
endpoint: error 16c9a003
Jan 23 17:30:05 blr8-119-97 winbindd[17991]: [2013/01/23 17:30:05.257219,  0]
rpc_client/cli_pipe.c:2698(rpc_pipe_open_ncalrpc)
Jan 23 17:30:05 blr8-119-97 winbindd[17991]:   connect(/var/newxad/rpc/xadsd)
failed: Connection refused
Jan 23 17:30:05 blr8-119-97 winbindd[17991]: [2013/01/23 17:30:05.257396,  0]
rpc_client/cli_pipe.c:2698(rpc_pipe_open_ncalrpc)
Jan 23 17:30:05 blr8-119-97 winbindd[17991]:   connect(/var/newxad/rpc/xadsd)
failed: Connection refused
Jan 23 17:30:33 blr8-119-97 winbindd[17991]: [2013/01/23 17:30:33.354367,  0]
rpc_client/cli_pipe.c:2698(rpc_pipe_open_ncalrpc)
Jan 23 17:30:33 blr8-119-97 winbindd[17991]:   connect(/var/newxad/rpc/xadsd)
failed: Connection refused
Jan 23 17:30:33 blr8-119-97 winbindd[17991]: [2013/01/23 17:30:33.354655,  0]
rpc_client/cli_pipe.c:2698(rpc_pipe_open_ncalrpc)
Jan 23 17:30: