Server Software

Local logon failure (Windows only). Users might encounter a situation when logon fails because they do not have the local logon privilege on the server. To resolve this problem, you need to make changes to the spssprod.inf file. For more information on this known issue and the related interim fix, see Workaround for Server requirement that users have "allow log on locally" privilege.

Port number conflict. If there is a port number conflict, the server software may fail to start. Correct the problem by using the administration application (IBM® SPSS® Statistics Administration Console, which is installed as part of IBM SPSS Deployment Manager) to change the port number. See the topic Connections in the Deployment Manager User's Guide (included in the help for IBM SPSS Collaboration and Deployment Services) for more information.

Erratic behavior. The server software may behave erratically if its configuration file (for example, statisticsd.conf) is corrupted or missing. To correct the problem, restore the configuration file from your backup copy. Copy it to the location specified in the administration application or the configuration file environment variable and restart the server software. For more information on restarting, see Starting and Stopping the Server Software in.

Administration application doesn’t work (UNIX only). If you use the administration application to control or configure the server software and it doesn’t work (for example, you cannot stop the server), it may be because you did not start the server software with the startup script that is provided by IBM Corp.. Correct the problem by starting the server software with the start_statistics_server startup script. See the topic To Stop the Service or Daemon for more information. If you get an error message when you attempt to control or configure the server software, it may be because you have connected with an account that does not have administrator permissions. See the topic Users for more information.

Can’t change the location of temporary files (UNIX only). If you use the administration application to change the location of temporary files and the change is not effective, it may be because the new location doesn’t have sufficient file permissions for the end users. Choose a location that has a read, write, and execute access for all the users who connect to the server software.

Server doesn’t start (UNIX only). If the server software does not start, it may be because you do not have the required operating system patches. To correct the problem, download and install the appropriate patch. The required patches are listed in the UNIX installation instructions for your server product.