C move responded with error code a801

from pydicom.dataset import Dataset
import logging, os

from pynetdicom import AE, evt, StoragePresentationContexts
from pynetdicom.sop_class import PatientRootQueryRetrieveInformationModelMove



logging.basicConfig(level=logging.DEBUG, format='%(asctime)s %(levelname)-8s %(message)s', datefmt='%a, %d %b %Y %H:%M:%S', filename='test.log', filemode='w')
LOGGER = logging.getLogger('pynetdicom3')


def handle_store(event):
    """Handle a C-STORE request.
    Parameters
    ----------
    event : pynetdicom.event.event
        The event corresponding to a C-STORE request. Attributes are:
        * *assoc*: the ``association.Association`` instance that received the
          request
        * *context*: the presentation context used for the request's *Data
          Set* as a ``namedtuple``
        * *request*: the C-STORE request as a ``dimse_primitives.C_STORE``
          instance
        Properties are:
        * *dataset*: the C-STORE request's decoded *Data Set* as a pydicom
          ``Dataset``
    Returns
    -------
    status : pynetdicom.sop_class.Status or int
        A valid return status code, see PS3.4 Annex B.2.3 or the
        ``StorageServiceClass`` implementation for the available statuses
    """

    mode_prefixes = {
        'CT Image Storage' : 'CT',
        'Enhanced CT Image Storage' : 'CTE',
        'MR Image Storage' : 'MR',
        'Enhanced MR Image Storage' : 'MRE',
        'Positron Emission Tomography Image Storage' : 'PT',
        'Enhanced PET Image Storage' : 'PTE',
        'RT Image Storage' : 'RI',
        'RT Dose Storage' : 'RD',
        'RT Plan Storage' : 'RP',
        'RT Structure Set Storage' : 'RS',
        'Computed Radiography Image Storage' : 'CR',
        'Ultrasound Image Storage' : 'US',
        'Enhanced Ultrasound Image Storage' : 'USE',
        'X-Ray Angiographic Image Storage' : 'XA',
        'Enhanced XA Image Storage' : 'XAE',
        'Nuclear Medicine Image Storage' : 'NM',
        'Secondary Capture Image Storage' : 'SC'
    }

    ds = event.dataset

    # Because pydicom uses deferred reads for its decoding, decoding errors
    #   are hidden until encountered by accessing a faulty element
    try:
        sop_class = ds.SOPClassUID
        sop_instance = ds.SOPInstanceUID
    except Exception as exc:
        # Unable to decode dataset
        return 0xC210

    try:
        # Get the elements we need
        mode_prefix = mode_prefixes[sop_class.name]
    except KeyError:
        mode_prefix = 'UN'

    filename = '{0!s}.{1!s}'.format(mode_prefix, sop_instance)
    LOGGER.info('Storing DICOM file: {0!s}'.format(filename))

    if os.path.exists(filename):
        LOGGER.warning('DICOM file already exists, overwriting')

    # Presentation context
    cx = event.context

    ## DICOM File Format - File Meta Information Header
    # If a DICOM dataset is to be stored in the DICOM File Format then the
    # File Meta Information Header is required. At a minimum it requires:
    #   * (0002,0000) FileMetaInformationGroupLength, UL, 4
    #   * (0002,0001) FileMetaInformationVersion, OB, 2
    #   * (0002,0002) MediaStorageSOPClassUID, UI, N
    #   * (0002,0003) MediaStorageSOPInstanceUID, UI, N
    #   * (0002,0010) TransferSyntaxUID, UI, N
    #   * (0002,0012) ImplementationClassUID, UI, N
    # (from the DICOM Standard, Part 10, Section 7.1)
    # Of these, we should update the following as pydicom will take care of
    #   the remainder
    meta = Dataset()
    meta.MediaStorageSOPClassUID = sop_class
    meta.MediaStorageSOPInstanceUID = sop_instance
    meta.ImplementationClassUID = PYNETDICOM_IMPLEMENTATION_UID
    meta.TransferSyntaxUID = cx.transfer_syntax

    # The following is not mandatory, set for convenience
    meta.ImplementationVersionName = PYNETDICOM_IMPLEMENTATION_VERSION

    ds.file_meta = meta
    ds.is_little_endian = cx.transfer_syntax.is_little_endian
    ds.is_implicit_VR = cx.transfer_syntax.is_implicit_VR

    status_ds = Dataset()
    status_ds.Status = 0x0000

    # Try to save to output-directory
    filename = os.path.join(os.getcwd(), filename)
    print(filename)

    try:
        # We use `write_like_original=False` to ensure that a compliant
        #   File Meta Information Header is written
        ds.save_as(filename, write_like_original=False)
        status_ds.Status = 0x0000 # Success
    except IOError:
        LOGGER.error('Could not write file to specified directory:')
        LOGGER.error("    {0!s}".format(os.path.dirname(filename)))
        LOGGER.error('Directory may not exist or you may not have write '
                     'permission')
        # Failed - Out of Resources - IOError
        status_ds.Status = 0xA700
    except:
        LOGGER.error('Could not write file to specified directory:')
        LOGGER.error("    {0!s}".format(os.path.dirname(filename)))
        # Failed - Out of Resources - Miscellaneous error
        status_ds.Status = 0xA701

    return status_ds


