Non-central adapter engine not visable in integration builder

ls,
I have a pi system and a separate non-central adapter engine. After installing i did all the post actions including the following part:
5.13 Clearing the SLD Data Cache after Installing a Non-central Advanced Adapter Engine
When you have installed a non-central Advanced Adapter Engine, you need to manually clear the SLD Data Cache in the Integration Builder to make it visible and selectable in the communication channels.
Procedure
1.
After SAPinst has finished, open the Integration Builder of your PI system at http://<host>:<port>/dir/start/index.jspIntegration Directory and logon as a user with the ABAP role SAP_XI_CONFIGURATOR assigned.
2.
In the Integration Builder, choose Environment.
3.
From the drop-down list, choose Clear SLD Data Cache.
(as described in: Installation GuideAdapter Engine (Java EE) 7.1 Including Enhancement Package 1 on Windows: MS SQL ServerTarget)
However when creating a communication channel in the integration builder there is only the central adapter engine to choose in parameter tab screen.
I was hoping maybe some-one knows what else need to be done to make de non-central known as adapter engine.
thanks in advance
Peter

HI,
with user PIDIRUSER i was indeed able to refresh the af cache. Unfortunately without a positive
Under the runtime workbench (http://<host>:<port>0/rwb/index.jsp) tab sld registration i don't see the ae neither under non-central components. If i try to register i get:
Registration of Adapter Framework with SLD was successful
Registration of fix AF adapter services with the SLD was successful
Registration of dynamic CPA cache based AF adatper services with SLD was successful
but no AAE...although it is visible in the SLD under technical systems...

Similar Messages

  • Non Central adapter engine error

    Hi All, Here is my Scenario: Trying implement /configure Non-central adapter engine hosted separate (J2EE) server. This will be connected to XI server(Integration engine and SLD) from where messages are sent/received. When I try to post message from XI to Non_central adapter engine following is the message u201CThe requested protocol u201CXIu201D is currently unavailableu201D Then I realized there is a problem in Non-central adapter engine configuration, which will be connected to SLD and Integration engine. I can see technical system and business system in SLD for Non-central adapter engine. Following is the findings in NWA of same host where non-central adapter engine. 1) I see all J2EE services are running 2) Application u201Ccom.sap.aii.adapter.soap.libu201D is no started and status is u201Cfailed to startu201D. Later I tried to restart and following are the 4 error messages in sequence from trace file. a) Message: Access to XI AF MS resource failed. Date: 2010-07-02 Time: 22:05:15:273 Category: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory Location: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory.SPIManagedConnectionFactory() Application: Thread: Deploy Start Application Thread Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc B) [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. [EXCEPTION] com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:619) at com.sap.engine.services.deploy.server.application.StartTransaction.rollbackPart(StartTransaction.java:653) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:506) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) ... 8 more Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) C) Cannot bind "com.sap.aii.adapter.soap.lib";. [EXCEPTION] com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) d) Global operation [startApp] over [application] [sap.com/com.sap.aii.adapter.soap.lib] finished with errors for [16]ms on server [4796750 >>> without warnings << >> Errors <<< 1). Cannot bind "com.sap.aii.adapter.soap.lib";. -> Object with name com.sap.aii.adapter.soap.lib is already bound. 2). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) Any of you have seen this kind of problem. Thanks Sam Edited by: sam robert on Jul 2, 2010 10:24 PM

    Hi Sam,
    1- What is your PI version?
    2- Do you use a High Availability system?
    3- Can you describe your scenario?
    From the 503 error, here is a generic description:
    The error message 503 Service unavailable Application stopped! is displayed.
    Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
    Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
    Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
    u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
    u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
    u2022 Refer SAP Note 803145,807000,791655
    Regards,
    Caio Cagnani

  • Sand box Non-central adapter engine entry is shown under development rwb

    Hi All,
    Recently we had a sand box which is a sytem copy of our development server, and everything works fine now.
    I have observed a strange issue here is, in the developement rwb under the Non-Central Adapter engines I see a entry as "Adapter Engine T49 (sand box host name)" the SID seen here is a sand box SID, and till today we never installed any non-central adapter engine either on dev or sand box, I am suprised to see this entry, can some one
    please help me to understand why is this sand box entry is shown under development rwb and where can I set this or where how can I delete this entry.
    Surprisingly I do not see the same non central adapter engine entry on sand box rwb.
    All the servers are XI 3.0 (SP 19).
    Thanking you in advance..
    Regards
    Sonali
    Edited by: Sonali R on Sep 14, 2009 10:59 AM

    Hi Sonali,
    The adapter and integration server engines gets registered with the data in SLD. Please check SLD associations for all XI classes.
    Best Regards
    Raghu

  • Working with non-central adapter engine

    Hi Experts,
    I have a non-central adapter engine in my PI installation. I want to use it in my integration. But I am not able to do so. In ID when I create an RFC CC the Adapter Engine combo box is empty.
    What should I do?
    Can I configure this non-central engine as central engine?
    Please guide me. I am on critical path.
    Jitendra

    Hi
    Try this
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars/configuring%20a%20local%20adapter%20engine%20to%20work%20with%20a%20central%20instance%20-%20webinar%20powerpoint.pdf
    This will help u

  • Central vs Non-central adapter engine.

    Hi all,
    Can any one tell me how can I find out whether central or non-central adapter engine is configured in my XI system.
    Is there any difference between accessing the central and non-central adapter engine cofiguration screen.
    Any help will be appreciated.
    Regards,
    Amith

    Hi,
    Central adapter engine is used for conversion of objects within a single sld.
    A decentral adapter engine is used when we need to connect to other applicaton systems through a firewall.
    Xi does not provide any such security, so in order to ensure security and to allow minimal access to out sld and other objects we use an external adapter engine(a decentralised adapter engine).
    An example of using a decentralised AE would be when we connect the PCK
    <b>"Both the central and non-central Adapter Engines are configured centrally in the Integration Directory, and a central monitor"</b>
    Regards,
    Smitha.
    Message was edited by: Smitha Rao

  • In-depth knowlege von non-central adapter engine required

    We are considering usage of a non-central adapter engine, but of course beforehand I need as much knowledge as possible about different aspects.
    So far I have not found very much detailed knowledge in the help section. There I may ask you whether you have some more information material, links, experiences etc. on all topics of the non-central adapter engine, such as:
    - architecture
    - configuration
    - installation
    - configuring connection with integration engine / SLD (?)
    - security aspects
    - and all other things that might be interesting / important
    Any kind of information or help would be nice!
    Thank you very much for your support on this topic.

    check below links, it will surely help you a lot.
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/03fd85cc-0201-0010-8ca4-a32a119a582d
    Re: Decentral Adapter Engine on the same XI Server

  • Non-central adapter engine setup with web dispatcher

    Our PI setup is working perfectly in our private zone, now the requirement is to expose our PI to public zone to do our B2B transactions. We have proposed a solution but I need your expert suggestion on this. Solution proposed 
    Public Zone -|Semi public zone| Semi private zone |----Private zone
    |>>>Application gateway >>>>>>>>| Non-Central Advanced<==========>|------ PI 7.1
    |>>>(For Inbound message) >>>>>>| Engine (For both Inbound and<=====>|------(IS, central AAE, IE)
    |<<<<< Proxy<<<<<<<<<<<<<<<<<<|Outbound message and<==========>|                                               
    |<<<<<For outbound)<<<<<<<<<<<<|Load balancing for B2B)<=========>|                                                                               
    Non-central AAE will be in semi private DMZ. It will send/receive all B2B messages from/to semi public DMZ via Application gateway for inbound messages and proxy for outbound messages.
    Then Non-central AAE will work with the PI central instance running in Private DMZ to receive and send messages.
    My Questions:
    1) Do we need a SAP web dispatcher to work in between (Application gateway, Proxy) and (Non-central AAE)   ?
        My understanding: SAP web dispatcher balances the load which will enhance the performance but it is not mandatory. Non-central AAE can work independently with Application gateway and Proxy to receive and send messages.
    2) What is the configuration we need at non-central AAE to exchange messages with the application gateway and proxy?
    Thanks
    Amaresh

    what is use of non central Adapter engine in Java server proxy?
    The collaboration profile agreement service (CPA service) does not read the CPA cache from the Integration Directory.
    You define the user that is to send the messages to the Integration Server in a service parameter. When the Integration Server receives the message with this user, it checks the user using the access control list. This check is not performed for the technical user XIAFUSER.
    pls refer below link:
    http://help.sap.com/saphelp_nw73/helpdata/en/48/d7fb415ba90783e10000000a42189d/frameset.htm

  • Non central adapter engine & adapter monitoring

    Hi ,
    we installed PI7.0 sp12,and can we see all the available adapter as a list in RWB and adapter monitoring if adapter engine installed as non central?
    And we will see Adapter engine under Integration server if AE is centran and under non-central adapter engine if AE is non central ,right?
    thank you,
    Babu

    I could see both Communication Channel monitoring as well as Adapter monitoring.
    but once I click adapter monitoring I could see only JPR but not any other adapters.if I click CC monitoring there are no CC cos we havent created any yet.
    I am asking like,if we see only JPR in adapter monitoring not any other adapter ,is that a error while doing the installation and configurations? or is that ok?
    thank you for your reply.
    Babu

  • Seeing old deleted comm. channels on Non-Central Adapter Engines

    hello,
    We have a landscape of PI 7.0 machine connected with 3 Non-Central Adapter Engines installed on another machine, which generally works fine.
    Somehow, after doing a lot of changes in the integration directory (creating and deleting object: scenario, comm. channels and ect...)  -  two of the non-central AE shows comm. channels which were already deleted (and activated ofcourse) in the integration directory.
    What i tried already:
    run CPACache in mode=full on each of those AE, clear SLD cache and even restarted those J2EE instances. but it didn't work out. the thing that is also weird is that I can start/stop those old comm. channels. how do we get rid of those old channels?
    I would appreciate any suggestions .

    Problem is solved.
    In integration directory we could not see the old comm. channels under the objects tab or under any scenario, but they existed as shown in RWB.
    From CPA cache we picked up the comm. channels object IDs and search for it in integration directory UI, once they were found - it was easy to actually delete them.
    What went wrong?
    These old comm. channels were assigned under deleted services which were under deleted parties. For some unknown reason, after deleting the services and parties successfully, the comm. channels underneath were not deleted and could not shown in any of objects tab GUI tree's nodes.
    We could not reproduce this behaviour.

  • "Non-Central Adapter Engines" in RWB

    Hi.
    We install XI system and we changed host name according to notes 757692.
    After then, We found one problem in RWB.
    When we run Component Monitor in RWB, Adapter engine is in "Non-Central Adapter Engines".
    Why Adapter engine is in "Non-Central Adapter Engines" node ?
    Any ideas ?
    Regards, Arnold.

    Hello Sonali
    This is most likely caused by errors registering the XI components in the SLD. Apply the notes below:
    #764176 Error in XI due to inconsistent SLD contents
    #1117249 Incomplete Registration of PI components in SLD
    #1334053 No automatic PI 7.10 SLD Registration
    Also search the forum for similar issues registering the adapter engine in the SLD components.
    Regards
    Mark

  • Issue when receiving SOAP message with HTTPS on non-central adapter engine

    Hi,
    we have a central XI system (PI 7.1 EHP1 SP03) and a non-central adapter engine (XI 3.0) in the DMZ, both systems on HP-UX.
    In the affected configuration scenario, a business partner is sending us IDocs (INVOIC.INVOIC01) over HTTPS with Certificate Authentication and without SOAP Envelope.
    The configuration and security settings seem to be correct, because we've already received several messages successfully over this connection. Now, since several weeks no message arrives anymore in our system, while the business partner always gets a HTTP_OK_200 response. So the messages seem to be accepted by our system, but nothing is shown, neither in the MessageMonitoring or CommunicationChannelMonitoring of the Runtime Workbench, nor in the in the traces/logs of the NetweaverAdministrator (trace level = DEBUG for "com.sap.aii.adapter.soap").
    I also removed the assigned user in the sender agreement which should cause a HTTP_500_error on sender side, but our business partner still got a "OK_200" notification and we didn't find any information in the trace of our system.
    When using TCPGateway to trace the communication, I can see an arriving message and the response, but it's encrypted because of HTTPS.
    1) Did anyone have similiar issues yet?
    2) Are there any further possibilities to check if an incoming message at the SOAP adapter fails?
    3) Which further trace settings can be done, to get most detailed informations about the soap traffic?
    4) Is there a way to decrypt the message of the TCPGateway (e.g. with private key of server)?
    I'm looking forward for any helpful hints or information!
    Regards,
    Juergen

    Issue solved by SAP note 1115650 "J2EE Engine kernel.sda SP20 cumulative patch"

  • ExchangeProfile Webdynpro on non central Adapter Engine

    Hi all,
    can anybody tell me, if and how it is possible to get the exchangeprofile Webdynpro running on non central Adapter Engine (NW2004s, 7.0).
    I know, that it is part of SAP XITOOLS 7.0. But i am not sure if the installation of XI Tools has any impact on the Adapter Engine installation.
    BR,
    Martin

    Does nobody have an answer to this question ?
    BR,
    Martin

  • Problems with Non central Adapter Engine

    Hi Friends,
    We installed an non central Adapter engine. Then as per the documents we made entry for connection in exchange profile.Then in visual administrator in SLD data supplier i provided the required credentials for connecting to my XI server.
    XILDUSER and XISUPER these users and passwords were provided for connection.
    From visual admin we manually send the trigger to hit the SLD and make an entry there.It was successful in visual admin.
    But after doing all this successfully we are not able to see the Local i.e non-central adapter in our XI SLD as well as in RWB.
    can anyone throw some light on it.
    Thanks,
    yomesh

    Hi Friends ,
    I have solved this problem. The password provided for XILDUSER was wrong thats why it was not able to register in the SLD .also the differents user has to be created in Security provider service in visual administrator.
    then it worked finr.
    Yomesh

  • Non-central adapter engine entry is shown under development rwb

    Hi All,
    Recently we had a sand box which is a sytem copy of our development server, and everything works fine now.
    I have observed a strange issue here is, in the developement rwb under the Non-Central Adapter engines I see a entry as "Adapter Engine T49 (sand box host name)" the SID seen here is a sand box SID, and till today we never installed any non-central adapter engine either on dev or sand box, I am suprised to see this entry, can some one
    please help me to understand why is this sand box entry is shown under development rwb and where can I set this or where how can I delete this entry.
    Thanking you in advance..
    Regards
    Sonali

    Hello Sonali
    This is most likely caused by errors registering the XI components in the SLD. Apply the notes below:
    #764176 Error in XI due to inconsistent SLD contents
    #1117249 Incomplete Registration of PI components in SLD
    #1334053 No automatic PI 7.10 SLD Registration
    Also search the forum for similar issues registering the adapter engine in the SLD components.
    Regards
    Mark

  • Unable to contact non-central adapter engine

    Hi All
    I install the local J2EE Adapter Engine, and configure the connection in exchange profile and set the SLD Data Supplier in Visual Admin
    and i could see my local adapter engine in adapter configuration.
    But in Runtime work bench ->component monitor->non-central adapter engine-> error:
    Ping Status:        status_image        HTTP request failed. Error code: "401". Error message: "Unauthorized [http://host:port/AdapterFramework/rtc]"
    how could i solve this?
    thanks in advance

    Hi , Lawrence
    There was a solution to this problem?
    Thanks
    Leôncio

