


10.3.7 Acuserve and Portmap daemons
Problem: AcuServer fails to start or complains that the portmap daemon isn't running.
Diagnostics for UNIX:
On UNIX systems, use the "rpcinfo" command to verify that the portmap or rpcbind daemon is running on the server. On the UNIX server or a UNIX client, enter:
rpcinfo -p server-name
The system should return a list of all RPC processes running on server-name.
If you run "rpcinfo -p" without a server-name, it will default to your local machine. If you are running on the server, this will eliminate the possibility of specifying an invalid server-name.
program vers proto port 100000 2 tcp 111 portmap 100000 2 udp 111 portmap 100005 1 udp 728 mountd 100005 1 tcp 730 mountd 100003 2 udp 2049 nfs 300301 1 tcp 4443
Under UNIX, if the portmap is not running, the system will return an error message similar to the following:
rpcinfo: can't contact portmap:
RPC: Remote system error - Connection refused
To start the portmap, contact your system administrator.
Diagnostics for Windows NT (Intel):
On a Windows NT (Intel) server, enter:
sc query Portmap
sc query Acuserve
The system should display the current state of the Portmap and Acuserve services, and they should say "RUNNING".
Under Windows NT (Intel), if the services are not running, the system will return an error message similar to the following:
[sc]EnumQueryServiceStatus:OpenService failed 1060
Another method for verifying the status of the services is to select:
Start/Settings/Control Panel/Services
and then check the Portmap service status. You should see "Started" under "Status".
You may also check the Event Viewer for more information. Select these options:
Start/Programs/Administrative Tools/Event Viewer/Log/Application
You can examine Acuserve or Portmap service events to determine if there were any errors at startup.
Verify that the permissions are set correctly on the files in the "\acusrv\bin" directory. See Chapter 6, System Security.
To start the Portmap service, contact your system administrator.