handlers = [(evt.EVT_C_STORE, handle_store)]


# Initialise the Application Entity
ae = AE()
ae.ae_title = b'MY_AE_TITLE21'

# Add the Storage SCP's supported presentation contexts
ae.supported_contexts = StoragePresentationContexts

# Start our Storage SCP in non-blocking mode, listening on port 104
scp = ae.start_server(('', 104), block=False, evt_handlers=handlers)


# Add a requested presentation context
ae.add_requested_context(PatientRootQueryRetrieveInformationModelMove)

# Create out identifier (query) dataset
ds = Dataset()
ds.PatientID = '24759123'
ds.QueryRetrieveLevel = 'PATIENT'

assoc = ae.associate('www.dicomserver.co.uk', 104, ae_title=b'DICOM_SERVER')

if assoc.is_established:
    # Use the C-MOVE service to send the identifier
    # A query_model value of 'P' means use the 'Patient Root Query
    #   Retrieve Information Model - Move' presentation context
    responses = assoc.send_c_move(ds, b'MY_AE_TITLE21', query_model='P')

    for (status, identifier) in responses:
        if status:
            print('C-MOVE query status: 0x{0:04x}'.format(status.Status))

            # If the status is 'Pending' then the identifier is the C-MOVE response
            if status.Status in (0xFF00, 0xFF01):
                print(identifier)
        else:
            print('Connection timed out, was aborted or received invalid response')

    # Release the association
    assoc.release()
else:
    print('Association rejected, aborted or never connected')

# Stop our Storage SCP
scp.shutdown()

