Blog Directory blogs.sas.com RSS BUSINESS LEADERSHIPSAS Voices RSSNews and views from the people who make SAS a great place to workCustomer Intelligence RSSEvolving relationships for business growthGETTING TECHNICALThe SAS Dummy RSSA Reply Chris Hemedinger Posted August 31, 2015 at 4:24 pm | Permalink Jon, yes, I'd agree with that. Reply Pablo Posted December 9, 2013 at 1:51 pm | Permalink Sr. I believe something is not right with the install on my machine. Check This Out
you could try posting in the community forums for advise on this... Thanks Reply Neha Posted August 23, 2016 at 7:57 pm | Permalink Oh I am sorry. using the AD, or a generic common ID? I checked out setinit to verify we had SAS/ACCESS to PC files and we do. http://support.sas.com/kb/49533
Anne Posted August 24, 2016 at 9:20 am | Permalink Thanks. However, you might not have expected it to kick in when you upgraded to 64-bit SAS on Windows. And, it is not likely that so many staff members will be able to systematically coordinate the change of all of the existing catalogs from 32-to-64-bits at one time.
Additional information is that I'm running 64-bit SAS 9.4 on Windows 7. SAS on my laptop was unable to import data containing strange Danish letters (æ,ø,å). It still yields good information for SAS Tech Support diagnostics, but for an accurate in-process picture you should launch this from Help->About->Configuration Details within the SAS application you're checking (EG or Sas Libname Pcfiles With SAS 9.4m1, the 32-bit version of SAS continues to be available and supported.
You can accomplish this by using the Generic Library template though. Sas Error Failed To Connect To The Server Message 1 of 5 (255 Views) Reply 0 Likes ballardw Grand Advisor Posts: 8,187 Re: Connection Error Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Read this SAS note to determine whether these differences will affect your work. http://support.sas.com/kb/16/831.html In addition, the XLS engine cannot be used with a LIBNAME statement.
Thanks again; I can't wait to take your code for a test drive. ----MMMMIIIIKKKKEEEE (aka Michael A. Error: Error In The Libname Statement. Reply Michael A. So, what can they use to tell the difference between the 32 and 64-bit catalogs? In the not-so-distant future, all apps will eventually become native 64-bit.
Then you can rebuild them on the target system using PROC FORMAT and the CTLIN= option. http://support.sas.com/kb/43933.html I hate Universal viewer and love my old viewer. Error: Connect: Class Not Registered Sas Thanks! Sas Pc Files Server You can still use it with the PC Files Server, as described in this note.
Tighten space to use less pages. http://qaisoftware.com/unable-to/unable-to-open-the-specified-video-output-device.html it may helps http://support.sas.com/kb/16/833.html 0 Message Author Comment by:SASnewbie ID: 338596782010-10-08 Hi Iowaloysius, I apologize... I tried using ACCESSCS to export SAS Dataset to ACCESS Database but got the error that "Failed to conenct to the server". I will see what our data manager says about that Reply Anne Posted August 31, 2016 at 2:44 am | Permalink Tried it now, didnt work. Sas 9.4 Pc Files Server
Reply Chris Hemedinger Posted August 23, 2016 at 7:18 am | Permalink If you have 64-bit MS Access and 64-bit SAS, then you should probably try DBMS=ACCESS (not ACCESSCS), since SAS The database might support different time precision than SAS. Still getting this: ERROR: Unable to transcode data to/from UCS-2 encoding. this contact form I'm asking because my co-workers ran into this problem, but it processed fine on my computer and I had the same exact file and version of SAS that they do.
And I am sorry as I am bothering you with my stupid questions one after the another. Unable To Connect To Service/port 9621 Code=3 Operating System and Release InformationProduct FamilyProductSystemProduct ReleaseSAS ReleaseReportedFixed*ReportedFixed*SAS SystemSAS/ACCESS Interface to PC FilesMicrosoft® Windows® for x649.39.3 TS1M0Microsoft Windows Server 2003 for x649.39.3 TS1M0Microsoft Windows Server 2008 for x649.39.3 TS1M0Windows 7 Enterprise if integrated with Windows, have those user accounts been added into the MSSQL to be allowed to connect? 0 LVL 14 Overall: Level 14 Databases 13 MS SQL Server
by the way, is the same code being used across all people? - copy and pasted or typed? permalinkembedsaveparentgive gold[–]jsquared82[S] 0 points1 point2 points 1 year ago(0 children)Hi, just saw this response. There's really no downside to using the 32-bit version of EG 6.1 -- it will work fine with the 64-bit version of SAS. Error: Statement Or Option "getnames" Not Valid For Excelcs Import. Then I need to change the SAS code to the followings accordingly: libname xlsfile pcfiles type=Excel port=8621 server=localhost path = "c:\temp\ExcelFile.xlsx"; libname accfile pcfiles type=Access port=8621 server=localhost path = "c:\temp\AccessFile.accdb";Thanks to
the author said he's not using any libname statement hence the SAS note not being applicable. Here are the results: Grace Period: 45 days (ending 13JAN2011). If you're using [...] By Transitioning to 64-bit SAS on Windows—some resources - SAS Users on September 9, 2014 at 12:45 pm […] The top gotchas when moving to 64-bit SAS http://qaisoftware.com/unable-to/unable-to-add-forward-map-from-timed-out-dhcpd.html I missed out this line "The 32-bit version of SAS Enterprise Guide can save data as MDB (the older MS Access format).
Thanks. Then I started to have problems running some SAS code to read Excel and Access files. Can you try using DBMS=XLS (for xls files) or DBMS=XLSX? 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?
But this is not available in the 64-bit version, due to the architecture differences." So do you mean I wouldn't be able to export data as MDB as I am using on the machines that have an error, could you please execute the following code: proc setinit; run; and attach the log of the resulting run? 0 Message Author Comment by:SASnewbie For another (on an encrypted drive, that I have made sure is accessed when importing) I get this: ERROR: Unable to transcode data to/from UCS-2 encoding. Reply Chris Hemedinger Posted August 24, 2016 at 12:56 pm | Permalink That's right.
However, now with the OS upgrade I cant find a way of moving these elements of the sasuser.profile catalog. However in EG this does not appear possible, I do't want to have to use Proc Import and then write a loop etc....Is it not possible to just use the Excel Make it a deliberate business decision to consider. A quick search came across this helpful blog post.