ERROR - BAD DUPLEX CONNECTION - HP 5000N

After switching our HP5000N laserject printer off and then back on, we are now getting the error "BAD DUPLX CONNECTION"
The problem is that we do not have a duplex unit. Never have had, never will have.
Therefore, clearly the printer is picking up a problem incorrectly.
Does any clever guru type person out there know what I can do to fix this situation?
Any further information you feel i may need to provide, please don't hesitate to ask.
Thanks in advance.
Greg.

How did you replave the duplex belt? How to deassemble the backside of a officejet and click the new belt on? I can't see nor do it y self

Similar Messages

  • Just upgraded to Lion an am discovering that I cannot send email photos from within iPhoto. Error message says bad Internet connection or server not working, when that's not the case. Never happened in Snow Leopard! Help!!!

    Just upgraded to Lion an am discovering that I cannot send email photos from within iPhoto. Error message says bad Internet connection or server not working, when that's not the case. Never happened in Snow Leopard! Help!!!

    what email service - Yahoo mail have been acting up lately
    you can try setting Mail as your email client - it resolves this pfoblem for some people
    LN

  • Heartbeat failed to connect to standby ORA-12160: TNS:internal error: Bad e

    <msg time='2010-09-03T11:37:46.548+06:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='DC-DB-01' host_addr='192.168.100.101' module=''
    pid='24310'>
    <txt>Error 12160 received logging on to the standby
    </txt>
    </msg>
    <msg time='2010-09-03T11:37:46.548+06:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='DC-DB-01' host_addr='192.168.100.101' module=''
    pid='24310'>
    <txt>Errors in file /u01/app/oracle/diag/rdbms/bddipdc/bddipdc1/trace/bddipdc1_arcq_24310.trc:
    ORA-12160: TNS:internal error: Bad error number
    </txt>
    </msg>
    <msg time='2010-09-03T11:37:46.548+06:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='DC-DB-01' host_addr='192.168.100.101' module=''
    pid='24310'>
    <txt>PING[ARCq]: Heartbeat failed to connect to standby &apos;bddipdrs&apos;. Error is 12160.
    </txt>
    </msg>
    From trace file,
    [oracle@DC-DB-01 ~]$ less /u01/app/oracle/diag/rdbms/bddipdc/bddipdc1/trace/bddipdc1_arcq_24310.trc
    Redo shipping client performing standby login
    OCIServerAttach failed -1
    .. Detailed OCI error val is 12160 and errmsg is 'ORA-12160: TNS:internal error:
    Bad error number
    OCIServerAttach failed -1
    .. Detailed OCI error val is 12160 and errmsg is 'ORA-12160: TNS:internal error:
    Bad error number
    OCIServerAttach failed -1
    .. Detailed OCI error val is 12160 and errmsg is 'ORA-12160: TNS:internal error:
    Bad error number
    *** 2010-09-03 11:37:46.548 4132 krsh.c
    Error 12160 received logging on to the standby
    *** 2010-09-03 11:37:46.548 869 krsu.c
    Error 12160 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'bddipdrs'
    Error 12160 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'bddipdrs'
    ORA-12160: TNS:internal error: Bad error number
    *** 2010-09-03 11:37:46.548 4132 krsh.c
    PING[ARCq]: Heartbeat failed to connect to standby 'bddipdrs'. Error is 12160.
    *** 2010-09-03 11:37:46.548 2747 krsi.c
    krsi_dst_fail: dest:2 err:12160 force:0 blast:1

    SQL> select
    2 substr(local.name,1,50) "Archive Name",
    case when remote.sequence# is null then 'NOT TRANSMITTED'
    3 4 else 'transmitted'
    5 end,
    6 local.sequence#,
    7 local.thread#
    8 from
    9 (select * from v$archived_log where dest_id = 1) local
    10 left join
    11 (select * from v$archived_log where dest_id = 2) remote
    12 on local.sequence# = remote.sequence# and
    13 local.thread# = remote.thread#
    14 order by local.sequence#;
    Archive Name CASEWHENREMOTE. SEQUENCE# THREAD#
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         1       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         2       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         3       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         4       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s transmitted             5       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         6       2
    +RECOVERY/bddipdc/archivelog/2010_08_31/thread_1_s NOT TRANSMITTED         6       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         7       2
    +RECOVERY/bddipdc/archivelog/2010_08_31/thread_1_s NOT TRANSMITTED         7       1
    +RECOVERY/bddipdc/archivelog/2010_08_31/thread_1_s NOT TRANSMITTED         8       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         8       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED         9       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         9       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        10       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        10       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s transmitted            11       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        11       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        12       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        12       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        13       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        13       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        14       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        14       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        15       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        15       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        16       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        16       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        17       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        17       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        18       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        18       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        19       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        19       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        20       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        20       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        21       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        21       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        22       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        22       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        23       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        23       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        24       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        24       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        25       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        25       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        26       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        26       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        27       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        27       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        28       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        28       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        29       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        29       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        30       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        30       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        31       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        31       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        32       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        32       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        33       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        33       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        34       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        34       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        35       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        35       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        36       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        36       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        37       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        37       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        38       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        38       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        39       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        39       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        40       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        40       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        41       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        41       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        42       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        42       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        43       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        43       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        44       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        44       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        45       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        45       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        46       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        46       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        47       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        47       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        48       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        48       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        49       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        49       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        50       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        50       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        51       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        51       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        52       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        52       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        53       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        53       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        54       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        54       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        55       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        55       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        56       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        56       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        57       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        57       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        58       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        58       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        59       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        59       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        60       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        60       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        61       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        61       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        62       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        62       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        63       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        63       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        64       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        64       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        65       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        65       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        66       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        66       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        67       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        67       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        68       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        68       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        69       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        69       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        70       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        70       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        71       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        71       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        72       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        72       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        73       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        73       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        74       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        74       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        75       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        75       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        76       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        76       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        77       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        77       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        78       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        78       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        79       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        79       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        80       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        80       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        81       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        81       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        82       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        82       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        83       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        83       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        84       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        84       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        85       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        85       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        86       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        86       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        87       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        87       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        88       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        88       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        89       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        89       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        90       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        90       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        91       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        91       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        92       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        92       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        93       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        93       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        94       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        94       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        95       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        96       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        97       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        98       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        99       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       100       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       101       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       102       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       103       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       104       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       105       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       106       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       107       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       108       1
    Archive Name CASEWHENREMOTE. SEQUENCE# THREAD#
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       109       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       110       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       111       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       112       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       113       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       114       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       115       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       116       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       117       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       118       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       119       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       120       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       121       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       122       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       123       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       124       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       125       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       126       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       127       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       128       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       129       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       130       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       131       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       132       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       133       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       134       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       135       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       136       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       137       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       138       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       139       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       140       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       141       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       142       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       143       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       144       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       145       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       146       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       147       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       148       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       149       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       150       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       151       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       152       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       153       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       154       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       155       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       156       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       157       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       158       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       159       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       160       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       161       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       162       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       163       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       164       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       165       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       166       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       167       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       168       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       169       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       170       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       171       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       172       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       173       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       174       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       175       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       176       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       177       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       178       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       179       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       180       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       181       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       182       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       183       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       184       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       185       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       186       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       187       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       188       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       189       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       190       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       191       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       192       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       193       1
    282 rows selected.

  • TS3297 I keep getting the error 306 cannot connect to the iTunes Network when downloading songs on iTunes. I've tried all the troubleshooting steps from the forums and my technical issues are still unresolved. I have Windows 7. Please help!!

    I keep getting the error 306 cannot connect to the iTunes Network when downloading songs on iTunes. I've tried all the troubleshooting steps from the forums and my technical issues are still unresolved. I have Windows 7. Please help!!

    iTunes Store loads partially or returns "Error 306" or "Error 10054"
    Proxies, parental control settings and software, security or filtering software, or a bad iTunes Store cache can cause this.
    To address proxies, Remove Internet Options proxy settings  ( http://support.apple.com/kb/TS1490 ) and connect to the Internet without a proxy.
    To reset iTunes Store cache:
    In iTunes, choose iTunes > Preferences (Mac) or Edit > Preferences (PC).
    Click the Advanced tab.
    Click the "Reset cache" button.
    Click OK and see if the issue is resolved.
    Adjust Parental Controls in iTunes:
    Open iTunes.
    Access iTunes preferences:
    On a Mac: From the iTunes menu, choose Preferences.
    On a Windows PC: From the Edit menu, choose Preferences.
    Click the Parental Controls tab.
    Remove restrictions on Parental Controls.
    For more information on parental controls or content filtering software, see iTunes 10.5 for Windows: May see performance issues and blank iTunes Store.
    http://support.apple.com/kb/TS4123?viewlocale=en_US

  • I get error time out connection

    i want to upgrade my ipad 1 software (i have 4.2.1 version and i want to upgrade it to a next version, as Itunes store suggests me every time i open it) but after the usual time of 13 minutes upgrade, i get this error: time out connection, contact your provider or control your connection (but it does function elsewhere)
    how can i solve it? (excuse my bad english)

    For me it worked when I switched the virus protection off while doing the installation. After you run the installation you then switch the virus protection back on.
    Hope it works for you too!

  • B2B-50079 Transport Error : Bad Message

    Hi All,
    I have an SFTP outbound TPA which is used to transfer a PGP file from our internal system to TP vendor.
    So the transfer is as follows B2B(Internal System) -> WebServer(acts as proxy while connecting to third party server)-->ThirdParty.
    The use proxy is checked in the Channels of the Trading Partner.
    The transfer fails while transfering the file to the TP with the below error.
    "B2B-50079 Transport Error : Bad Message" I have manually sftpd from web server to the TP server and it is working absolutely fine.
    Also i have verified that the certificate and host,port username details to connect to the TP are correct.
    Please let us know on what the problem area could be.
    There is no problem with file naming convention since the file is getting picked up by the listening channel and also we have checked the preserve file name option in the TP channel.
    Any help on this is much appreciated.
    Thanks,
    Naveen Kumar T.

    Thanks Anuj for the response.
    We already have the required patch, also its working fine with other Trading partners which uses SFTP. We are facing this issue with only one Trading partner and the same is working fine with 10g B2B but not with 11g.
    Please let us know if there is any other configurations which we can check.
    Thanks,
    Sirisha

  • *** ERROR = BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.

    Hello All,
    In our development system,  we are able to perform all the transactions normally(SAP level) and there is no performance issues..
    We have checked from OS level in work directory file dev_disp..
    We are getting below error.
    Can you please suggest us on this..............
    =========================================================
    ERROR => DpRqCheck: T72 in stat TM_SLOT_FREE [dpxxdisp.c   5805]
    ***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c   4621]
    ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c   4623]
    -IN-- sender_id DISPATCHER        tid  72    wp_ca_blk   -1      wp_id -1
    -IN-- action    SEND_TO_WP        uid  8012   appc_ca_blk -1      type  DIA
    -IN-- new_stat  NO_CHANGE         mode 0     len         -1      rq_id 53650
    -IN-- req_info  MS_ERROR
    ERROR => DpRqCheck: T73 in stat TM_SLOT_FREE [dpxxdisp.c   5805]
    ***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c   4621]
    ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c   4623]
    -IN-- sender_id DISPATCHER        tid  73    wp_ca_blk   -1      wp_id -1
    -IN-- action    SEND_TO_WP        uid  8013   appc_ca_blk -1      type  DIA
    -IN-- new_stat  NO_CHANGE         mode 0     len         -1      rq_id 53651
    -IN-- req_info  MS_ERROR
    ERROR => DpRqCheck: T74 in stat TM_SLOT_FREE [dpxxdisp.c   5805]
    ***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c   4621]
    ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c   4623]
    -IN-- sender_id DISPATCHER        tid  74    wp_ca_blk   -1      wp_id -1
    -IN-- action    SEND_TO_WP        uid  8014   appc_ca_blk -1      type  DIA
    -IN-- new_stat  NO_CHANGE         mode 0     len         -1      rq_id 53652
    -IN-- req_info  MS_ERROR
    ERROR => DpRqCheck: T77 in stat TM_SLOT_FREE [dpxxdisp.c   5805]
    ***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c   4621]
    ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c   4623]
    -IN-- sender_id DISPATCHER        tid  77    wp_ca_blk   -1      wp_id -1
    -IN-- action    SEND_TO_WP        uid  8019   appc_ca_blk -1      type  DIA
    -IN-- new_stat  NO_CHANGE         mode 0     len         -1      rq_id 53653
    -IN-- req_info  MS_ERROR
    Wed Apr  7 08:55:32 2010
    ***LOG Q0K=> DpMsAttach, mscon ( ussapdir00) [dpxxdisp.c   10127]
    Wed Apr  7 08:55:33 2010
    use SAPLOCALHOST=<ussapdir00> as internal hostname
    NiPAccept: accept failed (socket=7;errno=72)
    ***LOG Q0I=> NiPRead: recv (73: Connection reset by peer) [niuxi.c 928]
    SoftCancel request for T45 U8133 M0 received from REMOTE_TERMINAL
    Network error of client T46, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
    Client address of T46 is 10.228.250.65(10.228.250.65)
    ***LOG Q04=> DpRTmPrep, NiBufReceive (8135 MKK27890 46 BREWL07D4359) [dpxxdisp.c   9830]
    RM-T46, U8135, 620     MKK27890, BREWL07D43598, 08:43:19, M0, W4,     , 2/0
    Network error of client T45, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
    Client address of T45 is 10.228.250.65(10.228.250.65)
    ***LOG Q04=> DpRTmPrep, NiBufReceive (8133 RR606033 45 BREWL07D4359) [dpxxdisp.c   9830]
    RM-T45, U8133, 600     RR606033, BREWL07D43598, 08:38:22, M0, W0, SPRO, 2/3
    Release check o.K.
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1025]
    MBUF state ACTIVE
    Wed Apr  7 08:55:39 2010
    ERROR => DpRqCheck: T45 in stat TM_SLOT_FREE [dpxxdisp.c   5805]
    ***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c   4621]
    ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c   4623]
    -IN-- sender_id DISPATCHER        tid  45    wp_ca_blk   -1      wp_id -1
    -IN-- action    SEND_TO_WP        uid  8133   appc_ca_blk -1      type  DIA
    -IN-- new_stat  NO_CHANGE         mode 0     len         -1      rq_id 53678
    -IN-- req_info  LOGOFF CANCELMODE
    Wed Apr  7 08:55:44 2010
    ERROR => DpRqCheck: T46 in stat TM_SLOT_FREE [dpxxdisp.c   5805]
    ***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c   4621]
    ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5195): [dpxxdisp.c   4623]
    -IN-- sender_id DISPATCHER        tid  46    wp_ca_blk   -1      wp_id -1
    -IN-- action    SEND_TO_WP        uid  8135   appc_ca_blk -1      type  DIA
    -IN-- new_stat  NO_CHANGE         mode 0     len         -1      rq_id 53676
    -IN-- req_info  LOGOFF CANCELMODE
    ======================================================================
    Thanks in advance..
    Best Regards,
    Kiran

    Hi Kiran,
    It's not a problem or error, it's just a message and hence can be ignored. However you can check out SAP note 1111154 once, it will fix the issue probably if it's happening due to HTTP problem. Else you can very well ignore it.
    Regards
    Sourabh Majumdar

  • ASR9K PPPoE ERROR - bad session data

    In a month the second case all are disconnected Rrroyesessii and new aren't connected not to reboot a router yet.
    Messages
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: Bundle-Ether100.10: I dst ffff.ffff.ffff src bcee.7bed.90a0: len 46 0x11090000000c01010000010300040001000000000000000000000000000000000000000000000000000000000000
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]: Bundle-Ether100.10 peer-mac bcee.7bed.90a0
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]:    vlan-id-outer 600
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]:    Service-name: 
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]:    Host-uniq: 00010000
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: Bundle-Ether100.10: O dst bcee.7bed.90a0 src e4c7.227c.ea0b: len 31 0x11070000001901010000010300040001000001020009415352394b2d424e47
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADO-Sent]: Bundle-Ether100.10 peer-mac bcee.7bed.90a0
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADO-Sent]:    vlan-id-outer 600
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: Bundle-Ether100.10: I dst ffff.ffff.ffff src 0860.6e24.0390: len 46 0x11090000000c01010000010300040001000000000000000000000000000000000000000000000000000000000000
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]: Bundle-Ether100.10 peer-mac 0860.6e24.0390
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]:    vlan-id-outer 88
    RP/0/RSP0/CPU0:Feb 12 20:17:00.396 : pppoe_ma[378]: [PADI-Recv]:    Service-name: 
    RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: Bundle-Ether100.10: O dst 5404.a68e.2160 src e4c7.227c.ea0b: len 31 0x11070000001901010000010300040001000001020009415352394b2d424e47
    RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADO-Sent]: Bundle-Ether100.10 peer-mac 5404.a68e.2160
    RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADO-Sent]:    vlan-id-outer 210
    RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: Bundle-Ether100.10: I dst ffff.ffff.ffff src 5404.a6e6.81d4: len 46 0x11090000000c01010000010300040001000000000000000000000000000000000000000000000000000000000000
    RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADI-Recv]: Bundle-Ether100.10 peer-mac 5404.a6e6.81d4
    RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADI-Recv]:    vlan-id-outer 32
    RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADI-Recv]:    Service-name: 
    RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADI-Recv]:    Host-uniq: 00010000
    RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: Bundle-Ether100.10: O dst 5404.a6e6.81d4 src e4c7.227c.ea0b: len 31 0x11070000001901010000010300040001000001020009415352394b2d424e47
    RP/0/RSP0/CPU0:Feb 12 20:17:00.410 : pppoe_ma[378]: [PADO-Sent]: Bundle-Ether100.10 peer-mac 5404.a6e6.81d4
    RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: Bundle-Ether100.10: I dst ffff.ffff.ffff src 60a4.4c8c.8ddc: len 46 0x11090000000c01010000010300040001000000000000000000000000000000000000000000000000000000000000
    RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: [PADI-Recv]: Bundle-Ether100.10 peer-mac 60a4.4c8c.8ddc
    RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: [PADI-Recv]:    vlan-id-outer 60
    RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: [PADI-Recv]:    Service-name: 
    RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: [PADI-Recv]:    Host-uniq: 00010000
    RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: [PADI-Recv]:   ERROR - bad session data
    RP/0/RSP0/CPU0:Feb 12 20:17:00.518 : pppoe_ma[378]: Bundle-Ether100.10: O dst 60a4.4c8c.8ddc src e4c7.227c.ea0b: len 31 0x11070000001901010000010300040001000001020009415352394b2d424e47
    ASR9001 
    Cisco IOS XR Software, Version 5.1.1[Default]
    Copyright (c) 2014 by Cisco Systems, Inc.
    ROM: System Bootstrap, Version 2.04(20140227:092320) [ASR9K ROMMON]
    How to fight against it? before such it wasn't noticed 

    hi vladimir,
    I checked the source code when this error is set. this is seen when a session stage packet is received that has no valid idb (aka subscriber interface) for the session ID that was found in the packet together with the vlan tags.
    Now this is a PADI, so it is not a session packet to start with.
    Next I see that the function that sets this error is only called for on data packets when the opcode is 0x00 in your case the opcode is 0x09 which is a PADI.
    what I am thinking that is happening here is that the punt software has provided incorrect pointers to the start of the packet due to a sw bug.
    I would like to request if you can evaluate xr513 for this as I see some fixes in 512/513 relating to the punt handling sw that might be of benefit here.
    regards
    xander

  • Airplay Connection issues - An error occurred while connecting to the AirPlay device "x". The network connection failed.

    I recently upgraded to a new MacBook Pro running Mountain Lion, and got my Airport Express (802.11g) out of the closet and set up an AirPlay network for my speakers. 
    All worked well for the first while, but recently I've been having an inconsistent problem with this: "An error occurred while connecting to the AirPlay device “my network name”. The network connection failed."
    Since it came up, more often than not, I can't connect. 
    I can play without issue from my iPhone, and from my iPad. 
    I looked around these forums, and found a couple threads dealing with this from 2011, with no clear resolution to them.  No one with Mountain Lion seems to complain about it, though a few people mused about whether Mountain Lion might fix the problem. 
    I'm running iTunes 10.7(21), and don't recall doing any upgrades to it that might have brought this about, though I can't say for sure. 
    My Airport Express is updated to firmware version 6.3, which I believe is the last one issued for the 'g' Airport Express.
    My wireless network runs off an Airport Extreme 802.11n (Second Generation) with verion 7.6.1 firmware. 
    My Mac has 10.8.2 on it right now. 
    Hopefully some of that info might help sort this out - any replies greatly appreciated!

    One quick update.  A workaround that was mentioned in one post did seem to work - if music is started via the Remote app it seems to connect fine. 
    And I'm not sure if I dare upgrade to iTunes 11 given the firestorm of bad impressions I see, including some that relate to Airplay functions...

  • Error in TRFC Connection

    Hi Experts ,
    Pls help us in solving this error Some of our process chain are throwing error like Trfc connection not available
    Points will be assigned for right answer

    Hi ,
    See ur trfc connection not available may be because due to the work processors in R/3 would have not been available for the whole period of ur loading process .
    Pls wait for the parallel processes to end and then load ur data again after deleting the bad req from the manage tab
    if this error persists then go for a Ticket
    Assign some good points if answer helpfull
    Regards ,
    Subash Balakrishnan

  • LIBGWT_CAT:1313: ERROR: Bad message

    I am trying to connect a clarifyCRM 11.5 based system from BEA WebLogic 7.0 Sp2
    through WebLogic Tuxedo Connector.
    I am getting a "Bad Message" error on the clarify side. PLease let me know what
    might be the error.
    Details are as follows:
    ================
    1. BEA Weblogic is installed on Win2k and Clarify is installed on Solaris8.
    2. On Solaris8 machine, the ULog shows the following error:
    ==============================================
    150353.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1129: INFO: Connection established
    with domain (domainid=<BEA001
    )150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1313: ERROR: Bad message from BEA001.
    Closing file descriptor
    150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1130: INFO: Disconnected from domain
    (domainid=<BEA001>)
    150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1354: INFO: Retrying domain (domainid=<BEA001>)
    every 60 seconds
    ==========================================================
    3.The configuration for WTC in config.xml :
    ===========================================================
    <WTCServer Name="MyWTCServer" Targets="myserver">
    <WTCImport LocalAccessPoint="BEA001"
    Name="WTCImport-1056499621875"
    RemoteAccessPointList="CLAR115" RemoteName="CB_EXESUB" ResourceName="MyImportedService"/>
    <WTCLocalTuxDom AccessPoint="BEA001" AccessPointId="BEA001"
    ConnectionPolicy="ON_DEMAND" MaxRetries="5000000"
    NWAddr="//172.24.3.208:7001" Name="WTCLocalTuxDom-1055806963906"/>
    <WTCRemoteTuxDom AccessPoint="CLAR115" AccessPointId="CLAR115"
    ConnectionPolicy="ON_DEMAND" LocalAccessPoint="BEA001"
    NWAddr="//10.3.0.14:53401" Name="WTCRemoteTuxDom-1056499341890"/>
    </WTCServer>
    ==================================================================
    4. DMConfig on on clarify machine:
    ==================================================
    # DMCONFIG FILE
    *DM_RESOURCES
         VERSION="U22"
    *DM_LOCAL
    CLAR115     GWGRP=GWDOM
              TYPE="TDOMAIN"
              DOMAINID="CLAR115"
         AUDITLOG="/u02/program/tuxedo/clr_115/AUDITLOG"
         BLOCKTIME=10
         CONNECTION_POLICY="ON_DEMAND"
         DMTLOGDEV="/u02/program/tuxedo/clr_115/DMTLOG"
         DMTLOGNAME="DMTLOG_TDOM"
         MAXDATALEN=56
         MAXRACCESSPOINT=89
         MAXTRAN=100
         BLOB_SHM_SIZE=1000000
    *DM_REMOTE
    BEA001     TYPE=TDOMAIN
         DOMAINID="BEA001"
    *DM_TDOMAIN
    BEA001     NWADDR="//172.24.3.208:7001"
    #     NWDEVICE="/dev/tcp"
    CLAR115     NWADDR="//jupiter:53401"
    #     NWDEVICE="/dev/tcp"
    *DM_LOCAL_SERVICES
    CB_EXESUB     LDOM="CLAR115"
    *DM_REMOTE_SERVICES
    ===============================================================

    Bhaskar,
    The ULOG message about "Retrying" does not go with a configuration
    of "ON_DEMAND". The best guess is that BEA001 is not really communicating
    with whom you think. Two things to look at:
    1)Check that "jupiter"=="10.3.0.14"
    2) Do a dmunloadcf on the CLAR115 domain and see if the domain that is
    booted
    is what you expected from your configuration.
    Bob Finan
    Bhaskar wrote:
    Bob,
    No success by changing port numbers.
    However after some more experimentation I am getting the following:
    I installed tuxedo on another Windows 2000 m/c. (say TUX001). If I call the Clarify
    domain as CLAR115 and BEA domain as BEA001 then
    a) I am able to communicate between CLAR115 and TUX001
    b) I am able to communicate between TUX001 and BEA001 by using WTC in BEA001
    c) But, I am still not able to communicate between BEA001 and CLAR115. I still
    obtain a BAD Message error on the CLAR115 side
    Quite puzzled with this.
    Regards
    Bhaskar
    "Bhaskar" <[email protected]> wrote:
    Thanks Bob,
    I would surely try with using another port.
    Currently,I am using a different port for the WLS admin server. Secondly,
    in case
    I was using a port that was already being used by some other server,
    one of the
    two servers would not have come up.
    Is there any method to read the ULogs for the Local tuxedo domain on
    WLS end.
    thanks and regards
    Bhaskar
    Bob Finan <[email protected]> wrote:
    Bhaskar,
    You are probably using the //172.24.3.208:7001 port for other purposes
    and this is
    causing the problem(e.g. 7001 is the default WLS admin port).Try
    changing the
    NWAddr port number for the WTCLocalTuxDom..
    Bob Finan
    Bhaskar wrote:
    I am trying to connect a clarifyCRM 11.5 based system from BEA WebLogic
    7.0 Sp2
    through WebLogic Tuxedo Connector.
    I am getting a "Bad Message" error on the clarify side. PLease let
    me
    know what
    might be the error.
    Details are as follows:
    ================
    1. BEA Weblogic is installed on Win2k and Clarify is installed on Solaris8.
    2. On Solaris8 machine, the ULog shows the following error:
    ==============================================
    150353.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1129: INFO: Connection
    established
    with domain (domainid=<BEA001
    150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1313: ERROR: Bad message
    from BEA001.
    Closing file descriptor
    150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1130: INFO: Disconnected
    from domain
    (domainid=<BEA001>)
    150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1354: INFO: Retrying
    domain
    (domainid=<BEA001>)
    every 60 seconds
    ==========================================================
    3.The configuration for WTC in config.xml :
    ===========================================================
    <WTCServer Name="MyWTCServer" Targets="myserver">
    <WTCImport LocalAccessPoint="BEA001"
    Name="WTCImport-1056499621875"
    RemoteAccessPointList="CLAR115" RemoteName="CB_EXESUB"
    ResourceName="MyImportedService"/>
    <WTCLocalTuxDom AccessPoint="BEA001" AccessPointId="BEA001"
    ConnectionPolicy="ON_DEMAND" MaxRetries="5000000"
    NWAddr="//172.24.3.208:7001" Name="WTCLocalTuxDom-1055806963906"/>
    <WTCRemoteTuxDom AccessPoint="CLAR115" AccessPointId="CLAR115"
    ConnectionPolicy="ON_DEMAND" LocalAccessPoint="BEA001"
    NWAddr="//10.3.0.14:53401" Name="WTCRemoteTuxDom-1056499341890"/>
    </WTCServer>
    ==================================================================
    4. DMConfig on on clarify machine:
    ==================================================
    # DMCONFIG FILE
    *DM_RESOURCES
         VERSION="U22"
    *DM_LOCAL
    CLAR115     GWGRP=GWDOM
              TYPE="TDOMAIN"
              DOMAINID="CLAR115"
         AUDITLOG="/u02/program/tuxedo/clr_115/AUDITLOG"
         BLOCKTIME=10
         CONNECTION_POLICY="ON_DEMAND"
         DMTLOGDEV="/u02/program/tuxedo/clr_115/DMTLOG"
         DMTLOGNAME="DMTLOG_TDOM"
         MAXDATALEN=56
         MAXRACCESSPOINT=89
         MAXTRAN=100
         BLOB_SHM_SIZE=1000000
    *DM_REMOTE
    BEA001     TYPE=TDOMAIN
         DOMAINID="BEA001"
    *DM_TDOMAIN
    BEA001     NWADDR="//172.24.3.208:7001"
    #     NWDEVICE="/dev/tcp"
    CLAR115     NWADDR="//jupiter:53401"
    #     NWDEVICE="/dev/tcp"
    *DM_LOCAL_SERVICES
    CB_EXESUB     LDOM="CLAR115"
    *DM_REMOTE_SERVICES
    ===============================================================
    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    <html>
    <head>
    <title></title>
    </head>
    <body>
    Bhaskar,<br>
    You are probably using the //172.24.3.208:7001 port for other purposes
    and
    this is<br>
    causing the problem(e.g. 7001 is the default WLS admin port).Try changing
    the <br>
    NWAddr port number for the WTCLocalTuxDom..<br>
    Bob Finan<br>
    <br>
    Bhaskar wrote:<br>
    <blockquote type="cite" cite="[email protected]">
    <pre wrap="">I am trying to connect a clarifyCRM 11.5 based system
    from BEA WebLogic 7.0 Sp2
    through WebLogic Tuxedo Connector.
    I am getting a "Bad Message" error on the clarify side. PLease let me
    know what
    might be the error.
    Details are as follows:
    ================
    1. BEA Weblogic is installed on Win2k and Clarify is installed on Solaris8.
    2. On Solaris8 machine, the ULog shows the following error:
    ==============================================
    150353.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1129: INFO: Connection
    established
    with domain (domainid=<BEA001
    </pre>
    <blockquote type="cite">
    <pre wrap="">)
    </pre>
    </blockquote>
    <pre wrap=""><!---->150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1313:
    ERROR: Bad message from BEA001.
    Closing file descriptor
    150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1130: INFO: Disconnected
    from domain
    (domainid=<BEA001>)
    150354.jupiter!GWTDOMAIN.8761.1.0: LIBGWT_CAT:1354: INFO: Retrying domain
    (domainid=<BEA001>)
    every 60 seconds
    ==========================================================
    3.The configuration for WTC in config.xml :
    ===========================================================
    <WTCServer Name="MyWTCServer" Targets="myserver">
    <WTCImport LocalAccessPoint="BEA001"
    Name="WTCImport-1056499621875"
    RemoteAccessPointList="CLAR115" RemoteName="CB_EXESUB" ResourceName="MyImportedService"/>
    <WTCLocalTuxDom AccessPoint="BEA001" AccessPointId="BEA001"
    ConnectionPolicy="ON_DEMAND" MaxRetries="5000000"
    NWAddr="//172.24.3.208:7001" Name="WTCLocalTuxDom-1055806963906"/>
    <WTCRemoteTuxDom AccessPoint="CLAR115" AccessPointId="CLAR115"
    ConnectionPolicy="ON_DEMAND" LocalAccessPoint="BEA001"
    NWAddr="//10.3.0.14:53401" Name="WTCRemoteTuxDom-1056499341890"/>
    </WTCServer>
    ==================================================================
    4. DMConfig on on clarify machine:
    ==================================================
    # DMCONFIG FILE
    *DM_RESOURCES
         VERSION="U22"
    *DM_LOCAL
    CLAR115     GWGRP=GWDOM
              TYPE="TDOMAIN"
              DOMAINID="CLAR115"
         AUDITLOG="/u02/program/tuxedo/clr_115/AUDITLOG"
         BLOCKTIME=10
         CONNECTION_POLICY="ON_DEMAND"
         DMTLOGDEV="/u02/program/tuxedo/clr_115/DMTLOG"
         DMTLOGNAME="DMTLOG_TDOM"
         MAXDATALEN=56
         MAXRACCESSPOINT=89
         MAXTRAN=100
         BLOB_SHM_SIZE=1000000
    *DM_REMOTE
    BEA001     TYPE=TDOMAIN
         DOMAINID="BEA001"
    *DM_TDOMAIN
    BEA001     NWADDR="//172.24.3.208:7001"
    #     NWDEVICE="/dev/tcp"
    CLAR115     NWADDR="//jupiter:53401"
    #     NWDEVICE="/dev/tcp"
    *DM_LOCAL_SERVICES
    CB_EXESUB     LDOM="CLAR115"
    *DM_REMOTE_SERVICES
    ===============================================================
    </pre>
    </blockquote>
    <br>
    </body>
    </html>
    [att1.html]

  • Error internet not connecting

    I have a Powermac G4 933A Mhz that I cannot get any web browser to load a URL. I go to system preferences/Network and see that I have an IP Address and see all setting are right. I am using a local network on DHCP with Ethernet. I then go back to safari and try to go to web site but get an error that it could not find the Internet. Could this be a bad Ethernet port on the motherboard? I even erased the HD and reinstalled OSX 10.4 and still I get the same error and cannot connect to the Internet. Has anyone had experience with this?
      Mac OS X (10.4.6)  

    If putting this into the URL bar connects to
    Apple.com, then it's a DNS issue...
    http://17.254.3.183
    If that works, try putting...
    208.67.222.222
    208.67.220.220
    Into your Network>TCP/IP>DNS Servers: spot... maybe
    your Router too if you have one.
    Thanks I will test that tomarow.
    Any other tips?
      Mac OS X (10.4.6)  
      Mac OS X (10.4.6)  

  • Whenever i try and open a social network app it comes up with an error message sayinng "Connect to itunes to use Push Notifications" I have successfully conntected to itunes via phone and computer however this message is still appearing and will not go?

    Whenever i try and open a social network app it comes up with an error message sayinng "Connect to itunes to use Push Notifications" I have successfully conntected to itunes via phone and computer however this message is still appearing and will not go, therefore i cannot use the apps?HELP PLEASE

    http://support.apple.com/kb/TS3281

  • I am unable to receive or send email from my IPAD.  The error message says "Connection to server failed".  Help!! geandreamer44

    I am unable to receive or send email from my IPAD.  The error message says "Connection to server failed".  Help!! geandreamer44

    Reset the device:
    Press and hold the Sleep/Wake button and the Home button together for at least ten seconds, until the Apple logo appears.
    If that doesn't help, tap Settings > General > Reset > Reset All Settings
    If that doesn't help, tap Settings > General > Reset > Reset Network Settings
    You will have to re enter your Wi-Fi password.
    If nothing above helped, restart your router.
    No data is lost due to a reset.

  • Internet Download error message: the connection with the server has been reset

    With an WRT54GS v6 firmware v 1.50.9 on Windows XP SP2 with Internet Explorer 7, Intel wireless internal adaptor w/ 802.11b,  I was getting the error message "The connection with the server has been reset" when downloading most anything from the Internet.  My IP address would then be reset and download would be interrupted.  To resolve, I turned off the WZC (Wireless Zero Configuration) Services, and this seems to correct the problem.
    Control Panel > Admin Tools > Services > Wireless Zero Configuration > Disable
    Hopes this helps.

    Hi!
    Im using Windows 7.... I tried looking for the Wireless Config - but it isn't in the Services options!
    So, what can I do now?
    Thanx

Maybe you are looking for

  • ITunes can no longer find my iPhoto - no iPhone photo sync ability...help!?

    Hello...okay, some data - I am currently running Lion and all the latest software updates, I am also running multiple users on this iMac, I am also sharing the iPhoto library using the "Shared Library" method.  My wifes iPhone (via her own account on

  • Sharing Canon LBP7010C no longer works in Mavericks

    I've noticed there's plenty of troubles with network printing in Mavericks. Here's mine: I have an MacBook Air 2012 and a new iMac, with Canon LBP7010C connected to it. Both computers have the most recent (10.9 compatible) drivers installed and can p

  • Dell 1905FP

    I have a new Dell 1905FP monitor. When I hook it up DVI and reboot my machine I cannot view anything due to it being green and messed up. Any ideas as to what I'm doing wrong? Thanks, Scott Manies

  • Searching for pictures by both date and keyword

    When I have the calendar tab up and a date with pictures is highlighted, when I go to select a keyword the calendar goes away and then I am back to my library. How do I search for pictures by both date and keyword? Thank You, Margaret

  • Script for no sound when receiving spam

    Hi there, I'm looking for a script for Apple Mail that shuts off sound when a message that's labeled as spam comes in. I have several e-mail accounts running in Apple Mail. It happens often that while checking for new mail only spam comes in. It woul