Maybe you are looking for

  • Droid RAZR (not MAXX) 4G, service drops on GB and ICS

    Okay, the forums are full of threads concerning this issue. The phone loses data connectivity as well as voice. Every person seems to have a different opinion as to when or where their service drops, and I have tried to find a fix (official or not) s

  • ITunes will not work with my computer.  iMac G3 processor, OS 10.4.11

    Original message posted about a week ago - I have an iMac, OS is 10.4.11. I just updated my Quicktime software to 7.5, I also updated my iTunes to 8.2.1 (I think, it is definitely higher than 8.0). When I would open up iTunes. I would get this messag

  • [semi-solved] Question about firefox css theming

    With my current firefox theme, authenticated urls (top screenshot) show up as dark text on a green background.  However, regular urls (bottom) show up as dark text on a black background, which is almost unreadable unless you highlight the area. authe

  • ITunes 9.something won't update

    My mother-in-laws has an older iMac circa 2006 with 10.4.11. The computer has iTunes 9.something. iTunes opens but doesn't do anything. I tried to update to 10.5 - it won't let me. Any suggestions?

  • How to stop tabs auto hiding

    The auto hide feature of the tabs is quite annoying on my Galaxy Tab 10.1 browser.chrome.dynamictoolbar stops the address bar from hiding but not the tabs. Any ideas?