For SAS Learning Edition 4.1 installation troubleshooting, see
 #018818 .

For pre-4.1 SAS Learning Edition, read the following:

Use the following steps to correct SAS Learning Edition (SAS/LE)
installation and invocation errors such as "Cannot create a copy of the
datasource" and "Cannot connect to the local server". This is the first
of two sections.

There are 3 components to the SAS/LE architecture:

   * EG
   * COM/DCOM connection
   * The SAS System itself

The likely cause of the error is a problem with the COM configuration.
Known causes of this error message are insufficient permissions to
SASUSER or WORK libraries, corrupt SASUSER profiles or SAS portable
registries, expired SAS System products, or SAS System COM registration
problems.

Follow these steps in order and test SAS/LE between each to see if the
problems are corrected:

Section I
Part A. Invoke SAS from SAS.EXE
1. Find the sas.exe on your machine (It is usually in
   c:\program files\sas institute\sas\v8).
2. Double-click on the SAS.EXE.
3. If SAS does not invoke, send any error messages, the SASSETUP.LOG
   and a screen shot of the Event Viewer to SAS Technical Support
   (screen shots of error messages are preferred).
4. If SAS invokes, open an editor window and submit the following
   code: data x; x=1; run;
5. If error message appears, send the error messages, the SASSETUP.LOG
   and a screen shot of the Event Viewer to SAS Technical Support
   (screen shots of error messages are preferred). If the code runs
   successfully and no error message appears, go to Part B.

Part B.  Verify Windows registry settings
1. Navigate to Start>Run.
2. Type regedit in the Run field, and select OK.
3. Drill down to this path:

   HKey_Local_Machine/Software/SAS Institute Inc.
   /The SAS System/CurrentVersion

   i. What is the the CurrentVersion value?
   ii. If there is no value or if the value is not an 8, SAS Learning
       Edition will not work. Make sure that you have administrative
       privileges and reinstall SAS Learning Edition.

4. If SAS/LE does not run as expected, go to Part C.

Part C. Re-register SAS as a COM Server
1. Navigate to Start>Run, type cmd, and press Enter.
2. Change to the directory where the sas.exe module is located
   (the default is c:\program files\sas institute\sas\v8).
3. Type the following command and option and press enter:

   sas.exe /regserver

   Note: SAS gets registered as the default SAS COM server but you
         do not see anything appear in the command window.

4. Restart SAS/LE. If the error message still appears,
   go to Part D.

Note: For Win98, step 1 of part C will not work. You need to access
      the DOS window through the Program button.

Part D. Delete the sdslocal repository and run sdslocal.

1. Navigate to <drive>:\Program Files\SAS Institute\Shared Files\
   SAS Directory Services.
2. Delete the sdslocal repository.
3. From a Windows Command prompt in that same directory, run the
   following command:

      sdsdbmnt -n sdslocal

4. If not sdslocal exists or you cannot create one, go to part E.

E. Install MDAC and Jet Engine
1. Navigate to the Microsoft Web site:

      http://www.microsoft.com/downloads/en/default.aspx

2. Download and install Microsoft Data Access Components (MDAC) 2.7,
   or later, the Jet Engine 4.0 SP3, or later.
3. Reboot.
4. If SAS/LE does not run as expected, go to part F.

Note: In some cases, DCOM on Windows 98 needs to be upgraded and has
resolved this issue. Currently DCOM 1.3 for Windows 98 can be downloaded
from Microsoft at this url:

   http://www.microsoft.com/com/dcom/dcom98/download.asp

Please go to Section II, Part F in SAS Note  #011066 .

Operating System and Release Information