Tue, 04 Jun 2019 23:16:39 INFO     Requesting Association
Tue, 04 Jun 2019 23:16:40 DEBUG    Request Parameters:
Tue, 04 Jun 2019 23:16:40 DEBUG    ========================= BEGIN A-ASSOCIATE-RQ PDU =========================
Tue, 04 Jun 2019 23:16:40 DEBUG    Our Implementation Class UID:      1.2.826.0.1.3680043.9.3811.1.3.1
Tue, 04 Jun 2019 23:16:40 DEBUG    Our Implementation Version Name:   PYNETDICOM_131
Tue, 04 Jun 2019 23:16:40 DEBUG    Application Context Name:    1.2.840.10008.3.1.1.1
Tue, 04 Jun 2019 23:16:40 DEBUG    Calling Application Name:    MY_AE_TITLE21   
Tue, 04 Jun 2019 23:16:40 DEBUG    Called Application Name:     DICOM_SERVER    
Tue, 04 Jun 2019 23:16:40 DEBUG    Our Max PDU Receive Size:    16382
Tue, 04 Jun 2019 23:16:40 DEBUG    Presentation Context:
Tue, 04 Jun 2019 23:16:40 DEBUG      Context ID:        1 (Proposed)
Tue, 04 Jun 2019 23:16:40 DEBUG        Abstract Syntax: =Patient Root Query/Retrieve Information Model - MOVE
Tue, 04 Jun 2019 23:16:40 DEBUG        Proposed SCP/SCU Role: Default
Tue, 04 Jun 2019 23:16:40 DEBUG        Proposed Transfer Syntaxes:
Tue, 04 Jun 2019 23:16:40 DEBUG          =Implicit VR Little Endian
Tue, 04 Jun 2019 23:16:40 DEBUG          =Explicit VR Little Endian
Tue, 04 Jun 2019 23:16:40 DEBUG          =Explicit VR Big Endian
Tue, 04 Jun 2019 23:16:40 DEBUG    Requested Extended Negotiation: None
Tue, 04 Jun 2019 23:16:40 DEBUG    Requested Common Extended Negotiation: None
Tue, 04 Jun 2019 23:16:40 DEBUG    Requested Asynchronous Operations Window Negotiation: None
Tue, 04 Jun 2019 23:16:40 DEBUG    Requested User Identity Negotiation: None
Tue, 04 Jun 2019 23:16:40 DEBUG    ========================== END A-ASSOCIATE-RQ PDU ==========================
Tue, 04 Jun 2019 23:16:40 DEBUG    Accept Parameters:
Tue, 04 Jun 2019 23:16:40 DEBUG    ========================= BEGIN A-ASSOCIATE-AC PDU =========================
Tue, 04 Jun 2019 23:16:40 DEBUG    Their Implementation Class UID:    1.2.826.0.1.3680043.1.2.100.8.40.109.8
Tue, 04 Jun 2019 23:16:40 DEBUG    Their Implementation Version Name: DicomObjects.NET
Tue, 04 Jun 2019 23:16:40 DEBUG    Application Context Name:    1.2.840.10008.3.1.1.1
Tue, 04 Jun 2019 23:16:40 DEBUG    Calling Application Name:    MY_AE_TITLE21   
Tue, 04 Jun 2019 23:16:40 DEBUG    Called Application Name:     DICOM_SERVER    
Tue, 04 Jun 2019 23:16:40 DEBUG    Their Max PDU Receive Size:  65536
Tue, 04 Jun 2019 23:16:40 DEBUG    Presentation Contexts:
Tue, 04 Jun 2019 23:16:40 DEBUG      Context ID:        1 (Accepted)
Tue, 04 Jun 2019 23:16:40 DEBUG        Abstract Syntax: =Patient Root Query/Retrieve Information Model - MOVE
Tue, 04 Jun 2019 23:16:40 DEBUG        Accepted SCP/SCU Role: Default
Tue, 04 Jun 2019 23:16:40 DEBUG        Accepted Transfer Syntax: =Explicit VR Little Endian
Tue, 04 Jun 2019 23:16:40 DEBUG    Accepted Extended Negotiation: None
Tue, 04 Jun 2019 23:16:40 DEBUG    Accepted Asynchronous Operations Window Negotiation: None
Tue, 04 Jun 2019 23:16:40 DEBUG    User Identity Negotiation Response: None
Tue, 04 Jun 2019 23:16:40 DEBUG    ========================== END A-ASSOCIATE-AC PDU ==========================
Tue, 04 Jun 2019 23:16:40 INFO     Association Accepted
Tue, 04 Jun 2019 23:16:40 INFO     Sending Move Request: MsgID 1
Tue, 04 Jun 2019 23:16:40 INFO     
Tue, 04 Jun 2019 23:16:40 INFO     # Identifier DICOM Dataset
Tue, 04 Jun 2019 23:16:40 INFO     (0008, 0052) Query/Retrieve Level                CS: 'PATIENT'
Tue, 04 Jun 2019 23:16:40 INFO     (0010, 0020) Patient ID                          LO: '24759123'
Tue, 04 Jun 2019 23:16:40 INFO     
Tue, 04 Jun 2019 23:16:40 DEBUG    ========================== OUTGOING DIMSE MESSAGE ==========================
Tue, 04 Jun 2019 23:16:40 DEBUG    Message Type                  : C-MOVE RQ
Tue, 04 Jun 2019 23:16:40 DEBUG    Message ID                    : 1
Tue, 04 Jun 2019 23:16:40 DEBUG    Affected SOP Class UID        : 1.2.840.10008.5.1.4.1.2.1.2
Tue, 04 Jun 2019 23:16:40 DEBUG    Move Destination              : MY_AE_TITLE20   
Tue, 04 Jun 2019 23:16:40 DEBUG    Identifier                    : Present
Tue, 04 Jun 2019 23:16:40 DEBUG    Priority                      : Low
Tue, 04 Jun 2019 23:16:40 DEBUG    ============================ END DIMSE MESSAGE =============================
Tue, 04 Jun 2019 23:16:40 DEBUG    pydicom.read_dataset() TransferSyntax="Little Endian Implicit"
Tue, 04 Jun 2019 23:16:40 DEBUG    ========================== INCOMING DIMSE MESSAGE ==========================
Tue, 04 Jun 2019 23:16:40 DEBUG    Message Type                  : C-MOVE RSP
Tue, 04 Jun 2019 23:16:40 DEBUG    Message ID Being Responded To : 1
Tue, 04 Jun 2019 23:16:40 DEBUG    Affected SOP Class UID        : 1.2.840.10008.5.1.4.1.2.1.2
Tue, 04 Jun 2019 23:16:40 DEBUG    Identifier                    : None
Tue, 04 Jun 2019 23:16:40 DEBUG    DIMSE Status                  : 0xa801
Tue, 04 Jun 2019 23:16:40 DEBUG    ============================ END DIMSE MESSAGE =============================
Tue, 04 Jun 2019 23:16:40 DEBUG    
Tue, 04 Jun 2019 23:16:40 INFO     Move SCP Result: 0xa801 (Failure)
Tue, 04 Jun 2019 23:16:40 INFO     Sub-Operations Remaining: 0, Completed: 0, Failed: 0, Warning: 0
Tue, 04 Jun 2019 23:16:40 DEBUG    pydicom.read_dataset() TransferSyntax="Little Endian Explicit"
Tue, 04 Jun 2019 23:16:40 INFO     Releasing Association

