Share via

Installer cannot save the digital signature at this time - Error

Anonymous
2023-10-07T21:58:18+00:00

Hi All,

Hope all is well.

I am using Ms Access 2016 and when I try to sign the VBA code I get the above error. If I move the same file that contains the VBA code to a machine that is running office 365, I am able to sign the VBA code.

Why am I getting the "Installer cannot save the digital signature at this time" error on the machine that is running Ms Access 2016, Version 2309 (Build 16827.20130 Click-to-Run)?

Thanks and kind regards

Annesly

Microsoft 365 and Office | Access | Other | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

George Hepworth 22,855 Reputation points Volunteer Moderator
2023-10-21T13:06:07+00:00

Thank you.

I thought Karl was quite clear in his statement:

"Microsoft so far only offers a meager documentation, which is also somewhat misleading regarding the versions, because it is possible to sign file formats from Access 2013 upwards (apparently even from the unsupported 2007/2010), but only with Access 365, which was the sole version to get the new signing built in."

"... it is possible to sign file formats from Access 2013 upwards (apparently even from the unsupported 2007/2010)..."

So, yes, other accdb formats can be digitally signed.

"... but only with Access 365, which was the sole version to get the new signing built in."

So, yes, you can only implement the version of signing only if you have the appropriate Access 365.

Colin Riddington provides a rather more extensive discussion, but again, nothing that suggests the ability to use earlier versions of Access. I doubt he would have left that out, knowing how thoroughly he does his research.

On the other hand, the MS documentation here does include information on finding and creating self certs in earlier versions. And here it is, the telling statement in this documentation:

"All versions of Access allow you to apply a digital signature to the components in .mdb and .mde database formats. Starting with Access for Microsoft 365 Version 2211, .accdb and .accde database formats are also supported."

To me, that suggests you should probably not anticipate a change to those earlier versions of Access, i.e. prior to MS 365 where it was introduced.

Never say never, of course, but I wouldn't plan future development around the possibility that MS will deviate from prior practice.

Was this answer helpful?

1 person found this answer helpful.
0 comments

10 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-10-20T22:43:06+00:00

    Thanks Sola,

    I have been doing some research on the topic and it seems only office 365 has been given the option to code sign at this moment. Does anyone know if code signing in Ms access 2016 will be introduced?

    Thanks

    Annesly

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-10-08T22:50:49+00:00

    Hi,

    Unfortunately, I do not have any more troubleshooting to offer, there are knowledgeable experts on the platform and I hope someone else will take a look at your issue.

    Thanks, Sola

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-10-07T23:18:56+00:00

    Hi Sola,

    Thank you for your prompt reply.

    I do not believe this is a windows issue, it looks like a Ms Access 2016 issue due to the following:

    • If I open Ms Access 2016 and go to save Package and Sign, then I am able to sign with the digital signature.
    • The error is when I try to sign the VBA code in Ms Access by opening Database Tools/Visual Basic/Tools/Digital Signature and then trying to sign the VBA code the error occurs.

    By the way I am running Windows 11 Home

    Kind regards

    Annesly

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-10-07T22:40:03+00:00

    Hi AnneslyRayan,

    Thanks for contacting us and sorry for the inconveniences, Here are some possible solutions that you can try:

    • Perform a system restore to a previous point when the VBA code signing was working. This may undo any changes that might have caused the error. To do this, follow these steps:
      • Hard restart your computer and keep pressing F8 numerous times as the system is booting up.
      • Select the Troubleshoot option.
      • Now, click the Advanced options.
      • Select System Restore and choose a restore point.
      • Follow the on-screen instructions to complete the process.
    • Repair the boot manager of your system. This may fix any issues with the digital signature verification. To do this, follow these steps:
      • Insert your Windows 10 disc into the disc drive and restart the computer.
      • Press the F key that corresponds to your system recovery boot (if any).
      • Choose Repair your computer from the menu.
      • Select Troubleshoot > Advanced options > Command Prompt.
      • Type the following commands and press Enter after each one:
        • bootrec /fixmbr
        • bootrec /fixboot
        • bootrec /scanos
        • bootrec /rebuildbcd
      • Restart your computer and try to sign the VBA code again.
    • Temporarily disable the digital signature enforcement on your system. This may allow you to sign the VBA code without getting the error. However, this is not recommended as it may expose your system to security risks. To do this, follow these steps:
      • Restart your computer and press F8 repeatedly until you see the Advanced Boot Options menu.
      • Select Disable Driver Signature Enforcement and press Enter.
      • Try to sign the VBA code again.

    I hope this helps!

    Regards, Sola

    Was this answer helpful?

    0 comments