Still Awaiting Acknowledgement in SXMB_MONI - RFC Adapter

Have a scenario where we are using an RFC adapter on the reciever end to bring in data into R/3. The message in SXMB_MONI is showing successfully processed, but in column "Ack Status" - the icon states "Still Awaiting Acknowledgement". As a result of this the data is not being posted into R/3.
What is the best way to check the reason for "Still Awaiting Acknowledgement" and how to fix the problem so that the data is successfully processed in the R/3 system as well. Have already checked the adapter engine for adapter RFC and it does not show the any status - error or successful.

Hi,
RFCs usually use application acknowledgements and not system acks, and hence we shouldn't be getting that 'awaiting ack' symbol in the moni.
Try unchecking the 'maintain order at runtime' checkbox in interface determination and see if that helps.
Also make sure that the sender adapter's quality of service(QOS) is not EOIO.
Regards,
Smitha.

Similar Messages

  • IDOC to flat file "Still Awaiting Acknowledgement"

    Hi All,
    Our scenario is IDOC to flat file .
    I have created User module also in receiver communication channel.... but I didn't create FCC  parameters
    please see the attachments, even I am getting "Still Awaiting Acknowledgement" in sxmb_moni.....
    could you please tell me why I am getting that?
    Thanks In Advance....
    Vishnu pallamreddy

    Hi Vishnu,
    Check this below discussion,
    Still awaiting acknowledgment 
    Are you sending test message from RWB or Source system, try to trigger message from Source system and see the status.

  • Proxy - File Adapter - "Still awaiting acknowledgment"

    Hi,
    I have a "Proxy -> BPM -> File" scenario and have configured acknowledgment. When the data is sent from proxy and written to file without errors I get the correct acknowledgment back to the R3 system. But when the file can't be written (FTP cant be reached) then  I get an error in the BPM step but get an Wait step in R3. "Still awaiting acknowledgment"
    sxmb_moni in PI:
    Processed successfully@ @Still awaiting acknowledgment           @ 04.08.2009 14:47:18 14:47:18     @R3System
    Processed successfully@ @Acknowledgment contains system errors   @ 04.08.2009 14:47:19 14:47:19 @Integration Process
    In SWWL I see this status:
    Waiting for event 'SEND_OK_TRANSPORT' of object type 'CL_SWF_XI_MESSAGE'
    Maybe it has something to do with the "Guaranteed delivery". It retries 4 times and maybe it is waiting for an retry limit or something. I am not sure.
    Any ideas on this one?

    Shouldn't this be a "Acknowledgment contains system errors" ?
    Are you implementing any logic once the deadline is met?
    To send the NACK to R3 you need to have a Send step in your Exception/ deadline branch which will send the required message to R3.
    A similar approach is shown here: /people/michal.krawczyk2/blog/2006/06/22/xi-playing-with-the-file-adapters-acknowledgments
    Instead of the Control Step you need to have a Send Step.
    Update:
    Please note that any acknowledgement from AE will come into the BPM and will not go directly/ automatically to R3. The meaning of acknowledgement coming back to the Sender Application means ACK/ NACK to the BPM and not any other system.
    Regards,
    Abhishek.
    Edited by: abhishek salvi on Aug 5, 2009 2:48 PM

  • Idoc- XI- Idoc - still awaiting acknowledgement

    Hi guys!
    We send Idoc->XI->Idoc and in sxi monitor we have a green flag - still awaiting acknowledgment. What does it mean? How can we be sure, that Idoc is received bu target application?
    Thanx olian!

    Hi Olian,
    One way is to logon to R/3 system and use tcode WE02 or WE05 and there give your idoc type and press F8. you can see your idoc here.
    Also go through it.
    /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
    Note: IDoc technology supports its own acknowledgment technology, namely the ALE Audit. Here there are no acknowledgment requests from the sender. Instead, the receiver decides whether an acknowledgment IDoc should be sent back to the sender based on the ALE configuration. These acknowledgment IDocs are only used for monitoring on the sender side.
    IDoc technology is the only technology in which positive acknowledgments from the application contain data. This data is sent by the IDoc adapter in an acknowledgment IDoc if the sender is an IDoc system. Otherwise, the data is discarded.
    For the inbound IDoc adapter to be able to send an acknowledgment IDoc to the sender, a communication channel with the interface ALEAUD.ALEAUD01 must be maintained for the sender.
    Regards,
    Sarvesh
    Message was edited by:
            Sarvesh Singh

  • Problem receiving acknowledgement: abap proxy == file adapter

    Hi experts,
    I am developing an asynchrone interface using PI 7.0. The scenario is: SAP ==> FILE.
    In SAP I have created an abap proxy in wich I requested an acknowledgement when calling from the abap code. In PI I have created an Integration Process with a receive step, and a send step. In de send step I am asking for a transport acknowledgement.
    When I test the interface and I look in the SXMB_MONI in PI, I see the acknowledgement given back to the IP, but in the SAP backend system I don't receive anything in the abap proxy which had send the original message. In de SXMB_MONI from SAP I see a "?" Still awaiting  acknowledgement.
    Can anyone help me with this scenario? I really need an acknowledgement from the file adapter in the calling abap proxy.
    Regards, Jeroen

    You need to crate a REceiver Agreement for this sender...
    The Integration Server sends an acknowledgment message back to the sender (CENTRAL_BACK). It uses the name of the sender system for logical and technical backward routing.
    If the sender is addressed using an ABAP proxy, you must define a corresponding receiver agreement for this sender.
    http://help.sap.com/saphelp_nw04/helpdata/en/29/345d3b7c32a527e10000000a114084/content.htm
    -SM

  • Error in Reciever RFC Adapter

    Hi All,
    While working with JDBCXIRFC, the only error with Reciever RFC Adapter is as
    follows.
    ZBAPICUSTOMER_DETAILS: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not get functionname from XML requst: com.sap.aii.af.rfc.RfcAdapterException: failed to read funtionname from XML document: missing namespace declaration(2)
    In SXMB_MONI, the messages are queued up.
    How to debug this error?
    Regards
    Pavan

    1. Map all the mandatory fields..
    I have mapped all the mandatory fields. If i enter same kind of values in the same fields of BAPI manually (in se37), the table gets updated.
    <b>how you can say that data is getting into the right tables...when you are sending the same data..</b>...may be the data is old only..
    <b>Perform the Message Mapping  and Interface Mapping test in IR only...</b>
    3. Kindly check the Sender_MM Mapping once more...If it is fine...reactivate and Update the cache..
    Its fine and reactivated and even updated cache.
    Now one doubt....
    In Message mapping, the sender mesage type is as follows.
    sender_mt 1:1
    ->Row element 1:unbounded
    > zkunnr element xsd:string 1: unbounded
    > zname1 element xsd:string 1: unbounded
    > zstras element xsd:string 1: unbounded
    > zadrnr element xsd:string 1: unbounded
    > ztelf1 element xsd:string 1: unbounded
    I have mapped ROW with ZBAPI_DETAILS.
    the root of sender message type SENDER_MT is left as it is....
    Is there anything need to be done (mapped) with this root of sender message type?
    <b>No i don't think so, what i can get from your approach is that you want to receive n similar type of records in a Message and want 2 create n different messages for each record from source structure..  </b>
    With this status, i have tested the Test Configuration in Integration Directory. Still getting same error message as follows...
    Kindly let me know the name of BAPI.
    <b>Perform the Message Mapping  and Interface Mapping test in IR only...</b>
    java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_sender_mm_:
    Regards,

  • RFC Adapter not getting data

    Hi experts!
    I am developing a RFC to File scenario on PI 7.1 EHP1 and ECC 6.0 which is synchronous. Following the Help page Setting Up an RFC Destination for the RFC Adapter I created two destinations. The fist one is a TCP/IP, name RFCDE1COMPANY2, program id BAPI_COMPANY_GETLIST and corresponding gateway host and service I found at SMGW (Parameters). The second one is a Logical with name RFCDE1and reference entry RFCDE1COMPANY2.
    At my RFC Sender Adapter I configured the same gateway info and the same program id. After that I tested both destinations and it worked. I created the following report to call the bapi on that destinations::
    REPORT  ZREP_BAPI_COMPANY_GETLIST.
    DATA: company_list TYPE STANDARD TABLE OF BAPI0014_1.
    CALL FUNCTION 'BAPI_COMPANY_GETLIST'
      IN BACKGROUND TASK
      DESTINATION 'RFCDE1'
      TABLES
         COMPANY_LIST = company_list.
    COMMIT WORK.
    At SXMB_MONI the request message was processed and the output file generated, but it has only the root tag. At moni the inbound message has no data (company data).
    I tested the BAPI_COMPANY_GETLIST at SE37 and there are 149 entries. When I executed this same BAPI with RFC target sys configured to my destination, it didn´t show any data and has an exception called SYSTEM_FAILURE. I think probably the error is on RFC destinations but I can´t figure it out what is wrong.
    Best Regards,
    Gabriela

    Hi experts,
    Thank you all for your quick response.
    At the TCP/IP Destination there is a button "Unicode Test", according to this test my target system is unicode (character size 2). I changed the option at MDPM&Unicode on that TCP/IP Destination like Madhusudana described. I also selected the checkbutton "Unicode" on sender RFC communication channel.
    About the sync/async, I will not use sync async bridge because this scenario can be async. One think that I realized is that when I call my report, I am implicitly calling PI asynchronously and when I call the BAPI directly by the test tool, I am implicitly calling PI synchronously. That is why most part of my tests did not work before.
    Now I can see on SXMB_MONI that the scenario worked and the file was generated. But the data are still not being showed on inbound payload. I think something is wrong with my destinations but I can´t figure it out what is.
    Ps.: I would prefer to use XI proxies, but this scenario will be configured (not now) on a XI 3.0 with ERP 4.6 C. Now I´m just learning how to handle with RFC Adapter.
    Any ideia?
    (Points granted)
    Thank you and best regards,
    Gabriela

  • RFC -File Sync Async bridge RFC Adapter Exception

    Hi
    I am using sync async bridge to send a response back to rfc.
    Although there is no error in sxmb_moni as well as the auditlog shows that the response was sent successfully to rfc.. still the RFC adapter gives the following error with no response sent to RFC..
    Error in processing caused by: com.sap.aii.af.rfc.RfcAdapterException: failed to identify XML document:java.lang.Exception: javax.xml.parsers.FactoryConfigurationError: Provider com.sap.engine.lib.jaxp.SAXParserFactoryImpl not found
    please help

    Solved the problem..
    The problem could be due to the following..
    1. the response structure was just a single character..while i was sending a whole string..
    2. I restarted the server...probably the problem
    javax.xml.parsers.FactoryConfigurationError: Provider com.sap.engine.lib.jaxp.SAXParserFactoryImpl not found
    system property must have set mismatch for the SAXFactoryImpl.... by deploying modules before in which i was using SAX parser.. may be the i set the system property earlier to other provider dont remember...
    Hope this information will be useful to someone in future using Sync/Async bridge

  • RFC adapter - AE_DETAILS_GET_ERROR - no adapter engine

    Hello,
    have a strange error.
    Our scenario connects two R/3 systems via RFC adapter (outbound / inbound) for an RFC in a standard R/3 function module SUSR_ZBV_GET_REMOTE_PROFILES.
    The RFC is synchronous.
    When starting the RFC call from the sender system the error message in the trace is "exception while reading from SLD:Property sap_xiadapterservice.adapterType does not exist".
    Message in RWB:
    "Transmitting the message using connection http://abc038.ceu.test.com:8077/sap/xi/engine?type=entry failed, due to: XIServer:AE_DETAILS_GET_ERROR:Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines."
    - SLD connection is working
    - Vis.Admin.: no problems found
      (SAP RFC adapter active)
    - Component monitoring: no errors
    - all rfc connections checked: ok
    Does anybody have an idea, how to fix that?
    Best regards
    Dirk

    Hello Dirk and all posters,
    We get the same problem just as you described.
    We also see no entries in the sxi_cache part for the adapter engine which indicates a problem in getting AE metadata from the SLD.
    I see we are all not alone so i believe SP12 is the cause for the problem.
    We have another SP11 system that works well.
    We tried all those things to understand the problem:
    1. look at the structure of the calsses maintained in the SLD to make sure the property "adapterType" exists.
    2. Checked the log of the SLD with level "Finest" to make sure the data for the property is sent - all OK.
    3. Try to completely delete SLD and reimport CIM 1.4 and CR content 2.0 - all the latest from the web - problem still exists.
    4. Put a huge trace on the RFC gateway in the ABAP engine to make sure all XML data is received from SLD server including specific proprty. all ok.
    5. Of course we made sure all caches are refreshed, access to SLD is performed all right (logs, traces).
    6. Try to disable SM59 entry: SAPSLDAPI and look at the trace in SXMB_MONI. It shows error of connection of course instead of the error of the non exsitene property. But it still shows the error for not getting the access data - so this is only a side affect of the real problem.
    Now, as you can see we turned the system from inside out.
    I beleive the problem is SAP's problem regarding the parsing of the COM model in the CIM client. I believe that if i could debug the actual abap that parses the XML in the ABAP WAS i would find the problem - i could'nt find a way of debugging the actual processing of a message in QRFC so i'm stuck here.
    - Does all of you who have the problem has SP12 ?
    - Does any one have an idea of anything else we can all check ?
    Good luck for us all :->
    Yoad Snapir.

  • FILE-RFC ADAPTER problem

    Hi all,
    I am trying file->xi->rfc adapter scenario.
    My scenario is employee information is written to flat file n  will be kept on ftp server.THe file adapter will pickup the file and sends it to rfc adapter through pipeline service.
    This is going well. The problem is the data is not being updated into receiving sap system.
    in SXMB_MONI transaction the messages are successully processed . But there are no messges in rfc adapter when i gone through idx5 transaction???
    Any one have idea??
    Thanks in advance.
    Rgds,
    Ram Sri

    sxmb_moni only shows the status of the integration engine's processing, not the result of what happened in the rfc call.  First, you can check if the adapter framework successfully passed the message to the destination system (not on moni, thru RWB)
    as far as did the rfc succeed - it's as difficult as always with internal processing.  We did a lot of testing by debugging modules on the destination side (manually putting in the data as the adapter would've to step thru & see where the message is "lost") - have not yet found a better way, sorry.  It's not so much a problem with XI, just in general the difficulty to debug rfc's

  • Error while doing commint from RFC Adapter

    Hi,
    We have a SOAP-PI-RFC synchronous scenario. Through this Soap request comes to PI and passed on to BAPI via RFC adapter. This BAPI saves the transaction & return the document number. We are using " PI PI parameter u201CCommit Handling for single BAPI' in RFC receiver Channel.
    While this setup works for 1 posting, when we do the mass load ( Say 20 Documents) half of the documents are not able to Save. Although BAPI, returns the document number but on checking the document does not exists in SAP. To do further test, we created a program in ECC and try calling BAPI in loop and calling BAPI Commit.
    This way program works fine and there is no error
    So in nutshell, when we PI do the commit, half of the documents are not saving where as when the ABAP program commits no error. Is there any  special way that PI calls this commit work.
    PS: We created a wrapper BAPI which calls the orgirnal BAPI and Commit BAPI & called this from PI but still the same problem is coming.
    Appreciate help on this.
    Regards,
    Harish

    Are there any error messages in the RFC Reciever channel in Runtime Workbench?
    RWB -> Component monitoing -> Adapter Engine -> Comm Channel -> filter for type RFC
    Please try to give some more details on why the system says the messages are failing.

  • RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C

    Here is the scenario.
    An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format.  This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
    call function 'BAPI_TRANSACTION_COMMIT'
    The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
    Here is what happens within XI and our SAP system.
    The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer.  All seems to be working properly except that when the original RFC is sent from XI to SAP,  SAP creates a short dump stating
    "call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
    I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
    Any ideas.
    Thanks,
    Jim d'Hulst

    Hi,
    I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
    CALL FUNCTION 'ZABCD'
    destination <tcp/ip destination>
    exporting
    input = ack.
    In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
    Also, check your config with the blog mentioned below:
    <a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
    Regards,
    Amitabha

  • RFC Adapter not Call

    Hello Friends,
    I am working on XI 2.0
    My Scenario is
    IDOC --> XI --> RFC Adapter --> R/3 System
    I am configuring the RFC adapter for the SAP system.
    But when I am able to try to call using the Integration Engine it’s not call the RFC adapter.
    I define the end point as
    RFC Adapter
    (X) Load Balancing Deactivated
           Application Server -- <host name>
           System Number      -- 00
    When I run the scenario it show me in the <b>sm58</b> transaction as
    <b>Connection Close (no Data)</b>
    And in the SXMB_MONI Transaction it shows
    <b>A. Status</b> as <b>Green Flag</b> means <b>Message schedule on outbound side</b>.
    So can you please identify and suggest me the solution or what else configuration is required.
    Thanks & Regards,
    Gaurav Jain

    try to register all queues in SXMB_ADM -> Manage queues.
    I think that should help you solve the issue.

  • RFC to XML-RFC Parsing issue in RFC Adapter as Sender

    Hi all,
    I tried to use RFC adapter as a sender. The scenario I am trying to achieve is R3 -> RFC Adapter Sender --> BPM --> RFC Adapter Receiver --> SAP Auto-ID system.
    The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails. Everything works as expected, except the RFC Adapter Sender.
    The RFC I am calling has an input table. The input data I use works fine if I call it via SE37 or remotely from another SAP system. However, if I call it via RFC adapter, when XI parses the data into RFC-XML format, the input data is all messed up.
    DATA: BEGIN OF ID_STR,
            ID_VERSION(8)       TYPE C,
            ID(96)              TYPE C,
            ELEMENT_NAME(50)    TYPE C,
            ELEMENT_VALUE(128)  TYPE C,
          END OF ID_STR.
    DATA: it_id LIKE TABLE OF ID_STR,
          ls_id LIKE ID_STR.
    ls_id-ID_VERSION = 'EPC_1.30'.
    ls_id-ID = '30340242206DC3C00000000A'.
    ls_id-element_name = 'BATCH_ID'.
    ls_id-element_value = 'BATCH001'.
    APPEND ls_id TO it_id.
    CALL FUNCTION '/AIN/UI_MOBILE_MSG_SEND'
      IN BACKGROUND TASK
      DESTINATION  'RFC_UPDATEAII'
      EXPORTING
        IV_BUSINESS_PROCESS       = '09'
        IV_COMMAND                = 'DO'
        IV_ACTION_TYPE            = 'APL2'
        IV_PRT_ID                 = '31140242200000000F000000'
        IV_DEVGRP_EXTID           = 'MOBILE'
      TABLES
        IT_ID                     = it_id
      commit work.
    And the parsed RFC-XML message is:
    <?xml version="1.0" encoding="UTF-8" ?>
    <rfc:_-AIN_-UI_MOBILE_MSG_SEND
    xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
    <IV_ACTION_TYPE>APL2</IV_ACTION_TYPE>
    <IV_BTD_EXTID />
    <IV_BTD_TYPE />
    <IV_BUSINESS_PROCESS>09</IV_BUSINESS_PROCESS>
    <IV_COMMAND>DO</IV_COMMAND>
    <IV_DEVGRP_EXTID>MOBILE</IV_DEVGRP_EXTID>
    <IV_LOC_EXTID />
    <IV_LOC_TYPE />
    <IV_PRT_ID>31140242200000000F000000</IV_PRT_ID>
    <IV_PRT_ID_VERSION />
    <IV_REASON_CODE />
    <IV_UNAME/>
    <ET_RETURN />
    <IT_ID>
    <item>
    <ID_VERSION>EPC_1.30</ID_VERSION>
    <ID>206DC3C00000000A BATCH_ID</ID>
    <ELEMENT_NAME />
    <ELEMENT_VALUE />
    </item>
    </IT_ID>
    </rfc:_-AIN_-UI_MOBILE_MSG_SEND>
    You can see the data in the table is all wrong, it should be:
    <IT_ID>
    <item>
    <ID_VERSION>EPC_1.30</ID_VERSION>
    <ID>30340242206DC3C00000000A</ID>
    <ELEMENT_NAME>BATCH_ID</ELEMENT_NAME>
    <ELEMENT_VALUE>BATCH001</ELEMENT_VALUE>
    </item>
    </IT_ID>
    The calling system is a 4.6C non-unicode system, and the destination system is a unicode system (this does not matter since the first part of the integration is between R3 and XI). There is no config found on R3 side to specify non-unicode because it is a rather old system. In XI RFC Adapter config, I checked non-unicode checkbox (I also tested it with this unchecked, but still the same issue).
    Have any of you seen this problem and how you resolve it?
    Thanks a lot for your help!
    Regards,
    Hart

    Hi Hart
    long time no seen - hope you remember me
    >The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails
    there is an easy way (guess max 3-4 hours) to solve all of your issues
    and get rid of a BPM
    use IDOC - XI - ABAP Proxy
    then you will have IDOC and ABAP Proxy that always log the message on both ends (and you can restart ABAP proxies easily in AII - and every AII supports ABAP proxies) + you get rid of a BPM as it's not necessary as far as I understand (as it's asyn communication right?)
    maybe you can go this way and IDOCs always work...
    good luck,
    Regards,
    Michal Krawczyk
    http://mypigenie.com XI/PI FAQ

  • Sender RFC Adapter AND Rec. File Adapter

    Hi
    Workflow of my scenario is like this :
    <b>SAP R/3 ---> Sender RFC Adapter ---> XI Server -
    > Rec. File Adapter -
    > Legacy System</b>
    I am using Async Inbound interface for this as I dont need any response back & I just need to create file.
    I am just picking some data from BAPI & creating a file on a folder in Legacy System.
    Now during execution, file is getting created but I am getting dump on SAP R/3 and even when I am using Async communication, response is coming back from Legacy Business System ( service ) & giving an error " <i>No Mapping Program Found</i> " in sxmb_moni.
    Kindly suggest how can I avoid getting response from Legacy System. Pls. take note again I am using Async Inbound Interface.
    Regards
    - Lalit -

    Hi Lalit,
    When your RFC is called from R/3 by default it would be in Sync mode. When this is in Sync mode it obviously will expect a response and where as in your scenario XI dose'nt give any response and there is no mapping for that and I think that is the reason you are getting that error.
    So when your Sender RFC is triggered it will like this in ABAP
    CALL Function "Function Name" <SM59 Destination>
    and this is Sync call. To make it Async i should be
    CALL Function "Function Name" IN BACKGROUND TASK <SM59 Destination>
    Hoep this helps
    Thanks,
    Prakash

