Произошла ошибка при попытке подтверждения подписи проекта vba

Having come across this just now, this is how I ultimately solved it (none of the other suggestions worked for me):

1. Create a self cert – I called mine “Self Cert” (generated from here in Office 2013 — C:Program Files (x86)Microsoft OfficeOffice15SELFCERT.EXE)
2. Run certmgr.crt from the start menu and copy “Self Cert” from “PersonalCertificates” to the “Trusted Root Certification AuthoritiesCertificates” folder
3. Open Outlook.exe as Administrator
4. Open VBA (i.e. Developer -> Visual Basic)
5. Open your module containing the VBA code
6. Select Tools -> Digital Signature -> Choose…
7. Select OK to select “Self Cert” (VB then shows the project as being signed with this certificate) then click OK again accept and close the window
8. Click to save the macro in VBA – actually click the save button in VB (bizarrely it breaks if you don’t expressly save here)
9. Close VBA
10. Close Outlook, and choose Yes to save the VBA project
11. Restart Outlook.exe again as Administrator
12. Either now, or after you go “Developer -> Visual Basic” again, a window should pop-up prompting you about the newly signed macro – I clicked remember and don’t prompt again
13. Macros should now work! I’m using them as part of an email rule and this now processes perfectly.

I’m not strictly sure you need to run Outlook as an administrator in the above, but it now works without being run as an administrator so I’m happy.

Thanks to this resource for getting this working for me! I’ve basically just updated, consolidated and expanded on answers given. https://social.technet.microsoft.com/Forums/en-US/07f0158c-085b-4031-93a1-c9d047cf855c/unable-to-sign-outlook-2010-vbaproject?forum=outlook

answered Jan 23, 2018 at 22:28

Ok, I found the reason for my problem:

(1) The Certificate nameofmycert by selfcert.exe was assigned to my VBA project.

(2) However I didn’t assign it to a trusted authority, like seen in: https://technet.microsoft.com/en-us/library/cc754841.aspx#BKMK_addlocal

(3) Outlook was set to allow all macros (not only digitally signed). Anyhow it found that my VBA project was certified, but was not sure if the cerification is correct, because of (2). Therefore it deactivated all macros.

(4) In VBA/Tools / Dignital Signature it appeared:

Certificate name: [no certificate]
Sign as: nameofmycert

The remove-botton was deactivated.

Solution:

(1) VBA/Tools / Digital Signature

(2) Click on Choose .. and select a cerificate. Then the remove-botton is activated.

(3) Click on Remove Certificate

(4) Save VBA project

(5) Restart Outlook

answered Jun 9, 2015 at 14:58

answered Jun 3, 2015 at 12:44

Having come across this just now, this is how I ultimately solved it (none of the other suggestions worked for me):

1. Create a self cert – I called mine “Self Cert” (generated from here in Office 2013 — C:Program Files (x86)Microsoft OfficeOffice15SELFCERT.EXE)
2. Run certmgr.crt from the start menu and copy “Self Cert” from “PersonalCertificates” to the “Trusted Root Certification AuthoritiesCertificates” folder
3. Open Outlook.exe as Administrator
4. Open VBA (i.e. Developer -> Visual Basic)
5. Open your module containing the VBA code
6. Select Tools -> Digital Signature -> Choose…
7. Select OK to select “Self Cert” (VB then shows the project as being signed with this certificate) then click OK again accept and close the window
8. Click to save the macro in VBA – actually click the save button in VB (bizarrely it breaks if you don’t expressly save here)
9. Close VBA
10. Close Outlook, and choose Yes to save the VBA project
11. Restart Outlook.exe again as Administrator
12. Either now, or after you go “Developer -> Visual Basic” again, a window should pop-up prompting you about the newly signed macro – I clicked remember and don’t prompt again
13. Macros should now work! I’m using them as part of an email rule and this now processes perfectly.

I’m not strictly sure you need to run Outlook as an administrator in the above, but it now works without being run as an administrator so I’m happy.

Thanks to this resource for getting this working for me! I’ve basically just updated, consolidated and expanded on answers given. https://social.technet.microsoft.com/Forums/en-US/07f0158c-085b-4031-93a1-c9d047cf855c/unable-to-sign-outlook-2010-vbaproject?forum=outlook

answered Jan 23, 2018 at 22:28

Ok, I found the reason for my problem:

(1) The Certificate nameofmycert by selfcert.exe was assigned to my VBA project.

(2) However I didn’t assign it to a trusted authority, like seen in: https://technet.microsoft.com/en-us/library/cc754841.aspx#BKMK_addlocal

(3) Outlook was set to allow all macros (not only digitally signed). Anyhow it found that my VBA project was certified, but was not sure if the cerification is correct, because of (2). Therefore it deactivated all macros.

(4) In VBA/Tools / Dignital Signature it appeared:

Certificate name: [no certificate]
Sign as: nameofmycert

The remove-botton was deactivated.

Solution:

(1) VBA/Tools / Digital Signature

(2) Click on Choose .. and select a cerificate. Then the remove-botton is activated.

(3) Click on Remove Certificate

(4) Save VBA project

(5) Restart Outlook

answered Jun 9, 2015 at 14:58

answered Jun 3, 2015 at 12:44