21:03:42 (1041329) IN  TCP connection from <my ip address here>, Port : 59212  to local port : 104
21:03:42 (1041329) IN  Association request
21:03:42 (1041329) IN    Initiating AET=MY_AE_TITLE21
21:03:42 (1041329) IN    Called AET=DICOM_SERVER
21:03:42 (1041329) IN    Application Context=1.2.840.10008.3.1.1.1
21:03:42 (1041329) IN    Presentation Context 1
21:03:42 (1041329) IN      Abst Syntax=1.2.840.10008.5.1.4.1.2.1.2
21:03:42 (1041329) IN        Transfer Syntax=1.2.840.10008.1.2
21:03:42 (1041329) IN        Transfer Syntax=1.2.840.10008.1.2.1
21:03:42 (1041329) IN        Transfer Syntax=1.2.840.10008.1.2.2
21:03:42 (1041329) IN    User information
21:03:42 (1041329) IN      Max length= 16382
21:03:42 (1041329) IN      Imp UID= 1.2.826.0.1.3680043.9.3811.1.3.1
21:03:42 (1041329) IN      Imp Name= PYNETDICOM_131
21:03:42 (1041329) OUT Association acceptance
21:03:42 (1041329) OUT   Initiating AET=MY_AE_TITLE21
21:03:42 (1041329) OUT   Called AET=DICOM_SERVER
21:03:42 (1041329) OUT   Application Context=1.2.840.10008.3.1.1.1
21:03:42 (1041329) OUT   Presentation Context 1
21:03:42 (1041329) OUT     Accepted
21:03:42 (1041329) OUT       Transfer Syntax=1.2.840.10008.1.2.1
21:03:42 (1041329) OUT   User information
21:03:42 (1041329) OUT     Max length= 65536
21:03:42 (1041329) OUT     Imp UID= 1.2.826.0.1.3680043.1.2.100.8.40.109.8
21:03:42 (1041329) OUT     Imp Name= DicomObjects.NET
21:03:42 (1041329) IN  (0000,0000) UL : 100 (64H)
21:03:42 (1041329) IN  (0000,0002) UI : 1.2.840.10008.5.1.4.1.2.1.2 (PatientRootQR_MOVE)
21:03:42 (1041329) IN  (0000,0100) US : 33 (21H)
21:03:42 (1041329) IN  (0000,0110) US : 1 (1H)
21:03:42 (1041329) IN  (0000,0600) AE : MY_AE_TITLE21
21:03:42 (1041329) IN  (0000,0700) US : 2 (2H)
21:03:42 (1041329) IN  (0000,0800) US : 1 (1H)
21:03:42 (1041329) IN  (0008,0052) CS : PATIENT
21:03:42 (1041329) IN  (0010,0020) LO : 24759123
21:03:42 (1041329) IN  Command = C_MOVE
21:03:42 (1041329) IN  SOP Class = 1.2.840.10008.5.1.4.1.2.1.2
21:03:42 (1041329) IN  Q/R request received
21:03:42 (-) ===RemoteIP is <my ip address here> ===
21:03:42 (-) ===CallingAET is MY_AE_TITLE21 ===
21:03:42 (-) ===Destination is MY_AE_TITLE21 ===
21:03:42 (-) Select DISTINCT SOPClassUID from ImageRetrievalView  WHERE StudyUID = '' 
21:03:42 (1041330) OUT About to create socket
21:03:42 (1041330) OUT Connecting to  <my ip address here>, Port : 104
21:03:42 (1041330) OUT Socket connected, outgoing Port : 50199
21:03:42 (1041330) OUT Association request
21:03:42 (1041330) OUT   Initiating AET=DICOM_SERVER
21:03:42 (1041330) OUT   Called AET=MY_AE_TITLE21
21:03:42 (1041330) OUT   Application Context=1.2.840.10008.3.1.1.1
21:03:42 (1041330) OUT   Presentation Context 1
21:03:42 (1041330) OUT     Abst Syntax=1.2.840.10008.5.1.4.1.1.7
21:03:42 (1041330) OUT       Transfer Syntax=1.2.840.10008.1.2.1
21:03:42 (1041330) OUT       Transfer Syntax=1.2.840.10008.1.2
21:03:42 (1041330) OUT       Transfer Syntax=1.2.840.10008.1.2.4.57
21:03:42 (1041330) OUT       Transfer Syntax=1.2.840.10008.1.2.4.70
21:03:42 (1041330) OUT       Transfer Syntax=1.2.840.10008.1.2.5
21:03:42 (1041330) OUT       Transfer Syntax=1.2.840.10008.1.2.4.100
21:03:42 (1041330) OUT       Transfer Syntax=1.2.840.10008.1.2.4.101
21:03:42 (1041330) OUT       Transfer Syntax=1.2.840.10008.1.2.4.102
21:03:42 (1041330) OUT       Transfer Syntax=1.2.840.10008.1.2.4.103
21:03:42 (1041330) OUT   User information
21:03:42 (1041330) OUT     Max length= 65536
21:03:42 (1041330) OUT     Imp UID= 1.2.826.0.1.3680043.1.2.100.8.40.109.8
21:03:42 (1041330) OUT     Imp Name= DicomObjects.NET
21:03:42 (1041330) IN  Association acceptance
21:03:42 (1041330) IN    Initiating AET=DICOM_SERVER
21:03:42 (1041330) IN    Called AET=MY_AE_TITLE21
21:03:42 (1041330) IN    Application Context=1.2.840.10008.3.1.1.1
21:03:42 (1041330) IN    Presentation Context 1
21:03:42 (1041330) IN      Accepted
21:03:42 (1041330) IN        Transfer Syntax=1.2.840.10008.1.2.1
21:03:42 (1041330) IN    User information
21:03:42 (1041330) IN      Max length= 16382
21:03:42 (1041330) IN      Imp UID= 1.2.826.0.1.3680043.9.3811.1.3.1
21:03:42 (1041330) IN      Imp Name= PYNETDICOM_131
21:03:42 (1041330) OUT Association Closed Normally
21:03:42 (1041330) IN  Association Closed Normally
21:03:42 (1041329) OUT PCID = 1
21:03:42 (1041329) OUT (0000,0000) UL : 116 (74H)
21:03:42 (1041329) OUT (0000,0002) UI : 1.2.840.10008.5.1.4.1.2.1.2 (PatientRootQR_MOVE)
21:03:42 (1041329) OUT (0000,0100) US : 32801 (8021H)
21:03:42 (1041329) OUT (0000,0120) US : 1 (1H)
21:03:42 (1041329) OUT (0000,0800) US : 257 (101H)
21:03:42 (1041329) OUT (0000,0900) US : 0 (0H)
21:03:42 (1041329) OUT (0000,1020) US : 0 (0H)
21:03:42 (1041329) OUT (0000,1021) US : 0 (0H)
21:03:42 (1041329) OUT (0000,1022) US : 0 (0H)
21:03:42 (1041329) OUT (0000,1023) US : 0 (0H)
21:03:42 (1041329) IN  Association Closed Normally
21:03:42 (1041329) OUT Association Closed Normally

