ODBC actions failing using SQL Driver

Version 1

    Verified Product Versions

    AppSense Environment Manager 8.6AppSense Environment Manager 8.5AppSense Environment Manager 8.4AppSense Environment Manager 8.2AppSense Environment Manager 8.1AppSense Environment Manager 8.3AppSense Environment Manager 8.0

    Introduction

    When creating ODBC connections using the SQL Driver via Environment Manager, actions are failing with either

    Error Code 8 - Not enough storage is available to process this command.

    Error Code 6 - The handle is invalid

    An Example of the Audit error:

    Node Name: ODBC Action: Create ODBC Connection called 'Test Connection 'SQL Server' Error Code: component not found in registry. Error Text: 6. The ODBC settings is not created
     
    (To Capture this event Audit events 9406; Using either enabled using an Environment Manager Configuration with Auditing Enabled to the Event Log or Via the Management Center > Enterprise Auditing)

    Detail

    Certain information detected by the Environment Manager console when importing an ODBC connection is not required and causes the action to fail.

    The driver type is created via the "Driver Type" field in the Connection Details so this Data Pair just duplicates this information 

    The "LastUser" will always be the ID of the person using the Environment Manager console to import the connection, so should not be specified when creating a User DSN at logon
    Within each of the SQL Server connections, edit the action and click on the "ODBC Data Pairs" tab, then remove any entries for:
    • Driver
    • LastUser