Error in Importing
in [SAS]
|
Prev: help with plotting confidence intervals on the Kaplan-Meier survival curve
Next: Count of distinct records using SQL
From: Gerhard Hellriegel on 22 Aug 2007 05:27 I think there is a error in your LIBNAME! How does it look like? Do you have some special chars in there? Where do the parts of the libname come from? Gerhard On Wed, 22 Aug 2007 10:44:16 +0300, Richie N.M. <sas.kenya(a)GMAIL.COM> wrote: >Hi All, > I get this error > > >ERROR: Connect: > >ERROR: Error in the LIBNAME statement. > >NOTE: Import Cancelled. > >when I try importing Access tables and Excel spreadsheets. The data files >are in a server (OS = Windows 2003 Server). The program for importing used >to run fine but now I get the error above. Even if I copy the files to the >local drive (Windows XP), I still get the same error. What could be the >problem? Thanks in advance for your anticipated help with this. > > > >Regards, > >Richie.
From: "Richie N.M." on 22 Aug 2007 08:04 This is the code: * proc* *import* datafile = "\\fsp-kec1\Data\Projects\HIV-R\Laboratory Data\Coulter Data\Machine_data\CBC_2005.xls" out = work.cbc_05; sheet = "CBCData"; getnames = yes; * run*; There is no libname in the code. On 8/22/07, Gerhard Hellriegel <gerhard.hellriegel(a)t-online.de> wrote: > > I think there is a error in your LIBNAME! > How does it look like? Do you have some special chars in there? Where do > the > parts of the libname come from? > > Gerhard > > > On Wed, 22 Aug 2007 10:44:16 +0300, Richie N.M. <sas.kenya(a)GMAIL.COM> > wrote: > > >Hi All, > > I get this error > > > > > >ERROR: Connect: > > > >ERROR: Error in the LIBNAME statement. > > > >NOTE: Import Cancelled. > > > >when I try importing Access tables and Excel spreadsheets. The data files > >are in a server (OS = Windows 2003 Server). The program for importing > used > >to run fine but now I get the error above. Even if I copy the files to > the > >local drive (Windows XP), I still get the same error. What could be the > >problem? Thanks in advance for your anticipated help with this. > > > > > > > >Regards, > > > >Richie. >
From: Gerhard Hellriegel on 22 Aug 2007 08:22 Normally PROC IMPORT creates a DATA ...; INFILE ....; INPUT ....; program. That is listed in the log. Do you see something like that? Does that look ok? You said, you tried it with a (short?) local path? What happens then? Exactly the same? Or something different? Perhaps you could copy and paste the first part of the generated DATA step? Gerhard On Wed, 22 Aug 2007 15:04:22 +0300, Richie N.M. <sas.kenya(a)GMAIL.COM> wrote: >This is the code: >* > >proc* *import* datafile = "\\fsp-kec1\Data\Projects\HIV-R\Laboratory >Data\Coulter Data\Machine_data\CBC_2005.xls" > >out = work.cbc_05; > >sheet = "CBCData"; > >getnames = yes; >* > >run*; >There is no libname in the code. > > >On 8/22/07, Gerhard Hellriegel <gerhard.hellriegel(a)t-online.de> wrote: >> >> I think there is a error in your LIBNAME! >> How does it look like? Do you have some special chars in there? Where do >> the >> parts of the libname come from? >> >> Gerhard >> >> >> On Wed, 22 Aug 2007 10:44:16 +0300, Richie N.M. <sas.kenya(a)GMAIL.COM> >> wrote: >> >> >Hi All, >> > I get this error >> > >> > >> >ERROR: Connect: >> > >> >ERROR: Error in the LIBNAME statement. >> > >> >NOTE: Import Cancelled. >> > >> >when I try importing Access tables and Excel spreadsheets. The data files >> >are in a server (OS = Windows 2003 Server). The program for importing >> used >> >to run fine but now I get the error above. Even if I copy the files to >> the >> >local drive (Windows XP), I still get the same error. What could be the >> >problem? Thanks in advance for your anticipated help with this. >> > >> > >> > >> >Regards, >> > >> >Richie. >>
From: "Richie N.M." on 22 Aug 2007 10:14 The error I get is a result of running the proc import. I don't have a data step in the code. I get the same error message whether I read the data from the file server or from the local drive. I have tried using the menu (File -> Import Data) and I still get the same error message. The code is as below: ** *proc import* datafile =3D "C:\Data\CBC_2005.xls" out =3D work.cbc_05; sheet =3D "CBCData"; getnames =3D yes; *run;* ** And the error code is as below: ERROR: Connect: =01 ERROR: Error in the LIBNAME statement. Connection Failed. See log for details. NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE IMPORT used (Total process time): real time 7.04 seconds cpu time 0.26 seconds ** * *
From: Nat Wooding on 22 Aug 2007 10:38
Richie How about using the import wizard and then look at the code generated to see how your code differs from what the wizard produces. Nat Wooding Environmental Specialist III Dominion, Environmental Biology 4111 Castlewood Rd Richmond, VA 23234 Phone:804-271-5313, Fax: 804-271-2977 "Richie N.M." <sas.kenya(a)GMAIL. COM> To Sent by: "SAS(r) SAS-L(a)LISTSERV.UGA.EDU Discussion" cc <SAS-L(a)LISTSERV.U GA.EDU> Subject Re: Error in Importing 08/22/2007 10:14 AM Please respond to "Richie N.M." <sas.kenya(a)GMAIL. COM> The error I get is a result of running the proc import. I don't have a data step in the code. I get the same error message whether I read the data from the file server or from the local drive. I have tried using the menu (File -> Import Data) and I still get the same error message. The code is as below: ** *proc import* datafile = "C:\Data\CBC_2005.xls" out = work.cbc_05; sheet = "CBCData"; getnames = yes; *run;* ** And the error code is as below: ERROR: Connect: ERROR: Error in the LIBNAME statement. Connection Failed. See log for details. NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE IMPORT used (Total process time): real time 7.04 seconds cpu time 0.26 seconds ** * * ----------------------------------------- CONFIDENTIALITY NOTICE: This electronic message contains information which may be legally confidential and/or privileged and does not in any case represent a firm ENERGY COMMODITY bid or offer relating thereto which binds the sender without an additional express written confirmation to that effect. The information is intended solely for the individual or entity named above and access by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. |