Topic
  • 9 replies
  • Latest Post - ‏2013-09-23T14:20:26Z by irina999
irina999
irina999
23 Posts

Pinned topic Problems with configuring Access Manager Runtime 6.1.1 on Win2008 R2 server

‏2013-09-12T12:18:28Z |

Components installed:

All Tivoli Access Manager for e-buisiness 6.1.1 up to FP6 level. Did not configure any component yet.

After installing FP6 run pdconfig GUI application. The first component is Access Manager Runtime.

When I am trying to configure it I am getting TDS Client 6.1 is not found error msg.

TDS Client V6.1 + the latest Inerim fix 57 is installed as  per requirements in the TAM FP6 Readme.

The problem seems to be related to GSK7. I installed GSK7 64 bit with TDS Client installation but looks like its still looking for 32-bit GSK. I am not able to install it. When I run GSK installation from the Policy Server the 32-bit version still can not be installed.

I also tried to install 7.0.4.45-ISS-GSKIT-WinX64-FP0045 as per requirements in FP6 but was not able to run neither 32-bit nor 64-bit installs. When run 64-bit install GSK7BAS_64.msi getting error message "The InstallScript engine is missing from the machine".  When run 32-bit installer getting error saying that need to run it in command prompt with the following syntax

setup gsk7 c:\Progra~1\ibm\gsk7 -sf1".\setup.iss"

The installer still does not create an installation directory in Program Files (86x) folder.

Any help is appreciated. I installed TAM for e-B 6.1.1 before on Linux and did not have issues like this.

Regards,

