Receiver IDoc Adapter - Outbound IDocs in IDX5 but stucked in SM58

Hi Gurus,
I have a Receiver IDoc issue with the above error.
My message is successful in the IE pipeline (but with error on outbound side)
I can even view the generated IDoc numbers for those messages in IDX5,   but when double-clicking on those IDX5 entries SM58 is called and there I see the error as follows:
Caller:  PIAFUSER
FM:  IDOC_INBOUND_ASYNCHRONOUS
Status Text: No Authorization to send IDocs with Message Type 0
The weird thing is why is the caller showing as PIAFUSER, when my RFC destination is using a custom RFC user id.
Shouldn't it be that the Caller be my custom RFC user id since this is the user used by the RFC destination i specified in the receiver idoc comm channel?
Would anyone of you know how to resolve this?
I have already implemented Note 837595 for (a) my custom RFC user id in the target system (b) PIAFUSER and PIISUSER in my Integration Server;  and assigned SAP_XI_APPL_SERV_USER role to PIISUSER also as specified in  http://help.sap.com/saphelp_nwpi711/helpdata/en/d4/d12940cbf2195de10000000a1550b0/content.htm
I am aware that IDoc should be sent to the receiving system by using the IDoc adapter and NOT by using the IDoc Interface (tRFC port)
Thanks in advance

Hi All,
I resolved this on my own.
The steps i specified in my 1st post (Note implementation & Role assignment) was not enough, we had to assign SAP_ALL & SAP_NEW to the rfc user.    The Note implementation & role assignment should have solved this problem, but strangely it was not enough.
As for the question on why PIAFUSER is showing up as the caller and not the RFC user id used in the rfc destination used by the port, it's because the original caller is what gets recorded in SM58, in this case Receiver IDoc adapter on the AE so PIAFUSER,   and not the RFC user id.   you can verify this in table ARFCSSTATE
Thanks to all answers

