A Client of ours is having issues with the Quick Fields not being able to connect to the Oracle Database. The Oracle Client software version 11g (32-bit) is now installed on the Quick Fields machine which is running 64- bit Server 2012 R2. The Quick Fields version is 9.0.1.

There is VB script that runs during the storage process to query the Oracle data source and apply the results to the template field values. The Quick Field session in question was copied from a Server 2008 R2. The error below is encountered:

1. Client is able to set-up a 32-bit ODBC connection to the Oracle database successfully through the Windows ODBC.
2. The oracle folder has been added to the path and environment variables in Windows. This set-up with kind of the replica in the 2008 R2 environment where it works.
3. Attempts to register the OraOLEDB11.dll results in failure.

Below is an extract of the VB# script that Quick Fields is using:

Imports System
Imports System.ComponentModel
Imports System.Data
Imports Laserfiche.QuickFields.Scripting
Imports Laserfiche.QuickFields.Scripting.Events

Namespace QuickFields.Scripting
    '''<summary>
    '''Provides one or more methods that can be executed when a Quick Fields event occurs.
    '''</summary>
    Partial Public Class Script1
        ' The ShowMessageBox, ShowErrorBox, ShowDialog, and WriteMessage functions, accessible
        ' through the e.API property, are available to help debug your scripts.

        Private OledbConnectionString As String = "Provider=OraOLEDB.Oracle;Data Source=Database;User Id=dbouser;Password=dbouser;"
        '                   

        '''<summary>
        '''This method executes when the Before document stored (Document.Stored.Before) event occurs.
        '''</summary>
        '''<param name="e">Contains data about the document being stored.</param>
        <ScriptEvent("Document.Stored.Before")>  _
        Public Sub OnBeforeDocumentStored(ByVal e As BeforeDocumentStoredArgs)

            Try

            Dim oledbCon As New Oledb.OledbConnection(OledbConnectionString)         

.....

Any assistance or insight into this issue will be highly appreciated.