Hmm, the problem is that the machine running IMS and CF hangs stalls
whenever a large mailing is going out.  I've traced it to the service (this
shows up in the POST Log)

Error Occurred While Processing Request Error occurred while attempting to
start service.

Windows NT error number 1056 occurred.

Unfortunately, when this happens the machine becomes basically unusable
until CF is restarted.  This means that all the other processes that write
to the queue fail, and basically it's a big disaster.

The advantage to a network drive is that even if CF/IMS is failing, the
messages get properly queued.

I guess a better question would be: How can I stop the 1056 Errors from
happening?  And I'd encourage you to support networked drives, for the
reasons mentioned above.

Thx,

Tac


----- Original Message -----
From: "Howie Hamlin" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Monday, March 25, 2002 4:33 PM
Subject: Re: [iMS] IO Error 103


> I'm not sure why that would happen.  However, we do not support the
outgoing queue on anything but a local drive.
>
> Regards,
>
> Howie
>
> ----- Original Message -----
> From: "Tac/Smokescreen" <[EMAIL PROTECTED]>
> To: "inFusion Support List" <[EMAIL PROTECTED]>
> Sent: Monday, March 25, 2002 3:30 PM
> Subject: Re: [iMS] IO Error 103
>
>
> > Same (periodic) problem with UNC:
> >
> > 0: 03/25/2002 03:25:57 PM [011] Send mail start for message (Priority 1)
> > 1: 03/25/2002 03:25:57 PM [011] Error reading mail file
> > (\\CANCUN\U_DRIVE\imsqueue\A4A320C71FF01C4B8BE7.mbx): I/O error 103
> > 2: 03/25/2002 03:25:57 PM [011] Completed Processing
> > 3: 03/25/2002 03:25:57 PM [011] Rescheduling:
> > 20020325154557/E8016D70CEC9D24BB9FF_A4A320C71FF01C4B8BE7.mail
> > 4: 03/25/2002 03:25:58 PM Current Post Queue status (8 records in all
> > queues) [0,8,0,0,0,0,0,0,0,0]
> > 5: 03/25/2002 03:25:58 PM Next queued mail is scheduled for 03/25/2002
> > 03:26:30 PM
> >
> > Ideas?  I'm not seeing other network failure messages -- this is the
drive I
> > use frequently for shared information.
> >
> > Tac
> >
> > ----- Original Message -----
> > From: "Howie Hamlin" <[EMAIL PROTECTED]>
> > To: "inFusion Support List" <[EMAIL PROTECTED]>
> > Sent: Monday, March 25, 2002 2:09 PM
> > Subject: Re: [iMS] IO Error 103
> >
> >
> > > That error means that the file is not open - which means that the
server
> > could not open the file.  I would suggest using UNC
> > > mappings instead of drive letter mappings although this may not solve
the
> > problem (this may be due to network errors).
> > >
> > > Regards,
> > >
> > > Howie
> > >
> > > ----- Original Message -----
> > > From: "Tac/Smokescreen" <[EMAIL PROTECTED]>
> > > To: "inFusion Support List" <[EMAIL PROTECTED]>
> > > Sent: Monday, March 25, 2002 1:55 PM
> > > Subject: [iMS] IO Error 103
> > >
> > >
> > > > What could be causing IO Error 103?  I thought it might be because
the
> > files
> > > > are on a networked drive, but I've made sure that Cold Fusion and
all
> > the
> > > > IMS products are logged in with full permissions.  And most stuff
works,
> > so
> > > > the periodic messages are very odd:
> > > >
> > > > 0: 03/25/2002 01:49:51 PM [001] Send mail start for message
(Priority 9)
> > > > 1: 03/25/2002 01:49:51 PM [001] Error reading mail file
> > > > (u:\imsqueue\416FF361EE3FD61180E0.mbx): I/O error 103
> > > >
> > > > Drive U is mapped, and as I said, the messages are mostly going out,
but
> > > > sometimes this message shows up.  What is Error 103?
> > > >
> > > > Tac
> > > >
> > > >
==^=======================================================
     This list server is Powered by iMS
   "The Swiss Army Knife of Mail Servers"
   --------------------------------------
To leave this list please complete the form at 
http://www.coolfusion.com/iMSSupport.cfm
Need an iMS Developer license?  Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [email protected]
==^=======================================================


Reply via email to