Error 10060 - Wsaetimedout Sas
RAW] nevin.krishna@GMAIL.COM wrote: > I have been tinkering with an url access program which was posted on > the SAS-L quite a while ago..I had it working fine up until about a > week ago when i started encountering a the error (ERROR: 10060 - > WSAETIMEDOUT). i had not changed the program at all, and am not sure > why all of a sudden i am getting this..below please find the log of the > program with error..any advice? Thanks, nevin > NOTE: AUTOEXEC processing completed. > > 1 %let zip=71104; > 2 %let dates=2004/01/01-2004/12/31; > 3 > 4 %let url=http://www.wunderground.com/history/zipcode/&zip/ > 5 %substr(&dates,1,10)/CustomHistory.html > 6 ?dayend=%substr(&dates,20,2) > 7 %nrstr(%str(&)monthend)=%substr(&dates,17,2) > 8 %nrstr(%str(&)yearend)=%substr(&dates,12,4)); > 9 > 10 data Temperatures(keep=Date AvgTemp precip); > 11 length AvgTemp 8 precip 8; > 12 infile %sysfunc(compress("&url")) url lrecl=6000 termstr=cr; > 13 input; > 14 i=index(_infile_,"/DailyHistory.html"); > 15 if i; > 16 date=mdy(scan(substr(_infile_,1,i-1),-2,'/'), > 17 scan(substr(_infile_,1,i-1),-1,'/'), > 18 scan(substr(_infile_,1,i-1),-3,'/')); > 19 input ////; > 20 AvgTemp=scan(_infile_,3,'<>'); > 21 if AvgTemp^=.; > 22 precip=&zip; > 23 run; > > NOTE: Character values have been converted to numeric values at the > places given by: > (Line):(Column). > 16:12 17:10 18:10 20:11 > ERROR: 10060 - WSAETIMEDOUT. > NOTE: The SAS System stopped processing this step because of errors. > WARNING: The data set WORK.TEMPERATURES may be incomplete. When this > step was stopped there were 0 > observations and 3 variables. > NOTE: DATA statement used (Total process time): > real time 23.16 seconds > cpu time 0.17 seconds WSAETIMEDOUT error 10060 is a WinSock error. It's not a SAS error. It's a 'connection timeout' error. You tried to make a connection through Winsock. The target didn't respond properly in the allotted time, or you established a connection which bombed because the host failed to respond properly this time around. It could be due to a ton of things, including changes made at the website you're trying to read. I see that you're just tinkering with this. Still, as I have said approximately 437.3 times before in SAS-L, the SAS URL engine is not made for reliable transmission of HTTP data. Try something else. Try a pipe to a better way of scraping webpages. Use lynx or webget at the other end of your PIPE. Or use a Perl program with some
Samples & SAS Notes Focus Areas SUPPORT License Assistance Manage My Software Account Downloads & Hot Fixes TRAINING & BOOKS Books Training Certification SAS Global Academic 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 http://marc.info/?l=sas-l&m=1166253504136144&w=2 Search Problem Notes Focus Areas Installation Note 37013: SAS Object Spawner might not start during a SASĀ® Enterprise Miner(tm) single machine installation In a SAS Enterprise Miner single machine Windows installation, the following error message might appear in the Object Spawner log when the Object Spawner attempts to start: Processing configuration file (C:\SAS\\Lev1\ObjectSpawner\metadataConfig.xml). http://support.sas.com/kb/37013 The TCP/IP tcpSockConnect() support routine failed with error 10060 (The connection has timed out.). The Bridge Protocol Engine Socket Access Method was unable to connect to host port 8561. This message appears more commonly for the following SAS Enterprise Miner products on machines that are not connected to a domain in a network: SAS Enterprise Miner™ for Desktop Data Mining for the Classroom SAS Enterprise Miner for Personal Workstation (Single–User) As a result of the message, the Object Spawner services will be in a state of "starting". In order to stop the service, you will need to stop objspawn.exe via Windows Task Manager before you can continue with corrective steps. To resolve the problem, follow these steps: Stop the ObjectSpawner service (Start ► Run ► services.msc). If the ObjectSpawner service is in a state of "starting", then end the objspawn.exe process using Windows Task Manager. Make a copy of the file C:\SAS\
is a broadcast address, but the appropriate flag was not set. 10014 WSAEFAULT The function argument is incorrect. 10022 WSAEINVAL Invalid argument or function sequence, or the socket has not http://support.sas.com/documentation/cdl/en/odbcdref/64777/HTML/default/n0a4vhitp9m31an1jsq71z2la752.htm been bound with bind. 10024 WSAEMFILE No more file descriptors are available. http://www.yqcomputer.com/1169_22281_1.htm 10035 WSAEWOULDBLOCK The socket is marked as non-blocking and the operation would block. 10036 WSAEINPROGRESS A blocking Windows sockets call is in progress. 10037 WSAEALREADY The asynchronous routine being canceled has already completed. 10038 WSAENOTSOCK The description is not a socket. 10039 WSAEDESTADDREQ A destination address is required. 10040 error 10060 WSAEMSGSIZE The datagram was too large to fit into the specified buffer and was truncated. 10041 WSAEPROTOTYPE The specified protocol is the wrong type for this socket. 10042 WSAENOPROTOOPT The option is unknown or unsupported. 10043 WSAEPROTONOSUPPORT The specified protocol is not supported. 10044 WSASOCKTNOSUPPORT The specified socket type is not supported in this address family. 10045 WSAEOPNOTSUPP The referenced socket is error 10060 - not the proper type. 10046 WSAEPFNOSUPPORT The protocol family is not supported. 10047 WSAEAFNOSUPPORT The specified address family is not supported. 10048 WSAEADDRINUSE The specified address is already in use. 10049 WSAEADDRNOTAVAIL The specified address is not available from the local machine. 10050 WSAENETDOWN The Windows sockets implementation has detected that the network subsystem has failed. 10051 WSAENETUNREACH The network cannot be reached from this host at this time. 10052 WSAENETRESET The connection must be reset because the Windows sockets implementation dropped it. 10053 WSAECONNABORTED The virtual circuit was terminated due to timeout or another failure. 10054 WSAECONNRESET The virtual circuit was reset by the remote side. 10055 WSAENOBUFS No buffer space is available. 10056 WSAEISCONN The socket is already connected. 10057 WSAENOTCONN The socket is not connected. 10058 WSAESHUTDOWN The socket has been shut down. 10059 WSAETOOMANYREFS Too many references: cannot splice. 10060 WSAETIMEDOUT Attempt to connect timed out without establishing a connection. 10061 WSAECONNREFUSED The attempt to connect was forcefully rejected. 10062 WSAELOOP Too many levels of symbolic links. 10063 WSAENAMETOOLONG The filename is too long. 10064 WSAEHOSTDOWN The h
posted on the SAS-L quite a while ago..I had it working fine up until about a week ago when i started encountering a the error (ERROR: 10060 - WSAETIMEDOUT). i had not changed the program at all, and am not sure why all of a sudden i am getting this..below please find the log of the program with error..any advice? Thanks, nevin NOTE: AUTOEXEC processing completed. 1 %let zip=71104; 2 %let dates=2004/01/01-2004/12/31; 3 4 %let url= http://www.yqcomputer.com/ 5 %substr(&dates,1,10)/CustomHistory.html 6 ?dayend=%substr(&dates,20,2) 7 %nrstr(%str(&)monthend)=%substr(&dates,17,2) 8 %nrstr(%str(&)yearend)=%substr(&dates,12,4)); 9 10 data Temperatures(keep=Date AvgTemp precip); 11 length AvgTemp 8 precip 8; 12 infile %sysfunc(compress("&url")) url lrecl=6000 termstr=cr; 13 input; 14 i=index(_infile_,"/DailyHistory.html"); 15 if i; 16 date=mdy(scan(substr(_infile_,1,i-1),-2,'/'), 17 scan(substr(_infile_,1,i-1),-1,'/'), 18 scan(substr(_infile_,1,i-1),-3,'/')); 19 input ////; 20 AvgTemp=scan(_infile_,3,'<>'); 21 if AvgTemp^=.; 22 precip=&zip; 23 run; NOTE: Character values have been converted to numeric values at the places given by: (Line):(Column). 16:12 17:10 18:10 20:11 ERROR: 10060 - WSAETIMEDOUT. NOTE: The SAS System stopped processing this step because of errors. WARNING: The data set WORK.TEMPERATURES may be incomplete. When this step was stopped there were 0 observations and 3 variables. NOTE: DATA statement used (Total process time): real time 23.16 seconds cpu time 0.17 seconds 24 Top url access error:ERROR: 10060 - WSAETIMEDOUT by tobydun » Thu, 02 Jun 2005 00:44:04 Nevin, It can be caused by a number of problems depending on your systems setup. Go to the SAS tech notes: http://www.yqcomputer.com/ and search for: ERROR: 10060 - WSAETIMEDOUT you will pull up roughly five hits. HTH Toby Dunn From: XXXX@XXXXX.COM Reply-To: XXXX@XXXXX.COM To: XXXX@XXXXX.COM Subject: url access error:ERROR: 10060 - WSAETIMEDOUT Date: Tue, 31 May 2005 08:30:57 -0700 Hello all, I have been tinkering with an url access program which was posted on the SAS-L quite a while ago..I had it working fine up until about a week ago when i started encountering a the error (ERROR: 10060 - WSAETIMEDOUT). i had not changed