IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

Getting this error in IS SERVER " [WmAuditingSC.logger.3405E] (tid=1455) [3405] In logger 'Error Logger', failed to log to destination; reason: Fatal SQLException detected"

  • 1.  Getting this error in IS SERVER " [WmAuditingSC.logger.3405E] (tid=1455) [3405] In logger 'Error Logger', failed to log to destination; reason: Fatal SQLException detected"

    Posted Fri May 19, 2023 07:21 AM

    HI,
    Good Day!

    Whenever I login to the IS, I get the below error. Can you please help me on this

    “[WmAuditingSC.logger.3405E] (tid=1455) [3405] In logger ‘Error Logger’, failed to log to destination; reason: Fatal SQLException detected”

    Thanks in advance

    SQLErrorhttps://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/2513eacfb0112f483ad679638195867cdb2a0801_2_1035x325.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/2513eacfb0112f483ad679638195867cdb2a0801_2_1380x434.png 2x" data-dominant-color="E1E8EE">
    SQLError1922×605 73 KB


    #webMethods
    #Integration-Server-and-ESB


  • 2.  RE: Getting this error in IS SERVER " [WmAuditingSC.logger.3405E] (tid=1455) [3405] In logger 'Error Logger', failed to log to destination; reason: Fatal SQLException detected"

    Posted Sun May 21, 2023 10:09 PM

    Hi Aamir. The message is telling you that the table used by the Error Logger (the WMERROR table) isn’t in the database the your ISCoreAudit JDBC pool connects to. You should check that and, if not there, use the Database Component Configurator tool to run the scripts that will create the ISCoreAudit tables. Another possibility is that you’ve created the auditing tables but your ISCoreAudit JDBC pool is connecting to a different database or a different schema.


    #Integration-Server-and-ESB
    #webMethods


  • 3.  RE: Getting this error in IS SERVER " [WmAuditingSC.logger.3405E] (tid=1455) [3405] In logger 'Error Logger', failed to log to destination; reason: Fatal SQLException detected"

    Posted Mon May 22, 2023 04:06 AM

    Thanks Michael for your help. Much Appreciated!!!

    Now, I have configured the ISCoreAudit JDBC pool for the right database connection (webmuser_IS). The error has disappeared. However, I am unable to see the logs of my operation; it is throwing the another error.

    Error_IShttps://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/e835cde905f6db7820e8cf7df65d90df366b831a_2_1035x450.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/e835cde905f6db7820e8cf7df65d90df366b831a_2_1380x600.png 2x" data-dominant-color="F6F5F5">
    Error_IS1516×660 44.7 KB

    FYI, I have created separate connections in the database for each component. For the ISCoreAudit component, I have connected the JDBC pool to webmuser_IS in the database. I have attached the screenshot for your reference.

    imagehttps://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/5ef34aced8a69ab537a1c5174fb6a331b90aebc3_2_1035x393.png 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/5ef34aced8a69ab537a1c5174fb6a331b90aebc3.png 2x" data-dominant-color="EEEDEE">
    image1157×441 85.3 KB

    For this “Central User Manager initialization failed”. Do I need to modify any connections?

    Thanks in advance for the help!!


    #webMethods
    #Integration-Server-and-ESB


  • 4.  RE: Getting this error in IS SERVER " [WmAuditingSC.logger.3405E] (tid=1455) [3405] In logger 'Error Logger', failed to log to destination; reason: Fatal SQLException detected"

    Posted Mon May 22, 2023 04:07 AM

    image
    image970×776 15.8 KB


    #webMethods
    #Integration-Server-and-ESB


  • 5.  RE: Getting this error in IS SERVER " [WmAuditingSC.logger.3405E] (tid=1455) [3405] In logger 'Error Logger', failed to log to destination; reason: Fatal SQLException detected"

    Posted Mon May 22, 2023 06:18 AM

    Hi Aamir,

    depending on how you have setup your database schema, you will only need four connection pools at minimum:
    IS (containing PE, ProcessAudit, IS Core Audit, IS Internal etc.)
    TN (TradingNetworks)
    MWS (Central User Management)
    Archive (for archiving/deleting old Audit entries)

    Assign the MWS Pool to the Central Users function.

    Remember to configure the SAML-URL under Settings-> Ressources to the MWS URL and the WmMonitor package to the MWS connectivity.

    If you plan to use Optimize, you should setup an additional schema for the Optimize tables.

    In the DB Configurator you should setup the schemas using the PRODUCT section instead of the Components section as the PRODUCT section contains all the components relevant for each product:
    IS: BPM & IntegrationServer (contains PE, IS Core Audit, IS Internal, ProcessAudit, XRef, DocHistory, …)
    MWS: MyWebMetthodsServer (contains the tables for Central Users as well
    TN: TradingNetworks
    Optimize: Optimize
    Archive: Archiving (contains IS Core Audit & ProcessAudit tables additionally for archiving purposes)

    Regards,
    Holger


    #Integration-Server-and-ESB
    #webMethods


Related Content