Irina

  • Mathanleo
    Mathanleo
    6 Posts

    Re: Problems with configuring Access Manager Runtime 6.1.1 on Win2008 R2 server

    ‏2013-09-16T12:24:42Z  

    Hello Irina,

    Try to find the Registered APP: If you've installed GSKit when installing TDS client, Registered App will be LDAP(instead of Policy Director shown below)
     
    1.In the cmd prompt window run the following command
     
    C:\>reg query HKLM\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion /s
     
    the output will be (In My case)
     
    PolicyDirector   REG_SZ   Registered
     
    2.For Uninstalling:
    ==================
     
    C:\Windows>gsk7bui.exe PolicyDirector
     
    3.Execute the below command to delete the installation folder manually.
    C:\> rmdir /S /Q "C:\Program Files (x86)\ibm\gsk7"
     
    4.Delete the registry key value and query registry to double check the uninstallation.
    C:\> reg delete HKLM\SOFTWARE\Wow6432Node\IBM\GSK7
     
    5. Reinstall Gskit(x32 bit) even if you're installing in 64-bit machine. I'd suggest you not to use GSKit x64bit and don't use GSKit provided with TDS client. It will install GSKit with Registered App as LDAP.

    6. To install Gskit(x32) please follow the below steps:

        C:\TAM Installers\CZG8LML_TAMBase611\windows\GSKit> setup PolicyDirector

    7. Set PATH = C:/Program Files(x86)/ibm/gsk7/lib

    8. Check whether the installation works or not with the below command

     C:/Program Files(x86)/ibm/gsk7/bin> gskv7ver

    To configure TAM JAVA RUN TIME use the below command:

    C:\Program Files\Tivoli\Policy Director\sbin>pdjrtecfg.exe -java_path "C:\Program Files (x86)\IBM\Java50\jre" -action config -config_type full -host MachineName -port 7135 -java_home "C:\Program Files (x86)\IBM\Java50\jre"

     

    Thanks 
    Mathan

     

     

    Updated on 2013-09-17T05:14:51Z at 2013-09-17T05:14:51Z by Mathanleo
  • irina999
    irina999
    23 Posts

    Re: Problems with configuring Access Manager Runtime 6.1.1 on Win2008 R2 server

    ‏2013-09-18T14:44:51Z  
    • Mathanleo
    • ‏2013-09-16T12:24:42Z

    Hello Irina,

    Try to find the Registered APP: If you've installed GSKit when installing TDS client, Registered App will be LDAP(instead of Policy Director shown below)
     
    1.In the cmd prompt window run the following command
     
    C:\>reg query HKLM\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion /s
     
    the output will be (In My case)
     
    PolicyDirector   REG_SZ   Registered
     
    2.For Uninstalling:
    ==================
     
    C:\Windows>gsk7bui.exe PolicyDirector
     
    3.Execute the below command to delete the installation folder manually.
    C:\> rmdir /S /Q "C:\Program Files (x86)\ibm\gsk7"
     
    4.Delete the registry key value and query registry to double check the uninstallation.
    C:\> reg delete HKLM\SOFTWARE\Wow6432Node\IBM\GSK7
     
    5. Reinstall Gskit(x32 bit) even if you're installing in 64-bit machine. I'd suggest you not to use GSKit x64bit and don't use GSKit provided with TDS client. It will install GSKit with Registered App as LDAP.

    6. To install Gskit(x32) please follow the below steps:

        C:\TAM Installers\CZG8LML_TAMBase611\windows\GSKit> setup PolicyDirector

    7. Set PATH = C:/Program Files(x86)/ibm/gsk7/lib

    8. Check whether the installation works or not with the below command

     C:/Program Files(x86)/ibm/gsk7/bin> gskv7ver

    To configure TAM JAVA RUN TIME use the below command:

    C:\Program Files\Tivoli\Policy Director\sbin>pdjrtecfg.exe -java_path "C:\Program Files (x86)\IBM\Java50\jre" -action config -config_type full -host MachineName -port 7135 -java_home "C:\Program Files (x86)\IBM\Java50\jre"

     

    Thanks 
    Mathan

     

     

    Hi Mathan,

    Thank you for your response. I managed to run Access Manager Runtime configuration. There were 2 issues:

    1. I installed TDS Client 6.1 from the TAM base components package rather than from any other packages. I tried a few including from the TDS server V6.1.

    2. The issue with GSK7 32-bitI also was able to resolve but not sure if its actually fully resolved. At least I was able to proceed further.

    When I run this command

    C:\TAM Installers\CZG8LML_TAMBase611\windows\GSKit> setup PolicyDirector

    its actually installing GSK7 64-bit and not 32-bit.

    When I tried to run GSK 32 bit from the TAMBase611\windows\GSKit using command line I mentioned in my original post the C:/Program Files(x86)/ibm/gsk7 directory would not be created. You can not see it. What I eventually managed to to is to install and make gsk7 32-bit to show up on a non-default directory c:\gsk7.

    Also I think some gsk dlls should be copied to windows\system32 and windows\SysWOW64 directories. When I tried to launch the Configuration tool I was getting missing dlls errors. When I copied them there I was able to launch it.

    Now when I run

    C:\>reg query HKLM\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion /s

    I am getting the following output

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion
        Version    REG_SZ    7.0.4.45
        InstallPath    REG_SZ    C:\ibm\gsk7
        LibPath    REG_SZ    C:\ibm\gsk7\lib
        BinPath    REG_SZ    C:\ibm\gsk7\bin

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\REGAPPS
        gsk7    REG_SZ    Registered

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\Uninstall
        UninstallFile    REG_SZ    C:\ibm\gsk7\gsk7BUI.isu
        UninstallExe    REG_SZ    C:\Windows\gsk7BUI.exe

    The Runtime configuration task has passed. But when I tried to configure Policy Server next it failed at end with this error:

    HPDBG0938E   Configuration failed.

    I went though all configuration panels and checked that the security domain in TDS was created in the location I specified in config tool.

    One of the failures I came across in the log file is this:

    2013-09-18-07:36:12.051-07:00I----- 0x10652125 PID#3472 FATAL bas mts E:\build\am611\src\mts\mtsicc.cpp 105 0x00000ac0
    HPDBA0293E   ICC API failed. ICC_Init() returns 0, The specified module could not be found.

    2013-09-18-07:36:12.051-07:00I----- 0x10652126 PID#3472 WARNING bas mts E:\build\am611\src\mts\mtsicc.cpp 216 0x00000ac0
    HPDBA0294W   Could not get ICC context.

    Not sure if this is the cause of the failure. Appreciate your feedback.

    Regards,

    Irina

  • Mathanleo
    Mathanleo
    6 Posts

    Re: Problems with configuring Access Manager Runtime 6.1.1 on Win2008 R2 server

    ‏2013-09-19T04:51:20Z  
    • irina999
    • ‏2013-09-18T14:44:51Z

    Hi Mathan,

    Thank you for your response. I managed to run Access Manager Runtime configuration. There were 2 issues:

    1. I installed TDS Client 6.1 from the TAM base components package rather than from any other packages. I tried a few including from the TDS server V6.1.

    2. The issue with GSK7 32-bitI also was able to resolve but not sure if its actually fully resolved. At least I was able to proceed further.

    When I run this command

    C:\TAM Installers\CZG8LML_TAMBase611\windows\GSKit> setup PolicyDirector

    its actually installing GSK7 64-bit and not 32-bit.

    When I tried to run GSK 32 bit from the TAMBase611\windows\GSKit using command line I mentioned in my original post the C:/Program Files(x86)/ibm/gsk7 directory would not be created. You can not see it. What I eventually managed to to is to install and make gsk7 32-bit to show up on a non-default directory c:\gsk7.

    Also I think some gsk dlls should be copied to windows\system32 and windows\SysWOW64 directories. When I tried to launch the Configuration tool I was getting missing dlls errors. When I copied them there I was able to launch it.

    Now when I run

    C:\>reg query HKLM\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion /s

    I am getting the following output

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion
        Version    REG_SZ    7.0.4.45
        InstallPath    REG_SZ    C:\ibm\gsk7
        LibPath    REG_SZ    C:\ibm\gsk7\lib
        BinPath    REG_SZ    C:\ibm\gsk7\bin

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\REGAPPS
        gsk7    REG_SZ    Registered

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\Uninstall
        UninstallFile    REG_SZ    C:\ibm\gsk7\gsk7BUI.isu
        UninstallExe    REG_SZ    C:\Windows\gsk7BUI.exe

    The Runtime configuration task has passed. But when I tried to configure Policy Server next it failed at end with this error:

    HPDBG0938E   Configuration failed.

    I went though all configuration panels and checked that the security domain in TDS was created in the location I specified in config tool.

    One of the failures I came across in the log file is this:

    2013-09-18-07:36:12.051-07:00I----- 0x10652125 PID#3472 FATAL bas mts E:\build\am611\src\mts\mtsicc.cpp 105 0x00000ac0
    HPDBA0293E   ICC API failed. ICC_Init() returns 0, The specified module could not be found.

    2013-09-18-07:36:12.051-07:00I----- 0x10652126 PID#3472 WARNING bas mts E:\build\am611\src\mts\mtsicc.cpp 216 0x00000ac0
    HPDBA0294W   Could not get ICC context.

    Not sure if this is the cause of the failure. Appreciate your feedback.

    Regards,

    Irina

    I'd suggest you to install GSKit from the command prompt window and not directly by executing .exe file.
     
    To Install:
     
    C:\TAM Installers\CZG8LML_TAMBase611\windows\GSKit> setup PolicyDirector
     
    The above command will install GSKit with Registered App as Policy Director.
     
    The directory where gskit is installed is not a problem. We too have a system in which GSKit is installed with partition D: and directory same as like you mentioned.
     
    Below is the output:
     
    C:\>reg query HKLM\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion /s
     
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion
        Version    REG_SZ    7.0.4.44
        InstallPath    REG_SZ    D:\ibm\gsk7
        LibPath    REG_SZ    D:\ibm\gsk7\lib
        BinPath    REG_SZ    D:\ibm\gsk7\bin
     
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\REGAPPS
        gsk7bas    REG_SZ    Registered
        policydirector   REG_SZ    Registered
     
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\Uninstall
        UninstallFile    REG_SZ    D:\ibm\gsk7\gsk7BUI.isu
        UninstallExe    REG_SZ    C:\Windows\gsk7BUI.exe
     
     
    The above command should list PolicyDirector as Registered App. In your case I could find policydirector in REGAPPS is missing.

    Thanks,

    Mathan

  • irina999
    irina999
    23 Posts

    Re: Problems with configuring Access Manager Runtime 6.1.1 on Win2008 R2 server

    ‏2013-09-19T08:53:56Z  
    • Mathanleo
    • ‏2013-09-19T04:51:20Z
    I'd suggest you to install GSKit from the command prompt window and not directly by executing .exe file.
     
    To Install:
     
    C:\TAM Installers\CZG8LML_TAMBase611\windows\GSKit> setup PolicyDirector
     
    The above command will install GSKit with Registered App as Policy Director.
     
    The directory where gskit is installed is not a problem. We too have a system in which GSKit is installed with partition D: and directory same as like you mentioned.
     
    Below is the output:
     
    C:\>reg query HKLM\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion /s
     
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion
        Version    REG_SZ    7.0.4.44
        InstallPath    REG_SZ    D:\ibm\gsk7
        LibPath    REG_SZ    D:\ibm\gsk7\lib
        BinPath    REG_SZ    D:\ibm\gsk7\bin
     
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\REGAPPS
        gsk7bas    REG_SZ    Registered
        policydirector   REG_SZ    Registered
     
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\Uninstall
        UninstallFile    REG_SZ    D:\ibm\gsk7\gsk7BUI.isu
        UninstallExe    REG_SZ    C:\Windows\gsk7BUI.exe
     
     
    The above command should list PolicyDirector as Registered App. In your case I could find policydirector in REGAPPS is missing.

    Thanks,

    Mathan

    Hi Mathan,

    I re-run the install for GSK7 as you suggested and this time Policy Director application was registered in REGAPPS.

    C:\Users\Administrator>reg query HKLM\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion /s

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion
        Version    REG_SZ    7.0.4.45
        InstallPath    REG_SZ    C:\ibm\gsk7
        LibPath    REG_SZ    C:\ibm\gsk7\lib
        BinPath    REG_SZ    C:\ibm\gsk7\bin

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\REGAPPS
        gsk7    REG_SZ    Registered
        PolicyDirector    REG_SZ    Registered

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\Uninstall
        UninstallFile    REG_SZ    C:\ibm\gsk7\gsk7BUI.isu
        UninstallExe    REG_SZ    C:\Windows\gsk7BUI.exe

    But this still did not resolve my problem with configuring Policy Server in Configuration tool. It still failed with the same error.

    Any ideas would be appreciated.

    Regards,

    Irina

  • Mathanleo
    Mathanleo
    6 Posts

    Re: Problems with configuring Access Manager Runtime 6.1.1 on Win2008 R2 server

    ‏2013-09-19T10:21:55Z  
    • irina999
    • ‏2013-09-19T08:53:56Z

    Hi Mathan,

    I re-run the install for GSK7 as you suggested and this time Policy Director application was registered in REGAPPS.

    C:\Users\Administrator>reg query HKLM\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion /s

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion
        Version    REG_SZ    7.0.4.45
        InstallPath    REG_SZ    C:\ibm\gsk7
        LibPath    REG_SZ    C:\ibm\gsk7\lib
        BinPath    REG_SZ    C:\ibm\gsk7\bin

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\REGAPPS
        gsk7    REG_SZ    Registered
        PolicyDirector    REG_SZ    Registered

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\Uninstall
        UninstallFile    REG_SZ    C:\ibm\gsk7\gsk7BUI.isu
        UninstallExe    REG_SZ    C:\Windows\gsk7BUI.exe

    But this still did not resolve my problem with configuring Policy Server in Configuration tool. It still failed with the same error.

    Any ideas would be appreciated.

    Regards,

    Irina

    Hi Irina,

    1.Make sure TDS server is not started in config only mode.

    2. Create the Suffix  SecAuthority=Default (case sensitive) manually:

    dn: SecAuthority=Default
    objectclass: secAuthorityInfo
    objectclass: eApplicationSystem
    objectclass: eSystem
    objectclass: cimLogicalElement
    objectclass: cimManagedSystemElement
    objectclass: cimManagedElement
    objectclass: top
    SecAuthority: Default
    version: 3.0
     

    Save the above content as suffix.ldif file

    3. Run the below command:

    C:\Program Files\IBM\LDAP\V6.2\bin> ldapadd -h localhost -D cn=root -w password -f "D:\suffix.ldif"

    Output:

    Operation 0 adding new entry SecAuthority=Default

    4. Restart TDS server.

    5. Check ibmslapd.log for any issues related to TDS server startup.

    6. Try to configure Policy Server again.

    Configuration Steps:

    Management domain name : Default

    LDAP management domain location DN: Leave blank

    press ok

     

    Then proceed with the other configuration settings

    Lemme know if it works

    Thanks,

    Mathan

    Updated on 2013-09-19T10:29:37Z at 2013-09-19T10:29:37Z by Mathanleo
  • irina999
    irina999
    23 Posts

    Re: Problems with configuring Access Manager Runtime 6.1.1 on Win2008 R2 server

    ‏2013-09-19T10:53:51Z  
    • Mathanleo
    • ‏2013-09-19T04:51:20Z
    I'd suggest you to install GSKit from the command prompt window and not directly by executing .exe file.
     
    To Install:
     
    C:\TAM Installers\CZG8LML_TAMBase611\windows\GSKit> setup PolicyDirector
     
    The above command will install GSKit with Registered App as Policy Director.
     
    The directory where gskit is installed is not a problem. We too have a system in which GSKit is installed with partition D: and directory same as like you mentioned.
     
    Below is the output:
     
    C:\>reg query HKLM\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion /s
     
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion
        Version    REG_SZ    7.0.4.44
        InstallPath    REG_SZ    D:\ibm\gsk7
        LibPath    REG_SZ    D:\ibm\gsk7\lib
        BinPath    REG_SZ    D:\ibm\gsk7\bin
     
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\REGAPPS
        gsk7bas    REG_SZ    Registered
        policydirector   REG_SZ    Registered
     
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IBM\GSK7\CurrentVersion\Uninstall
        UninstallFile    REG_SZ    D:\ibm\gsk7\gsk7BUI.isu
        UninstallExe    REG_SZ    C:\Windows\gsk7BUI.exe
     
     
    The above command should list PolicyDirector as Registered App. In your case I could find policydirector in REGAPPS is missing.

    Thanks,

    Mathan

    I did not create a suffix using the command line before but when I use Web Admin to create a new suffix I do not see the object classes start with cim* name. Please advise. Also should I select all object classes listed above or secAuthorityInfo is sufficient?

    Also even through the configuring policy director task failing but the secAuthority suffix does get created with secAuthorityInfo object class.. Should I still create it manually?

    -------------------------------------------------------------------------------------------------------------------------------

    Additional info:

    Just forgot to mention that my TDS version is 6.3. TAM 6.1.1 server is on a separate machine from the TDS.

    I tried to create Suffix manually through Web Admin tool rather than you using the steps above through the ldif file and it created successfully.

    The Top Object class is secAuthorityInfo. The other object classes that I mentioned did not appear now listed. The TDS server restarted successfully.

    The configuration of the Policy Server failed with the same error.

    -----------------------------------------------------------------------------------------------------------------------

    Now this time I tried to add suffix from the ldif file using the command ldapadd and I got this output:

    Operation 0 adding new entry SecAuthority=Default
    ldap_add: No such object

    The suffix was not created.

    Updated on 2013-09-19T12:59:32Z at 2013-09-19T12:59:32Z by irina999
  • Mathanleo
    Mathanleo
    6 Posts

    Re: Problems with configuring Access Manager Runtime 6.1.1 on Win2008 R2 server

    ‏2013-09-20T04:58:13Z  
    • irina999
    • ‏2013-09-19T10:53:51Z

    I did not create a suffix using the command line before but when I use Web Admin to create a new suffix I do not see the object classes start with cim* name. Please advise. Also should I select all object classes listed above or secAuthorityInfo is sufficient?

    Also even through the configuring policy director task failing but the secAuthority suffix does get created with secAuthorityInfo object class.. Should I still create it manually?

    -------------------------------------------------------------------------------------------------------------------------------

    Additional info:

    Just forgot to mention that my TDS version is 6.3. TAM 6.1.1 server is on a separate machine from the TDS.

    I tried to create Suffix manually through Web Admin tool rather than you using the steps above through the ldif file and it created successfully.

    The Top Object class is secAuthorityInfo. The other object classes that I mentioned did not appear now listed. The TDS server restarted successfully.

    The configuration of the Policy Server failed with the same error.

    -----------------------------------------------------------------------------------------------------------------------

    Now this time I tried to add suffix from the ldif file using the command ldapadd and I got this output:

    Operation 0 adding new entry SecAuthority=Default
    ldap_add: No such object

    The suffix was not created.

    Oops!. I missed this step. Actually we need to create suffix manually before adding the ldif file. 

    Refer to the attached screenshot for manually creating suffix. Once you've created, you can import the ldif file.

    Have you checked ibmslapd.log file? Does it shows any errors?

    As per the IBM documentation we followed these steps:

    http://www-01.ibm.com/support/docview.wss?uid=swg1IY69937

    Thanks,

    Mathan

    Attachments

    Updated on 2013-09-20T05:12:12Z at 2013-09-20T05:12:12Z by Mathanleo
  • irina999
    irina999
    23 Posts

    Re: Problems with configuring Access Manager Runtime 6.1.1 on Win2008 R2 server

    ‏2013-09-20T15:05:41Z  
    • Mathanleo
    • ‏2013-09-20T04:58:13Z

    Oops!. I missed this step. Actually we need to create suffix manually before adding the ldif file. 

    Refer to the attached screenshot for manually creating suffix. Once you've created, you can import the ldif file.

    Have you checked ibmslapd.log file? Does it shows any errors?

    As per the IBM documentation we followed these steps:

    http://www-01.ibm.com/support/docview.wss?uid=swg1IY69937

    Thanks,

    Mathan

    Hi Mathan,

    I was able to go trough all steps and created a security domain from the ldif file successfully, however, the configuration of the Policy Server failed with the same error.

    Found this errors in the configuration log file:

    HPDBA0293E   ICC API failed. ICC_Init() returns 0, The specified module could not be found.


    2013-09-20-07:59:40.825-07:00I----- 0x10652126 PID#2148 WARNING bas mts E:\build\am611\src\mts\mtsicc.cpp 216 0x000007dc
    HPDBA0294W   Could not get ICC context.

    Any other ideas very much appreciated as I seems to be stuck.

    Many thanks,

    Irina

    Updated on 2013-09-20T15:10:13Z at 2013-09-20T15:10:13Z by irina999
  • irina999
    irina999
    23 Posts

    Re: Problems with configuring Access Manager Runtime 6.1.1 on Win2008 R2 server

    ‏2013-09-23T14:20:26Z  
    • irina999
    • ‏2013-09-20T15:05:41Z

    Hi Mathan,

    I was able to go trough all steps and created a security domain from the ldif file successfully, however, the configuration of the Policy Server failed with the same error.

    Found this errors in the configuration log file:

    HPDBA0293E   ICC API failed. ICC_Init() returns 0, The specified module could not be found.


    2013-09-20-07:59:40.825-07:00I----- 0x10652126 PID#2148 WARNING bas mts E:\build\am611\src\mts\mtsicc.cpp 216 0x000007dc
    HPDBA0294W   Could not get ICC context.

    Any other ideas very much appreciated as I seems to be stuck.

    Many thanks,

    Irina

    Hi Mathan,

    Just to inform you that I was able to configure Policy Server successfully by uninstalling, cleaning and re-installing GSK7 32-bit as per your instruction above.

    Both configurations of TAM Runtime and Policy Server completed successfully.

    Thank you for all your help and support.

    Regards,

    Irina