var cmove = new DicomCMoveRequest(AEServer, studyUID); // AEServer is my server name which listening for a C-STORE request.

var client = new DicomClient();
client.AddRequest(cmove);
client.Send(ip, port, false, AEClient, serverName);  // AEClient is a clinent name.

4

Thanks:  0

Likes:  0

Dislikes:  0

1. 05-24-2010

   
   

   #1

   IR 5050 with error code 801
   

   I have a newly installed IR5050 set up to scan to email. There are twenty destinations set up in the address book. The client is using exchange 2003 and all of the addresses are internal. Each destination can scan successfully when sending a tiff or jpeg. Five of the destinations fail to send when trying to send a pdf. I get an error code NG 801. I also get a message on the copier screen to check the server. Any ideas.

   ---

2. 05-24-2010

   
   

   #2

   I don’t think there is a problem with your ir5050 since you can send PDF’s to 15 out of 20 addresses. Usually copier issues are can’t send anything at all.
   Check your size settings in System settings-> Communication Settings-> E-mail/I-Fax Settings. I would set it to the same size limit as your Global default on the exchange server.

   It’s more likely a lower size limit on just those 5 addresses. Look in the properties for those mailboxes for delivery restrictions. Increase receive size.
   image0101118307817&#.jpg

   Click on pic view it larger

   ---

