ATG : Not able to connect to ACC

Could not connect to URL rmi://localhost:8860/atg/devtools/UpdateAgent
Could not get manifest for module <app> from URL http://LP-047DFGRDMDNS:10180/dyn/admin/dynamoModuleResource/?moduleNMae=app&resourceURI=META-INF/MENIFEST.MF
This is usually caused by an incorrect setting of the adminPort property of the Nucleus component /atg/devtools/UpdateAgent.
That property should be set to the HTTP port number for the Dynamo Administration server.

Hi,
Please verify your manifest file, if you are using DafEar.Admin module and check if the manifest contains a blank line at the end (indicating the EOF).
Also, verify if you are pointing to the correct class jar file, like this (assuming that you have two .jar folders:
ATG-Class-Path: lib/classes.jar lib/resources.jar
ATG-Client-Class-Path: lib/classes.jar lib/resources.jar
The last tip is: each manifest.mf line cannot contains more than 72 characters. Verify this.
Hope it helps. Bye.

Similar Messages

  • Not able to connect to My SQL from CIM in ATG 10.2

    Hi,
    I have installed ATG10.2 and trying to configure MySQL database with cim. I have given all the details as per the documentation. After creating the database connection for production_core, i have tried to test the connection but it says that
      >> Not able to connect to database jdbc:mysql://localhost:3306/production_core @prod
    I started My SQL Server from ATG Tools before testing the connection.
    Could you please help me to resolve this issue.
    Regards,
    Ravinder

    There can be multiple reasons:
    mysqld.exe is not running(Start ATG\ATG10.2\MySQL\win32\bin\mysqld.exe)
                        It's the MySQL Daemon, the program that manages MySQL.This should be running if u wish to connect to mysql db.
    While CIM database configuration, wrong connector jar(\ATG\ATG10.2\MySQL\mysql-connector-java-5.1.15-bin.jar) is given, So CIM is not able to connect.
    Db details are wrong CIM
    Refer ATG ENVIRONMENT SETUP ISSUE
    Thanks,
    Nitin.

  • ATG CIM: Not able to connect to database jdbc:oracle:thin

    Hi All,
    I am trying to setup a ATG environment on windows boxes. Below is the setup:
    VM1) DC - Windows Domain Controller (Windows Server 2008)
    VM2) javadb - Oracle 11g (Windows Server 2008)
    VM3) javaweb - ATG 10.0.3 / WebLogic wlserver_10.3/ TomCat 7 (Windows Server 2008)
    Installation / Setup Progress
    * Oracle 11g installation successful. Sample DB successfully created.
    * WebLogic installation successful. Base_Domain successfully created.
    * Able to create successful connection to Oracle (javadb vm) from TomCat (javaweb vm) and query data
    Error: When configuring CIM I keep on getting >> "Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @ scott"+_
    Corrective action already taken:
    1) Disabled firewall on all boxes
    2) Added path of JDBC driver (ojdbc6.jar) in Environment Variables
    3) Tested Oracle 11g (javadb vm) connectivity both from Eclipse and Tomcat. Which is successful
    4) Cleared all files under C:\ATG\ATG10.0.3\CIM\data to reset CIM
    Please refer CIM details below:
    ===========================================
    CIM DISPLAY START
    ===========================================
    -------ENTER CONNECTION DETAILS-----------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    Select Database Type
    *[1] Oracle Thin
    [2] MS SQL
    [3] iNet MS SQL
    [4] DB2
    [5] My SQL
    Select one > 1
    Enter User Name [[system]] > scott
    Enter Password [[**********]] > **********
    Re-enter Password > **********
    Enter Host Name [[javadb]] > javadb
    Enter Port Number [[1521]] > 1521
    Enter Database Name [[sampledb]] > SampleDB
    Enter Database URL [[jdbc:oracle:thin:@javadb:1521:SampleDB]]
    >
    Enter Driver Path [[C:/Oracle/Middleware/wlserver_10.3/server/lib/ojdbc6.jar]]
    Enter JNDI Name [[ATGProductionDS]] >
    -------CONFIGURE DATASOURCE PRODUCTION CORE-----------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    [C] Connection Details - Done
    *[T] Test Connection
    [S] Create Schema
    Import Initial Data
    [D] Drop Schema
    [O] Configure Another Datasource
    > T
    -------TEST DATASOURCE CONNECTION---------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    >> Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @ scott
    ===========================================
    CIM DISPLAY END
    ===========================================
    ===========================================
    CIM LOG START
    ===========================================
    **** Warning     Mon Jul 23 22:46:25 IST 2012     1343063785645     atg.cim.worker.status.StatusUpdateValidator     Status id nonswitchingCore-DatasourceConnectionTemplateStep is unknown.
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator     Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB : -1     java.lang.ArrayIndexOutOfBoundsException: -1
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CTTIoauthenticate.setSessionFields(T4CTTIoauthenticate.java:948)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CTTIoauthenticate.<init>(T4CTTIoauthenticate.java:225)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:358)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:538)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at java.sql.DriverManager.getConnection(DriverManager.java:582)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at java.sql.DriverManager.getConnection(DriverManager.java:185)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.BasicDataSource.getDriverManagerConnection(BasicDataSource.java:526)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.BasicDataSource.getDriverManagerConnection(BasicDataSource.java:588)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.BasicDataSource.getConnection(BasicDataSource.java:475)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.FakeXADataSource.getXAConnection(FakeXADataSource.java:671)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.MonitoredDataSource.createResource(MonitoredDataSource.java:837)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.resourcepool.ResourcePool.populateSlot(ResourcePool.java:2064)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.resourcepool.ResourcePool.checkOut(ResourcePool.java:1332)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.MonitoredDataSource.co(MonitoredDataSource.java:1792)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.service.jdbc.MonitoredDataSource.getConnection(MonitoredDataSource.java:1070)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.worker.databaseconfig.TestJdbcConnectionValidator.performTestConnection(TestJdbcConnectionValidator.java:319)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.worker.databaseconfig.TestJdbcConnectionValidator.validate(TestJdbcConnectionValidator.java:266)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.executeValidations(StepExecutor.java:280)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.ui.text.TextDisplay.processStep(TextDisplay.java:338)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.ui.UIDispatchImpl.processStep(UIDispatchImpl.java:89)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:201)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:69)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:129)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:69)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:129)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchTemplate.execute(LaunchTemplate.java:69)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:129)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.types.LaunchWizard.execute(LaunchWizard.java:73)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.execute(CommandExecutor.java:128)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.command.CommandExecutor.executeCommands(CommandExecutor.java:156)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processStep(StepExecutor.java:216)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.step.StepExecutor.processCurrentStep(StepExecutor.java:80)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.runner.Runner.run(Runner.java:152)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.flow.CimFlow.startupFlow(CimFlow.java:69)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.flow.CimFlowCreator.startDefaultCimFlow(CimFlowCreator.java:78)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.Launcher.startCimFlow(Launcher.java:168)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator          at atg.cim.Launcher.main(Launcher.java:68)
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792213     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator     
    **** Error     Mon Jul 23 22:46:32 IST 2012     1343063792218     atg.cim.worker.databaseconfig.TestJdbcConnectionValidator     Error initializing connection from parameters. Test for jdbc connection failed
    ===========================================
    CIM LOG END
    ===========================================
    Any suggestion how to resolve this issue. Thanks in advance.
    cheers,
    Sandeep
    Edited by: 948180 on Jul 23, 2012 11:29 PM

    Hi,
    Earlier my ojdbc6.jar path was not at the beginning of ClassPath. I have made necessary changes. Please refer below:
    Environment Variables Settings on machine where CIM resides:
    PATH = C:\Oracle\Middleware\wlserver_10.3\server\lib\ojdbc6.jar+;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Java\jre7\bin;C:\Program Files\Apache Software Foundation\Tomcat 7.0\bin;C:\Program Files\cvsnt;C:\Program Files\Java\jdk1.7.0\bin;C:\Program Files\Sun\JavaDB\bin;C:\Program Files\Sun\JavaDB\lib;;C:\ATG\ATG10.0.3\MySQL\win32\bin;C:\ATG\ATG10.0.3\home\bin\;C:\Oracle\Middleware\wlserver_10.3\server\lib\;
    Note: I have verified by ojdbc6.jar path.
    Below are the precise steps I executed after updating my environment variables and restarting CMD.
    ===========================================
    CIM DISPLAY START
    ===========================================
    C:\ATG\ATG10.0.3\home\bin>cim.bat
    Nucleus running
    _ | () |
    __ _ | |_ __ _ ----
    / _` | | __| / _` |
    | (_| | | |_ | (_| |
    \__,_| \__| \__, |
    |___/
    Configuration Installation Manager
    =======CIM MAIN MENU============================================================
    enter [h]elp, [q]uit to exit
    Choose the task you want to perform:
    *[1] Database Configuration
    [2] Server Instance Configuration
    [3] Application Assembly & Deployment
    [P] Product Selection - Done (ATG B2C Commerce)
    [A] Select Application Server - Done (Weblogic Online)
    [C] Custom CIM Plugin Launcher
    > 1
    -------CALCULATE DATASOURCE DEPENDENCIES----------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Calculating Datasource Dependencies. View log file at C:/ATG/ATG10.0.3/home/
    ../CIM/log/cim.log
    |. . |
    |. . |
    -------SELECT A DATASOURCE TO CONFIGURE-----------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    *[P] Publishing
    [C] Production Core
    [D] Done
    > c
    -------CONFIGURE DATASOURCE PRODUCTION CORE-------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    [C] Connection Details - Done
    *[T] Test Connection
    [S] Create Schema
    Import Initial Data
    [D] Drop Schema
    [O] Configure Another Datasource
    > t
    -------TEST DATASOURCE CONNECTION-----------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    >> Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @
    scott
    *[E] Edit Connection Details
    [R] Redo
    [D] Done
    > e
    -------RE-USE VALUES FROM PREVIOUS DATASOURCE-----------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    Base on previous database details:
    [1] system@jdbc:oracle:thin:@javadb:1521:sampledb
    [2] scott@jdbc:oracle:thin:@javadb:1521:SampleDB
    *[3] None/Use Existing
    Select one > 2
    -------ENTER CONNECTION DETAILS-------------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    Select Database Type
    *[1] Oracle Thin
    [2] MS SQL
    [3] iNet MS SQL
    [4] DB2
    [5] My SQL
    Select one > 1
    Enter User Name [[scott]] > scott
    Enter Password [[**********]] > **********
    Re-enter Password > **********
    Enter Host Name [[javadb]] > javadb
    Enter Port Number [[1521]] > 1521
    Enter Database Name [[SampleDB]] > SampleDB
    Enter Database URL [[jdbc:oracle:thin:@javadb:1521:SampleDB]]
    > jdbc:oracle:thin:@javadb:1521:SampleDB
    Enter Driver Path [[C:/Oracle/Middleware/wlserver_10.3/server/lib/ojdbc6.jar]
    ] > C:\Oracle\Middleware\wlserver_10.3\server\lib\ojdbc6.jar
    Enter JNDI Name [[ATGProductionDS]] > ATGProductionDS
    -------CONFIGURE DATASOURCE PRODUCTION CORE-------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    [C] Connection Details - Done
    *[T] Test Connection
    [S] Create Schema
    [I] Import Initial Data
    [D] Drop Schema
    [O] Configure Another Datasource
    > T
    -------TEST DATASOURCE CONNECTION-----------------------------------------------
    enter [h]elp, [m]ain menu, [q]uit to exit
    Production Core
    >> Not able to connect to database jdbc:oracle:thin:@javadb:1521:SampleDB @
    scott
    *[E] Edit Connection Details
    [R] Redo
    [D] Done
    >
    ===========================================
    CIM DISPLAY END
    ===========================================
    Don't understand what could possibly be going wrong.
    Cheers,
    Sandeep
    Edited by: 948180 on Jul 24, 2012 12:23 AM

  • 10g Enterprise Manager is not able to connect to the database instance

    I am running a Oracle 10g database in Solaris 10 server. When i am trying to connect to the enterprise manager it says Enterprise Manager is not able to connect to the database instance.
    The database instance is open,the listener is up and the agent connection also says that it succeeded.
    The server houses two 10g databases and the EM was working properly till yesterday. Kindly Help.
    Thanks in advance.
    Ram

    Hi,
    The EM is started and if i give emctl status dbconsole
    -bash-3.00$ emctl status dbconsole
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.3.0
    Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
    http://gladiator:1158/em/console/aboutApplication
    Oracle Enterprise Manager 10g is running
    Logs are generated in directory /db8/ora10gr2/product/10.2.0/Db_4/gladiator_TROY/sysman/log
    it says that the EM is running. But when i am trying to access the URL it is in IE it says Page cannot be displayed what could be the problem for this???
    Thanks in advance.
    Ram

  • Reporting Services not able to connect with sharepoint

    HI
    We have a Sql server instance where we are not able to install reporting services, so what we have done is we have created one more sql server instance on the same server with reporting services.
    When we configured reporting services in sharepoint integrated mode and try to connect that web service url in sharepoint we are getting an error in sharepoint central administartion  that not able to connect to the reporting services.
    Request you to throw some light on the same.
    Thanks
    Geeth If you feel that the answer which i gave you is Helpful please select it as Answer/helpful.

    Hi Geeth,
    Based on the limited information, I am not very clearly about you issue. In order to solve the problem more efficiently, I need to clarify some information. Could you post more detail information about “try to connect that web service url in sharepoint we
    are getting an error in sharepoint central administartion”? For example, the detail steps about the action, the screenshot of the action, and what error message you received. I’m not sure which step are you trying to do. And could you tell me the edition of
    your SQL Server and SharePoint? It is benefit for us to do further analysis.
    References:
    2008 R2:
    http://technet.microsoft.com/en-us/library/bb283190(v=sql.105).aspx
    http://sharepointtaskmaster.blogspot.in/2010/11/intergration-reporting-service-with.html
    http://technet.microsoft.com/en-us/library/bb326213(v=sql.105).aspx
    2012:
    http://technet.microsoft.com/en-us/library/47efa72e-1735-4387-8485-f8994fb08c8c
    http://denglishbi.wordpress.com/2011/07/22/configuring-sql-server-denali-reporting-services-sharepoint-2010-integration/
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Not able to connect CRM Online to PowerBI

    Not able to connect CRM Online to PowerBI, Please let me know if you have an idea to resolve this issue.
    oops, something went wrong
    Failed to update model parameters
    Activity Id59a2a854-8e34-6636-0679-3d2e245d2241
    Request Id9b7fa606-324e-4ec8-495f-13f91d03bc54
    Error Code400
    TimeWed Mar 18 2015 21:24:18 GMT-0400 (Eastern Daylight Time)
    Version11.0.9165.945
    Cluster URIhttps://wabi-south-east-asia-redirect.analysis.windows.net

    Hi Kiran
    Please chcek the Note 1359600-MDM stopped communicating after upgrading to 7.1.03 from SAP NOTES.
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1359600
    SAP Note Description:
    Summary
    Symptom
    MDM components stopped communicating after upgrading to 7.1.03
    Other terms
    TCP ports, Firewall, connection, network, SP03, SP3, 7.1
    Reason and Prerequisites
    Starting from version 7.1.03 the MDM suite is using different TCP ports for its operations. The change was in order to be compliant with the Internet Authority for Numbering Assignment. Port numbers changed as follows:
    Application Old Port # New Port #
    MDS 20005 59950
    MDLS 20008 59650
    MDIS 20009 59750
    MDSS 20010 59850
    If firewalls were configured to allow MDM's communication throughout the landscape, they actually might prevent (depending on their rules table) the communication after an upgrade to MDM suite starting at version 7.1.03 and higher.
    Solution
    Revise the firewall rules such that they will allow the communication according to the changes described above.
    In order to check that the ports are allowed to pass trough the firewall a telnet test could be done like so:
    1) Open a terminal window (on UNIX) or a command window (on Windows) on the same machine which hosts the application which tries to connect, and issue the following command:
    telnet <MDM server host name or IP address> <TCP port to test>
    2) If no error response is received than it means that the TCP port is allowed to go trough.
    3) Repeat steps 1,2 for all the other ports need by the application.
    Thanks
    Sowseel
    Edited by: sowseel pasumarthi on Jan 18, 2011 6:36 AM

  • Not able to connect N70 to pc(xp) using ca-53 cabl...

    Not able to connect N70 to pc(xp) using ca-53 cable
    hi i am having this trouble from a year... i am unable to connect my phone n70 using cable to my pc,.,. even after installing all drivers n pc suite n havin it reinstalled also n again doin d same process.. its not getting detected at all.. please help me out... pleaseeee..been tryin 4m a year..nevr checkd des forumss.. hopin som bdy ll help ,me out.. !!!. !!!!

    The DKU-2 cable is no longer supported and so cannot be guaranteed to be compatible with current PC Suites, you should be using either your current CA-53 or the CA-70.
    Have you had the chance to connect any other phone with the PC using this cable? This would test if thr cable itself might be faulty.
    Otherwise remove PC Suite, PC Connectivitiy Solution and Connectivity Cable Drivers from control panel, run the PC Suite Cleaner program that you can get from the PC Suite support pages on the web site, then reinstall everything.

  • Not able to connect to wifi wpa2 networks in lenovo vibe x2

    Not able to connect to wifi wpa2 networks in lenovo vibe x2. It displayed saved.but not connecting. It connects to open and WEP wifi networks. Please help

    Are you trying to connect to a 2.4GHz or a 5GHz network?
    What encryption is your router set to use : AES,TKIP/AES,..?
    Have you tried to unplug the router from the power source for 2-3 minutes->Plug it back in-> Wait until it establishes an Internet connection-> Try to recreate the phone connection.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as ''ACCEPT AS SOLUTION"! 
    Unsolicited PM's will not be answered! ....Please post your question/s in the appropriate forum board.
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Not able to connect to a queue under a foreign server.

    Not able to connect to a queue under a foreign server.
    I'm using WebLogic Server Version: 10.3.3.0. The foreign server is running, and can be pinged from this local server. Also the port where queue resides on foreign server, can be accessed through the my local server.
    OS used is AIX 6.0 on both servers.
    Tried restarting the local server but nothing helps. Same error continues.
    HAS ANYBODY FACED THIS PROBLEM? WHAT IS THE CAUSE AND SOLUTION FOR THIS?
    It throws following errors:
    <Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
    javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable [Root exception is java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown']
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:247)
         at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
         at javax.naming.InitialContext.internalInit(InitialContext.java:286)
         at javax.naming.InitialContext.<init>(InitialContext.java:211)
         at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:179)
         at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
         at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
         at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
         at javax.naming.InitialContext.lookup(InitialContext.java:436)
         at weblogic.jms.common.CDS$2.run(CDS.java:503)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
         at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
         at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
         at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
         at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown'
         at weblogic.common.internal.BootServicesStub.getMsg(BootServicesStub.java:34)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         at weblogic.security.acl.internal.RemoteAuthenticate.authenticate(RemoteAuthenticate.java:90)
         at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:746)
         at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:678)
         at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         at weblogic.jndi.Environment.getContext(Environment.java:285)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:239)
         ... 46 more
    >
    <Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
    Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is null>
    <Jun 25, 2012 12:14:45 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:15:03 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:15:25 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:15:35 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:15:43 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:20:53 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    >
    <Jun 25, 2012 12:24:16 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
    java.io.IOException: RJVM has already been shutdown
    java.io.IOException: RJVM has already been shutdown
         at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
         at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
         at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
         at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
         at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
         Truncated. see log file for complete stacktrace
    Edited by: 942523 on Jun 24, 2012 11:38 PM

    Thanks René van Wijk for the reply.
    I have a foreign server created in my local server, where i have already given the provider URL. This foreign server has the one queue and one queue connection factory under it to which I'm referring to.
    Under JNDI tree i noticed this, for the queue(NOTIFY_QUEUE) i'm trying to read from one of the EJB:
    This page displays details about this bound object.
    Failed to create InitialContext using factory specified in hashtable
    Also,etc/hosts has already these IP entries. Even after hardcoding the provider URL its throwing following:
    <Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
    javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
         at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:408)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
         at javax.naming.InitialContext.lookup(InitialContext.java:436)
         at weblogic.jms.common.CDS$2.run(CDS.java:503)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
         at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
         at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
         at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
         at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
         at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
         java.io.EOFException
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
         at weblogic.jndi.internal.ServerNamingNode_1033_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:405)
         ... 36 more
    Caused by: java.io.EOFException
         at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:338)
         at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:768)
         at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:702)
         at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:890)
         at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
         at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:130)
         at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
    >
    <Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
    Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is t3://10.52.50.51:7002>
    Let me know if any other thing i'm missing or it can be something else like network or some other issue.

  • IPad 2 - I am not able to connect my iPad 2 to my tv anymore using AV adapter.

    What is wrong with my iPad 2? I'm not able to conect my iPad to my proyector or tv anymore using AV adaptor. Is there something wrong with my iPad?
    I tried it with my wife's iPad 2 and it was the same result. I was not able to connect her iPad to my TV. Niether TV or a proyector couldn't find the device.
    Would you please help me? Your help will be well appreciated.

    Sounds like the one common thing is the adapter. The cheaper, non apple branded ones tend to fail.
    Try another adaptor before worrying about your ipad.

  • Enterprise Manager is not able to connect to the database instance. The sta

    Enterprise Manager is not able to connect to the database instance. The state of the components are listed below.
    Listener is shown as unavailable.
    lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 27-NOV-2012 11:52:40
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=freds-server.i-surname.co.uk)(PORT=1521)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 27-NOV-2012 11:50:02
    Uptime 0 days 0 hr. 2 min. 37 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /opt/oracle/11g/network/admin/listener.ora
    Listener Log File /opt/oracle/diag/tnslsnr/freds-server/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=freds-server)(PORT=1521)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=freds-server)(PORT=8080))(Presentation=HTTP)(Session=RAW))
    Services Summary...
    Service "GWORCL.i-surname.co.uk" has 2 instance(s).
    Instance "GWORCL", status UNKNOWN, has 1 handler(s) for this service...
    Instance "GWORCL", status READY, has 1 handler(s) for this service...
    Service "GWORCLXDB.i-status.co.uk" has 1 instance(s).
    Instance "GWORCL", status READY, has 1 handler(s) for this service...
    The command completed successfully
    I suspect that this is not just an OEM issue.
    see
    Listener working but not working for Enterprise manager oracle 11gr2 Linux.
    for configuration files
    Edited by: Neill_R on Nov 27, 2012 11:51 AM

    This was solved by : Osama_mustafa
    in the general questions forum
    emca -deconfig dbcontrol db -repos drop
    emca -config dbcontrol db -repos create

  • Problem with EM (Enterprise Manager is not able to connect to the database)

    Hi all,
    I've Oracle DB 11g Rel.1 installed on Windows XP SP3. The database is up and running i.e. everyone can connect to the DB by using any App tool e.g. SQL*Plus, Forms, or Reports. It means that the listener and the service is running. But the problem is that when I try to start the EM I see some error messages on the webpage.
    It says:
    Enterprise Manager is not able to connect to the database instance. The state of the components are listed below.Database Instance (Green arrow)
    Status     Open                         Details     The instance is open.
    Host          shiman
    Port          *1521*
    SID          orcl
    Oracle Home     d:\Oracle\product\11.1.0\db_1
    Agent Connection to Instance (Green arrow)
    Status Succeeded
    Details
    Listener (Green arrow)
    Status     Up
    Host          shiman
    Port          *1521*
    Name          LISTENER
    Oracle Home     d:\Oracle\product\11.1.0\db_1
    Location     d:\Oracle\product\11.1.0\db_1\network\admin
    Details          
    please see the attached file:
    http://rapidshare.com/files/404840300/em.JPGI've already checked all the services, they are running. And when I execute emctl command I got the following message.
    emctl status dbconsole
    Oracle Enterprise Manager 11g Database Control Release 11.1.0.6.0
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    http://shiman:1158/em/console/aboutApplication
    Oracle Enterprise Manager 11g is running.I have checked some documents around config files in sysman and test_orcl\sysman directories. Moreover, I have checked dbsnmp and sysman account for unlockness and password accuracy. But they did not help me to solve the problem.
    My question is if every thing is working fine then what is the problem with the EM? Why it is not connecting to the DB?
    Thanks.
    Iman

    emdctl.trc2010-07-13 18:42:21 Thread-2196 WARN http: snmehl_connect: connect failed to (shiman:1158): No connection could be made because the target machine actively refused it.
    (error = 10061)
    2010-07-13 18:42:26 Thread-4856 WARN http: snmehl_connect: connect failed to (shiman:1158): No connection could be made because the target machine actively refused it.
    (error = 10061)
    2010-07-13 18:42:28 Thread-5684 ERROR ssl: nzos_Handshake failed, ret=28864
    2010-07-13 18:42:28 Thread-5684 ERROR http: 1704: Unable to initialize ssl connection with server, aborting connection attempt
    2010-07-13 18:42:28 Thread-5684 ERROR main: nmectla_agentctl: Error connecting to https://shiman:3938/emd/main. Returning status code 1
    emoms.trc2010-07-13 18:45:44,562 [ApplicationServerThread-1] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:46,875 [ApplicationServerThread-2] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:46,921 [ApplicationServerThread-0] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:47,078 [ApplicationServerThread-2] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:47,125 [ApplicationServerThread-1] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:47,140 [ApplicationServerThread-3] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:47,187 [ApplicationServerThread-0] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:47,234 [ApplicationServerThread-5] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:47,281 [ApplicationServerThread-4] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:47,328 [ApplicationServerThread-6] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:48,984 [ApplicationServerThread-2] ERROR conn.ConnectionService verifyRepositoryEx.818 - Invalid Connection Pool. ERROR = Locale not recognized
    2010-07-13 18:45:49,000 [EMUI_18_45_48_/console/aboutApplication] ERROR svlt.PageHandler handleRequest.639 - java.lang.IllegalStateException: Response has already been committed
    java.lang.IllegalStateException: Response has already been committed
         at com.evermind.server.http.EvermindHttpServletResponse.resetBuffer(EvermindHttpServletResponse.java:1853)
         at com.evermind.server.http.ServletRequestDispatcher.unprivileged_forward(ServletRequestDispatcher.java:260)
         at com.evermind.server.http.ServletRequestDispatcher.access$100(ServletRequestDispatcher.java:42)
         at com.evermind.server.http.ServletRequestDispatcher$2.oc4jRun(ServletRequestDispatcher.java:204)
         at oracle.oc4j.security.OC4JSecurity.doPrivileged(OC4JSecurity.java:283)
         at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:209)
         at oracle.sysman.emSDK.svlt.PageHandler.render(PageHandler.java:1113)
         at oracle.sysman.emSDK.svlt.PageHandler.myRender(PageHandler.java:1173)
         at oracle.sysman.emSDK.svlt.PageHandler.handleRequest(PageHandler.java:597)
         at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:781)
         at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:337)
         at oracle.sysman.eml.app.Console.doGet(Console.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
         at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:87)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
         at oracle.sysman.db.adm.inst.HandleRepDownFilter.doFilter(HandleRepDownFilter.java:134)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
         at oracle.sysman.eml.app.BrowserVersionFilter.doFilter(BrowserVersionFilter.java:122)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
         at oracle.sysman.emSDK.svlt.EMRedirectFilter.doFilter(EMRedirectFilter.java:102)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
         at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:306)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:627)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
         at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230)
         at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
         at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)
    2010-07-13 18:45:49,000 [EMUI_18_45_48_/console/aboutApplication] ERROR em.console doGet.357 - java.lang.IllegalStateException: Response has already been committed, be sure not to write to the OutputStream or to trigger a commit due to any other action before calling this method.
    java.lang.IllegalStateException: Response has already been committed, be sure not to write to the OutputStream or to trigger a commit due to any other action before calling this method.
         at com.evermind.server.http.EvermindHttpServletResponse.sendRedirect(EvermindHttpServletResponse.java:1339)
         at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:806)
         at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:337)
         at oracle.sysman.eml.app.Console.doGet(Console.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
         at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:87)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
         at oracle.sysman.db.adm.inst.HandleRepDownFilter.doFilter(HandleRepDownFilter.java:134)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
         at oracle.sysman.eml.app.BrowserVersionFilter.doFilter(BrowserVersionFilter.java:122)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
         at oracle.sysman.emSDK.svlt.EMRedirectFilter.doFilter(EMRedirectFilter.java:102)
         at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
         at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:306)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:627)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
         at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
         at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
         at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
         at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230)
         at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
         at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
         at java.lang.Thread.run(Thread.java:595)

  • Enterprise Manager is not able to connect to the database instance. The state of the components are listed below.

    Dear all,
    I have trouble to connect em console to database instance. My database is 11.2.0.3 and before this I did the patching from version 11.2.0.1, and now i cannot get fully functionality of em console.
    error is:
    Enterprise Manager is not able to connect to the database instance. The state of the components are listed below.
    It shows that agent is connected, database and listener is up.
    I did recreation, dropping and recreating with emca, but no success.
    Did anyone have similar problems with em console?
    Regards,

    You need to first of all, Connect to the Database as SYSDBA (because your were not connected), then start the database (because it is not started).
    If you already used the username and password in the command prompt and you are sure that the database is already stared, then you need to set the ORACLE_SID before you open SQLPlus. This is because if SQLPlus does not know the SID you are connecting to, it simply thinks it is not up or has no service hence the message "Connected to an idle instance".

  • Enterprise manager is not able to connect to database instance

    Hi
    I am having a problem with Oracle EM. I would appreciate very much if anyone can help me.
    I installed Oracle on XP which runs on virtual pc on XP as well. Everything is fine, I can connect to database with sqlplus, and there were no errors during installation.
    But the problem is that, when I try to connect to database with EM, it says:
    Enterprise manager is not able to connect to database instance . The state of the components are listed below.
    Can anoyone help me?

    user10637311 wrote:
    When you want OEM DB , your existing DB should be created by DBCA or if suppose manually creaed DB then you have to configure that DB to EM by
    "emca -config dbcontrol db -repos create". for these two cases istener should be running.
    emctl start dbconsole -> to start dbconsole service
    emctl status dbconsole-> status of servicesI am sorry, I was looking at $ORACLE_HOME\admin . And in the proper path, both listener.ora and tnsnames.ora do exist.
    emca -config dbcontrol db -repos create :
    <last part>:
    INFO: This operation is being logged at C:\oracle\product\10.2.0\db_1\cfgtoollog
    s\emca\orcl\emca_2010-02-18_02-01-40-AM.log.
    Feb 18, 2010 2:02:46 AM oracle.sysman.emcp.util.DBControlUtil stopOMS
    INFO: Stopping Database Control (this may take a while) ...
    Feb 18, 2010 2:03:19 AM oracle.sysman.emcp.EMReposConfig createRepository
    INFO: Creating the EM repository (this may take a while) ...
    Feb 18, 2010 2:03:19 AM oracle.sysman.emcp.EMReposConfig invoke
    SEVERE: Error creating the repository
    Feb 18, 2010 2:03:19 AM oracle.sysman.emcp.EMReposConfig invoke
    INFO: Refer to the log file at C:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\or
    cl\emca_repos_create_<date>.log for more details.
    Feb 18, 2010 2:03:19 AM oracle.sysman.emcp.EMConfig perform
    SEVERE: Error creating the repository
    Refer to the log file at C:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\orcl\emc
    a_2010-02-18_02-01-40-AM.log for more details.
    Could not complete the configuration. Refer to the log file at C:\oracle\product
    \10.2.0\db_1\cfgtoollogs\emca\orcl\emca_2010-02-18_02-01-40-AM.log for more deta
    ils.
    C:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\or
    cl\emca_repos_create_<date>.log:
    Check if repos user already exists.
    old 6: WHERE username=UPPER('&EM_REPOS_USER');
    new 6: WHERE username=UPPER('SYSMAN');
    old 8: IF ( '&EM_CHECK_TYPE' = 'EXISTS') THEN
    new 8: IF ( 'NOT_EXISTS' = 'EXISTS') THEN
    old 11: raise_application_error(-20000, '&EM_REPOS_USER does not exists..');
    new 11: raise_application_error(-20000, 'SYSMAN does not exists..');
    old 14: ELSIF ( '&EM_CHECK_TYPE' = 'NOT_EXISTS' ) THEN
    new 14: ELSIF ( 'NOT_EXISTS' = 'NOT_EXISTS' ) THEN
    old 17: raise_application_error(-20001, '&EM_REPOS_USER already exists..');
    new 17: raise_application_error(-20001, 'SYSMAN already exists..');
    old 21: raise_application_error(-20002, 'Invalid Check type &EM_CHECK_TYPE');
    new 21: raise_application_error(-20002, 'Invalid Check type NOT_EXISTS');
    DECLARE
    ERROR at line 1:
    ORA-20001: SYSMAN already exists..
    ORA-06512: at line 17

  • Enterprise Manager is not able to connect to the database instance. Open??

    Hello there,
    After I installed oracle database and tried to start Enterprise Manager, I got the message:
    Enterprise Manager is not able to connect to the database instance.
    All statuses are OK (green and up) except database instance. It is also green and up but open. (Details: The instance is open.)
    Can anyone help me about it?
    I use Windows XP x64 with all patches installed. Oracle database R11g x64.
    I tried with different database versions and different machines and different OS and loopback adapter and... my EM still want to log in.
    I can log in with sqlplus. It accepts any pass for sys (as sysdba). Why?
    My log files are available here: http://195.66.185.187/log.zip

    You are using a bequeath connection when logging in with SQL*Plus on the server so the password is not validated.
    Log in using SQL*Plus this way:
    sqlplus /nolog
    followed by
    conn sys@<service_name> AS SYSDBA
    and provide the correct password
    My guess it it will fail.
    If so then you need to use the correct password and if you don't know what it is set it when logged on as SYS.

Maybe you are looking for