monreale...
Hello again!
Assuming that your email account is actually through comcast.net
and you are able to finally send the emails from Outlook Express,
as you mentioned, the problem here is simply one of timing.
The error code you're getting simply indicates that, for the
moment, your email could not be sent through the server you
have designated. If you are able to send it later, through
Outlook Express, using the same account as indicated in the
error message, then it was simply a matter of your email server
being unavailable at the time you tried to send it originally.
When you send email via Wordpad, it actually opens an email in
Outlook Express, and attaches the document, in rtf. format, to
an email from OE. When you click 'send', you are sending from
OE. The only thing that would cause an error at this point is
the temporary unavailability of your email server - in this case
the Comcast server. This can occur because of a temporary glitch
in your connectivity with your ISP (internet service provider),
which is also Comcast, or because, even though your internet
connection is OK, the email server of your ISP is temporarily
unavailable.
The fact that you are able to send the emails at a later time
indicates that your basic parameters for connection and email
are not at fault, and that the ISP and email connections are
functional at that later time.
This has nothing at all to do with Wordpad, but is simply a
temporary problem with either your connection with your ISP
or with their email server.
The very first time I tried sending a message from Wordpad,
subsequent to your question, I encountered the same error,
and the message I had tried to send was to be found in the
Outbox in OE. I then clicked "Send and Receive All" in OE,
and the message was sent. The next several times I sent a
message from Wordpad, it was sent without a glitch.
I hope that satisfies your interests in posing this question.
Please do not rate this answer until you are satisfied that
the answer cannot be improved upon by way of a dialog
established through the "Request for Clarification" process.
sublime1-ga |
Request for Answer Clarification by
monreale-ga
on
30 Mar 2005 10:13 PST
Plausible but not persuasive. Reason: It's not sporadic but all the
time. Meanwhile, everything else on my computer, including the "send"
function in OE, is working normally. Pls. take another look. Thanks,
sublime.
|
Clarification of Answer by
sublime1-ga
on
30 Mar 2005 11:30 PST
monreale...
If what I've written hasn't helped to resolve the issue,
I'll need to know a lot more about how your situation
differs from my description.
The fact is, when you select File -> Send from Wordpad,
you open an outgoing email in Outlook Express, with the
Wordpad document attached as an .rtf file, and you are
no longer dealing with the functionality of Wordpad at
that juncture. The next steps to completing the process
of emailing the document are to fill in the Subject,
the email address to which you're sending the document,
and then to click the 'Send' icon at the top left of the
email window.
At that point, you are sending from OE, and any message
you receive pertains to it. If the message is not sent
immediately, due to an error, that's why it is being held
in your Outbox. Yet, if you are able to send them later,
again, this indicates that there is no problem with your
basic account settings (at all) or your connection (at
that time). The only reason for them not to be sent
immediately is that the connection was not available at
the time you originally tried to send, or because you
didn't hit the Send button, but did something else, which
caused the email to be held in the Outbox rather than sent.
If the process you are using differs in the slightest from
what I've described above, I'll need to know in exact detail
the manner in which your process for sending email from
Wordpad differs from my description.
You've said: "This error message appears when I click 'send.'"
and I can only assume that this is when you are clicking the
Send icon at the top left of the window which opens subsequent
to selecting File -> Send in Wordpad. That window is an email
in Outlook Express, which you can verify by looking at the
Title Bar. It will say New Message until you type in the Subject
field of the email, at which point you will see the words you
type into the Subject field appear in the Title Bar.
If you are using some other method than selecting File -> Send
in Wordpad, I will need to know that. I don't see any other way
to 'Send' from Wordpad, and when I do this, the window that
opens at that point is an email from OE, as described above.
Let me know precisely how your experience differs from this.
sublime1-ga
|
Clarification of Answer by
sublime1-ga
on
30 Mar 2005 11:40 PST
P.S.
It occurs to me that one thing which might cause the email
to be held upon hitting Send is if there is some error which
would normally cause an error message window if you were truly
starting from OE vs Wordpad. There could be some functional
differences (e.g., when you select File -> Send from Wordpad,
the email window which opens doesn't have a 'minimize' symbol
at the top right of the window, as it would if you opened a
new email from OE, directly).
So it might be that, if you failed to fill in the Subject field
in the email opened from Wordpad, which would normally cause a
dialog box to open, if you were in Outlook Express, asking if
you'd like to add something to the subject line, this might
cause an error in which, rather than opening a dialog box, it
simply consigns the un-titled email to the Outbox.
The error message you're receiving doesn't match this description,
but I thought it might be worth including as a consideration.
sublime1-ga
|
Request for Answer Clarification by
monreale-ga
on
01 Apr 2005 13:11 PST
The sequence of events you outline is precisely what I follow,
sublime, but there's one more curious thing, When the email is ready
to go, the text is formatted as a Word attachment. When I click to
open it (before sending), Word opens the mail attachment but with the
following error message: "Microsoft Visual C++ Runtime Library.
Runtime error. Program: C:\Program Files\Microsoft Office\Office
10\WINWORD.EXE. Abnormal program termination."
Hope this helps.
|
Clarification of Answer by
sublime1-ga
on
01 Apr 2005 14:56 PST
monreale...
The .rtf file you're attaching to an OE email is actually a
Wordpad document (created by Wordpad), but the default program
to open such a file is Word, so it will appear as an attachment
in the email with a Word icon next to it, and when you click on
it, Word will be the program to open it. It does so on my system,
with no error message.
The error message you mention is addressed in this Microsoft
Knowledge Base Article, and, with any luck, addressing this
issue with the recommended fixes will also resolve the error
you're seeing when you try to send the email. They may,
however, be totally unrelated.
Also, You don't indicate whether you *routinely* open the .rtf
file attachment prior to attempting to send the email. If this
is the case, you might try sending the email without opening
the file prior to doing so. It's possible that, once Word gets
hold of the file (with or without the termination error you
mention), it alters the nature of the attachment, and creates
a send error in terms of immediate dispatch, which is somehow
resolved by the time you find the unsent messages in your
Outbox at a later time.
And, in regard to that last sentence, you note that you find
these messages in the Outbox when you later go to shutdown
Outlook Express. My guess is that this must be fairly soon
after you quit Wordpad, since OE is set to "Send & Receive
All messages" every 10 minutes or so, and any messages in
the Outbox would be automatically sent at that time.
If your OE program isn't set up this way (mine is, but I
don't now remember is 10 minutes is the default setting,
or simply what I've set it to), it's easy enough to do so:
Go to Tools -> Options, and on the General tab, under
Send/Receive Messages, check the box next to "Check for
new messages every [select 10 minutes].
Under the Send tab, check the box next to "Send messages
immediately".
If your version of OE is slightly different than mine,
you might have to browse around for these settings in a
different location.
Let me know where this takes you...
sublime1-ga
|
Clarification of Answer by
sublime1-ga
on
01 Apr 2005 14:58 PST
Oops...
Here's the link to the Microsoft Knowledge Base Article
I mentioned:
http://support.microsoft.com/default.aspx?scid=kb;en-us;320475
|
Request for Answer Clarification by
monreale-ga
on
02 Apr 2005 16:20 PST
sublime...
I do not routinely open the .rtf file attachment before attempting to send email.
I've set OE to check for new messages every 10 minutes. It was already
set to send messages immediately.
I'm not competent to search for a solution by working through the
routines in the Microsoft Knowledge Base Article you suggested.
Do you believe you've done what you can with this problem at this
point? Or perhaps you believe the payment offered is inadequate for
the time required? Please give me your frank assessment of where we
should go from here. Thanks.
|
Clarification of Answer by
sublime1-ga
on
02 Apr 2005 17:52 PST
monreale...
As far as the error message of the original issue, I'm stymied
in finding any correlation between that message and your use
of Wordpad. Simply put, it's a connection error, originating
from Outlook Express. As to why this error occurs apparently
only in conjunction with sending from Wordpad, this remains a
mystery beyond my knowing or research.
As to the runtime error in Winword when you open the .rtf
attachment, that's unrelated to, and beyond the scope of the
original question, since you've verified that you don't
routinely open the .rtf file prior to sending the email,
which means that Word's involvement with the file is not
connected to the problem sending the email.
As for the fixes for that issue in the Microsoft Knowledge
Base Article, the recommended solutions are offered in a
sequential order, with the most likely fix offered first.
Renaming the normal.dot template is the first and most likely
solution, and a link is given to another MS article where the
exact steps are outlined:
http://support.microsoft.com/kb/319154/
I won't reiterate the 8 steps outlined there, but if you
follow them precisely, it may resolve the runtime error.
Be aware of the note that is made about this process:
"When you Rename Normal.dot, a global template, it will
reset some options to their default settings. These
options include custom styles, custom toolbars, macros,
and AutoText entries. Therefore, we strongly recommend
that you do not delete your Normal.dot file."
By only renaming it, thus prompting the creation of a new
one, you will retain the option of deleting the new one and
remaming the old one, thereby restoring any preferences,
if you find that the procedure doesn't resolve the runtime
error.
The other solution I would explore is the possibility that
Norton Antivirus is somehow related to the runtime error,
or even the email send error. If you have Norton installed,
you can explore this simply by disabling or shutting down
Norton, which you can probably do by right-clicking the
icons of any Norton utilities which are running in the
System Tray to the right of your Taskbar. Then try both
sending an email from Wordpad and opening the .rtf file
prior to sending, and see if both errors still occur.
You asked for a frank assessment of payment vs time spent,
and I can certainly say that I've spent much longer on this
than I anticipated for the 75% of the question price that I
earn by answering. However, much of that time has been due
to my inability to satisfactorily resolve your problem with
my initial efforts, so I don't count that as your responsibility.
Best regards...
sublime1-ga
|
Request for Answer Clarification by
monreale-ga
on
03 Apr 2005 20:30 PDT
sublime...
I find that when I disable Norton Internet security I can send an
email fron Wordpad without triggering the email send error. Do you
know how to tweak Norton so I can get get this same result without
disabling Norton? (For what it's worth, I didn't have this problem
before re-installing Wordpad.)
As to the runtime error in Winword, I've eliminated that by installing
Office 2003. I had Office 2002.
|
Clarification of Answer by
sublime1-ga
on
03 Apr 2005 23:13 PDT
monreale...
So glad to hear we're making progress! I don't own Norton
and could only suggest that you seek support directly from
them, as my research doesn't indicate a simple fix for this.
What my research and experience do suggest is that Norton
is well-known for not playing well with others, especially
those programs that interact with the internet, and is
specifically known to cause the 0x800CCCOD error with
Outlook Express.
Honestly, the most common means of resolving this is to
choose another antivirus program. There are numerous free
ones available which typically find problems (viruses)
overlooked by Norton.
I've personally explored several of these before settling
on AntiVir, which not only scans for viruses via a context
menu in Windows Explorer, and when you schedule it to scan
part or all of your disk drives, but it also has a Guard
program which is indispensible for catching and preventing
hidden malicious downloads (trojans) from websites you might
visit, doing this 'on the fly'. I run into at least one of
these a week, and wouldn't otherwise have a clue as to their
existence.
AntiVir:
http://www.free-av.com/
I know that you probably paid for Norton Internet Security,
and that it has other components besides the antivirus, but
honestly, after all the incompatibility stories I've heard
with regard to Norton, I would simply obtain free components
which are readily available on the internet, and known to
cause less problems.
For a firewall, e.g., I'd use the free version of ZoneAlarm:
http://www.zonelabs.com/store/content/company/products/znalm/freeDownload.jsp?lid=dyncomp_za
If you're determined to keep using Norton, you might see if
you can determine which part of the program is monitoring
your email for viruses, and see if you can disable only that
part of the program, and if that adjustment allows you to
send email from Wordpad without shutting down the whole of
the Norton suite. It's quite possible that the email component
of Norton Internet Security is monitoring not only incoming,
but outgoing mail (especially with attachments), and is the
component causing the problem.
Let me know where this takes you, and what else I can do
for you. Since you asked earlier for frank feedback regarding
compensation, at this point, having achieved some degree of
success with your original question, and with the additional
runtime error, I would be appreciative if, when you feel we've
arrived at a suitable conclusion, you saw fit to include a tip
which seems appropriate to you.
Best regards...
sublime1-ga
|
Request for Answer Clarification by
monreale-ga
on
09 Apr 2005 15:04 PDT
sublime...
I disabled the Norton component that scans outgoing email but that
didn't solve the problem. I'm considering your advice to choose
another antivirus program.
The solution we've found for the original problem, i.e., disabling
Norton each time, is unwieldy but not useless. And certainly, you've
made a diligent and professional effort. So I'll say thanks, and call
it a day.
|
Clarification of Answer by
sublime1-ga
on
09 Apr 2005 15:22 PDT
monreale...
Thanks very much for the tip. I'm sorry a perfect solution
couldn't be found, but that's the risk involved in trying
to solve computer problems at a distance.
Best regards...
sublime1-ga
|