Maybe you are looking for

  • File Sharing works only with Firewall inactive

    I used to share files with an Xp Pc with no problem on my wifi network. When I upgraded to SL even though I see the pc in finder and the file sharing option is active I can access to my pc only if i stop the firewall. Bye

  • Using currentTarget.label as variable in path?

    I have the following code: <s:FormItem label="First" click="onItemFocus(event)">       <s:TextInput id="First" enabled="false" text="some text here..."/> </s:FormItem> Which when you click the FormItem it fires this function: protected function onIte

  • Error AC531 - Design question

    Hello experts, A US company with fiscal year running from Oct-Sept wants to roll out the fixed asset template to a Asian country e.g. China having fiscal year Jan-Dec. Since US is the parent company the depreciation area 01 has US GAAP valuation in C

  • Can I run Photoshop CS4 and CS1 on the same Mac?

    I've been building pages for a website on my old Mac with Photoshop CS1 then slicing and optimising them in ImageReady before uploading to the site I'm building in Dreamweaver where I put in the body text. Recently I upgraded to a newer Mac running S

  • ADS and ECC 5.0

    I'm looking into installing a DI on a Windows platform to be able to use Adobe Document Services.  I've read over Barbara Roth's document concerning system i and ADS and looked at the threads on this forum.  I guess I'm just too dense to "get it". Al