Troubleshooting

Using SPD Server Log Files for Troubleshooting

Troubleshooting networked applications can be difficult. Key information for SPD Server troubleshooting can be found in the the Name Server and SPD Server host process log files. With those two log files, you can reconstruct SAS interaction with SPD Server components.

Entries in these log files are time-stamped for reference. You should be able to correlate activities between the two logs by using the time-stamp information. The logs are formatted as plain text files.

Name Server Start-Up Failed

Check the Name Server log file. The log should contain information about the problem. Some common things to look for include:

Invalid -LICENSEFILE file specification.
-LICENSEFILE specifies a file with invalid contents.
The Name Server port is in use by another process. Check for another Name Server process running already on the same node. For example:
```
ps -ef | grep -i spdsnsrv
```

SPD Server Host Start-Up Failed

Check the SPD Server host log file for information. Some common things to look for include:

-NAMESERVER node name is incorrect.
-NAMESERVERPORT specifies the wrong port number, if the SPD Server Name Server is running with a non-standard port assignment.
-PARMFILE file specification is invalid, or the specified file does not exist.
-LIBNAMEFILE file specification is invalid, or the specified file does not exist.
The contents of the specified -LIBNAMEFILE does not conform to expected syntax. Check the SPD Server host log file for messages about invalid entries.
-ACLDIR option was omitted from the command line.
-ACLDIR option specifies an invalid directory path for the SPD Server password file, or the specified directory path does not contain a valid SPD Server password file.

SAS LIBNAME Assignment Failed

On the SAS side, first attempts to diagnose a failure depend on the error messages from the SPD Server LIBNAME engine through the SAS LOG output. In most circumstances you should be able to diagnose the reason for the failure from this message. Some common problems include:

Invalid specification of the LIBNAME engine selector in the LIBNAME statement. The SPD Server engine name is sasspds and is misspelled in the following LIBNAME statement:
```
LIBNAME foo sasspds 'test' 
  server=sunspot.spdsname
  passwd='xxx';
ERROR: Module FOO not found in search paths.
ERROR: Error in the LIBNAME or FILENAME statement.
```
Invalid specification of the logical LIBNAME domain name in the LIBNAME statement. The domain name 'test' is not defined in the SPD Server Name Server sunspot.spdsname:
```
LIBNAME foo sasspds 'test' 
  server=sunspot.spdsname
  passwd='xxx';
ERROR: ERROR: Libname path info not found in SPDS name server.
ERROR: Error in the LIBNAME or FILENAME statement.
```
No name server is running on the specified node name, or no name server is available at the specified port address. In this case, no Name Server is running on the specified node stelling. This same message is generated if the port address is incorrect:
```
LIBNAME foo sasspds 'test' 
  server=stelling.spdsname
  passwd='xxx';
ERROR: Unable to connect to SPDS name server.
ERROR: Connection refused.
ERROR: Error in the LIBNAME or FILENAME statement.
```
An invalid or unknown node name is specified in the LIBNAME statement. In this case, node xxx is not accessible in the network.
```
LIBNAME foo sasspds 'test' 
  server=xxx.spdsname
  passwd='xxx';
ERROR: Unable to connect to SPDS name server.
ERROR: xxx.
ERROR: Error in the LIBNAME or FILENAME statement.
```
Invalid SPD Server user password specified in the LIBNAME statement. In this case, the SPD Server user ID is derived from the UNIX user ID running the SAS session. The SPD Server password file has an entry for this SPD Server user ID, but the password is not xxx:
```
LIBNAME foo sasspds 'test' 
  server=sunspot.spdsname
  passwd='xxx';
ERROR: Error on server LIBNAME socket.
ERROR: SPD server has rejected login from user
sasetb.. ERROR: Error in the LIBNAME or FILENAME
statement.
```
Invalid SPD Server user ID specified in the LIBNAME statement. In this case, the SPD Server user ID xxx does not exist in the SPD Server host's password file. The resulting message is the same for the invalid password case:
```
LIBNAME foo sasspds 'test' 
  server=sunspot.spdsname
  user='xxx' 
  passwd='xxx';
ERROR: Error on server LIBNAME socket.
ERROR: SPD server has rejected login from user xxx..
ERROR: Error in the LIBNAME or FILENAME statement.
```

Using SETINIT to Extend SPD Server Software

When you receive SPD Server, licensing information is pre-initialized. When you renew the license, you receive a new license to replace your existing license. You must restart SPD Server to use the new license.

Note: You should not change the licensing information unless you are logged in with the user ID of the owner of the SPD Server software. You designate the owner of SPD Server when you license the software.