Similar Messages

  • REG: Error in IDoc adapter outbound processing

    Hi All,
          I had a couple of doubts regarding these IDoc's.
    1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
    "IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
    Can any one help me to Solve my Problem
    2) How to find out whether the IDoc is of synchronous or Asynchronous mode
        and how to  handle the synchronous type of IDoc's
    Thanks in advance.
    with Regards,
    Kalyan Dannapaneni.

    Hi Kalyan,
    IDOCs are only Aynchronous (EO or EOIO).
    If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
    Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
    Best regards,
    Silvia

  • How configure a Logical System (XI) as receiver for an Outbound Idoc?

    Hi all,
    How can I configure a Logical System (XI) as receiver for an Outbound Idoc?
    Points will be given,
    Regards,
    Daniela

    hi,
    it all depends on what kind of document you need to send to XI
    if you want to send some logistic documents (like orders, deliveries etc)
    have a look at my book - where you will find step by step guides
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    then you will undestand where to change to get it send via LS
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • SM58 - IDoc adapter inbound: IDoc data record table contains no entries

    Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
    Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
    IDoc adapter inbound: IDoc data record table contains no entries
    I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
    Please point me in the right direction.

    hi,
    i think in sm 58 u can find entries only when there is some failure in login credential .
    if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
    please check the logical system name pointing to the your requird target system....
    please also verify thet your port should not be blocked.
    pls find the link it may help
    Monitoring the IDOC Adapter in XI/PI using IDX5
    regards,
    navneet

  • IDoc adapter inbox: IDoc sender partner is initial

    Hi,
       I have requirement to read the IDOC flat file and post IDOCs to SAP. As suggested in the following guide I am using report RSEINB00 to post IDOCS. This report basically calls the function module IDOC_INBOUND_FROM_FILE.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how%20to%20convert%20between%20idoc%20and%20xml%20in%20xi%203.0.pdf
    While executing the IDOC_INBOUND_FROM_FILE I am getting error:
    "IDoc adapter inbox: IDoc sender partner is initial".  
    Please advise.
    Thanks
    Rajeev Gupta

    Hi,
    Idoc will be processed in SAP ECC based on the sender details (snprn,sndpor,sndpfc...) of idoc control record..
    instead of different partners name sending in the sender details of control record ...pass the value of the PI logical system name in SNDPRN.... (use only one and this is common for all partners...) any how data records of idoc will have the needed partner details...
    In SAP ECC you need to have this logical system ...to process the received idocs..
    thats it... Hope you got
    Regards
    Rajesh

  • Why we use IDOC adapter for IDOC as reciever?

    hello,
    Why we use IDOC adapter while using IDOC as receiver, whereas we don't use IDOC adapter while IDOC is sender?
    I am clear about why we don't use adapter for sender IDOCs.
    Thank you.
    Sarika

    Hi Sarika,
    >>>>Why we use IDOC adapter while using IDOC as receiver,
    maybe the easiest answer would be that we use
    IDOC adapter as receiver to tell the XI where he should
    send the data - there are many systems to which we can
    connect our XI and somewhere there has to be an object
    which will tell thx XI "where to" -> which RFC destination should it use
    BTW
    I believe IDOC apdater is also used as sender
    although you don't configure it in AF:
    "Once the IDoc has left the application through the RFC interface and has reached the <b>IDoc adapter</b> at the Integration Server inbound channel, the system converts it from IDoc format to IDoc XML format"
    from:
    http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
    Regards,
    michal

  • Converting Inbound idoc to Outbound idoc

    Hii,,
    How to convert inbound idoc to outbound idoc.
    I have IDOC -> SOAP -> IDOC Scenario.
    In case of error at SOAP side , it return idoc with 51 status.
    Now i need to convert the Inbound idocs to Outbound Idocs and send it back to the Sender system...
    How to do accomplish this??
    Regards,
    Siya

    Hii,
    By using we19 and by exchanging sender & receiver we can convert outbound idoc to inbound idoc.
    Just want to confirm is it proper way??
    Regards,
    Siya

  • Stop generating delivery IDOC output (outbound IDOC)  if goods issued!

    How to stop generating delivery IDOC output (outbound IDOC)  if the delivery has been goods issued?! Any user exit or BADI for this?!
    Thanks

    We take a routine in output requirement! it's done!

  • Trying to change Inbound IDOC to Outbound IDOC for testing....

    Hi Friends,
    I am trying to do the following
    1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
    2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
    3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
    4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
    HELP!! Rewards

    Hi Friend,
            The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
    Use
    You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an “empty” IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
    You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
    Activities
    ·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
    You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the “file“ type. The default file is the inbound file entered there.
    ·        You generate the IDoc using .
    The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
    ·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
    You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
    ·        Click on the white fields to change data in the segments.
    In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
    In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
    ·        The additional procedure depends on whether you want to test inbound or outbound processing.
    Test: Outbound Processing from MC
    Use
    Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
    Prerequisites
    You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
    ·        Customer or vendor records
    ·        Material records
    ·        Info records
    ·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as “messages” from the respective application.
    The appropriate file ports and partner profiles must exist in the IDoc Interface.
    Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to “1” (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
    Activities
    Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
    Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
    Use
    This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
    Prerequisites
    You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
    Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to “Collect IDocs” in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode “Collect IDocs” in live operation.
    Activities
    You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
    You can decide whether the output mode is set to “Start subsystem” or “Do not start subsystem” in the partner profile. This defines whether the external (sub) system processes the IDocs further.
    Use
    This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to “File”.
    Prerequisites
    A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are “credited” to the relevant IDoc in the form of status records in the SAP System.
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
    Test: Inbound Processing: Modified Outbound File
    Use
    This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to “File”.
    Prerequisites
    You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type “File” must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
    Standard inbound processing is then triggered;
    ·        Reading the modified file
    ·        Generating the IDoc(s) in the SAP System
    ·        Processing in the application
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
    Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
    The recipient in this case is the SAP System. The port is used for identification purposes:
    ·        SAP (for example RSMITH
    Test: Inbound Processing: Original Inbound File
    Use
    This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
    Prerequisites
    You require a correct inbound file. In this case, correct means that the:
    ·        Sender and recipient in the control record are correct
    ·        Direction in the control record is set to 2 (inbound)
    ·        Client in the control record and data records are correct or empty
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
    The file is deleted after being read successfully!
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
    ·        Inbound port
    ·        Name and directory of the file
    These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
    Thanks

  • Receiver File Adapter doesn't write file but no error appers.

    Hi all,
    we have a simple scenario that was working fine. It receives a message from R3 and writes a file. Now the file is not being created, no error appears at Integration Engine message monitor, I only see at RWB Message Monitor that the message is in state "Holding..."
    Anybody knows where can I check to find errors?
    Thanks in advance,
    Diego.

    Hi Diego,
    Please check if the adapter status is Active and the changes are activated.
    Thanks
    Gaurav

  • IDoc Adapter -  ATTRIBUTE_BE_NOT_SUPP Async processing

    Hello,
    I'm trying to establish IDoc communication. Here is the scenario that I need:
    <XML Data> --- <SOAP> --> PI Server ( Map XML to IDoc XML) --- <IDoc> --> SAP Retail System
    I have the following components set up:
    1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
    2. Sender Agreement
    3. Map from InXML to OutIDoc. OutIDoc - Message Interface - Inbound Asynchronous
    4. Receiver Determination
    5. Interface Determination
    6. Receiver Agreement
    7. Receiver IDoc Communication Channel
    8. Business Service for all this
    No Integration Scenario.
    If I replace item 7 to the FTP for example, everything works just perfect - I send XML it gets Mapped to IDoc and in my FTP I have the IDoc file.
    Now, I've asked SAP support specialist to establish communication from PI Server to Retail using IDoc. He send me parameters, which I used for IDoc Communication Channel:
    RFC Destination: NX7CLNT800
    Port: A000000022
    SAP Release: 3 - this is I put myself
    But when I run the whole system again, I'm getting the error:
    IDOC_ADAPTER  ATTRIBUTE_BE_NOT_SUPP - "Only asynchronous processing supported for IDoc adapter outbound processg"
    This is very confusing because both my message interfaces are Asynchronous.
    Can anyone tell me what I'm doing wrong and why I'm getting this error.
    Thanks.

    8. Business Service for all this
    Should it not be Business System for IDOC.....for SOAP it will be Business Service
    1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous
    Check what is the QoS that is specified in the SOAP Channel.....if it is Best Effort then it will be a cause of the error......change it to Exactly Once (EO).
    Regards,
    Abhishek.
    Edited by: abhishek salvi on Dec 4, 2009 10:29 AM

  • IDoc Adapter throws error

    We are trying to send data to SAPR/3 47 IDES using IDoc Adapter.
    the data is sent to XI from SQL database thro JDBC adapter and then to R/3 thro IDoc adapter.
    All this is in Asynchronous mode and at no point we chose synchronous (IDoc adapter does not suppost Asynchronous process right).
    But we are getting the following error:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>SystemError</SAP:MessageClass>
      <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
      <SAP:MessageId>B7685EB2-42F1-554B-80CC-6ADFC86C7975</SAP:MessageId>
      <SAP:RefToMessageId>35A42550-81F9-11D9-AFC7-00C09F450580</SAP:RefToMessageId>
      <SAP:TimeSent>2005-02-18T22:05:33Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>S70_812</SAP:Service>
      <SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">DEBMAS.DEBMAS04</SAP:Interface>
      </SAP:Sender>
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_BE_NOT_SUPP</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Only asynchronous processing supported for IDoc adapter outbound processing</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    We are not sure where from this synchronous is being picked?
    Please advise.
    Thanks,
    Bhaskar and Anil

    In the Processing Parameters section of the JDBC adapter, make sure you have Exactly Once (Asynchronous) selected.

  • Idoc adapter- communiccation channel

    Hi
              When we do an Idoc to file scenario sender communication channel is not required. Because Idoc is the sender adapter. but while doing a File to Idoc case why do we neeed a receiver communication channel. Here also we use Idoc so why use a communication channel ?

    Hi,
    You do not need A Sender IDOC Adapter. IDoc's are sent directly to XI's Integration Engine and so no need of Sender IDOC adapter and therby Sender Agreement as well.
    Yes, the port will be a TRFC port and you will use the RFC destination created in SM59 in this port.
    Idoc Metadata gets loaded automatically when your scenario is run. You can also do it manually, by going to IDX2 and probiing the Port and the Basic Type of the idoc whose metadata you want to load.
    but when we go for a fileto IDOC the file does not contain a standard structure
    for that reason we need to create the receiver IDOC adapter .
    pls chk this links
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    if found worth pls do the req
    Thanx
    Sampath

  • SA PI 7.1 EHP1 - Support for IDOC Adapter using AAE

    Hi,
    Can anyone confirm if the SAP PI 7.1 EHP1 supports the IDOC adapter in the AAE ?
    Cheers
    Colin.

    Hi Colin,
    I am workinngt on EHP1 PI7.1,but no support for IDoc Adapter in the AAE.
    The new features added for IDoc adapter is IDoc packging and new conversion module added .
    we have to wait till next release,but not sure...
    Regards,
    raj

  • SLSRPT Inbound or Outbound idoc ?

    is SLSRPT inbound idoc or outbound idoc and what is the Process code used ?
    Thanks
    Praveen chindam.

    Hi Praveen,
    Welcome to sdn.
    This function allows you to receive and process the following types of partner transmissions in CRM:
    ·        Resale Report u2013 (ANSI X12; EDI 867, Message Type SLSRPT)
    it is an inbound idoc.
    see this link
    http://repository.edifice.org/migs/slsrpt3/compare.htm
    thanks
    trinadh

Maybe you are looking for

  • Disable 'Find' (good /service) function in 'items in shopping cart' SRM 5.5

    Hi SRM experts, after clicking on Shopping Cart (- Full functionality) you have the choice of searching in catalogs or you can scroll down to 'Items in Shopping cart' and enter the product-id directly in 'Good / Service'. How can I disable this 'Find

  • Downloaded Photoshop Elements 12 for Windows now want to use it on Apple Mac

    Does Adobe support customers who bought Photoshop Elements 12 for Windows and then buy an apple Mac and want to use it on there (without having to buy a new subscription).

  • 2 TB WD "unreadable" (ticking)

    grrrr. i have two - 2 TB WD "My Book Essential" external drives that i bought within the last four months with one running my Time Machine backup and the other partitioned into two 1 TB partitions and /one/ of these is running a clone of my drive via

  • Unable to make changes to template given to me

    Using CS3, I am trying to modify some pages someone gave to me. It was a template so I detached it as a template. However, now, when I try to modify colors both manually, and through search-and-replace in both the XHTML and CSS files, I receive the f

  • How do I make a 7 x 8.5 or 3 x 5 etc canvas ?

    How do I make a 7 x 8.5 or 3 x 5 etc canvas ? I tried it in  the "artboard" panel but the custom choice is greyed out. This artboard panel seems like a roundabout work flow for what used to be easy, what am I missing? Garrett