3. 05-25-2010

   
   

   #3

   Originally Posted by dmclester
   

   I have a newly installed IR5050 set up to scan to email. There are twenty destinations set up in the address book. The client is using exchange 2003 and all of the addresses are internal. Each destination can scan successfully when sending a tiff or jpeg. Five of the destinations fail to send when trying to send a pdf. I get an error code NG 801. I also get a message on the copier screen to check the server. Any ideas.

   #801 [SMTP] Sending to e-mail server
   Cause / Remedy
   -A timeout error occurred during communication with the
   SMTP server to transmit an E-mail, or to transmit/receive
   I-Fax, due to a problem with the server.
   -The from E-mail address is not correct.
   -The SMTP server returned an error while trying to
   connect.
   -The SMTP server rejected the E-mail due to some kind of spam
   policy filtering.
   -Check and verify that the SMTP server is operating properly.
   -Check and verify that the from E-mail address is valid for the
   SMTP server that is being used.
   -Check the network status.
   -The SMTP server might be rejecting the E-mail because of
   some configuration settings that are configured in Canon device,
   try the following:
   Change the subject field to something other then ATTACHED
   IMAGE.
   Select
   Notes:
   Please use Microsoft Outlook Express (DO NOT USE OUTLOOK) from a computer to test, verify and confirm the correct
   requirements for the E-mail server that the customer is trying to use to send E-mail. You can bring up Microsoft Outlook Express by
   clicking START > RUN then type MSIMN and click OK. Then create an E-mail account using the information that was provided to you
   and try to send an email from MS Outlook Express.

   #801 [SMB] Sending to a shared folder
   Cause/ Remedy
   -The destination is full or out of available free space to write to.
   -The user account does not have proper privileges or enough
   disk space quota available for this user account to write to this
   destination.
   -The SMB client setting is not turned ON or not properly
   configured on the copier/machine.
   -Software FIREWALL or Internet Security application on the
   destination computer might be turned ON or not properly
   configured to permit this traffic.
   -The shared folder at the destination computer has folder
   encryption turned on.
   -Check and verify that the destination has enough available
   free disk space.
   -Check and verify that the user account does have proper access
   and disk quota available for writing files to this location.
   -Check and verify that the SMB client protocol is turn ON and
   that the SMB client is properly configured on the copier/machine.
   -Check and verify that there are no software firewalls or Internet
   security applications running on the destination computer and if
   so make sure that they properly configured to permit this traffic .
   -Check and verify that the destination shared folder does not
   have folder encryption turned on. If the customer is not able to
   turn off folder encryption then a new or different folder must be
   shared.

   #801 [FTP] Sending to an FTP server
   Cause/ Remedy
   -You are sending to a destination that you have no write
   permission to.
   -When the machine tried to send to the server, a file with
   the same name already exists on the FTP server and that
   file cannot be overwritten.
   -When the machine tried to send to the server, either the
   folder name is incorrectly specified or the password is
   incorrect.
   -Check that you have write permission to that destination.
   -Check that the destination does not already have a file
   with the same, make sure that the file on the server can
   be overwritten.
   -Check that you are sending to the proper destination and
   that you are entering the correct user name and password
   for that destination

   **Knowledge is time consuming, exhausting and costly for a trained Tech.**

   ---

