Cannot create server handle

The DR daemon could not start up the RPC server. You will see this message only if you manually execute the DR daemon without properly configuring the network services on the domain. Normally, network services spawn the DR daemon in response to an incoming RPC from the SSP. 

On the domain, fix the inetd.conf entry for the DR daemon.

Cannot fork: descriptive message

The DR daemon could not fork a process from which to run its RPC server. 

The descriptive error message corresponds to an errno_value and offers clues as to why the DR daemon could not fork off the RPC server. Check the resource limits and the load of the system to find a way to fix this error.

Permission denied

A user other than root tried to run the DR daemon. 

Only the superuser (root) can run the DR daemon because the daemon needs all of the root privileges to fully explore the system and to access the driver to detach and attach boards. 

Unable to register (300326, 4)

The DR daemon was executed without being properly registered with the network services in the domain. The first number represents the RPC number that is registered for the DR daemon. The second number represents the RPC version used by the DR daemon. 

On the domain, fix the inetd.conf entry for the DR daemon.

Unable to create (300326, 4) for netpath

The DR daemon was executed without being properly registered with the network services in the domain. The first number represents the RPC number that is registered for the DR daemon. The second number represents the RPC version used by the DR daemon. 

On the domain, fix the inetd.conf entry for the DR daemon.