I encountered a strange Sign In issue today after I click on ‘Start BI Services’ option … It was starting the services …Admin , Managed Server and then OPMN sequentially and try to access web URL and throw the issue as :
“There is a problem sending the command to the program” ….Also the sawserver crashed popup appeared .
Now I put the OBIEE11g access URL in browser to see what’s happening and strange …. I am not being able to access it as it is throwing ‘An invalid Username and password was entered’ . I am pretty sure that I have not make any mistake with Weblogic password and as the URL had been already accessed from past couple of days so there might be something wrong …..
While dig into Windows services it has been noticed that ‘Oracle 11g Database TNS Listener service’ not started though set as Automatic, also the Weblogic server log file “bi_server1-diagnostic.log” located under “user_projects\domains\bifoundation_domain\servers\bi_server1\logs” throwing below error :
Caused by: oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element “persistence-config”
MDS-01370: MetadataStore configuration for metadata-store-usage “OWSM_TargetRepos” is invalid.
MDS-00922: The ConnectionManager “oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl” cannot be instantiated.
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: The Network Adapter could not establish the connection
It seems while database Listener down OBIEE not being able to verify the Weblogic connection information including credential verification and hence causing the issue .
So I manually started the Listener service , Stop BI Services and restart it … This also not resolved my problem .
So it seems the problem with Loop back network Adapter configuration .I logged in using my IP address as : “http://<IP>:9704/analytics” and it works fine then I logged out and tried with host:port configuration and voila ! it working perfectly fine this time…. This is one of the strange incident and it is strange enough that the root cause of the issue could not been identified .
Hopefully I would face the same problem and dig into more details … will update the thread then … 🙂