ALSB 2.6 Error Accessing Test Configuration - Test Console

When trying to use the Test Console (bug) for any Proxy Service I get the following message.
An unexpected error occurred accessing the test service: java.net.ConnectException: t3://(domain name): No known valid port for: 'Default[t3]:t3(t3):null:7201:(ip address):-1'; No available router to destination
The test console was working in v2.5.
Thanks,
Christopher Venckus

Good day,
I am having a similar issue. I checked and the cluster address is properly set and the ALSB Test Framework EAR is deployed to the cluster. My cluster has two managed servers on separate machines and there is an admin server (not in the cluster) managing the domain. Are there any other things we could try? Also, how can we enable logging of this call? Nothing (no exceptions) are coming out in any of the log files.
Thanks,
Sean

Similar Messages

  • Error Accessing Test Configuration

    Hi,
    I am facing a similar issue. Test console gets opened for few services but for few of them the console is not opening.
    Below is the error i am facing
    Error Accessing Test Configuration
    Validation of ProxyService ProxyService/PS_V1 : ProxyService ProxyService/PS_V1 does not exist failed
    I could see the proxy servive clearly in the console. It happened for one of the service so i created another proxy based on the proxy which is not showing the test console and the new one got opened. But after some time one more proxies test console is not opening.
    I see both admin server and managed server running.
    And in ALSB debug.xml the test console flag is set to true.
    Wht is the issue. Any sugestions on this?? appreciate your help

    Hi,
    I saw the metalink ID but there the error was different it is somtthing like
    Validation failed for proxy service. Referenced component not found.
    But i am getting an error
    Validation of ProxyService MainFlow/ProxyService/PS_Dequeue_V2 : ProxyService MainFlow/ProxyService/PS_Dequeue_V does not exist failed
    Initially when i got this error i just recreated the proxy and it worked fine. But now i am getting this error for almost all the proxy services. I am not able to understand what is the issue. Any suggestions on this?

  • Error accessing Phone Configuration page in Call Manager

    I used BAT to delete auto-generated device profiles. Status and log file showed records were deleted successfully, however, I get the following error message when attempting to access the phone configuration page:
    Error
    The following error occurred while trying to retrieve the information for the requested phone.
    selecting device: OK
    Getting RIS for device: OK
    Getting device properties: OK
    authenticationStr [object Object]OK
    keySizeList 2OK
    certOperationList 1OK
    upgradeFinishTime 2005:7:23:10OK
    LSCStatus 1OK
    packetCaptureMode 0OK
    packetCaptureDuration 60 DONE selecting device: OK
    Getting hotelling info:
    The current item or one of its properties is not valid. It may have been deleted since the page was last refreshed. (2)
    Restarting our Pub and Subs did not resolve issue.
    Any suggestions?

    From the error, seems like a database corruption for the phone. You might just need to delete the phone and delete it from Unassigned DN list and then try to add it back in again . if this does not work trymodifying entries in the SQL TB .. IKEdevice_defaultprofile

  • Error accessing Application Server Control Console

    I just downloaded oc4j_extended_101330.zip and installed it at
    /u01/app/oracle/oracle/product/10.2.0/oc4j
    I then ran the following commands:
    export ORACLE_HOME=/u01/app/oracle/oracle/product/10.2.0/oc4j
    export J2EE_HOME=$ORACLE_HOME/j2ee/home
    export JAVA_HOME=/u01/app/oracle/oracle/product/10.2.0/db_1/jdk
    export PATH=$JAVA_HOME/bin:$PATH
    java -version
    java version "1.4.2_08"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
    Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)
    cd $J2EE_HOME
    java -jar jazn.jar -activateadmin <password>
    cd bin
    ./oc4j -start
    Once the server was up and running I went to http://localhost:8888 and saw the ocj4 home page. Then I tried to access the Application Server Control Console at http://localhost:8888/em and received an internal server error 500. The logs reported this exception:
    08/02/20 13:38:59.807 ascontrol: Error initializing servlet
    java.lang.NoClassDefFoundError
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:141)
    at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:62)
    at java.awt.Font.initializeFont(Font.java:308)
    at java.awt.Font.<init>(Font.java:344)
    at oracle.sysman.ias.studio.app.StudioConsole.loadFont(StudioConsole.java:292)
    at oracle.sysman.ias.studio.app.StudioConsole.init(StudioConsole.java:107)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpApplication.loadServlet(HttpApplication.java:2371)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpApplication.findServlet(HttpApplication.java:4824)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpApplication.findServlet(HttpApplication.java:4748)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2971)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:741)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:221)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:122)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].server.http.HttpRequestHandler.run(HttpRequestHandler.java:111)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.3.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:534)
    I believe I've followed the installation and startup directions correctly. Any thoughts on what I might have done wrong?
    Thanks

    Hi,
    It works with jdk 1.5 corect. With java 1.4.2 try to run oc4j using this command:
    OC4J_JVM_ARGS=-Djava.awt.headless=true ./oc4j -start
    Regards,
    Tomas

  • Error using the test console of the Oracle Service Bus 11gR1

    Hi I am facing a an issue while using the test console of the Oracle Service Bus 11gR1 .
    Every time I try to execute a business service or a proxy service I end up getting the following message.
    Error Accessing Test Configuration
    *"Test Console" service is not running. Contact administrator to start this service.*
    In fact to add to my frustration I am unable to execute any of my proxy services from outside clients like SOAPUI as well.
    Is anyone else facing this too ??
    Also every time the server starts I can see some diagnostic error messages on my Eclipse console.
    *[ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.*
    Attached the whole log at the end below.
    To provide an update on my trouble shooting
    1. ) I tried to give the IntegrationAdmin and IntegrationDeployer roles to my admin user. in fact i also tried to give it all the possible privileges.
    Result: Still the same error message.
    Error Accessing Test Configuration
    "Test Console" service is not running. Contact administrator to start this service.
    2.) I have already tried to change the following entry <java:alsb-test-console-debug>true</java:alsb-test-console-debug> in my C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\alsbdebug.xml
    I am also attaching the file contents here
    <java:sb-debug-logger xmlns:java="java:com.bea.wli.debug">
    <java:alsb-stages-transform-runtime-debug>false</java:alsb-stages-transform-runtime-debug>
    <java:alsb-alert-manager-debug>false</java:alsb-alert-manager-debug>
    <java:alsb-credential-debug>false</java:alsb-credential-debug>
    <java:alsb-jms-reporting-provider-debug>false</java:alsb-jms-reporting-provider-debug>
    <java:alsb-management-credential-debug>false</java:alsb-management-credential-debug>
    <java:alsb-management-dashboard-debug>false</java:alsb-management-dashboard-debug>
    <java:alsb-management-debug>false</java:alsb-management-debug>
    <java:alsb-management-user-mgt-debug>false</java:alsb-management-user-mgt-debug>
    <java:alsb-module-debug>false</java:alsb-module-debug>
    <java:alsb-monitoring-aggregator-debug>false</java:alsb-monitoring-aggregator-debug>
    <java:alsb-monitoring-debug>false</java:alsb-monitoring-debug>
    <java:alsb-pipeline-debug>false</java:alsb-pipeline-debug>
    <java:alsb-security-wss-debug>false</java:alsb-security-wss-debug>
    <java:alsb-service-account-manager-debug>false</java:alsb-service-account-manager-debug>
    <java:alsb-service-provider-manager-debug>false</java:alsb-service-provider-manager-debug>
    <java:alsb-service-repository-debug>false</java:alsb-service-repository-debug>
    <java:alsb-service-security-manager-debug>false</java:alsb-service-security-manager-debug>
    <java:alsb-service-validation-debug>false</java:alsb-service-validation-debug>
    <java:alsb-test-console-debug>true</java:alsb-test-console-debug>
    <java:alsb-transports-debug>false</java:alsb-transports-debug>
    <java:alsb-uddi-debug>false</java:alsb-uddi-debug>
    <java:alsb-wsdl-repository-debug>false</java:alsb-wsdl-repository-debug>
    <java:alsb-wspolicy-repository-debug>false</java:alsb-wspolicy-repository-debug>
    <java:alsb-security-encryption-debug>false</java:alsb-security-encryption-debug>
    <java:alsb-security-module-debug>false</java:alsb-security-module-debug>
    <java:alsb-sources-debug>false</java:alsb-sources-debug>
    <java:alsb-custom-resource-debug>false</java:alsb-custom-resource-debug>
    <java:alsb-mqconnection-debug>false</java:alsb-mqconnection-debug>
    <java:alsb-throttling-debug>false</java:alsb-throttling-debug>
    <java:alsb-flow-resource-debug>false</java:alsb-flow-resource-debug>
    <java:alsb-flow-transport-debug>false</java:alsb-flow-transport-debug>
    <java:alsb-flow-deployment-debug>false</java:alsb-flow-deployment-debug>
    <java:alsb-debugger-debug>false</java:alsb-debugger-debug>
    <java:alsb-console-debug>false</java:alsb-console-debug>
    <java:alsb-result-caching-debug>false</java:alsb-result-caching-debug>
    <java:alsb-bpel-debug>false</java:alsb-bpel-debug>
    <java:alsb-jca-framework-adapter-debug>false</java:alsb-jca-framework-adapter-debug>
    </java:sb-debug-logger>
    starting weblogic with Java version:
    java version "1.6.0_18"
    Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
    Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\home11g\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=AdminServer -Djava.security.policy=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server\lib\weblogic.policy -Xverify:none -da -Dplatform.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\home11g\WLSERV~1.3\server -Ddomain.home=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1 -Dcommon.components.home=C:\Oracle\MIDDLE~1\home11g\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\AdminServer -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\home11g\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\home11g\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\home11g\patch_wls1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\home11g\patch_oepe1033\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\home11g\patch_ocp353\profiles\default\sysext_manifest_classpath weblogic.Server
    <30-Jun-2010 16:22:43 o'clock BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 16.0-b13 from Sun Microsystems Inc.>
    <30-Jun-2010 16:22:47 o'clock BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
    <30-Jun-2010 16:22:48 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <30-Jun-2010 16:22:48 o'clock BST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <30-Jun-2010 16:22:49 o'clock BST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <30-Jun-2010 16:22:49 o'clock BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log00005. Log messages will continue to be logged in C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log.>
    <30-Jun-2010 16:22:49 o'clock BST> <Notice> <Log Management> <BEA-170019> <The server log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
    <30-Jun-2010 16:22:56 o'clock BST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <30-Jun-2010 16:22:58 o'clock BST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <30-Jun-2010 16:22:58 o'clock BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log00005. Log messages will continue to be logged in C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\access.log.>
    <30-Jun-2010 16:23:06 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <30-Jun-2010 16:23:06 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <30-Jun-2010 16:23:59 o'clock BST> <Warning> <JDBC> <BEA-001110> <No test table set up for pool "wlsbjmsrpDataSource". Connections will not be tested.>
    <30-Jun-2010 16:23:59 o'clock BST> <Warning> <JDBC> <BEA-001552> <The Logging Last Resource (LLR) data source wlsbjmsrpDataSource will not function when it is a participant in a global transaction that spans multiple WebLogic Server instances because remote JDBC support is disabled. LLR will function in single-server configurations.>
    <30-Jun-2010 16:25:35 o'clock BST> <Alert> <OSB Security> <BEA-387068> <There is no PKI credential mapper provider configured in your security realm. Service key provider management will be disabled. Configure a PKI credential mapper provider if you need service provider support. This is typically the case if you have Oracle Service Bus proxy services with web service security enabled or outbound 2-way SSL connections.>
    <30-Jun-2010 16:25:40 o'clock BST> <Warning> <WliSbTransports> <BEA-381917> <MQ Transport could not be registered due to : Missing MQ Library>
    [ERROR] AdapterManager - ServletContainerAdapter manager not initialized correctly.
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <LoggingService> <BEA-320400> <The log file C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log00005. Log messages will continue to be logged in C:\Oracle\Middleware\home11g\user_projects\domains\OSB_domain\servers\AdminServer\logs\OSB_domain.log.>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.128.2.170:7001 for protocols iiop, t3, ldap, snmp, http.>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "OSB_domain" running in Development Mode>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <30-Jun-2010 16:26:11 o'clock BST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    This is really putting me off and its really disappointing to see all these issues in this new release.
    How can oracle let a release slip in with such a Major Issue.
    Please can any one help or provide a work around atleast.
    Regards
    Nitin

    I guess till version 10gr3.1 you only needed to start one server and it allowed to access both admin and service bus console.Yes, in 11g as well you may access the admin and OSB console by just starting the admin server but in 11g OSB configuration gets deployed on OSB server (managed server) and test service also runs over this server.
    Are you saying there is some other server I need to start just for running the test console ????Yes. Managed server osb_server1 needs to be started for deploying, testing and accessing OSB resources.
    As If the OSB server was not running how can I check my published services, modify them and do all the bits and pieces after opening the open the service bus console but not just test them???You can modify and save your configuration without staring OSB server but if you will check in change centre then all the changes being done without starting OSB server will remain in partially activated state.
    I have been using the service bus for 3 years and I have never faced any such issue.With each new release you may get new features and with a major release like 11g, architecture and functionality may change.
    If it all there is some other server I need to start then whats the process to do so ??Open command prompt. Navigate to $Domain_Home/bin and run command
    startManagedWeblogic.cmd <nameOfManagedServer>
    for eg. -
    D:\OFMW11g\mw\user_projects\domains\ofmw_domain\bin>startManagedWebLogic.cmd osb_server1
    Once this server is up and running, try using test console.
    Regards,
    Anuj

  • Test Console not working any more in 11.1.1.3

    Hello,
    Running OSB 11.1.1.3 on Linux I get this error for any Proxy Service/Business Service
    in Test Console
    Error Accessing Test Configuration      
    "Test Console" service is not running. Contact administrator to start this service.
    It was working perfectly in any previous ALSB versions .. what could have
    change ? I did a fresh install with Oracle DB, derby, rcu or no rcu .. no way ..
    Edited by: user1518283 on Jun 18, 2010 7:18 AM

    I'm using the single server topology which is supposed to be Admin and Managed server together, ideal for dev enviroments. So this solution is not suitable for me.
    Under Windows the same config works fine.
    I'll try to reinstall Weblogic and OSB, but I'm almost sure this is an issue with OS.

  • OSB1031: (solaris10) cannot run Test Console from sbconsole

    Hi all,
    when I run the Test Console from sbconsole I got the below error:
    "Error Accessing Test Configuration
    An unexpected error occurred accessing the test service: java.net.UnknownHostException: wasdv1r3n1.dev.b-soiurce.net"
    My OSB domain is a clustered domain with one admin (bnk01osbadm) and 2 managed servers (bnk01osbm01 & bnk01osbm02).
    I checked the log files under the admin (bnk01osbadm.log, bnk01osb.log) and 2 managed servers but I've found no error.
    On the WLS console, under Deployments the column Health is OK for the application named "ALSB Test Framework". I checked also the sbtestservice web application and the status is active.
    What could I check too ? How could I increase the logging level to get more details ?
    Regards
    ferp

    How could I increase the logging level to get more details ?In your OSB domain root there is a file alsbdebug.xml. Change the below to true to get more details logged (Server log severity level should be debug).
    <java:alsb-test-console-debug>false</java:alsb-test-console-debug>
    Manoj

  • OSB sbconsole "Test Console" service is not running

    Hi all,
    A problem in the osb domain sbconsole I am facing during testing of proxy/business services. When clicking on the "Launch Test Console" icon I got following error:
    Error Accessing Test Configuration
    "Test Console" service is not running. Contact administrator to start this service.
    I have checked the test-console flag as true in ALSBdebug.xml file in all admin and managed servers. Still I am not able to test the service through sbconsole. All the servers are in OK state
    Please help.
    regards
    Mohit Sharma

    Cluster address should be comma-separated address of managed servers. For e.g. - If managed_server1 is listening on host:8011 and managed_server2 is listening on host:8013 then cluster address should be like host:8011,host:8013
    You may refer section "Cluster Address" at below link -
    http://download.oracle.com/docs/cd/E17904_01/web.1111/e13709/setup.htm#i717132
    Regards,
    Anuj

  • Proxy error with subversion read access test

    Hi,
    I specified the following repository URL: [http://l0762.domain.local/svn/io_se/trunk] and added username/password for this subversion server.
    I get the following error stack when doing 'Test Read Access':
    Testing read access for repository [http://l0762.domain.local/svn/io_se/trunk..].
    svn: PROPFIND of '/svn/io_se/trunk': 502 Proxy Error ( The ISA Server denied the specified Uniform Resource Locator (URL). ) ([http://l0762.domain.local|http://l0762.domain.local/])
    svn: PROPFIND of '/svn/io_se/trunk': 502 Proxy Error ( The ISA Server denied the specified Uniform Resource Locator (URL). ) ([http://l0762.domain.local|http://l0762.domain.local/])
    Access refused.
    In the generic preferences settings for Web Browser and Proxy, I have specified the proxy server, port number and even username/password for this proxy. The "Test Proxy" works fine. The exception list contains the l0762.domain.local. I also tested with *.domain.local.
    Any ideas?
    Thanks,
    Marcel
    Edited by: mmeijn on Nov 20, 2008 2:48 PM

    The problem is resolved by removing the proxy preference.

  • Error while Test Connection with Connector

    hi all:
         there is an error while  Test Connection with Connector , I also test it through sys administration->sys configuration->
    suport -> sap transaction, I got all errors, I put these two errors as folows, could you please tell me how to sovle it
    ***************ERROR 1 while *error while Test Connection with Connector ******************************************************
    Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this
    system object
      Results
    Retrieval of default alias successful
    Connection failed. Make sure that Single Sign-On is configured correctly
    ************error sys administration->sys configuration-> suport -> sap transaction        ********************** 1.5 #0025B3E02892006100000A0800001798000487530FB0122E#1274690722265#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt
    .runtime#guodongdong#47472##n/a##690347f0670e11df98cc0025b3e02892#SAPEngine_Application_Thread[impl:3]
    9##0#0#Error##Java###04:4524/05/10_0077_6087550
    [EXCEPTION]
    #1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Application URL
    &\#39;:///sap(ZT1KVXBWektldldTeV9QQXBXRjNaWTRBLS1OZmRvZzBRWWY2QmN0WThNUmgqdUlRLS0=)/bc/gui/sap/its/webgui&\#39; is not valid!
    Please check the protocol and host entries for system &\#39;sapdev&\#39;.
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass
    (AbstractIntegratorComponent.java:123)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:523)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:412)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
    (ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

    Hi,
    As per this part of the trace:
    Exception in SAP Application Integrator occured: Application URL &\#39;:///sap(ZT1KVXBWektldldTeV9QQXBXRjNaWTRBLS1OZmRvZzBRWWY2QmN0WThNUmgqdUlRLS0=)/bc/gui/sap/its/webgui&\#39; is not valid! Please check the protocol and host entries for system &\#39;sapdev&\#39;. at ...
    You can clearly see that the system object 'sapdev' is not configured correctly/at all - you are trying to launch transaction iView
    (WEBGUI) and in order to do so you should configure the 'internet transaction server' category of the system  object
    with the hostname of the ITS server.
    Generally the template is
    <System.Access.ITS.protocol>://<System.Access.ITS.hostname>/sap<ESID>/bc/gui/sap/its/webgui?\....
    So that's why you got
    Please check the protocol and host entries for system ..

  • Error while testing  FP_TEST_00

    Hi,
    I configured ADS in my machine where ABAP and JAVA stacks are running on same WAS.
    I did so many times but i never faced this error while testing FP_TEST_00 program.
    i'am getting this errror
    "ADS:com.adobe.processingexception:problem accessing d(200101)
    Message No.FPRUNX001"
    I checked with the sap notes and some blogs on FPRUNX001 error and i followed those documents where i couldnt find any problem in configuration.
    i think problem is with adsuser id but all the necessary security roles and groups are assigned to ADSUser as per the document.
    Please guide me with a solution.
    With Regards,
    Pradeep.B

    You are saying abt the HTTP destination which we need to create in Visual Admin right.
    Yes i created that FP_ICF_DATA_SID and the url maintained is http://hostname(Abap):portnumber (http port of ABAP),user ADS_AGENT and its password are maintained and when i click on save and test it is giving me the succesfull message.
    Infact i tested by extending the url http://hostname:portnumber/sap/bc/fp/fp_test_00.xdp
    it is showing me the success message.
    yes it NW 7.0
    With reagdrs,
    Pradeep

  • Testing SAML in ALSB test console

    Hi All,
    I have a wsdl with saml policy in alsb and i wanted to test it from alsb proxy service. I have done the below configurations in my alsb 2.6 environment
    1. added the wsdl for the webservice and edited the wsdl to add the saml policy(Please see the saml policy below) to implement the security
    2. created a business service from the wsdl
    3. created the proxy service from the business service and secured the proxy service with basic http auth
    4.Configured SAML Credential Mapping Providers in weblogic console
    SAML Policy
    =======
    <wsp:Policy
    xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
    xmlns:wssp="http://www.bea.com/wls90/security/policy"
    xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
    xmlns:wls="http://www.bea.com/wls90/security/policy/wsee#part"
    wsu:Id="SAMLPolicyId">
    <wssp:Identity>
    <wssp:SupportedTokens>
    <wssp:SecurityToken TokenType="http://docs.oasis-open.org/wss/2004/01/oasis-2004-
    01-saml-token-profile-1.0#SAMLAssertionID">
    <wssp:Claims>
    <wssp:ConfirmationMethod>sender-vouches</wssp:ConfirmationMethod>
    </wssp:Claims>
    </wssp:SecurityToken>
    </wssp:SupportedTokens>
    </wssp:Identity>
    </wsp:Policy>
    code snippet added to the wsdl document
    ==========================
    <wsp:UsingPolicy wsdl:Required="true"
    xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"/>
    <wsp:Policy
    xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
    <wsp:PolicyReference URI="policy:SAMLPolicyId"/>
    </wsp:Policy>
    Now, i tried invoking the service from proxy test console and got the error"Unable to add the security tokens"
    Please suggest me on this issue
    Thanks in advance!

    This is solved . make sure that you have the correct addresses in the config .xml

  • Exchange 2010 MP : Some Client Access test cmdlets failed to run

    Hi all,
    This error is triggered in SCOM 2012 R2 about a single Exchange 2010 SP3 server :
    Exchange 2010 MP : Some Client Access test cmdlets failed to run.
    When I dig into the error context, I can see it's about the cmdlet "Test-CalendarConnectivity -TestType:External".
    The TechNet
    https://technet.microsoft.com/en-us/library/hh377605(v=exchg.140).aspx proposes to verify that the URL for the external virtual directory can be accessed by running the Test-OwaConnectivity.
    OK.
    But what sould I specify for the parameter -MailBoxCredential required for Test-OwaConnectivity -URL my_url -MailBoxCredential ?
    Thank you.
    Have a good day.
    FXE

    Hi,
    Under Administration, run as configuration, profiles, you can check Default action account.
    Local system is the account account for agents by default, you can change to use another account.
    Regards,
    Yan Li
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Error while testing the endpoints in Service Registry

    Hi,
    I am getting the following error while testing the endpoint in the Service Registry
    Invalid Response Code: (404) Not Found. The request URL was:"http://<server>:8000/sap/bc/srt/wsdl/bndg_DD73518A3AD471F18558001D0910D3CA/wsdl11/binding/ws_policy/document?sap-client=800". Check, whether the URL is correct, and the Web Service that you are requesting is up and running.
    I have created an Enterprise Service at the backend and have published to the Service Registry of the CE server , but while testing the endpoint in service registry i am getting error.
    Can any one please help me to solve this issue.
    Thanks & Regards,
    Hamsa Shree

    Hi hamsa,
    Have you tested the service? If It works, maybe there's something wrong with your destination configuration.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/705459a3-bf1c-2b10-8a9d-d300ada5f0fc
    You may find a solution in the above article.
    Good luck!
    Wenhao

  • Error while testing demo app:Internet Explorer cannot display the webpage

    HI Gurus,
    I am new to the webdynpro development. I was starting with building demo application. However, finding below error while testing it using se80 transaction. Please suggest if any configuration is missing or anything else.
    I am using ECC6 : 720 Final Release....
    Error is below :
    This problem can be caused by a variety of issues, including:
    u2022Internet connectivity has been lost.
    u2022The website is temporarily unavailable.
    u2022The Domain Name Server (DNS) is not reachable.
    u2022The Domain Name Server (DNS) does not have a listing for the website's domain.
    u2022There might be a typing error in the address.
    u2022If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.

    Thanks sanasrinivas,
    I did the steps as mentioned by you. I also checked the link http://wiki.sdn.sap.com/wiki/display/EP/12ITSWebGUI-Activation(BackEnd) to activate the its webgui. Now the new error is coming as mentioned below.
    Note: After running webdynpro application a login screen apears and after giving uid and pwd following error appears. however, while testing the service in sicf, logon happens successfull.
    The URL ).
    Please let me know if anything is missing or the further steps i can take.
    Thanks,
    Janisar
    Edited by: janisar.munshi on Feb 15, 2012 3:33 PM
    Edited by: janisar.munshi on Feb 15, 2012 3:36 PM

Maybe you are looking for