Skip to main content

OBIEE 11g Bi Scheduler Gives Error: "[Nqserror: 75005] Failed To Send Auth Command. 5.7.3 Authentication unsuccessful"
            You get the following error messages running an iBot (agent) in Oracle Delivers:
    [nQSError: 75005] Failed to send AUTH command. SMTP server does not support any authentication mechanisms.  Remove email credentials, or use a server which supports authentication.
Exceeded number of SMTP delivery retries.

Cause:
There are two possible causes:

a)       The BI Scheduler cannot ping/telnet the mail server specified in the scheduler configuration.
b)      The user name and password are specified in the scheduler configuration.
    To check this, log in to Enterprise Manager and navigate to:
        Business Intelligence > Coreapplication > Deployment > Mail.
    If specified, they will be visible here.
Solution
            i.            If the BI Scheduler cannot ping the mail server specified in the scheduler configuration, check the correct server is specified. If it is, check that it is up and running.  
          ii.            If the username and password are specified in the scheduler configuration, log in to Enterprise Manager and navigate to:
        Weblogic Domain
        Right click on bifoundation_domain > Security > Credential
        Expand oracle.bi.enterprise
        Highlight mail.server and take a note of the entries prior to deleting the user name and password.
        Bounce opmn services.

Comments

Post a Comment

Popular posts from this blog

OBIEE 11g Error "Selected item is not of valid selection type" In Agent When Select Dashboard Page For Content

OBIEE 11g Error"Selected item is not of valid selection type" This error applies to OBIEE - version 11.1.1.7.0 and later . When you try to choose a dashboard page for delivery content in an agent, it constantly fails with the error message " Selected item is not of valid selection type ”.  Solution: This error may happen, when there is an added extra space after the end of the name of the dashboard page. For example, instead of "PAGE", it is "PAGE   "  It may happen with a space at the beginning of the name also. Removal of the extra space by renaming the dashboard page will correct the error.

Setting User Defined JVM Memory Arguments in JDeveloper 11g Integrated WebLogic Server

Setting User Defined JVM Memory Arguments in JDeveloper 11g Integrated WebLogic Server This guide explains how to set your own predefined JVM memory arguments for the JDeveloper WebLogic container at startup for the integrated WebLogic server.   This will help avoid java.lang.OutOfMemoryError s experienced on heavy java processes and also improve on the integrated JDeveloper WebLogic server’s performance overall. Steps Locate the file: setDomainEnv.cmd which should be at: [JDeveloper Working Directory]\jdeveloper\system.xxx.xx.xx\DefaultDomain\bin                                 i.             Note: [JDeveloper Working Directory] will be "C:\Documents and Settings\<username>\Application...

Oracle BI Scheduler Error: [nqSError:76015]

Oracle BI Scheduler Error: [nqSError:76015]. The active Oracle BI Scheduler instance in the cluster could not be determined This solution applies to Oracle Business Intelligence Server Enterprise Edition - Version 11.1.1.7 and later The above error appears when a user is unable to save and edit an iBOT/Agent job This is because the data source details are incorrect and not matching with the data connection from tnsnames.ora file To resolve the error, 1.        Log in to Enterprise Manager 2.        Navigate to coreapplication 3.        Open the Deployment tab and navigate to scheduler 4.        Lock and Edit configuration 5.        Copy connection details from tnsnames.ora file NB Don’t include the TNS alias, only copy the connection string after the equal (=) sign. Spaces are OK: For example: (DESCRIPTION=(ADDRES...