Message 1 of 10 (2,946 Views) Reply 0 Likes Accepted Solutions Solution 03-31-2015 02:23 AM KurtBremser Super User Posts: 3,793 Re: Error in SAS import..connection failed & error in libname statement For example I am used to using libname myfile "c:\myfile.xlsx"; and then I will see a connected libref in SAS, and inside each worksheet appears as a dataset. Still requre ACCESS to PC FILES, but they should work in mixed bitness systems. You would need to install (or ask your admin to install) the PC Files Server. Check This Out
Your cache administrator is webmaster. Here is the documentation for 9.4 PC files server http://support.sas.com/documentation/cdl/en/pcfsicg/67728/PDF/default/pcfsicg.pdfThanks ! Can I use my client's GPL software? The following link helped correct the problem 40228 - "Volatile ACE DSN" errors occur when you import Microsot Excel files using the EXCELCS engin...SAS provided technical support to resolve this issue.
See this SAS Note for how to get started. But you can also cure this problem in SAS 9.3/9.4 by aligning the bitness of MS Office with SAS. I have SAS 9.2 (32 bit) installed in a 64 bit OS (laptop) and have MS Office 2010 (32 bit). SAS Note 54413 details the SAS 9.4 PC Files Server installation and usage summary.
Error: Procedure ***** not Found. Reply Chris Hemedinger Posted August 25, 2014 at 8:45 am | Permalink Ray, If importing Excel, then I would expect your import tasks to continue working. However the BASE version of SAS have PC Files installed best I can see from the setinit. Thanks again; I can't wait to take your code for a test drive. ----MMMMIIIIKKKKEEEE (aka Michael A.
But, I was hoping for a better way to do this such as an indicator variable on the catalog's CONTENTS listing or some such facility. I tried to download and install it but still unbale to see it in Registry editor. Even if the files are similar I need to be able to run the export with no errors. Reply Jim Walker Posted January 23, 2015 at 5:04 pm | Permalink Hey Chris, Having an issue here where SAS support site not giving much detail how to fix.
There was a problem with access to the temp location, so the export failed, but the problem was difficult to trace and required some SAS expertise.Tom Message 6 of 10 (2,457 If you're updating database tables in MS Access, then you could use SAS/ACCESS to ODBC for that. However, I noticed the ACCESS Connectivity Engine is missing. But I have to point out that the solutions are far from optimal.
As you may find there are several ways online to deal with this error, for example, check and change the Microsoft Access Connectivity Engine (ACE) registry keys. Reply andre Posted January 29, 2015 at 8:02 am | Permalink Jim i have the same environment. Reply Haikuo Posted October 31, 2013 at 4:41 pm | Permalink Chris, This maybe a silly question, do I need to have MS office installed to use PCFILES engine? Trust SAS to not have a better solution to this.
To check whether you have 32-bit or 64-bit Excel on Office 2010: 1.Start an Office product, such as Excel. I've replaced it with a PROC IMPORT snippet. The PC File Server option is not avaialbe in the new library wizard as a Resource Template. Thanks to the info you provided, I was up and running again in just a couple of minute!
Now EG is running on your server and there is perhaps another way to reach your goal as PCfIle server is working with sas foundation http://www.sas.com/offices/europe/uk/support/sas-hints-tips/unix_windows.html http://www.umass.edu/statdata/software/sas/SASPCFilesServer_Install.pdf is working with a Message 4 of 6 (6,714 Views) Reply 0 Likes ChrisHemedinger Community Manager Posts: 2,256 Re: Error: Connect: Class not registered Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight I checked out setinit to verify we had SAS/ACCESS to PC files and we do. this contact form Your email is never published nor shared.
Is the only way of retrofitting that project to 64-bitness is to convert those Import Data Tasks to written Proc Import code? Speaking of formating excel via SAS DDE, you may have to change your code(Office14) for Microsoft Office 2010:       options noxwait noxsync;       x '"C:\Program Files (x86)\Microsoft I missed out this line "The 32-bit version of SAS Enterprise Guide can save data as MDB (the older MS Access format).
If I create a function with PROC FCMP in 32-bit SAS and save it to a dataset, can a 64-bit version then use the CMPLIB system option to access those functions? Then you can spot check the time/datetime values in your actual export file. System birthday: 07NOV2014. EXCELCS helps me to read in most xls file in SAS 9.4.
Is there anything we can do to the dataset inside or outside of SDD to make it work? Pablo Reply Chris Hemedinger Posted December 10, 2013 at 8:22 pm | Permalink Pablo, Are you talking about the Import Wizard in SAS (not SAS Enterprise Guide)? If this is true, contact SAS Technical Support. navigate here The SAS PC FILE SERVER don't open in windows 7 64bit.
See the following for additional information: SAS Note 43802 details the SAS 9.3 PC Files Server installation and provides code samples. Reply Martin Posted July 7, 2014 at 4:01 pm | Permalink Hi Chris, Thanks for the info. The alternative DBMS= options do not support the MIXED or (more importantly) the GETNAMES options, without which reading in big datafiles is a pain. Turns out the SAS PC files server was 64 bit which did not match with my 32 bit Windows Office.
I'm assuming it needs to be checked but it's a very large file. Gotcha #1: Importing Microsoft Excel files Imagine you have a program that looks like this: proc import out=work.class datafile="c:\temp\class.xls" DBMS = EXCEL; run; On 64-bit SAS for Windows, you might be And if you do go with the 64-bit app, budget the time/resources for 64-bit conversion, if necessary Related posts about 64-bit topics Myths about 64-bit computing on Windows Are 64-bit client On 64-bit SAS, it's WINDOWS_64.
By default, when you install your office 2003 or 2007, it's automatically 32-bit.