Error On Server Libname Socket
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 spds error error on server libname socket information. The logs are formatted as plain text files. Name Server Start-Up Failed SPD unable to connect to spd name server Server Host Start-Up Failed SAS LIBNAME Assignment Failed Using SETINIT to Extend SPD Server Software 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.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. The -ACLDIR option was omitted from the command line. The -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 SP
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 SPD Server Host Start-Up Failed SAS LIBNAME Assignment Failed Problems Renewing Your SPD Server License 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: The -LICENSEFILE file specification is not valid. http://support.sas.com/documentation/cdl/en/spdsag/63087/HTML/default/p1hy6iwf07p6h1n1hvzw6rcct8nq.htm -LICENSEFILE specifies a file with invalid contents. The name server port is in use by another process. Determine whether another name server process is already running on the same node by issuing the following command: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: The -NAMESERVER node name http://support.sas.com/documentation/cdl/en/spdsag/64019/HTML/default/n19qe5bglpt61nn0ze03jccp9cv8.htm is incorrect. -NAMESERVERPORT specifies the wrong port number if the SPD Server name server is running with a non-standard port assignment. The -PARMFILE file specification is invalid, or the specified file does not exist. The -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. The -ACLDIR option was omitted from the command line. The -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 If the SAS LIBNAME assignment fails, first check the error messages from the SPD Server LIBNAME engine through the SAS LOG output. In most circumstances, you will be able to diagnose the reason for the failure from these messages. Some common problems include: The LIBNAME engine selector that is specified in the LIBNAME statement is invalid. 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
Samples & SAS Notes Focus Areas SUPPORT License Assistance Manage My Software Account Downloads & Hot Fixes TRAINING & BOOKS Books Training Certification SAS Global Academic http://support.sas.com/kb/43945 Program SAS OnDemand For Academics USERS GROUPS Advanced Search support.sas.com Knowledge Base Support Training & Books Store Support Communities Knowledge Base Products & Solutions System Requirements Install Center Third-Party Software Reference Documentation Papers Samples & SAS Notes Browse by Topic Search Samples Search Usage Notes Search Installation Notes Search Problem Notes Focus Areas Problem Note 43945: error on Long table name in SQL JOIN might cause SAS® Scalable Performance Data Server® to disconnect in a Windows environment The code found in the Full Code tab in this Problem Note may cause SPD Server to disconnect and produces the following message in the SAS log file: NOTE: Implicit SQL: select a.xyz123456 from VERYLONGLONGLONGLONGLONGTABLE_A a, VERYLONGLONGLONGLONGLONGTABLE_B b error on server where a.xyz123456 = b.xyz123456 ERROR: ERROR: Server has disconnected.. ERROR: Error on server LIBNAME socket. ERROR: ERROR: Server has disconnected.. ERROR: 10053 - WSAECONNABORTED. The problem is observed when SAS Scalable Performance Data Server is running in a Windows environment. Select the Hot Fix tab in this note to access the hot fix for this problem. This problem is also fixed in SAS® Scalable Performance Data Server® 4.4TSM14. Operating System and Release InformationProduct FamilyProductSystemProduct ReleaseSAS ReleaseReportedFixed*ReportedFixed*SPDSScalable Performance Data ServerMicrosoft Windows XP 64-bit Edition4.52 HF24.52 HF5Microsoft® Windows® for x644.52 HF24.52 HF5Microsoft Windows Server 2003 Datacenter Edition4.52 HF24.52 HF5Microsoft Windows Server 2003 Enterprise Edition4.52 HF24.52 HF5Microsoft Windows Server 2003 Standard Edition4.52 HF24.52 HF5Microsoft Windows XP Professional4.52 HF24.52 HF5Microsoft Windows Server 2003 Enterprise 64-bit Edition4.52 HF24.52 HF5Microsoft Windows Server 2003 Datacenter 64-bit Edition4.52 HF24.52 HF5* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed. The following code assumes you have LIBNAME domain TMP defined in LIBNAMES.PARM
be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 14 Oct 2016 10:31:23 GMT by s_ac15 (squid/3.5.20)