Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    41
  • Subscribers subscribers
    201
  • Views views
    2224
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BSM 9.10: Error when trying to log into BSM

MigrationDeletedUser

Hello,  

 

I am getting the below error from IIS.   I have checked everything on the Microsoft website for the article on this error. 

 

HTTP Error 500.0 - Internal Server Error Calling LoadLibraryEx on ISAPI filter "I:\HPBSM\bin\IIS\isapi_redirect.dll" failed

 

Does anyone have a clue as to hpow to resovle this or seen this with BSM 9.10 and IIS 7.5?

 

Any information greatly appreciated.

 

Thanks.

Parents
  • 0

    Check the handlers for the IIS.

    Also mention what handlers are enabled currently for the website.

     

    Regards,

    kumaran dp

  • 0 in reply to 
    Hi Kumaran,

    Ensure the ID with which your BSM service is running is having admin rights on GW & DPS server.

    First stop BSM Service. Then run <BAC_install_dir>\dat\iisremoveconfig.bat and then again
    <BAC_install_dir>\dat\iisconfig.bat. It should fix the issue.
  • 0 in reply to 

    Hello Parkar and Rajasekhar,

     

    I performed the above requested steps and still I ge tthe same error.

     

     

    HTTP Error 500.0 - Internal Server Error Calling LoadLibraryEx on ISAPI filter "I:\HPBSM\bin\IIS\isapi_redirect.dll" failed

     

     

    I also cleared my cache and still get same error.

     

    Im running IIS 7.5

     

    Anything else I cna check or any ideas on how to resolve this?

     

    Thanks in advance.

  • 0 in reply to 

    Can you attach the supervisor log to see where it is having an issue. Also check that IIS is running without any issue. You can check System/Application event logs to see if IIS is starting fine when you try to restart IIS service. If it seems to that IIS is corrupted, you can stop BSM service and re-install IIS and then run the above config mentioned.

  • 0 in reply to 

    Rajeskare,

     

    Here are the supervisor log files attached.

     

    Let me know what you find.

     

    Thanks.

  • 0 in reply to 
    I don't see any issues on BSM side and there is no information about attaching to IIS. Have you tried re-installing IIS? Can you try again running the batch files manually from command prompt & provide the output?

    See the application/system event logs for any error information for IIS. One way to verify if your IIS is working fine is to remove topaz at the end BSM URL and open it in a browser. You should get "It Works" message.

    Just wondering if this is an upgraded environment from BAC 8.x to BSM 9.10 environment? If so, there is a bigger issue that need to be addressed.

    On the other note, is this a single server deployment & your DB installed on same server?
  • 0 in reply to 

    Looks to me like there was an upgrade and IIS settings (path to isapi_redirect.dll) have not been updated properly during the upgrade, causing access to BSM Gateway server to fail with HTTP error.

     

    The IIS configuration needs to be changed (via IIS applet in Windows) to reflect the new updated path.


    Can you try this, stop BSM services and on GW execute the following

     

    In the example below BAC 8.07 was installed in D:\HPBAC, BSM 9.12 was installed to D:\HPBSM,
    So the path needs to be changed from "D:\HPBAC" to "D:\HPBSM"

    start
     Internet Information Services (IIS) Manager
    on the left pane select
     <BSM_GW_host>
      IIS
    on the right pane click on
        ISAPI Filters
          Filter name : jakartaFilter
          Executable  : D:\HPBSM\bin\IIS\isapi_redirect.dll

    on the right pane click on
        ISAPI and CGI Restrictions
          ISAPI or CGI path : D:\HPBSM\bin\IIS\isapi_redirect.dll
          Description       : jakartaFilter
          Allow extension path to execute : checked

     


    --Sujith

  • 0 in reply to 

    Rajasekhar,

     

    IIS has not been reinstalled as it has been working prior to BSM isntall.

     

    I ran the batch scripts again and outputs are attahced.

     

    I can see IIS 7 is working fine and says "It works"

     

    No this is not an upgraded environment. This is a new clean install on W2K8 Server.

     

    This is a single server deployment.

     

    Also, I got this error after running the iisconfig.bat script:

     

     

    I:\HPBSM\dat>iisconfig.bat
    log4j:WARN No appenders could be found for logger (com.mercury.infra.utils.logge
    r.LogFactory).
    log4j:WARN Please initialize the log4j system properly.

     

    Thanks.

Reply
  • 0 in reply to 

    Rajasekhar,

     

    IIS has not been reinstalled as it has been working prior to BSM isntall.

     

    I ran the batch scripts again and outputs are attahced.

     

    I can see IIS 7 is working fine and says "It works"

     

    No this is not an upgraded environment. This is a new clean install on W2K8 Server.

     

    This is a single server deployment.

     

    Also, I got this error after running the iisconfig.bat script:

     

     

    I:\HPBSM\dat>iisconfig.bat
    log4j:WARN No appenders could be found for logger (com.mercury.infra.utils.logge
    r.LogFactory).
    log4j:WARN Please initialize the log4j system properly.

     

    Thanks.

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.