When I restarted Outlook, I had to give permission to various certificates, but it was very straightforward to check that each was genuine.īy the way, I had tried various settings of the security level before, but none of them had worked.ģ. After closing and relaunching Outlook a couple of times, I set the Trust Centre's Macro Settings to 'Notifications for all macros' - I'm not sure whether this was the best choice, but it has worked. I deleted the project file as you advised, and everything returned to what it was before I started fiddling with VBA macros. Windows on 64-bit desktop, with ESET Smart Security 9, and VPN by Private Internet Accessįixed! And it all survived reboot! (And apologies for mucking up the reply a few minutes ago.)ġ. Does anyone have any clues about all this? I know that Windows is obscure, but I have never struck anything like this - it's held me up for hours. QUESTION: Presumably I am doing something wrong with the Certificate, but I have googled obessively and read numerous blogs on the subject, and tried all sorts of suggestions proposed there, and I can't sort it out. Thus I am completely stuck, because I cannot even go back to where I was before I started doing all this. I've also set 'MacroSettings' temporarily to the lowest level, which one would expect should bypass certificates. There are now no macros to display, yet every time I start Outlook, I get the same error message, despite the fact that I keep trying to sign Project1 with my certificate. So I deleted the macro, intending to go back to 'Outlook-out-of-the-box' (but understandably I cannot delete Project1). Macros will be disabled.' Then whenever I went into the VBA editor, I found that the project was unsigned again.ĥ. Every time I opened Outlook, however, I got the error message, 'An error occurred while attempting to verify the VBA project's signature. Then I exited Outlook, saving the project.Ĥ. In Outlook's VBA editor, I signed Project1 with this certificate. I was unable to copy it into '(Local Computer)/Trusted Root Certification Authorities'.ģ. Then using MMC, I found the new certificate in 'Current User/Personal' and copied it (right-click Copy, then right-click Paste) into 'Current User/Trusted Root Certification Authorities'. It worked well, briefly, then it wanted a certificate.Ģ. On a brand-new home installation of Office 365 (currently 2016), I opened Outlook and created three new calendars, then copied the very nice Slipstick VBA macro to open Outlook at the calendar with two calendars selected, adapting the cases in the macro in the obvious way.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |