Messages to MQ series

Hi Experts,
To send messages to Message Queue (MQ Series) we use JMS adapter and send the messages. But how to get the messages from the Message Queue using JMS? because it will send objects...
Points will be awarded u2026u2026u2026u2026u2026
Thanks,
Manoj

i suggest for simple questions u pls hit a search button on SDN, these are answered many times.
ur XI JMS adapter wil pick the message from queue of MQ server.U need to configure the JMS adapter with detail information.
How to configure the sender & recevier JMS adapter.
How to use SAP's WebAS J2EE's JMS Queue in Exchange Infrastructure
chirag
Edited by: Chirag Gohil on Oct 30, 2008 9:26 PM

Similar Messages

  • Error message `the HP series 1050 J410 cannot be found

    i have an HP Deskjet 1050 All in one printer. I have been using it for a couple of years without problems, but since a month it doesn´t scan any more. The error message is `HP deskjet 1050 J410 series cannot be found`. This problem exists when I try to start the link on the desk of the computer as well as when I try to start the scan with the start menu of the computer, which is running on Windows 7. Do you know how to solve this problem?

    Hello missessgrass,
    Welcome to the HP Forums!
    I understand you're unable to scan a document and a message appears stating "The Deskjet 1050 J410 cannot be found". I will do my best to assist you! I would recommend following this entire HP document on A 'Connection Error' Message Displays during Scanning.
    If this document doesn't resolve your issue, then follow this HP document on Windows: HP Scan Software Does Not Open or Scan on a Printer Using a USB Connection.
    Please post your results, as I will be looking forward to hearing from you. Have a great night!
    I worked on behalf of HP.

  • Publish message to MQ Series

    I need to send data from Peoplesoft to MQ series. I have data scattered across two to three components. In order to publish the data from all these components would it be ideal to go for a view or is there any other way?

    Turns out that AUTO_ACK was not the problem. It was a MessageListener ...
    It turned out that when I got rid of the MessageListener that I was using on the Queue Manager that was trying to send to the cluster queue, my performance went through the roof. Maybe the MessageListener was blocking the mechanism by which messages get put to a cluster queue?!?!
    Anybody got any ideas that might shed some light on this behavior?
    Thanks,
    Mark

  • How to send jms message to mq series

    Hi all,
    I'm new to JMS and I've been asked to send an xml file to a IBM MQ series message queue.
    I need to send this message from an application running on a tomcat webserver.
    Basically, what packages do I need to start with that?
    Is that possible without installing an MQ client on the webserver?
    What parameters would I need to make a connection? I currently only know the QUEUE name and that the MQ is running on a different machine than the webserver is.
    Thank you!
    Steven

    This can help u writing to MQueue
    ==================================================================
    // Program Name
    // MQWrite
    // Last date of modification
    // 1 Oct 2000
    // Description
    // This java class will read a line of input from the keyboard
    // and send it as a message. The program will loop until the
    // user presses CTL^Z.
    // Sample Command Line Parameters
    // -h 127.0.0.1 -p 1414 -c CLIENT.CHANNEL -m MQA1 -q TEST.QUEUE
    // Copyright(C), Roger Lacroix, Capitalware
    import com.ibm.mq.*;
    import java.io.IOException;
    import java.util.Hashtable;
    import java.io.*;
    public class MQWrite {
    private MQQueueManager _queueManager = null;
    private Hashtable params = null;
    public int port = 1414;
    public String hostname = "127.0.0.1";
    public String channel = "CLIENT.TO.MQA1";
    public String qManager = "MQA1";
    public String outputQName = "SYSTEM.DEFAULT.LOCAL.QUEUE";
    public MQWrite()
    super();
    private boolean allParamsPresent()
    boolean b = params.containsKey("-h") &&
    params.containsKey("-p") &&
    params.containsKey("-c") &&
    params.containsKey("-m") &&
    params.containsKey("-q");
    if (b)
    try
    port = Integer.parseInt((String) params.get("-p"));
    catch (NumberFormatException e)
    b = false;
    // Set up MQ environment
    hostname = (String) params.get("-h");
    channel = (String) params.get("-c");
    qManager = (String) params.get("-m");
    outputQName = (String) params.get("-q");
    return b;
    private void init(String[] args) throws IllegalArgumentException
    params = new Hashtable(5);
    if (args.length > 0 && (args.length % 2) == 0)
    for (int i = 0; i < args.length; i+=2)
    params.put(args, args[i+1]);
    else
    throw new IllegalArgumentException();
    if (allParamsPresent())
    // Set up MQ environment
    MQEnvironment.hostname = hostname;
    MQEnvironment.channel = channel;
    MQEnvironment.port = port;
    else
    throw new IllegalArgumentException();
    public static void main(String[] args)
    MQWrite write = new MQWrite();
    try
    write.init(args);
    write.selectQMgr();
    write.write();
    catch (IllegalArgumentException e)
    System.out.println("Usage: java MQWrite <-h host> <-p port> <-c channel> <-m QueueManagerName> <-q QueueName>");
    System.exit(1);
    catch (MQException e)
    System.out.println(e);
    System.exit(1);
    private void selectQMgr() throws MQException
    _queueManager = new MQQueueManager(qManager);
    private void write() throws MQException
    String line;
    int lineNum=0;
    int openOptions = MQC.MQOO_OUTPUT + MQC.MQOO_FAIL_IF_QUIESCING;
    try
    MQQueue queue = _queueManager.accessQueue( outputQName,
    openOptions,
    null, // default q manager
    null, // no dynamic q name
    null ); // no alternate user id
    DataInputStream input = new DataInputStream(System.in);
    System.out.println("MQWrite v1.0 connected");
    System.out.println("and ready for input, terminate with ^Z\n\n");
    // Define a simple MQ message, and write some text in UTF format..
    MQMessage sendmsg = new MQMessage();
    sendmsg.format = MQC.MQFMT_STRING;
    sendmsg.feedback = MQC.MQFB_NONE;
    sendmsg.messageType = MQC.MQMT_DATAGRAM;
    sendmsg.replyToQueueName = "ROGER.QUEUE";
    sendmsg.replyToQueueManagerName = qManager;
    MQPutMessageOptions pmo = new MQPutMessageOptions(); // accept the defaults, same
    // as MQPMO_DEFAULT constant
    while ((line = input.readLine()) != null)
    sendmsg.clearMessage();
    sendmsg.messageId = MQC.MQMI_NONE;
    sendmsg.correlationId = MQC.MQCI_NONE;
    sendmsg.writeString(line);
    // put the message on the queue
    queue.put(sendmsg, pmo);
    System.out.println(++lineNum + ": " + line);
    queue.close();
    _queueManager.disconnect();
    catch (com.ibm.mq.MQException mqex)
    System.out.println(mqex);
    catch (java.io.IOException ioex)
    System.out.println("An MQ IO error occurred : " + ioex);
    // Description
    // This java class will read a line of input from the keyboard
    // and send it as a message. The program will loop until the
    // user presses CTL^Z.
    // Sample Command Line Parameters
    // -h 127.0.0.1 -p 1414 -c CLIENT.CHANNEL -m MQA1 -q TEST.QUEUE
    import com.ibm.mq.*;
    import java.io.IOException;
    import java.util.Hashtable;
    import java.io.*;
    public class MQWrite {
    private MQQueueManager _queueManager = null;
    private Hashtable params = null;
    public int port = 1414;
    public String hostname = "127.0.0.1";
    public String channel = "CLIENT.TO.MQA1";
    public String qManager = "MQA1";
    public String outputQName = "SYSTEM.DEFAULT.LOCAL.QUEUE";
    public MQWrite()
    super();
    private boolean allParamsPresent()
    boolean b = params.containsKey("-h") &&
    params.containsKey("-p") &&
    params.containsKey("-c") &&
    params.containsKey("-m") &&
    params.containsKey("-q");
    if (b)
    try
    port = Integer.parseInt((String) params.get("-p"));
    catch (NumberFormatException e)
    b = false;
    // Set up MQ environment
    hostname = (String) params.get("-h");
    channel = (String) params.get("-c");
    qManager = (String) params.get("-m");
    outputQName = (String) params.get("-q");
    return b;
    private void init(String[] args) throws IllegalArgumentException
    params = new Hashtable(5);
    if (args.length > 0 && (args.length % 2) == 0)
    for (int i = 0; i < args.length; i+=2)
    params.put(args[i], args[i+1]);
    else
    throw new IllegalArgumentException();
    if (allParamsPresent())
    // Set up MQ environment
    MQEnvironment.hostname = hostname;
    MQEnvironment.channel = channel;
    MQEnvironment.port = port;
    else
    throw new IllegalArgumentException();
    public static void main(String[] args)
    MQWrite write = new MQWrite();
    try
    write.init(args);
    write.selectQMgr();
    write.write();
    catch (IllegalArgumentException e)
    System.out.println("Usage: java MQWrite <-h host> <-p port> <-c channel> <-m QueueManagerName> <-q QueueName>");
    System.exit(1);
    catch (MQException e)
    System.out.println(e);
    System.exit(1);
    private void selectQMgr() throws MQException
    _queueManager = new MQQueueManager(qManager);
    private void write() throws MQException
    String line;
    int lineNum=0;
    int openOptions = MQC.MQOO_OUTPUT + MQC.MQOO_FAIL_IF_QUIESCING;
    try
    MQQueue queue = _queueManager.accessQueue( outputQName,
    openOptions,
    null, // default q manager
    null, // no dynamic q name
    null ); // no alternate user id
    DataInputStream input = new DataInputStream(System.in);
    System.out.println("MQWrite v1.0 connected");
    System.out.println("and ready for input, terminate with ^Z\n\n");
    // Define a simple MQ message, and write some text in UTF format..
    MQMessage sendmsg = new MQMessage();
    sendmsg.format = MQC.MQFMT_STRING;
    sendmsg.feedback = MQC.MQFB_NONE;
    sendmsg.messageType = MQC.MQMT_DATAGRAM;
    sendmsg.replyToQueueName = "ROGER.QUEUE";
    sendmsg.replyToQueueManagerName = qManager;
    MQPutMessageOptions pmo = new MQPutMessageOptions(); // accept the defaults, same
    // as MQPMO_DEFAULT constant
    while ((line = input.readLine()) != null)
    sendmsg.clearMessage();
    sendmsg.messageId = MQC.MQMI_NONE;
    sendmsg.correlationId = MQC.MQCI_NONE;
    sendmsg.writeString(line);
    // put the message on the queue
    queue.put(sendmsg, pmo);
    System.out.println(++lineNum + ": " + line);
    queue.close();
    _queueManager.disconnect();
    catch (com.ibm.mq.MQException mqex)
    System.out.println(mqex);
    catch (java.io.IOException ioex)
    System.out.println("An MQ IO error occurred : " + ioex);

  • Retrieving messages from MQ Series

    Hi,
    We have the situation where we need to receive messages from our partner, who only can use MQ Series to send them. So we are looking into ways how to solve it on our end, which is on a Unix server. We will only read messages, and the other side will be a black box for us which will provide us with settings to connect to their manager.
    Do we need to install a client software (which IBM seems to provide for free) and on top of that use a Java API? Or do we use JMS on top of the client?
    Or if we use JMS, isn't the client needed?
    Thanks

    Hi
    I am trying to read messages from the MQ using the following code.
    The queue used by this program is shared, msg is pushed other program and this progam fetch the msg and save it physically.
    I m facing a problem, say there are 15 messages, then 15 files should be created, some time it creates 15 files one for each message, while some times it creates less then 15 files.
    String messageType = null;
              String docId = null;
              String idocData = null;
              String fileName = null;
              String msgId = null;
              try {
                   // Create a queue manager object and access the queue
         // that will be used for getting the messages.
                   qMgr = new MQQueueManager(qManager, env);
                   //int openOptions = MQC.MQOO_INPUT_EXCLUSIVE | MQC.MQOO_BROWSE | MQC.MQOO_INQUIRE;
                   int openOptions = MQC.MQOO_INPUT_SHARED | MQC.MQOO_BROWSE | MQC.MQOO_INQUIRE | MQC.MQOO_FAIL_IF_QUIESCING;
                   queue = qMgr.accessQueue(qName, openOptions, null, null, null);
                   MQGetMessageOptions gmo = new MQGetMessageOptions();
                   // Get the count of messages present into Queue.
                   int messageCnt = queue.getCurrentDepth();
                   _logger.info("Current Depth of MQ is : "+ messageCnt);
                   if (messageCnt > cnt && cnt != 0) {
                        messageCnt = cnt;
                   // If count is greater than Zero then get the message from Queue
                   // and creates the file under the target folder.               
                   if (messageCnt > 0) {
                        for (int i = 0; i < messageCnt; i++) {
                             _logger.info("Depth of MQ Before reading : "+ queue.getCurrentDepth());
                             messageType = "";
                             docId = "";
                             idocData = "";
                             fileName = "";
                             msgId = "";
                             MQMessage message = new MQMessage();
                             queue.get(message, gmo);
                             byte[] data = new byte[message.getMessageLength()];
                             String msg = null;
                             message.readFully(data);
                             _logger.info("Getting File  : "+ (i+1));
                             try {
                                  msg = new String(data);
                                  messageType = msg.substring(147, 177).trim();
                                  docId = msg.substring(121, 137).trim();
                                  idocData = msg.substring(108, msg.length());                              
                                  msgId = String.valueOf(System.currentTimeMillis());
                                  // Getting inbox folder path                              
                                  if (messageType.trim().equalsIgnoreCase("INVOIC01")) {
                                       targetFolder = BOCConfig.getProperty("invoice.inbox.folder");
                                  } else if (messageType.trim().equalsIgnoreCase("DELVRY03")) {
                                       targetFolder = BOCConfig.getProperty("asn.inbox.folder");
                                  fileName = createFile(idocData, msgId, messageType, targetFolder);                              
                                  _logger.info("File Created no " + (i+1) +" with msgId " + msgId + " messageType " + messageType + " DocId " +docId);                              
                                  _logger.info("Depth of MQ After reading : "+ queue.getCurrentDepth());
                             } catch (NullPointerException ne) {
                                  String strMsg = "Edgeware got junk or null message from MQ which is not proceed by MQ Adapter.";
                                  fileName = createFile(idocData, msgId, messageType, failedFolder);
                                  raiseAlert(strMsg, messageType, docId, fileName, ne.getMessage());                              
                             } catch (StringIndexOutOfBoundsException siobe) {
                                  String strMsg = "Edgeware got invalid message from MQ which is not handled by MQ Adapter.";
                                  fileName = createFile(idocData, msgId, messageType, failedFolder);
                                  raiseAlert(strMsg, messageType, docId, fileName, siobe.getMessage());                         
                             } catch (Exception e) {
                                  String strMsg = "Edgeware got error while creating idoc file or DB transction";
                                  fileName = createFile(idocData, msgId, messageType, failedFolder);
                                  raiseAlert(strMsg, messageType, docId, fileName, e.getMessage());
                   // closing the queue.
                   queue.close();
              } catch (MQException ex) {
                   String strMsg = "Edgeware got MQ Error while connecting/retrieving message from Queue";
                   String err = "MQ exception: CC = " + ex.completionCode + " RC = " + ex.reasonCode;               
                   raiseAlert(strMsg, messageType, docId, failedFolder, err);
              } catch (IOException e) {
                   String strMsg = "Edgeware got MQ Error while reading message from the Queue";               
                   raiseAlert(strMsg, messageType, docId, failedFolder, e.getMessage());               
              }catch (Throwable th) {
                   String strMsg = "Edgeware got Runtime Exception";               
                   raiseAlert(strMsg, messageType, docId, failedFolder, th.getMessage());               
              }

  • Foreign Character Issue in Messages sent to MQ Series Queue

    Hi Experts,
    We are having a IDOC to JMS Scenario.We receive the IDOC and Convert it into a Single Line Flat File using a JAVA Mapping.We send the flat file message to MQ series 6.0 Queue using a JMS adapter.
    We are facing issues when message contains foreign character like Chinese , German and Greek.
    The Input\Output payload looks fine in SXMB_MONI and in the JMS Channel payload. when the message is put in the MQ Series Queue. When we open the messages in the JMS Q, the Foreign Character looks as "?????".
    PFB some details on the Java Code and other Config Settings.
    1. We read the messages from the Input Stream as UTF-8 and do the Transformation and Write the Output as UTF-8
    we use writer class to write the output after conversion (shown below).
    Writer osw = new OutputStreamWriter (osOutput,"UTF-8");
    2. The MQ series is in UNIX box and CCSID of the Queue Manager is 819.
    we have set the CCSID of the JMS channel 819.
    can you please clarify in case any transformation is happening before placing the message in the queue and how to we handle this case from the channel or in the Java code.
    Some Sample Character are u0395u03A3u03A4u0399u0391u03A4u039Fu03A1u0399u0391-u03A4u0391u0392u0395u03A1u039Du0395u03A3-u039Au0391u03A6 , u039Au039Fu039Du0399u039Fu03A1u0394u039Fu03A5 u03A7u03A1u03A5u03A3u0391 , and some Chinese Characters too

    Hi All,
    Thank you all . My problem is not resolved yet
    I have one more useful info.
    I set the Transport Protocol as TCP\IP and Kept the JMS Compliant as WebsphereMQ (Non-JMS) in JMS Channel Parameters TAB. In additional Parameters TAB i have set  "JMS.TextMessage.charset"     as ISO-8859-1.In this Setting, The Characters looks perfectly fine when i browse and view the messages in MQ Series Q. Messages are sent in MQSTR format, where the message has no header value.
    Intially i had set JMS Compliant Field as "JMS Compliant" with additional param TAB set as ISO-8859-1, where the message is sent in MQHRF2 format containing header details. i also configure dynamic header values using AF_Modules to this header. Special Chars didnt work.
    Now in MQSTR due to missing Header values the messages are not being identified and routed properly by the end system from the MQ series. 
    Now i need to find the missing loop, what happens when message is sent using WebSp MQ API's (MQSTR) and Java API (MQHRF2). I need to have MQHRF2 format with Messages body sent exactly as it is in MQSTR. Is there any parameter, which i need to set.
    can anyone help me in this  regard.

  • How to set user ID in JMS message

    I am looking for ways to set the user ID in a JMS message over MQ series. I have looked at various way of doing it including:
    1) setting the appropriate environment variable in MQEnvironment
    2) setting provider specific properties (of the format "JMS_IBM_xxxx")
    3) in desperation, setting any likely looking property, e.g. "JMSXUserId"
    None of these work, consequently the default user ID "mqm" is propagated. Rather than getting an error message back (with, I think, a 2059 code) when host authentication fails, I simply get nothing back.
    I'd be grateful for any suggestions
    Hugh Ferguson

    3) in desperation, setting any likely looking
    property, e.g. "JMSXUserId"I believe these properties are case-sensitive. We don't set the user id property in our JMS messages, but I can tell you that when we receive messages from apps on our mainframe host (which do not use JMS - they use the COBOL api), the user id is in a property called UserID (note that "ID" is capitalized). In raw form, it's JMSXUserID.
    Hope this helps,
    -Scott

  • JMS Sender Channel Error with MQ Series

    Hi,
    I am trying to send a message from MQ Series to XI via JMS Adapter.  I am getting this error message, and I have searched the forums for this error message with no luck.  Can someone please help?  I have asked the BASIS team to double check and make sure the JMS drivers have been deployed. I am still waiting for their reply.
    Thanks in advance
    Zeshan Anjum

    Sorry, I forgot to append the error message.
    Here it is:
    0 XI inbound processing failed for message at 2006-10-19|09:54:30.925-0500. JMS and XI identifiers for the message are ID:414d51205a3153505420202020202020448dda5420003f01 and b9be54c0-5f81-11db-a551-001125a6015a respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception: Value with name enableDynConfigSender not available
    at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java(Compiled Code))
    at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java(Compiled Code))
    at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java(Compiled Code))

  • Configuring MDB to receive message from MQSeries Queues bound on WL JNDI

    Hi,
    I am using weblogic7.0 sp2. I need to configure my MDB to receive message from MQ Series (on a different server). The queue is bound to WL JNDI using a server startup program.
    Anyone with experiece, please help.
    Thanks,
    Fasih

    I'd start here:
    http://e-docs.bea.com/wls/docs70/faq/index.html
    -- Rob
    WLS Blog http://dev2dev.bea.com/blog/rwoollen/

  • JMSReplyTo property for MQ-message (trouble)

    Hello all!
    I'm trying to send JMS message to MQ-queue and I need to set field JMSReplyToQ in JMS section.
    I'm using:
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0
    JMS_QUEUE_CONNECTION,
    Queue_payload_type => 'SYS.AQ$_JMS_TEXT_MESSAGE'
    FQ domain -> dbms_mgwadm.DOMAIN_QUEUE
    But I can’t set JMSReplyTo property for MQ-message. Please could you like help me for this trouble?
    See below my PL/SQL block:
    declare
    i_msg_id raw(24);
    l_id varchar2(25);
    l_msg_id raw(24);
    l_answer_queuename varchar2(80);
    l_answer_msg clob;
    l_answer_xml XMLType;
    procedure Put_MsgX (i_QueueName varchar2,
    i_msg CLOB,
    i_msg_id raw,
    i_characterSet number := 1208)
    is
    l_EnqueueOptions DBMS_AQ.ENQUEUE_OPTIONS_T;
    l_MsgProperties DBMS_AQ.MESSAGE_PROPERTIES_T;
    l_MsgID raw(16);
    l_msg_str CLOB:=i_msg;
    l_msg_str_len int;
    l_replyto sys.aq$_agent;
    l_header sys.aq$_jms_header;
    l_properties sys.aq$_jms_userproparray;
    l_mess_jms_text sys.aq$_jms_text_message;
    begin
    l_EnqueueOptions.visibility := DBMS_AQ.IMMEDIATE;
    -- Message object creating
    l_msg_str_len:=LENGTH(l_msg_str);
    l_mess_jms_text:=sys.aq$_jms_text_message(l_header
    ,l_msg_str_len
    ,l_msg_str
    ,null);
    -- MQRFH2 jms-folder properties
    l_mess_jms_text.set_groupid('grp_1');
    l_mess_jms_text.set_groupseq(5);
    -- Message corellation ID
    l_MsgProperties.correlation:='555D5120514D5F333C45584D4C2021115178D7BF20046922';
    -- Message priority
    l_MsgProperties.priority:=0;
    -- MQRFH2 usr-folder properties
    l_mess_jms_text.set_string_property('SOAPJMS_requestURI','jms:jndi:');
    l_mess_jms_text.set_string_property('SOAPJMS_contentType','text/xml; charset=utf-8');
    l_mess_jms_text.set_string_property('SOAPJMS_bindingVersion','1.0');
    /* -------- It is NOT WORKED !!! ----------------------------
    -- This code line isn’t effected to result (MQ Series message property ReplytoQ is empty)
    l_mess_jms_text.set_string_property('JMS_IBM_MQMD_ReplyToQ','queue:///PPV.JMS.MQ.OUT');
    -- This code line effected error
    -- oracle.jms.AQjmsException: JMS-147: Invalid ReplyTo destination type, or use of reserved `JMSReplyTo agent name,
    -- or serialization error with AQjmsDestination
    l_replyto:=sys.aq$_agent(null,'FXGTST.JMS_OUT',null);
    l_mess_jms_text.set_replyto(l_replyto);
    -- Sending message to MQ Series queue
    dbms_aq.enqueue(queue_name => i_QueueName,
    enqueue_options => l_EnqueueOptions,
    message_properties => l_MsgProperties,
    payload => l_mess_jms_text,
    msgid => l_MsgID);
    exception
    when others then
    Raise;
    end;
    begin
    i_msg_id:=UTL_RAW.SUBSTR(UTL_RAW.CAST_TO_RAW(SUBSTR(LPAD('999888777',24,'0'),1,24)),1,24);
    l_msg_id:=i_msg_id;
    l_answer_msg:=
    '<?xml version="1.0" encoding="UTF-8"?>'||
    '<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">'||
    '<SOAP-ENV:Header>'||
    '<m:UCBRUHeaders xmlns:m="urn:ucbru:gbo:v3"></m:UCBRUHeaders>'||
    '</SOAP-ENV:Header>'||
    '<SOAP-ENV:Body>'||
    -- some XML elements
    '</SOAP-ENV:Body>'||
    '</SOAP-ENV:Envelope>';
    l_answer_xml:=xmltype(l_answer_msg);
    l_answer_queuename :='FXGTST.JMS_IN';
    Put_MsgX(l_answer_queuename,l_answer_msg,l_msg_id);
    commit;
    exception
    when others then
    raise_application_error(-20020, 'Error: '||sqlerrm||' Queue='||l_answer_queuename);
    end;

    From JMS the correct way to set the mq message format to MQSTR is by using a JMS text message. You don't have to set anything explicitly.
    Can you try posting the message to a local mq and use some tool to see the message sitting on the format and check for the MQ format field. Also let know what exact error the other system is getting.
    P.S: For anything MQ, I would recommend to use this forum : www.mqseries.net.

  • WLS 5.1 JMS and Message load balancing

    Would I be right in thinking that WLS 5.1 offers no out of the box component that distributes incoming messages over a series of JMS Destinations? (much like a distributed destination would do in WLS 8.1?)
              Is it BEA's recommendation then that any JMS Client sending to these JMS destinations pick's up the responsibility for carrying out load balancing?
              regards
              Barry

    Would I be right in thinking that WLS 5.1 offers no          > out of the box component that distributes incoming
              > messages over a series of JMS Destinations? (much
              > like a distributed destination would do in WLS 8.1?)
              Yes.
              >
              >
              > Is it BEA's recommendation then that any JMS Client
              > sending to these JMS destinations pick's up the
              > responsibility for carrying out load balancing?
              Application dependent.
              For example, you could set up an EJB that enqueues to the local queue - where the local queue's name is inferred from the server the EJB is running on.
              Load balancing (and fail-over) would then be accomplished by invoking the EJB and depending on standard EJB features...
              >
              > regards
              > Barry

  • Scheduled series are not recording

    About 2 weeks ago I noticed that some of my scheduled series (record new only) were not being recorded.  After checking that there were no programming conflicts I manually programmed the following week's episode, and when I tried to program it as a series I received the message that the series was already programmed, so i chose to just record that episode.  Now I have to manually record these series.  What's up?
    This is happening with the new season of Parenthood, Revolution and Top Chef.  Does anyone know why this is happening?
    Solved!
    Go to Solution.

    Are you sure the programs you are trying to record are brand new (meaning they have never aired before). You may want to change the setting to "new and repeats".  This setting will make sure each episode will be recorded, even if the system is not sure if it is a re-run or a brand new episode, but it will not record duplicate episodes.

  • Can multiple Instances use Message Gateway on the same box ?

    I have message gateway propagating messages to MQ Series Queues on instance DV1. I'd like to set up similar propagation on instance DV2 on the same host. Is that possible ? Do I need different tnsnames/listener settings ?
    I tried to start the agent on both instances using dbms_mgwadm.startup. On querying mgw_gateway, DV1 shows the agent's running and reachable. However, DV2 shows that the agent's starting and unreachable. There are no corresponding messages in mgw.log.

    answered my own q. I had to put the instance name in the db_connect_info call.

  • SMI error on Web UI of SNC 5.1

    Dear experts,
    I'm working on SMI (Supplier Managed Inventory) implementation with SAP SNC 5.1. I'm trying  to do a demo on SNC.
    At moment I have:
    1) Created our set of master data.
    2) Configured the CIF communication to send from ECC to SNC the maser data: Material, Plant/Location, Vendor/Location, Contract.
    3) Sent successfully the Master data from ECC to SNC according to the CIF communication defined before.
    4) Configured Partner Profile in ECC.
    5) Created a Business Partner in SNC.
    6) Created a Transportation Line in SNC.
    7) Created a demand in ECC.
    8) Sent successfully the demand from ECC to SNC through PI (by PROACT and related XML).
    9) I have approached the portal on Web User Interface where the Vendor creates the Replenishment Plan (SMI Monitor details), here I can see the material, the plant but there is an error with display of demand.
    Here the error message is:
    Time series error in class /SCF/CL_ICHDM_DATAAXS method /SCF/IF_ICHDMAXS_2_CNTL~SELECT
    Planning object structure 9AINVM1 was not found
    I have seen and implemented the customization of OSS note 1019289 but the error is still there.
    I'm going crazy to solve it. Could you please help me?
    Thank you very much in advance for your support.
    Nicola
    Edited by: PTP Team Accenture on Jul 11, 2011 9:57 PM

    Hello Nicola,
    To activate Planning object structure 9AINVM1 go to transaction code:/N/SCA/TSDM09 select inactive Times series data type INVM1(Note there will be 2 INVM1 time series data type one with active check box checked and second with uncheck check box select the second one uncheck INVM1).
    Select Active planning Object structure and execute.
    If you are still getting same problem then checkout the SAP note 1143456.
    Regards,
    Nikhil

  • Time Machine - TROUBLESHOOTING

    This article provides some troubleshooting tips for common Time Machine errors and problems.
    It does not cover problems specific to Time Capsule or other wireless backups. See the Airport and Time Capsule forum, in the Digital Life section.
    Nor does it include general information about Time Machine. For those, see the Frequently Asked Questions *User Tip* at the top of this forum.
    _*C o n t e n t s*_
    *Section A. _TOOLS YOU MAY NEED*_
    *A1. Time Machine Buddy widget*
    *A2. Time Tracker*
    *A3. Tinker Tool*
    *Section B. _SET - UP PROBLEMS*_
    |
    *B1. I can't select my drive for use with Time Machine*
    *B2. The Change Disk option doesn't work*
    *B3. No last or oldest backup date shown*
    *B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*
    *Section C. _BACKUP FAILURES*_
    |
    *C1. Initial Backup Failed*
    *C2. Other Backup Fails*
    *C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*
    *C4. "This backup is too large"*
    *C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <Name>"*
    *C6. The backup volume is read only*
    *C7. "Error (12): Link of previous volume failed."*
    *C8. Backup fails after Logic Board replacement*
    *C9. "The back-up disk image could not be created."*
    *C10. Error: (-50) Creating directory*
    *C11. Drive does not appear to be the correct backup volume for this computer (Cookies do not match)*
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    |
    *D1. Stuck in Preparing*
    *D2. Backup is Slow or "hung"*
    *D3. TM is doing a full backup for no good reason*
    *D4. My backups seem too large*
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    |
    *E1. Backups were deleted unexpectedly*
    *E2. I can't see some backups*
    *E3. I can't see backups for a disk/partition that's no longer connected*
    *E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*
    *Section A. _TOOLS YOU MAY NEED*_
    There are some free 3rd-party tools that may be useful in diagnosing problems with Time Machine. You'll see references to them in several places below.
    _*A1. Time Machine Buddy widget*_
    |
    Click here to download the +*Time Machine Buddy*+ widget.
    It shows the messages from your logs for one TM backup run at a time, in a small window. An explanation of some of the error messages is in section #C2 below. Other common messages are explained in item #7 of the Frequently Asked Questions *User Tip* at the top of this forum.
    You can copy these messages by selecting them via dragging your mouse over them (be sure to get them all, as they may overflow the small window), then pressing CMD-C. This copies them to your "clipboard," so you can post them in a thread here (via CMD-V) to get help diagnosing a problem. (Occasionally, the widget won't let you copy while a backup is running.)
    If the message area is blank, but you know there were backups, your user account may not have permission to view your logs. Try signing-on as an Admin User. You can grant "read" rights to the folder /var/log for the other user.
    Note that the widget may only let you look back a few days. If you need to look back farther, you'll need the Console app (in your Applications/Utilities folder) to look at your older system logs (named +*system.log.1.bz2, system.log.2.bz2,+* etc). Click +*Show Log List*+ in the toolbar, then navigate to the desired logs in the sidebar that opens up. You can select only the messages from TM backups by typing backupd in the Filter box in the toolbar.
    |
    _*A2. Time Tracker*_
    |
    Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). This can help you figure out just what is (or is not) being backed-up.
    |
    _*A3. Tinker Tool*_
    |
    Click here to download the +*Tinker Tool*+ app. It allows you to change the Finder to show hidden files (among many other things). Select the first option under Finder, then click +Relaunch Finder+ at the bottom. Reverse this when done.
    Do not use any of the other options unless you know the possible consequences.
    |
    *Setcion B. _SET - UP PROBLEMS*_
    _*B1. I can't select my drive for use with Time Machine*_
    If the drive/partition you want to use for TM backups doesn't appear in the list when you select TM Preferences > Change Disk, it's probably not formatted correctly. See item #C1 for help determining whether it's right, and how to fix it.
    |
    _*B2. The Change Disk option doesn't work*_
    If the +*Change Disk*+ button in TM Preferences doesn't do anything, try turning-off the +*Back To My Mac*+ application temporarily.
    |
    _*B3. No last or oldest backup date shown*_
    |
    If these dates don't appear when selecting the TM icon in your Menubar, or TM Preferences, try the following:
    1. Do a +*Back Up Now.*+ That will often recover the info.
    2. De-select your TM Drive via TM Preferences (select "none"), quit System Preferences, then re-select it and do a +*Back Up Now.*+
    3. A Log Out or Restart may fix it.
    4. If they're still not shown, try a *"Full Reset:"*
    |
    a. Turn TM Off, de-select the drive (select "none"), note any exclusions in Options, quit System Preferences.
    b. Eject, disconnect, and power-off the drive for a few moments, then reconnect it.
    c. Delete the file /Library/Preferences/com.apple.TimeMachine.plist (in your top-level Library folder, not your home folder).
    d. Re-select your drive (and re-enter any exclusions).
    e. Do a +*Back Up Now*+ or wait for the next scheduled backup.
    |
    _*B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*_
    |
    Try de-selecting, then re-selecting the "Show" option in Finder > Preferences > General and/or Sidebar.
    Try a "Full Reset" as in item #B3.
    |
    *Section C. _BACKUP FAILURES*_
    _*C1. Initial Backup Failed*_
    The most common cause is the TM drive not being formatted correctly (even, on occasion, if TM formatted it!). Use Disk Utility (in your Applications/Utilities folder) to verify the setup:
    First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
    Next, select the line for your TM partition (indented, with the name). Towards the bottom, the *Format must* be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
    Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
    Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* should be GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be +Apple Partition Map+ for a PPC Mac. If this is wrong, you must completely erase the disk and reformat it. See item 5 of the Frequently Asked Questions *User Tip* at the top of this forum.
    Once you're sure your disk/partition is formatted correctly, if your backups still fail, continue to the next item:
    |
    _*C2. Other Backup Fails*_
    If this is your first backup, or the first one to a new external drive/partition, the most common cause is the drive not being formatted properly (even, on occasion, when Time Machine formatted it for you!). So if there's any question, see the previous item.
    If a backup fails, note any message it sends, and start with this Apple article: Troubleshooting Time Machine backup issues. It includes a wide range of problems, and has links to many other Apple technical articles.
    Those messages/problems are not repeated here, except for a couple that Apple doesn't cover completely.
    If that doesn't solve your problem, get the Time Machine Buddy messages (see #A1). Many of the common and normal messages are detailed in item 7 of the Frequently Asked Questions *User Tip* at the top of this forum. Only the ones that might indicate a problem are repeated here.
    *Messages that might indicate trouble:*
    Event store UUIDs don't match naming your internal HD (or any other drive/partition being backed-up). TM can't be sure the OSX internal log of file changes that it normally uses is correct. This is seen on your first backup of a disk, or after an improper shutdown, a full restore, certain hardware repairs, removal of certain exclusions, a large volume of changes (such as an OSX update), or many days without a successful backup. It may cause a lengthy backup, so if you see it frequently, without a good reason, you need to figure out why.
    Event store UUIDs don't match naming an external drive/partition. TM isn't sure that everything on it is what TM expects. This may be because the drive was disconnected improperly, or it doesn't appear to be the drive TM expects. Again, if you see this without a good reason, investigate.
    . . . node requires deep traversal. Instead of the log of file changes TM normally uses, it must examine every file and folder on the named drive/partition, and compare it to the last backup, to figure out what's changed and needs to be backed-up. Obviously, this is a lengthy procedure; and especially lengthy if you're doing wireless backups. As this is part of the "Preparing" phase, you may not see any more messages for quite a while. Try not to interrupt the backup, as this must be done again (and again) until a backup is completed successfully.
    Error: backup disk is full - all nn possible backups were removed, but space is still needed. This is pretty clear. TM deleted as many old backups as it could (and they're all listed in the first failed backup's messages). See item #C4.
    Bulk setting Spotlight attributes failed. or Waiting for index to be ready. There may be a problem with your TM drive, or difficulty communicating with it. See item #D2.
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    These may indicate a problem with the first file referenced. See the next item.
    If you don't see any of these messages, or nothing here seems to help, copy and post all the messages from the failed backup in a new thread here, along with specifics of your set up.
    |
    _*C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*_
    Occasionally, backups will fail with this message for no good reason, and the next one will complete normally. So either wait for the next scheduled backup, or do a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock. If that backup completes normally, there's no real problem.
    If the next one fails also, then there most likely is something wrong -- the question is, what?
    Get the Time Machine Buddy messages (see #A1). Look for the message(s) about a file that couldn't be copied, such as:
    |
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    |
    If you're not familiar with file "paths," it can be a little difficult to read these messages. They look something like this:
    /Users/<Name>/iMovie Events.localized/clip-2008-04-02.mov to /Volumes/TM Backups/ . . . etc.
    The end of the file in question is usually indicated either by " to " or just a comma and space before the next one.
    If it's a file you're sure you don't need, you can delete it. If not, for now, don't touch it. Instead, exclude it from TM:
    Go to TM's Preferences and click Options.
    In the next panel, click the plus sign at the bottom.
    In the sidebar of the next panel, select your computer name, internal HD, or home folder as necessary; then navigate to the file listed, or, perhaps, it's enclosing folder.
    Select it, click Exclude, then Done.
    Then do a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock.
    If the backup runs ok, then you need to figure out what's wrong with that file.
    If it fails again, check it's messages. If it's the *exact same* file, you didn't exclude the right one, or you need to do a "full reset" (see item #B3).
    If you get the same message for a different file, you may need stronger stuff:
    a. Exclude your TM disk from any anti-virus scanning.
    b. Also exclude it from Spotlight indexing, via System Preferences > Spotlight > Privacy.
    c. Do a +*Repair Disk*+ (not permissions) on your TM drive/partition, via Disk Utility (in your Applications/Utilities folder).
    d. If the original file is on an external disk, do a +*Repair Disk*+ on it, too.
    e. If the original file is on your internal HD, do a +*Verify Disk*+ (not permissions) on it. If that reports errors, you'll have to boot from your Leopard Install disc and use it's copy of Disk Utility to repair it:
    1. Insert your Leopard Install disc and restart while holding down the "C" key. This will take a few moments.
    2. Select your language when prompted.
    3. On the next screen select Utilities in the Menubar, then +*Disk Utility.*+
    4. Do a +*Repair Disk*+ on your internal HD. If it doesn't fix all the errors, run it again (and again), until it either fixes them all, or can't fix any more.
    5. Reboot normally.
    If all else fails, you may have a problem with the drive, or communicating with it. Try all the suggestions in #D2 below.
    |
    _*C4. "This backup is too large"*_
    |
    For one reason or another, TM is out of room on the backup disk/partition. When it's space gets near full, TM will normally delete as many old and expired backups as it can to make room for new ones.
    There are some backups that Time Machine *will not delete,* however. It won't delete the most recent backup, or any backups from a different Mac. Sometimes TM will start a new "sequence" of backups, as if you had a different Mac, and it won't delete any from the prior sequence, either.
    Also note that, although it deletes a backup, it doesn't necessarily delete it's copies of all the items that were on that backup. It only deletes it's copies of items that no longer exist on any other backup. Thus you won't lose the backup of anything that's currently on your system.
    When this happens, you have a few options:
    1. De-select the +*Warn when old backups are deleted*+ option in TM Preferences > Options, and try again.
    2. Erase the TM disk/partition and let TM start over, with a new, full backup of your entire system.
    3. Manually delete some old backups via the TM interface (do not use the Finder!). This is rather tedious, as it must be done one at a time, and there's no way to tell in advance which ones will be quick (and not gain much room) and which will take a long time and recover more space. See item #12 of the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    4. Get a different disk/partition for your Time Machine backups. Then either:
    Give it a different name, and use the +Change Disk+ button in TM Preferences to select it. Let TM start fresh on the new drive/partition, with a full backup of your entire system. Keep the old drive/partition for a while (disconnected) until you're sure everything is working and you don't need the old backups anymore.
    Or, duplicate the current backups to it via the Restore tab of Disk Utility in your Applications/Utilities folder. Note that you must duplicate an entire disk/partition to another entire disk/partition. See item #18 in the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    |
    _*C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <Name>"*_
    |
    Open the Terminal app (in your Applications/Utilities folder).
    Be extremely careful when using Terminal. It is a direct interface into UNIX, the underpinning of OSX. Unlike the Finder, there are few protections against making a mistake, which can cause untold damage.
    In Terminal, the prompt looks like this: user-xxxxxx:~ <your name>$
    (where <your name> is your short user name). It's followed by a non-blinking block cursor (unless it's been changed via Terminal > Preferences).
    At the prompt, type the following exactly as shown in the example, substituting the name of your TM drive exactly, including any spaces, between the quotes; and the string of numbers & letters from the message where the series of x's are (keep the dot):
    <pre> *sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx*</pre>
    example: *sudo chmod 644 /volumes/"TM Backups"/.0a1b2c3d4e5f*
    Press Return. You'll get some warnings and a request for your Administrator's password. Type it in (it won't be displayed) and press Return again.
    Then try a +*Back Up Now*+ from the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your dock.
    |
    _*C6. The backup volume is read only*_
    First, follow the Apple article mentioned above: Troubleshooting Time Machine backup issues.
    If that doesn't correct it,
    If you only have a partial backup, or don't need the ones you've done, the simplest thing to do is just erase the disk/partition with Disk Utility (in your Applications/Utilities folder).
    If you don't want to erase it, here's a workaround:
    First, you need to find the name of the hidden file that's causing the problem. If the Time Machine Buddy (see #A1) shows a message like the one in item #C5, follow the instructions there.
    If not, use the TinkerTool app (see #A3) to show hidden files.
    In a Finder window, select your Time Machine drive/partition. The very first file shown should have a name consisting of a period (dot) followed by 12 numbers and/or letters. (This is your Mac's Ethernet address). Copy or make a note of it.
    Then follow the rest of the instructions in item #C5.
    |
    _*C7. "Error (12): Link of previous volume failed."*_
    |
    This usually happens when you replaced a drive with a different one, but with the same name as the original.
    Because of the way Time Machine keeps track of drives, at one point it thinks they're the same, but later on realizes they aren't.
    Either rename the drive (append "_2" or something), or delete all previous backups of it, via the instructions in item 12 of the Frequently Asked Questions *User Tip* at the top of this forum.
    And note that TM will probably do a full backup of the drive. If there isn't much space on your TM drive/partition, see #C4. You may need to do item 2, 3, or 4 listed there.
    |
    _*C8. Backup fails after Logic Board replacement*_
    The logic board contains your Ethernet "Mac Address", which is a unique number that TM uses to be sure it knows which Mac is which. So, to TM, it is now a *different computer.*
    This is so it can keep each Mac's backups separate (you can back multiple Macs up to the same external disk or Time Capsule). It does this by putting a hidden file containing this address on the TM disk.
    There is a fairly elaborate way to attempt to persuade TM that the existing backups really are for your "new" Mac: http://www.macosxhints.com/article.php?story=20080128003716101
    It is very easy to make an error with Terminal, get no error message, and have it not work, or worse, so try it at your own risk.
    But there is an alternative: hold down the Option key while selecting the TM icon in your Menubar, or control-click (right-click) the TM icon in your Dock. Then use the (badly named) +*Browse Other Time Machine Disks*+ option. It will take you into the normal TM interface where you can see and restore from the old set of backups.
    Even if you're successful with the Terminal work, your first backup with the new logic board may be a full one -- every file and folder on your system. If TM decides to do that, you cannot prevent it.
    So if your TM disk/partition isn't over twice the size of the data it's backing-up, your best bet may be to just erase it with Disk Utility (in your Applications/Utilities folder) and let TM start over.
    |
    _*C9. "The back-up disk image could not be created."*_
    |
    If you get this message when backing-up wirelessly, check your +*System Name*+ at the top of the System Preferences > Sharing panel.
    It must not be blank; it should not be more than 25 characters long; and you should avoid punctuation (except periods and underscores), and unusual characters.
    |
    _*C10. Error: (-50) Creating directory*_
    |
    This may indicate a problem with your TM drive. Use Disk Utility (in your Applications/Utilities folder) to do a +*Repair Disk*+ (not permissions) on it. If any errors are found that Disk Utility can't fix, run it again (and again) until they're all fixed or it can't fix any more.
    If no errors are found, or they're all found and fixed, but you still get the message, try a "full reset" as in item #B3.
    If Disk Utility can't fix them all, the disk may be failing. Copy the messages from the last run of Disk Utility and post them in a new thread in this forum for advice.
    |
    _*C11. Drive does not appear to be the correct backup volume for this computer(Cookies do not match)*_
    |
    If this happens after getting a new Logic Board, see item #C8.
    This also happens on occasion after switching a TM drive from one Mac to another, erasing your TM disk/partition, or attaching a new TM drive with the same name as an old one.
    You can usually fix this by simply re-selecting your TM drive in TM Preferences > Change Disk.
    If that doesn't help, try a complete reset. See item #B3.
    |
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    _*D1. Stuck in Preparing*_
    |
    See this Apple Support document: Time Machine may display "Preparing" for a longer time
    Try not to interrupt the backup, as this procedure must be done again (and again) until a backup is completed successfully.
    Also see the next topic:
    |
    _*D2. Backup is slow or "hung"*_
    |
    Get the Time Machine Buddy messages (see #A1).
    If it shows Event store UUIDs don't match
    and/or . . . node requires deep traversal, it may not be "hung" at all. See item #C2.
    If it shows Waiting for index to be ready and/or Bulk setting Spotlight attributes failed messages, there may be a problem with your TM drive, or difficulty communicating with it. Unfortunately, any of a number of things may cause this. The list of things to try is:
    1. Exclude your TM disk/partition from any anti-virus scanning.
    2. Exclude it from Spotlight (System Preferences > Spotlight > Privacy).
    _*If backing up to a Time Capsule or External Disk connected to an Airport Extreme:*_
    3. Check your System Name via System Preferences > Sharing. It it's blank, that's likely the problem. If it's over 26 characters long, trim it. If it has any unusual characters, try removing them.
    4. Try moving the TC or AEBS and Mac closer together.
    5. Look for interference with another wireless device. Turn anything else off, or move it farther away.
    6. Try repairing the Sparse Bundle with Disk Utility (in your Applications/Utilities folder). Mount the Sparse Bundle, then drag it into the Disk Utility sidebar, then use +*Repair Disk*+ (not permissions).
    _*If backing up to an External hard drive:*_
    7. Do a +*Repair Disk*+ (not permissions) on it via Disk Utility (in your Applications/Utilities folder).
    8. At least temporarily, de-select +*Put the hard disk(s) to sleep ...+* in System Preferences > Energy Saver.
    9. Be sure it's connected directly to your Mac (no hubs, and not the USB port on the keyboard).
    10. Try different port(s), cable(s).
    11. See if your drive has an automatic sleep or "spin down" feature you can disable.
    12. Check the maker's web site (support or forum) for any updates.
    If nothing helps, your drive may be failing.
    |
    _*D3. TM is doing a full backup for no good reason*_
    Time Machine may do a full backup after any of the following:
    Using a new disk or partition for backups (always).
    A full restore (probably).
    Some hardware repairs, especially a new internal hard drive (probably) or logic board (always, but see #C8).
    Changing your computer's name via System Preferences > Sharing (probably).
    Renaming a disk/partition that's being backed-up (probably).
    Going several days without a backup (probably; also seems to depend on the volume of changes).
    Exactly why it doesn't always do full backups for the items marked "probably" is not clear, so to be safe, assume it will.
    |
    _*D4. My backups seem too large*_
    |
    Time Machine may be doing a full backup of your entire system. See item #D3.
    Doing an OSX update can cause a large backup, as it may add or update several thousand files.
    Removing exclusions, such as your top-level System and/or Library folders, can be sizeable.
    Renaming a folder or disk drive, or moving a file or folder, will cause the entire item moved or renamed to be backed-up. This includes all files and sub-folders in a moved or renamed folder.
    There are some OSX features and 3rd-party applications that cause large Time Machine backups. Common ones are FileVault, vmWare Fusion, Parallels Desktop, Entourage, and Thunderbird. Any application that uses a single large file or database may do this. See item 9 of the Frequently Asked Questions post.
    You can use the +Time Tracker+ app (see item #A2) to see just what was copied on any particular backup. There may be ways to minimize the size of such backups; search and/or post in this forum for help.
    |
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    _*E1. Backups were deleted unexpectedly*_
    |
    Time Machine manages it's space for you, automatically. When it's drive/partition gets near full, it will begin deleting your oldest backups to make room for new ones. See item #C4 for more info and your options.
    Usually when this happens unexpectedly, it's because TM has done a new full backup, which of course requires a lot of space. See item #D3 for the common reasons.
    If in doubt, get the widget messages (see #A1). They'll show how much it was trying to back up. See item #7 of the Frequently Asked Questions *User Tip* at the top of this forum for explanation of those messages.
    |
    _*E2. I can't see some backups*_
    |
    TM keeps the backups for each Mac separate, and normally only shows the ones for the Mac it's running on, even if there are other Macs' backups on its disk/partition.
    Also, sometimes TM will start a new "sequence" of backups, as if they were from a different Mac. See item #D3.
    To see these "other" backups, you need the (badly named) +*Browse Other Time Machine Disks*+ option. It's available by holding down the Option key while selecting the TM icon in your Menubar, or by control-clicking (right-clicking) the TM icon in your Dock.
    You'll see a selection screen showing all the disks/partitions that have TM backups on them. Select the one you want, and you'll be taken to the normal TM "Star Wars" interface, where you should see all the backups on that disk/partition.
    Note that, unfortunately, you cannot merge or combine two different "sequences" of backups.
    Also note that you cannot use the normal Restore button at the bottom of the screen to restore items, since they're from a different Mac. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
    |
    _*E3. I can't see backups for a disk/partition that's no longer connected*_
    |
    Open a Finder window and press ShiftCmdC (or select your computer name in the Finder Sidebar).
    Then either +*Enter Time Machine*+ or +*Browse Other Time Machine Disks*+ (see #E2).
    On the first Finder window in the "cascade," labelled +*Today (Now),+* you'll see all the volumes currently attached to your Mac.
    Select the Finder window for any backup, and you'll see a folder for each drive/volume that was backed-up, including any that are no longer connected. Navigate from there to whatever you're looking for.
    |
    _*E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*_
    |
    Do a +*Repair Disk*+ (not permissions) on your TM drive, via Disk Utility (in your Applications/Utilities folder).
    Re-select your TM drive via TM Preferences > Change Disk.
    If you're using Spaces, try disabling it, at least temporarily.
    If you have any sort of video out cable, especially HDMI, try disconnecting it, at least temporarily.
    Do a "complete reset" of TM, as in item #B3.

    This article provides some troubleshooting tips for common Time Machine errors and problems.
    It does not cover problems specific to Time Capsule or other wireless backups. See the Airport and Time Capsule forum, in the Digital Life section.
    Nor does it include general information about Time Machine. For those, see the Frequently Asked Questions *User Tip* at the top of this forum.
    _*C o n t e n t s*_
    |
    *Section A. _TOOLS and PROCEDURES YOU MAY NEED*_
    |
    *A1. Time Machine Buddy widget*
    *A2. Time Tracker*
    *A3. Tinker Tool*
    *A4. Full Reset of Time Machine*
    *A5. How to do a Repair or +Verify Disk+*
    *Section B. _SET - UP PROBLEMS*_
    |
    *B1. I can't select my drive for use with Time Machine*
    *B2. The +Change Disk+ button doesn't work*
    *B3. No last or oldest backup date shown*
    *B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*
    *Section C. _BACKUP FAILURES*_
    |
    *C1. Initial Backup Failed*
    *C2. Other Backup Fails*
    *C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*
    *C4. "This backup is too large"*
    *C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <name of TM drive>"*
    *C6. The backup volume is read only*
    *C7. "Error (12): Link of previous volume failed."*
    *C8. Backup fails after Logic Board replacement*
    *C9. "The back-up disk image could not be created."*
    *C10. Error: (-50) Creating directory*
    *C11. Drive does not appear to be the correct backup volume for this computer (Cookies do not match)*
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    |
    *D1. Stuck in "Preparing" or "Calculating changes"*
    *D2. Backup is Slow or "hung"*
    *D3. TM is doing a full backup for no good reason*
    *D4. My backups seem too large*
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    |
    *E1. Backups were deleted unexpectedly*
    *E2. I can't see some backups*
    *E3. I can't see or restore from backups for a disk/partition that's no longer connected*
    *E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*
    *Section A. _TOOLS and PROCEDURES YOU MAY NEED*_
    There are some free 3rd-party tools that may be useful in diagnosing problems with Time Machine. You'll see references to them in several places below.
    _*A1. Time Machine Buddy widget*_
    |
    Click here to download the +*Time Machine Buddy*+ widget.
    It shows the messages from your logs for one TM backup run at a time, in a small window. An explanation of some of the error messages is in section #C2 below. Other common messages are explained in item #7 of the Frequently Asked Questions *User Tip* at the top of this forum.
    You can copy these messages by selecting them via dragging your mouse over them (be sure to get them all, as they may overflow the small window), then pressing Cmd+C. This copies them to your "clipboard," so you can post them in a thread here (via Cmd+V) to get help diagnosing a problem. (Occasionally, the widget won't let you copy while a backup is running.)
    If the message area is blank, but you know there were backups, your user account may not have permission to view your logs. Try signing-on as an Admin User. You can grant "read" rights to the folder /private/var/log and it's contents for the other user.
    Note that the widget may only let you look back a few days. If you need to look back farther, you'll need the Console app (in your Applications/Utilities folder) to look at your older system logs (named +*system.log.1.bz2, system.log.2.bz2,+* etc). Click +*Show Log List*+ in the toolbar, then navigate to the desired logs in the sidebar that opens up. You can select only the messages from TM backups by typing backupd in the Filter box in the toolbar.
    |
    _*A2. Time Tracker*_
    |
    Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). This can help you figure out just what is (or is not) being backed-up.
    |
    _*A3. Tinker Tool*_
    |
    Click here to download the +*Tinker Tool*+ app. It allows you to change the Finder to show hidden files (among many other things). Select the first option under Finder, then click +Relaunch Finder+ at the bottom. Reverse this when done.
    Do not use any of the other options unless you know the possible consequences.
    |
    _*A4. Full Reset of Time Machine*_
    |
    a. Go to TM Preferences, turn TM Off, de-select the drive (select "none"), and click the Options button. Note any exclusions in the +Do Not Back Up+ box, and other option(s) on that panel. Then quit System Preferences.
    b. Eject, disconnect, and power-off the drive for a few moments, then reconnect it.
    c. Delete the file /Library/Preferences/com.apple.TimeMachine.plist (in your top-level Library folder, not your home folder).
    d. Go back to TM Preferences, re-select your drive, re-enter any exclusions and other options.
    e. Do a +*Back Up Now*+ or wait for the next scheduled backup.
    |
    _*A5. How to do a Repair or +Verify Disk+*_
    |
    This will Repair or Verify the +File System+ on a disk, partition, or sparse bundle (not the actual hardware). Use the +*Disk Utility+* app, in your Applications/Utilities folder. Do this when TM backups are turned-off, or at least not running.
    To Repair an *external disk attached to an Airport Extreme,* disconnect it from the Airport, connect it directly to your Mac and select it in the Disk Utility Sidebar.
    To Repair an external or *internal Time Machine* disk/partition, select it in the Disk Utility Sidebar.
    To Repair the *sparse bundle* on a Time Capsule, connect via an Ethernet cable if you can; it will be much faster. Then mount the sparse bundle by opening the TC in the Finder and double-clicking on the sparse bundle. Drag the sparse bundle into Disk Utility's sidebar and select it.
    With the desired partition or sparse bundle selected, click the +*Repair Disk+* (not permissions) button. This may take a while, especially on a Time Capsule. If errors are found, but not all of them were repaired, run the +*Repair Disk+* again, and again, until it either fixes all the errors or can't fix any more.
    To Verify your internal (boot) drive/partition (since you can't Repair the one you're running from), select it in Disk Utility's sidebar and click the +*Verify Disk+* (not permissions) button. If it shows errors, you'll need to fix them via this procedure:
    1. Insert your Leopard/Snow Leopard Install disc and restart while holding down the "C" key. This will take a few moments.
    2. Select your language when prompted.
    3. On the next screen, select Utilities in the Menubar, then +*Disk Utility.*+
    4. Do a +*Repair Disk*+ (not permissions) on your internal HD. If it doesn't fix all the errors, run it again (and again), until it either fixes them all, or can't fix any more.
    5. Reboot normally.
    |
    *Section B. _SET - UP PROBLEMS*_
    _*B1. I can't select my drive for use with Time Machine*_
    If the drive/partition you want to use for TM backups doesn't appear in the list when you select TM Preferences > Change Disk, it's probably not formatted correctly. See item #C1 for help determining whether it's right, and how to fix it.
    |
    _*B2. The +Change Disk+ button doesn't work*_
    If the +*Change Disk*+ button in TM Preferences doesn't do anything, try turning-off the +*Back To My Mac*+ application temporarily.
    |
    _*B3. No last or oldest backup date shown*_
    |
    If these dates don't appear when selecting the TM icon in your Menubar, or TM Preferences, try the following:
    1. Do a +*Back Up Now.*+ That will often recover the info.
    2. De-select your TM Drive via TM Preferences (select "none"), quit System Preferences, then re-select it and do a +*Back Up Now.*+
    3. A Log Out or Restart may fix it.
    4. If they're still not shown, try a Full Reset (see #A4).
    |
    _*B4. Wrong icon shown for TM drive/partition on desktop and/or Finder sidebar*_
    |
    Try de-selecting, then re-selecting the "Show" option in Finder > Preferences > General and/or Sidebar.
    Try a "Full Reset" as in item #A4.
    |
    *Section C. _BACKUP FAILURES*_
    _*C1. Initial Backup Failed*_
    The most common cause is the TM drive (but not a Time Capsule) not being formatted correctly (even, on occasion, if TM formatted it!). Use Disk Utility (in your Applications/Utilities folder) to verify the setup:
    First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be +Mac OS Extended (Journaled),+ although it might be +Mac OS Extended (Case-sensitive, Journaled).+
    Next, select the line for your TM partition (indented, with the name). Towards the bottom, the *Format must* be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
    Sometimes when TM formats a drive for you automatically, it sets it to +Mac OS Extended (Case-sensitive, Journaled).+ Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
    Last, select the top line of the TM drive (with the make and size). Towards the bottom, the *Partition Map Scheme* must be either GUID (preferred) or +Apple Partition Map+ for an Intel Mac. It must be either +Apple Partition Map+ (preferred) or GUID for a PPC Mac. If this is wrong, you must completely erase the disk and reformat it. See item 5 of the Frequently Asked Questions *User Tip* at the top of this forum.
    Once you're sure your disk/partition is formatted correctly, if your backups still fail, continue to the next item:
    |
    _*C2. Other Backup Fails*_
    If this is your first backup, or the first one to a new external drive/partition, the most common cause is the drive not being formatted properly (even, on occasion, when Time Machine formatted it for you!). So if there's any question, see the previous item.
    If a backup fails, note any message it sends, and start with this Apple article: Troubleshooting Time Machine backup issues. It includes a wide range of problems, and has links to many other Apple technical articles.
    Those messages/problems are not repeated here, except for a couple that Apple doesn't cover completely.
    If that doesn't solve your problem, get the Time Machine Buddy messages (see #A1). Many of the common and normal messages are detailed in item 7 of the Frequently Asked Questions *User Tip* at the top of this forum. Only the ones that might indicate a problem are repeated here.
    *Messages that might indicate trouble:*
    Event store UUIDs don't match naming your internal HD (or any other drive/partition being backed-up). TM can't be sure the OSX internal log of file changes that it normally uses is correct. This is seen on your first backup of a disk, or after an improper shutdown, a full restore, certain hardware repairs, removal of certain exclusions, a large volume of changes (such as an OSX update), or many days without a successful backup. It may cause a lengthy backup, so if you see it frequently, without a good reason, you need to figure out why.
    Event store UUIDs don't match naming an external drive/partition. TM isn't sure that everything on it is what TM expects. This may be because the drive was disconnected improperly, or it doesn't appear to be the drive TM expects. Again, if you see this without a good reason, investigate.
    . . . node requires deep traversal. Instead of the log of file changes TM normally uses, it must examine every file and folder on the named drive/partition, and compare it to the last backup, to figure out what's changed and needs to be backed-up. Obviously, this is a lengthy procedure; and especially lengthy if you're doing wireless backups. As this is part of the "Preparing" (Leopard) or "Calculating changes" (Snow Leopard) phase, you may not see any more messages for quite a while. Try not to interrupt the backup, as this must be done again (and again) until a backup is completed successfully.
    Error: backup disk is full - all nn possible backups were removed, but space is still needed. This is pretty clear. TM deleted as many old backups as it could (and they're all listed in the first failed backup's messages). See item #C4.
    Bulk setting Spotlight attributes failed. or Waiting for index to be ready. There may be a problem with your TM drive, or difficulty communicating with it. See item #D2.
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    These may indicate a problem with the first file referenced. See the next item.
    If you don't see any of these messages, or nothing here seems to help, copy and post all the messages from the failed backup in a new thread here, along with specifics of your set up.
    |
    _*C3. "An error occurred while copying files to the backup volume"* or *"Aborting backup because indexing a file failed"*_
    Occasionally, backups will fail with this message for no good reason, and the next one will complete normally. So either wait for the next scheduled backup, or do a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock. If that backup completes normally, there's no real problem.
    If the next one fails also, then there most likely is something wrong -- the question is, what?
    Get the Time Machine Buddy messages (see #A1). Look for the message(s) about a file that couldn't be copied, such as:
    |
    Error: (-36) SrcErr:YES Copying {a file path} to {"null" or another file path}
    or Indexing a file failed. Returned -12 for: {a file path}, {another file path}
    |
    If you're not familiar with file "paths," it can be a little difficult to read these messages. They look something like this:
    /Users/<Name>/iMovie Events.localized/clip-2008-04-02.mov to /Volumes/TM Backups/ . . . etc.
    The end of the file in question is usually indicated either by " to " or just a comma and space before the next one.
    If it's a file you're sure you don't need, you can delete it. If not, for now, don't touch it. Instead, exclude it from TM:
    Go to TM's Preferences and click Options.
    In the next panel, click the plus sign at the bottom.
    In the sidebar of the next panel, select your computer name, internal HD, or home folder as necessary; then navigate to the file listed, or, perhaps, it's enclosing folder.
    Select it, click Exclude, then Done.
    Then do a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock.
    If the backup runs ok, then you need to figure out what's wrong with that file.
    If it fails again, check it's messages. If it's the *exact same* file, you didn't exclude the right one, or you need to do a "full reset" (see item #A4).
    If you get the same message for a different file, you may need stronger stuff:
    a. Exclude your TM disk from any anti-virus scanning.
    b. Also exclude it from Spotlight indexing, via System Preferences > Spotlight > Privacy.
    c. Do a +*Repair Disk*+ on your TM drive/partition. See #A5 above.
    d. If the original file is on an external disk, do a +*Repair Disk*+ on it, too.
    e. If the original file is on your internal HD (your boot drive), do a +*Verify Disk*+ on it. See #A5 above.
    If all else fails, you may have a problem with the drive, or communicating with it. Try all the suggestions in #D2 below.
    |
    _*C4. "This backup is too large"*_
    |
    For one reason or another, TM is out of room on the backup disk/partition. When it's space gets near full, TM will normally delete as many old and expired backups as it can to make room for new ones.
    There are some backups that Time Machine *will not delete,* however. It won't delete the last remaining backup, or any backups from a different Mac. Sometimes TM will start a new "sequence" of backups, as if you had a different Mac, and it may not delete any from the prior sequence, either.
    Also note that, although it deletes a backup, it doesn't necessarily delete it's copies of all the items that were on that backup. It only deletes it's copies of items that no longer exist on any other backup. Thus you won't lose the backup of anything that's currently on your system.
    When this happens, you have a few options:
    1. De-select the +*Warn when old backups are deleted*+ option in TM Preferences > Options, and try again.
    2. Erase the TM disk/partition with Disk Utility (in Applications/Utilities) and let TM start over with a new full backup.
    3. Manually delete some old backups via the TM interface (do not use the Finder!). This is rather tedious, as it must be done one at a time, and there's no way to tell in advance which ones will be quick (and not gain much room) and which will take a long time and recover more space. See item #12 of the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    4. Get a different disk/partition for your Time Machine backups. Then either:
    Give it a different name, and use the +Change Disk+ button in TM Preferences to select it. Let TM start fresh on the new drive/partition, with a full backup of your entire system. Keep the old drive/partition for a while (disconnected) until you're sure everything is working and you don't need the old backups anymore.
    Or, duplicate the current backups to it via the Restore tab of Disk Utility in your Applications/Utilities folder (in Snow Leopard only, you can copy the Backups.backupdb folder via the Finder). Note that you must duplicate an entire disk/partition to another entire disk/partition. See item #18 in the Frequently Asked Questions *User Tip* at the top of this forum for detailed instructions.
    |
    _*C5. "You do not have appropriate access privileges to save file “.<nnnnnnn>” in folder <name of TM Drive>"*_
    |
    Open the Terminal app (in your Applications/Utilities folder).
    Be extremely careful when using Terminal. It is a direct interface into UNIX, the underpinning of OSX. Unlike the Finder, there are few protections against making a mistake, which can cause untold damage.
    In Terminal, the prompt looks like this: user-xxxxxx:~ <your name>$
    (where <your name> is your short user name). It's followed by a non-blinking block cursor (unless it's been changed via Terminal > Preferences).
    At the prompt, type the following exactly as shown in the example, substituting the name of your TM drive exactly, including any spaces, between the quotes; and the string of numbers & letters from the message where the series of x's are (keep the dot):
    <pre> *sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx*</pre>
    example: *sudo chmod 644 /volumes/"TM Backups"/.0a1b2c3d4e5f*
    Press Return. You'll get some warnings and a request for your Administrator's password. Type it in (it won't be displayed) and press Return again.
    Then try a +*Back Up Now*+ from the TM icon in your Menubar, or by right-clicking the TM icon in your dock.
    |
    _*C6. The backup volume is read only*_
    First, follow the Apple article mentioned above: Troubleshooting Time Machine backup issues.
    If that doesn't correct it,
    If you only have a partial backup, or don't need the ones you've done, the simplest thing to do is just erase the disk/partition with Disk Utility (in your Applications/Utilities folder).
    If you don't want to erase it, here's a workaround:
    First, you need to find the name of the hidden file that's causing the problem. If the Time Machine Buddy (see #A1) shows a message like the one in item #C5, follow the instructions there.
    If not, use the TinkerTool app (see #A3) to show hidden files.
    In a Finder window, select your Time Machine drive/partition. The very first file shown should have a name consisting of a period (dot) followed by 12 numbers and/or letters. (This is your Mac's Ethernet Address). Copy or make a note of it.
    Then follow the rest of the instructions in item #C5.
    |
    _*C7. "Error (12): Link of previous volume failed."*_
    |
    This usually happens when you replaced a drive with a different one, but with the same name as the original.
    Because of the way Time Machine keeps track of drives, at one point it thinks they're the same, but later on realizes they aren't.
    Either rename the drive (append "_2" or something), or delete all previous backups of it, via the instructions in item 12 of the Frequently Asked Questions *User Tip* at the top of this forum.
    And note that TM will probably do a full backup of the drive. If there isn't much space on your TM drive/partition, see #C4. You may need to do item 2, 3, or 4 listed there.
    |
    _*C8. Backup fails after Logic Board replacement*_
    The logic board contains your Ethernet "Mac Address", which is a unique number that TM uses to be sure it knows which Mac is which. So, to TM, it is now a *different computer.*
    This is so it can keep each Mac's backups separate (you can back multiple Macs up to the same external disk or Time Capsule). It does this by putting a hidden file containing this address on the TM disk.
    There is a fairly elaborate way to attempt to persuade TM that the existing backups really are for your "new" Mac: http://www.macosxhints.com/article.php?story=20080128003716101
    It is very easy to make an error with Terminal, get no error message, and have it not work, or worse, so try it at your own risk.
    But there is an alternative: hold down the Option key while selecting the TM icon in your Menubar, or right-click the TM icon in your Dock. Then use the (badly named) +*Browse Other Time Machine Disks*+ option. It will take you into the normal TM interface where you can see and restore from the old set of backups.
    Even if you're successful with the Terminal work, your first backup with the new logic board may be a full one -- every file and folder on your system. If TM decides to do that, you cannot prevent it.
    So if your TM disk/partition isn't over twice the size of the data it's backing-up, your best bet may be to just erase it with Disk Utility (in your Applications/Utilities folder) and let TM start over.
    |
    _*C9. "The back-up disk image could not be created."*_
    |
    If you get this message when backing-up wirelessly, check your +*System Name*+ at the top of the System Preferences > Sharing panel.
    It must not be blank; it should not be more than 25 characters long; and you should avoid punctuation (except periods and underscores), and unusual characters.
    If that doesn't help, apply the same rules to the name of your Time Capsule.
    |
    _*C10. Error: (-50) Creating directory*_
    |
    This may indicate a problem with your TM drive. Do a +*Repair Disk*+ on it. See #A5 above.
    If no errors are found, or they're all found and fixed, but you still get the message, try a "full reset" as in item #A4.
    If Disk Utility can't fix them all, the disk may be failing. Copy the messages from the last run of Disk Utility and post them in a new thread in this forum for advice.
    |
    _*C11. Drive does not appear to be the correct backup volume for this computer(Cookies do not match)*_
    |
    If this happens after getting a new Logic Board, see item #C8.
    This also happens on occasion after switching a TM drive from one Mac to another, erasing your TM disk/partition, or attaching a new TM drive with the same name as an old one.
    You can usually fix this by simply re-selecting your TM drive in TM Preferences > Change Disk.
    If that doesn't help, try a full reset. See item #A4.
    |
    *Section D. _OTHER PROBLEMS RUNNING BACKUPS*_
    _*D1. Stuck in "Preparing" or "Calculating changes"*_
    |
    See this Apple Support document: Time Machine may display "Preparing" for a longer time
    Try not to interrupt the backup, as this procedure must be done again (and again) until a backup is completed successfully.
    Also see the next topic:
    |
    _*D2. Backup is slow or "hung"*_
    |
    If this is your first backup under Snow Leopard after updating from Leopard, try cancelling the backup, doing a Restart, and trying again.
    Otherwise, get the Time Machine Buddy messages (see #A1).
    If it shows Event store UUIDs don't match
    and/or . . . node requires deep traversal, it may not be "hung" at all. See item #C2.
    If it shows Waiting for index to be ready and/or Bulk setting Spotlight attributes failed messages, there may be a problem with your TM drive, or difficulty communicating with it. Unfortunately, any of a number of things may cause this. The list of things to try is:
    1. Exclude your TM disk/partition from any anti-virus scanning.
    2. Exclude it from Spotlight (System Preferences > Spotlight > Privacy).
    _*If backing up to a Time Capsule or External Disk connected to an Airport Extreme:*_
    3. Check your System Name via System Preferences > Sharing. It it's blank, that's likely the problem. If it's over 26 characters long, trim it. If it has any unusual characters, try removing them. Remove any punctuation and spaces. Do the same with the Time Capsule or Airport Extreme name.
    4. Try moving the TC or AEBS and Mac closer together.
    5. Look for interference with another wireless device. Turn anything else off, or move it farther away.
    6. Try repairing the TC's Sparse Bundle or AEBS drive's TM disk/partition. See #A5 above.
    _*If backing up to an External hard drive:*_
    7. Do a +*Repair Disk*+ on it. See #A5 above.
    8. At least temporarily, de-select +*Put the hard disk(s) to sleep ...+* in System Preferences > Energy Saver.
    9. Be sure it's connected directly to your Mac (no hubs, and not the USB port on the keyboard, as some are USB 1.0).
    10. Try different port(s), cable(s).
    11. See if your drive has an automatic sleep or "spin down" feature you can disable.
    12. Check the maker's web site (support or forum) for any driver or firmware updates.
    If nothing helps, your drive may be failing (they all do, sooner or later).
    |
    _*D3. TM is doing a full backup for no good reason*_
    If this is your first backup on Snow Leopard after upgrading from Leopard, try cancelling the backup, doing a Restart, and trying again.
    Time Machine may do a full backup after any of the following:
    Using a new disk or partition for backups (always).
    A full restore (probably).
    Some hardware repairs, especially a new internal hard drive (probably) or logic board (always, but see #C8).
    Changing your computer's name via System Preferences > Sharing (maybe).
    Renaming a disk/partition that's being backed-up (probably).
    Going several days without a backup (probably; also seems to depend on the volume of changes).
    Exactly why it doesn't always do full backups for the items marked "probably" is not clear, so to be safe, assume it will.
    |
    _*D4. My backups seem too large*_
    |
    Time Machine may be doing a full backup of your entire system. See #D3.
    Doing an OSX update can cause a large backup, as it may add or update several thousand files.
    Removing exclusions, such as your top-level System and/or Library folders, can be sizeable.
    Renaming a folder or disk drive, or moving a file or folder, will cause the entire item moved or renamed to be backed-up. This includes all files and sub-folders in a moved or renamed folder.
    There are some OSX features and 3rd-party applications that cause large Time Machine backups. Common ones are FileVault, vmWare Fusion, Parallels Desktop, Entourage, and Thunderbird. Any application that uses a single large file or database may do this. See item 9 of the Frequently Asked Questions post.
    You can use the +Time Tracker+ app (see item #A2) to see just what was copied on any particular backup. There may be ways to minimize the size of such backups; search and/or post in this forum for help.
    |
    *Section E. _PROBLEMS VIEWING, RESTORING, or DELETING BACKUPS*_
    _*E1. Backups were deleted unexpectedly*_
    |
    Time Machine manages it's space for you, automatically. When it's drive/partition gets near full, it will begin deleting your oldest backups to make room for new ones. See item #C4 for more info and your options.
    In addition, regardless of space, TM also routinely "thins" your backups. It keeps one per week for as long as there's room; one per day (the first) for a month; all others for 24 hours.
    Usually when old weekly backups are deleted unexpectedly, it's because TM has done a new full or large backup, which of course requires a lot of space. See #D3 or D4 for common reasons.
    If in doubt, get the +Time Machine Buddy+ widget messages (see #A1). They'll show how much it was trying to back up. See item #7 of the Frequently Asked Questions *User Tip* at the top of this forum for explanation of those messages.
    |
    _*E2. I can't see some backups*_
    |
    If you can't see the backups for a disk/partition that's no longer connected, see #E3 below.
    TM keeps the backups for each Mac separate, and normally only shows the ones for the Mac it's running on, even if there are other Macs' backups on its disk/partition.
    Also, sometimes TM will start a new "sequence" of backups, as if they were from a different Mac. See item #D3.
    To see these "other" backups, you need the (badly named) +*Browse Other Time Machine Disks*+ option. It's available by holding down the Option key while selecting the TM icon in your Menubar, or by right-clicking the TM icon in your Dock.
    You'll see a selection screen showing all the disks/partitions that have TM backups on them. Select the one you want, and you'll be taken to the normal TM "Star Wars" interface, where you should see all the backups on that disk/partition.
    Note that, unfortunately, you cannot merge or combine two different "sequences" of backups.
    Also note that you cannot use the normal Restore button at the bottom of the screen to restore items, since they're from a different Mac. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
    |
    _*E3. I can't see backups for a disk/partition that's no longer connected*_
    |
    Open a Finder window and press ShiftCmdC (or select your computer name in the Finder Sidebar).
    Then either +*Enter Time Machine*+ or +*Browse Other Time Machine Disks*+ (see #E2).
    On the first Finder window in the "cascade," labelled +*Today (Now),+* you'll see all the volumes currently attached to your Mac.
    Select the Finder window or TimeLine entry for any backup, and you'll see a folder for each drive/volume that was backed-up, including any that are no longer connected. Navigate from there to whatever you're looking for.
    Also note that you cannot use the normal Restore button at the bottom of the screen to restore selected items, since they're from a different disk/partition. Instead, select the desired item(s), then click the "Gear" icon in the Finder window's toolbar and select the +*Restore <item> to ...+* option. You'll then get a prompt to specify the destination.
    You can restore an entire disk/partition to a different one (erasing any previous contents) via the procedure in item #14 of the Frequently Asked Questions *User Tip* at the top of this forum.
    |
    _*E4. Time Machine Interface ("Star Wars") won't display properly, or crashes*_
    |
    This can be caused by any of a number of things. Try these fixes:
    If you're using a Finder replacement (such as Pathfinder), be sure the Finder is running.
    If you're using Spaces, turn it off temporarily.
    If you have a second monitor, or anything plugged-in to a video-out port, disconnect it temporarily.
    De-select your TM drive via TM Preferences > Change Disk (select "none"), then re-select the correct one.
    Do a "complete reset" of TM, as in item #A4.
    Do a +*Repair Disk+* on your TM drive. See #A5 above.
    Try or create another user (System Preferences > Accounts). If it works ok from that user, delete the file:
    +*<home folder of the user where it doesn't work>/Library/Preferences/com.Apple.Finder.plist+*

Maybe you are looking for

  • Using my USA 17" intel mac in Japan?

    Hello everyone. I was wondering if anyone had any experience with bringing an US purchased intelmac up to Japan. I've read some forums saying that I don't need a converter. Some people and sites say that Japan's plugs are equal size holes (versus one

  • Capturing data changes in alv using classes

    Hello All, Currently am working on alv report using classes..,In this report am displaying 3 grids in the output in 3 different containers(cl_gui_custom_container)...,Am able to handle the data changes done in the grid  at the run time using event  d

  • Hide a row in CROSS TAB

    HI experts, I have a cross tab. The rows are automatic from a field, for example month: 1 2 3 4 5 6 .... I new to hide , for example the row of AUGUST. How can I hide the row in the cross table. I want to hide, I dont want to supress the result. Than

  • Iphoto glitch with retained masters

    Mavericks 10.9.4 iphoto 9.5.1 I am currently having a mysteriously bulky iphoto even after deleting most my photos. How can I delete the masters of iPhoto without losing my photos in the main iPhoto display library and all their masters and edits. I

  • Updating a PO

    While attempting to update a purchase order, I received the following error message: "Another user-modified table "(POR1) (ODBC -2039) [Message 131-183] What does this mean?