Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: Error: The Teradata TPT registry key cannot be opened

  1. #1
    Yossi Shitrit is offline US Technical Team
    Join Date
    Sep 2006
    Posts
    37
    Rep Power
    0

    Default Error: The Teradata TPT registry key cannot be opened

    Problem:

    I have installed the 64bit Teradata connector v1.0 and I am getting the following error when running SSIS package:
    The Teradata TPT registry key cannot be opened. Verify that the TPT API 12.0 for Windows x64 is installed properly.

    I checked and verified that the 64bit TPT API v12.0.0.3 is installed.

    Background:



    The 64bit Teradata connector v1.0 requires the following Teradata components:
    1. 64bit Teradata ODBC Driver
    2. 64bit TPT API version 12.0 with the following operators:

    • Load
    • Stream
    • Export
    The connector searches for the TPT API v12.0 registry key when trying to find the TPT API installation directory.
    The exact registry entry being searched is:
    HKEY_LOCAL_MACHINE\SOFTWARE\NCR\Teradata Parallel Transporter API x8664 12.0

    The 64bit TPT API v12.0.0.3 has the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\NCR\Teradata Parallel Transporter API x8664 12.0.0.3

    Because of the extra minor version number (0.3) in the key name, the connector fails to find the registry key and returns the error mentioned above.

    Solution:

    The solution is to duplicate the Teradata Parallel Transporter API x8664 12.0.0.3 registry key and name it Teradata Parallel Transporter API x8664 12.0. The content of the key should be the same as the original key.
    This will enable the Teradata connector to find the TPT key and to read the TPT installation directory.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  2. #2
    Gadi.Farhat is offline Development Manager
    Join Date
    Mar 2009
    Posts
    255
    Rep Power
    6

    Default

    A similar problem exists when working with the SSIS Teradata connector v1.1 with TPT API v13.10.

    In this case, the user gets one of the following error messages, when running the SSIS package:

    When running in 32-bit mode:
    The Teradata TPT registry key cannot be opened. Verify that the TPT API 12.0 or 13.0 Edition 2 (13.0.0.2) for Windows x86 is installed properly.
    When running in 64-bit mode:
    The Teradata TPT registry key cannot be opened. Verify that the TPT API 12.0 or 13.0 Edition 2 (13.0.0.2) for Windows x64 is installed properly.

    This error occurs although TPT 13.10 is installed, due to changes Teradata made to the registry key of the TPT client in version 13.10, that the connector use to locate the TPT client to load it.

    The Attunity connector is searching the following registry key to locate the TPT API installation folder:

    On x86 machine:
    HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Client\13.0\T eradata Parallel Transporter API 13.0

    On x64 machine:
    HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Client\13.0\T eradata Parallel Transporter API x8664 13.0


    Solution:

    The problem can be solved by creating the registry key, that the Attunity connector uses, manually.

    On x86 machine:
    Duplicate the "HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Client\1 3.10\Teradata Parallel Transporter API 13.10" registry key, with the original contents, and name it "HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Client\1 3.0\Teradata Parallel Transporter API 13.0".

    On x64 machine:
    Duplicate the "HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Client\1 3.10\Teradata Parallel Transporter API x8664 13.10" registry key, with the original contents, and name it "HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Client\1 3.0\Teradata Parallel Transporter API x8664 13.0".


    Regards,

    Gadi
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  3. #3
    jcalvert is offline Junior Member
    Join Date
    May 2011
    Posts
    3
    Rep Power
    0

    Default Teradata TPT key cannot be opened

    I have read the Solutions in the thread and I still have those problems.

    I have successfully installed the TPT but no keys are written to the Registry anywhere. Seems odd, but all the DLLs are in the correct folders under Program Files (x86).
    So I need someone to tell me the exact Key names and the subkey names and their values.
    I can interpret the Folder names to suit my names.
    Then I can build all of that in my Registry.
    My computer is Win 7 64bit but the TPT is 32bit.

    Thanks
    Jim Calvert

  4. #4
    Gadi.Farhat is offline Development Manager
    Join Date
    Mar 2009
    Posts
    255
    Rep Power
    6

    Default

    Hi Jim,

    By default the SSIS package will run in 64-bit mode and therefore, you need to install the 64-bit TPT client.

    Make sure you inastall the TPT client using an account that is a member of the Administrator group.


    Regards,

    Gadi
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  5. #5
    Tadikamalla is offline Junior Member
    Join Date
    Nov 2011
    Posts
    1
    Rep Power
    0

    Default SSIS + Teradat client

    Hi,
    I am trying to fetch data from Teradata using SSIS client. Do i have to download TPT API? I have not installed teradata client , i just installed ODBC driver. I get the following error,

    [Teradata Source [1]] Error: The Teradata TPT registry key cannot be opened. Verify that the TPT API 12.0 or 13.0 Edition 2 (13.0.0.2) for Windows x86 is installed properly.

    AFter googlling found out i have to download TPT API to connect to Teradata. I want to make sure if i am going in the right direction or we do not need tera data client?

    Thanks,
    Krishna

  6. #6
    Gadi.Farhat is offline Development Manager
    Join Date
    Mar 2009
    Posts
    255
    Rep Power
    6

    Default

    Hi

    Yes, you will need to install the TPTAPI with the following operators:
    • Load
    • Stream
    • Export


    Regards,

    Gadi
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  7. #7
    pbibler is offline Junior Member
    Join Date
    Nov 2011
    Posts
    2
    Rep Power
    0

    Default Teradata TPT registry key cannot be opened.

    I have TPT 13.10, SQL 2008, Teradata 12.0 ODBC installed. I believe I have everything I need installed. I am getting the error above, along with "Verify that the TPT API 12.0 for Windows x86 is installed properly". I copied the 13.10 registry key with same contents to a 12.0 registry key, but no luck. Would there possibly be any compatibility issues with the versions I have?

    Thanks in advance for any help. We do a lot of work with Teradata, and TPT will give us a lot more flexibility with our data.

    Regards,

    Paul B.

  8. #8
    Gadi.Farhat is offline Development Manager
    Join Date
    Mar 2009
    Posts
    255
    Rep Power
    6

    Default

    Hi Paul,

    Seems like you are working with the SSIS Teradata connector v1.0. First, i suggest you upgrade to the latest version currently available v1.1, which supports TPTAPI 13. Then follow the steps in post #2 in this thread.

    Note that the TPT registry path (Not only the key) is different in TPT 12.x and TPT 13.x. It was changed from "HKEY_LOCAL_MACHINE\SOFTWARE\NCR\" to "HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Client\13.0\ ".


    Regards,

    Gadi
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  9. #9
    pbibler is offline Junior Member
    Join Date
    Nov 2011
    Posts
    2
    Rep Power
    0

    Default Thanks

    Installing 1.1 did the trick, thank you very much. This is a very useful tool.

  10. #10
    MikeKnox is offline Junior Member
    Join Date
    Feb 2012
    Posts
    1
    Rep Power
    0

    Default Slight twist

    I get the same error message

    The Teradata TPT registry key cannot be opened. Verify that the TPT API 12.0 or 13.0 Edition 2 (13.0.0.2) for Windows x86 is installed properly.

    My issue is that when I go into Regedit -
    HKEY_LOCAL_MACHINE/SOFTWARE/TERADATA/CLIENT I only have 14.00 not 13.10.

    I've reinstalled Attunity 1.1 but that doesn't seem to have made any differences. Any suggestions would be gratefully received.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •