Date: Thu, 1 Apr 2010 19:40:00 +1300
Reply-To: Robin Templer <templerr@CLEAR.NET.NZ>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Robin Templer <templerr@CLEAR.NET.NZ>
Subject: Re: SAS/Access Interface suddenly not working
In-Reply-To: <201003311137.o2VAr8oa016288@mailgw.cc.uga.edu>
Content-type: text/plain; charset=us-ascii
If this is 9.2 - we have had exactly the same issue overnight - SAS/Access
to SybaseIQ stopped working overnight with no error messages. It appears
that even though our setinit has a grace period of 30 days and a warning
period of 30 days, we received no warnings. Perhaps it is just our Access
product not delivering warnings, or all access products, or heaven forbid
all SAS products !! I now have an open Tech Support track and will post any
results I get.
Cheers
Robin
-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Gerhard
Hellriegel
Sent: Thursday, 1 April 2010 12:38 a.m.
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: SAS/Access Interface suddenly not working
first thing to do is to find out which config file is used, maybe a change
there? In that config file, all pathes are defined. Find out which path is
used for ACCESS. Maybe the path is not defined? Check if there is another
config file, normally in the ...SAS\ - root directory. But could also
be "pricate". Check your SAS-start icon, what about a option -config?
Second, check the path from active config-file with windows explorer. Is
it available, is it accessable? If yes, check the contents. If you have
another SAS installation, compare the contents list. Something missing?
Gerhard
On Tue, 30 Mar 2010 13:26:04 -0400, Nathaniel Wooding
<nathaniel.wooding@DOM.COM> wrote:
>Paul
>
>As I understand matters, SETINIT tells you what is licensed but not what
is installed. The topic comes up every so often. Here is a reply posted in
2007:
>
>Nat Wooding
>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>An interesting support note from SAS:
>
> 007640 How to determine which SAS products are installed on a
>Windows system by
> using install detector (filedetv8 and filedetv9)
> Component: Internal DATA step compiler
> Release(s) Reported: 8.1,8.2
> Release(s) Fixed:
> Date Created: 28MAY2002
> Date Last Updated: 12MAR2007
> SN
>http://support.sas.com/techsup/unotes/SN/007/007640.html
>
>
>
>Untested (by me). Sounds interesting as it might help to compare
>SETINIT licensed products vs. installed products.
>
>
>Robert Bardos
>Ansys AG, Zurich, Switzerland
>
>+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>-----Original Message-----
>From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Paul
Kirby
>Sent: Tuesday, March 30, 2010 12:19 PM
>To: SAS-L@LISTSERV.UGA.EDU
>Subject: SAS/Access Interface suddenly not working
>
>Hello everyone, I have developed a strange issue, seemingly out of
nowhere.
>I sometimes kick out final data sets to Excel or Access (or bring things
>into SAS), using the import/export data tools (from the menu bar).
Suddenly,
>on my home machine, this has stopped working. I get an error message
saying
>that I do not have the SAS/Access interface installed. I know for a fact
>that I do, because 1) I have done this a million times before on the same
>machine, and 2) just to verify, I ran Proc Setinit and it shows that I do
>have everything installed (i.e., interfaces to DB2, Oracle, Sybase, PC
>Files, ODBC, OLE DB, Teradata, and MYSQL).
>
>Has anyone ever encountered this before? It's very strange. I'm using
>Vista, the machine is 32-bit (I read somewhere that 64-bit machines have
>problems, but mine's definitely 32), and my SAS version is 9.1.3, service
>pack 4.
>
>Thanks for any input anyone has - Paul Kirby
>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.
| 