4. 05-26-2010

   
   

   #4

   Originally Posted by D_L_P
   

   I don’t think there is a problem with your ir5050 since you can send PDF’s to 15 out of 20 addresses. Usually copier issues are can’t send anything at all.
   Check your size settings in System settings-> Communication Settings-> E-mail/I-Fax Settings. I would set it to the same size limit as your Global default on the exchange server.

   It’s more likely a lower size limit on just those 5 addresses. Look in the properties for those mailboxes for delivery restrictions. Increase receive size.
   image0101118307817&#.jpg

   Click on pic view it larger

   Thank you for the info. I set the size on the copier to the same size of the exchange server and added an additional line in the subject and everthing worked fine.

   ---

5. 05-26-2010

   
   

   #5

   Originally Posted by teckat
   

   #801 [SMTP] Sending to e-mail server
   Cause / Remedy
   -A timeout error occurred during communication with the
   SMTP server to transmit an E-mail, or to transmit/receive
   I-Fax, due to a problem with the server.
   -The from E-mail address is not correct.
   -The SMTP server returned an error while trying to
   connect.
   -The SMTP server rejected the E-mail due to some kind of spam
   policy filtering.
   -Check and verify that the SMTP server is operating properly.
   -Check and verify that the from E-mail address is valid for the
   SMTP server that is being used.
   -Check the network status.
   -The SMTP server might be rejecting the E-mail because of
   some configuration settings that are configured in Canon device,
   try the following:
   Change the subject field to something other then ATTACHED
   IMAGE.
   Select
   Notes:
   Please use Microsoft Outlook Express (DO NOT USE OUTLOOK) from a computer to test, verify and confirm the correct
   requirements for the E-mail server that the customer is trying to use to send E-mail. You can bring up Microsoft Outlook Express by
   clicking START > RUN then type MSIMN and click OK. Then create an E-mail account using the information that was provided to you
   and try to send an email from MS Outlook Express.

   #801 [SMB] Sending to a shared folder
   Cause/ Remedy
   -The destination is full or out of available free space to write to.
   -The user account does not have proper privileges or enough
   disk space quota available for this user account to write to this
   destination.
   -The SMB client setting is not turned ON or not properly
   configured on the copier/machine.
   -Software FIREWALL or Internet Security application on the
   destination computer might be turned ON or not properly
   configured to permit this traffic.
   -The shared folder at the destination computer has folder
   encryption turned on.
   -Check and verify that the destination has enough available
   free disk space.
   -Check and verify that the user account does have proper access
   and disk quota available for writing files to this location.
   -Check and verify that the SMB client protocol is turn ON and
   that the SMB client is properly configured on the copier/machine.
   -Check and verify that there are no software firewalls or Internet
   security applications running on the destination computer and if
   so make sure that they properly configured to permit this traffic .
   -Check and verify that the destination shared folder does not
   have folder encryption turned on. If the customer is not able to
   turn off folder encryption then a new or different folder must be
   shared.

   #801 [FTP] Sending to an FTP server
   Cause/ Remedy
   -You are sending to a destination that you have no write
   permission to.
   -When the machine tried to send to the server, a file with
   the same name already exists on the FTP server and that
   file cannot be overwritten.
   -When the machine tried to send to the server, either the
   folder name is incorrectly specified or the password is
   incorrect.
   -Check that you have write permission to that destination.
   -Check that the destination does not already have a file
   with the same, make sure that the file on the server can
   be overwritten.
   -Check that you are sending to the proper destination and
   that you are entering the correct user name and password
   for that destination

   Thank you for the information. I set the size of attachments on the copier to the same as the exchange server and added an additional line on the subject line and it worked fine.

   ---

6. 05-26-2010

   
   

   #6

   **Knowledge is time consuming, exhausting and costly for a trained Tech.**

   ---

7. 05-26-2010

   
   

   #7

   Glad to hear you got it working!

   ---

Tags for this Thread