We’ve developed some resources to help you work effectively from home during COVID-19 Click to learn more

Install windows client

In this article
    All installation tasks are performed by the new installer found in the folder Server\Client. SOLoader.exe is obsolete.

    To install the client run the MSI Installer SuperOffice7.EN-US.exe (or the correct for your language) found in the Server\Client folder,

    Note: If you want to use Oracles 11g, you need to install the Oracle client drivers on each client first. Oracle 10g may run on the Microsoft version of the Oracle driver. 

    Most probably you get this error message in logfile: 

    "Unable to locate Oracle in registry, based on ORACLE/KEY_OraClient* and ORACLE/ODP.NET; logon will most probably fail. Please reinstall Oracle drivers to get proper registry settings, or set the DynamicLoadedDataBaseDriver and DynamicLoadedDataBaseDriverPolicy settings in the SuperOffice/Data/Database section of superoffice.config manually. Src: DSNTypes::_GetOracleParameters at .\DSNTypes.cpp v$Revision: line 559"

    Then the problem you experience is caused by failure in locating driver and policy files. If you want to learn more about our search algorithm in code please check at the bottom of the answer.

    In order to solve it you have to manually change the SuperOffice.config to where the Oracle driver is installed.

          <Database>
            <add key="DatabaseMajor" value="Oracle" />
            <add key="DatabaseMinor" value="10" />
            <add key="Server" value="<name of the Local TNS Net Service Name>" />
            <add key="Database" value="" />
            <add key="CommandTimeOut" value="300" />
            <add key="TablePrefix" value="<prefix>" />
            <add key="ConnectionString" value="Data Source=[@Server];User Id=[@User];Password=[@Password];" />
            <add key="DynamicLoadedConnectionType" value="Oracle.DataAccess.Client.OracleConnection" />
            <add key="DynamicLoadedDataBaseDriver" value="C:\oracle\product\10.2.0\client_1\BIN\oracle.DataAccess.dll" />
            <add key="DynamicLoadedDataBaseDriverPolicy" value="C:\oracle\product\10.2.0\client_1\odp.net\PublisherPolicy\Policy.10.1.Oracle.DataAccess.dll" />


    Notice the Database key is blank, when you take a look at the connection string we do not use this at all.

    DatabaseMinor should be 10 or 11 depending on which version of Oracle, please not that including  a letter in DatabaseMinor will make the Outlook Mail link fail with version 7.1 or higher, since we create a netserver.config for the maillink at run time.
    The client also needs Oracle Data Provider for .NET version 2.x installed, we are looking for a driver in the x:\oracle\product\10.2.0\client_1\odp.net\bin\2.x folder .

    Our search algorithm in the code is as follows:

    1. Look in the folder where SuperOffice is installed (this is not the usual place for Oracle drivers, but they could be there as a way of distributing them)
    2. Look in the registry, under HKEY_CURRENT_USER
      a.       Look for Software\ORACLE\ODP.NET
      b.      Look for keys within this key
        i.      For each key, get the value of DllPath
        ii.      Go one step up, then add ODP.NET\bin\2.x to this path
        iii.      There should be an Oracle.DataAccess.dll here
        iv.      Using the additional path ODP.NET\PublisherPolicy\2.x
        v.      There should be a Policy dll there
    3. If this does not work, try again under HKEY_LOCAL_MACHINE

     

    Note: Since we're now using the MSI installer - you may not run one client with SQL Server driver and one with Native client. You need to install the Native client on the client if it's not installed.

    It will default install to c:\program files\superoffice\SuperOffice 7 windows.

    If you choose custom you may choose where you want to install it and also choose to install additional programs

     

     

    Repair

    All registration of COM/.Net components has been moved into the new installer which is MSI based and runs under windows installer. This means you must use the Repair-function in the installer to fix a non-working installation