Problem : to help prevent malicious code from running one or more objects in this form were not loaded

Problem : to help prevent malicious code from running one or more objects in this form were not loaded

Hello,

Some years ago, I developped a custom form which I published in My Organizational Forms Library. The form was designed in Outlook 2000 and I used the Excel object (msowc.dll). The form was still working in Outlook 2003 as long as the msowc.dll was registered.

When I upgraded to Outlook 2003 SP3, I had an error once I closed the form and this was fixed by installing the hotfix 935411.

Now I am not able to open the form. I got the message: “to help prevent malicious code from running one or more objects in this form were not loaded”

I don’t know what happened. I have other users with the same Outlook version and it is working for them

 

Solution: to help prevent malicious code from running one or more objects in this form were not loaded

Here are two options you can try. The first one covers a corrupted cache that might cause the form to fail. The second is a registry entry to specifically allow the form to run.

First:
http://www.pcreview.co.uk/forums/thread-3370960-2.php
Have you done any customizations to the form? The issue might be a corupted
form cache. You could try to clear your forms cache:

goto Tools->Options

Click on Advance Options button
Click on Custom Forms button
Click on Manage Forms button

Click the clear cache button.

Close all the opened dialogs and restart outlook.

Second:
The ideal solution for this issue is to avoid one-off forms completely. If you must use a one-off  and you are using Outlook 2003, you can use a registry entry or policy to control the behavior. (This option is not availble in Outlook 2002 SP3). To use a registry entry, add a DWORD value named AllowActiveXOneOffForms to the HKCU\Software\Microsoft\Office\11.0\Outlook\Security value and set it to one of these values:\

0               Load only the frm20.dll controls, the Outlook View Control, Outlook Recipient Control, and the docsite (message body) control
1               Allow only controls marked as “safe for initialization” to load
2               Allow all ActiveX controls to load