Statistician's PC: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 16: Line 16:
With Office/Access 2019 installed,  
With Office/Access 2019 installed,  
* [[#ChartRunner]] gives the following error:  
* [[#ChartRunner]] gives the following error:  
<code>CHARTRunner encountered an issue while displaying your chart. The chart settings need to be edited. The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. </code>
CHARTRunner encountered an issue while displaying your chart. The chart settings need to be edited.  
The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
* [[#SAS]] 9.4 gives the following error:  
* [[#SAS]] 9.4 gives the following error:  
<code>ERROR: Connect: Class not registered
ERROR: Connect: Class not registered  
 
ERROR: Error in the LIBNAME statement.
ERROR: Error in the LIBNAME statement.</code>


The solution is for someone with admin rights to install the following, '''in that order''':  
The solution is for someone with admin rights to install the following, '''in that order''':  

Revision as of 15:48, 7 July 2021

This page contains information that might be required by anyone who needs to do a re-build on the Statistician's computer.

Special Software installed

SAS

  • looks like this can be run with the standard Shared Health install now
  • do we need to provide any product key?
  • SMW


  • Cargo


  • Categories

ChartRunner

  • Julie, is there install media for this? A Product key?
  • SMW


  • Cargo


  • Categories

Microsoft Access Runtimes to deal with bit-wise and Office Version incompatibility

With Office/Access 2019 installed,

CHARTRunner encountered an issue while displaying your chart. The chart settings need to be edited. 
The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
  • #SAS 9.4 gives the following error:
ERROR: Connect: Class not registered 
ERROR: Error in the LIBNAME statement.

The solution is for someone with admin rights to install the following, in that order:

  1. 2013 Runtime - use the 64-bit one
    • regular install
  2. 2010 Runtime - use the 32-bit one, not the 64-bit one
    • run this from the command line with /passive parameter, ie AccessRuntime.exe /passive to avoid bitwise incompatibility error

Related articles

Related articles: