A place for info I've learnt in IT & stuff. (I get a little kick back from affiliate ads & links, just so you are aware)

Browsing Posts tagged Outlook

Very odd one. Appears to be from the upgrade to Windows 10 people are reporting. I’m sure I installed Office 2010 after Windows 10 was installed so shouldn’t of caused an issue.

But anyway. E-mails will just sit in the Out box and never send with errors such as:

Sending reported error (0x800CC13) Cannot connect to the network. Verify your network connection or modem.

Being throw back.

Simple fix in the end it appears. Run CMD as Admin and type sfc /scannow

Once scan is finished it appears to fix the issue.

Press windows key an x to get an admin user command prompt



sfc /scannow

Any one of the following will prevent email notifications from being sent:

You have added a Delegate and selected ‘Send meeting requests and responses only to my delegates, not to me’. (e.g., Tools | Options | Delegate).
You have your calendar set to auto-accept meeting requests.
You set ‘Author’ permissions on your calendar. This allows a person to open your calendar by choosing ‘Open a Shared Calendar’ and schedule a meeting directly on your calendar. Therefore, no email notification is sent.


Check the e-mail sort you may have set, that can end up putting all the calender notifications at the bottom of all your e-mails.

UPDATE:  This is now fixed as YouTube have added the http:// to the SRC addresses now to stop Outlook thinking it’s a network path.



If you attempt to open and e-mail from YouTube recently in Outlook you’ll probably get what seems to be a lock-up and sometimes a complete Outlook crash.  Most of the time it’s just timing out.  Why is this happening?  With the help of Process Monitor and some pointers from Mark Russinovich from Microsoft and creator of the great series of talks The Case Of The Unexplained it appears to be the way Outlook handles “//” tags.

While opening the e-mail Outlook, after a while frozen, would pop up the below message.  Why was it trying to look at a network address \\ when is clearly a http address.

Running Process Monitor and putting some filters on it’s capture I found this:


As you can see Outlook is trying to look for a file at \\\i\ and not finding it so timing out.   Sending the findings to Mark Russinovich for his Case Of The Unexplained talks he replied, after I sent a copy of the e-mail so he was able to recreate it, that it’s the table in the e-mail that is trying to load the avatar’s people use:

<td bgcolor=”#FFF” align=”left” width=”50″>
<img src=”//

v=4fc532bd” height=”50″ width=”50″>
<td width=”16″></td>


Turns out Outlook is interpreting the “//” as a file server and attempting to find it, but obviously failing.

Only way around it at the moment is turning off HTML on all e-mails or just moving the file to a junk folder, which also turns off all html but just in that e-mail.

Points to

Which is

Here’s what I found with the docmd.sendobject command. User XXXX is using Outlook 2003. Outlook 2003 has changed their security for sending emails with an attachment. For vba code, the docmd.sendobject command cannot be utilized with the Edit Message set to True and the “TO” left blank. A “TO” must be supplied and the Edit Message must be set to “False” in the vba code (at least to my knowledge so far).
Once these parameters are supplied in the vba command and a user clicks on the button to send the attachment, a message box will appear stating to the effect: “A program is trying to send an attachment on your behalf. Do you want to allow this?” and a progress bar appears. Once the progress bar has reached the end, the Yes box is enabled where the user must click Yes in order to complete the email.

For example, this (where me!EmailTo = the email address):

DoCmd.SendObject acReport, stDocName, “RichTextFormat(*.rtf)”, Me!EmailTo, “”, “”, “Some message”, “”, True, “”

will give the error 2293

whereas this:

DoCmd.SendObject acReport, stDocName, “RichTextFormat(*.rtf)”, Me!EmailTo, “”, “”, “Some Message”, “”, False, “”

does not.

Oh, and this issue seems to be Outlook service pack related.


When using Word as your e-mail editor you might encounter the error “Interface Not Registered” when trying to send your e-mail. As a result you are unable to send it but you are able to send e-mail when setting Outlook as your e-mail editor. To solve this so you are able to use Word as your e-mail editor close all running Office applications. Then use Start-> Run and type;

Regsvr32.exe %Windir%\System32\Ole32.dll

This will correctly register the ole32.dll file in the registry.

Out of Office Assistant – Command is not available

Unable to set or edit “Out of Office Assistant”
Users get the following error:Â The command is not available. See the program documentation about how to use this extension.

Open Outlook.
Click on Help.
Click on About Microsoft Outlook.
Click on the Disabled Items entry.
You will see a Disabled Items window open, with the following information within it:

The items below were disabled because they prevented Outlook from functioning correctly.
Please note that you may have to restart Outlook for these changes to take place.

Select the ones you wish to re-enable.
If you see “Addin: outex.dll (outex.dll)” listed, click on it to highlight it and then click on the Enable button. Then click on the Close button. Then click on the OK button to close the About Microsoft Office Outlook window.

When you reply to an e-mail message in Microsoft Office Outlook 2003, your e-mail signature does not appear in the e-mail message. You experience this symptom even if you configured Outlook 2003 to include an e-mail signature every time that you reply to or forward an e-mail message.
Back to the top
This problem occurs if you configured Outlook 2003 to use the Attach original message option when you reply to an e-mail message. If the original text of the e-mail message is not included in the reply, the reply header data is not created. In this situation, Outlook 2003 cannot determine when to add an e-mail signature to the e-mail message.

Service pack information
This problem is corrected in Office 2003 Service Pack 3. To resolve this problem, obtain the latest service pack for Office 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
870924 How to obtain the latest service pack for Office 2003