S
Sue
Hello all,
I've been having a very annoying problem with my macros in Outlook,
and I can't seem to find a solution on Microsoft's Support site, or in
any of my Google newsgroup searches - I found plenty of other people
with my problem, but no solution. Anyway, I know it's a longshot, but
I'm hoping that someone out there has a solution and I just haven't
been able to find it in my searches. Let me apologize in advance for
the length of this post, but I figure the more information the gurus
have to work with, the better.
First, here's a bit of background. I've created several macro tools
in Outlook XP that I use quite often. Because I have macros, I
receive a macro warning whenever I open Outlook due to the security
settings. To eliminate this warning, I created a self-signed digital
certificate using the selfcert.exe tool that comes with Office XP, and
used this to sign my macro VBA project.
Now here's the problem. For some reason, Outlook periodically "drops"
the digital signature from my VBA project. I attempted to sign the
project again using my same self-signed digital certificate, but
received the error "There was a problem with the digital certificate.
The VBA project could not be signed. The signature will be discarded."
Now, I don't think that there is a problem with this certificate,
since I use the same one to sign my Word macros, so this problem seems
to be related to Outlook.
Well, I decided to create a new self-signed digital certificate using
the selfcert.exe tool, since I couldn't get around this problem with
the current certificate. Unfortunately, when I tried to run
selfcert.exe, I received a most unhelpful error message of "Could not
create a certificate."
After scanning Google newsgroups, I found a solution that involves
using the makecert.exe tool directly (selfcert.exe is sort of a
"front-end" to makecert.exe). This worked and I was able to create a
new certificate and sign my VBA project.
Unfortunately, Outlook has once again "dropped" the digital signature
from my VBA project. And this time, neither selfcert.exe, or
makecert.exe will work. In fact, makescert.exe now gives me the very
odd error "Error: Can't create the key of the subject ('JoeSoft')."
And "JoeSoft" is not one of my makecert.exe parameters.
I've tried repairing and reinstalling Office XP, removing the Digital
Signature for VBA Projects component from Office XP and then
reinstalling it, and completely rebuilding my Outlook VBA project
using a new VbaProject.OTM file. I am now out of ideas. Has anyone
else had this problem, and if so, how do I fix it?
Thanks,
Sue
I've been having a very annoying problem with my macros in Outlook,
and I can't seem to find a solution on Microsoft's Support site, or in
any of my Google newsgroup searches - I found plenty of other people
with my problem, but no solution. Anyway, I know it's a longshot, but
I'm hoping that someone out there has a solution and I just haven't
been able to find it in my searches. Let me apologize in advance for
the length of this post, but I figure the more information the gurus
have to work with, the better.
First, here's a bit of background. I've created several macro tools
in Outlook XP that I use quite often. Because I have macros, I
receive a macro warning whenever I open Outlook due to the security
settings. To eliminate this warning, I created a self-signed digital
certificate using the selfcert.exe tool that comes with Office XP, and
used this to sign my macro VBA project.
Now here's the problem. For some reason, Outlook periodically "drops"
the digital signature from my VBA project. I attempted to sign the
project again using my same self-signed digital certificate, but
received the error "There was a problem with the digital certificate.
The VBA project could not be signed. The signature will be discarded."
Now, I don't think that there is a problem with this certificate,
since I use the same one to sign my Word macros, so this problem seems
to be related to Outlook.
Well, I decided to create a new self-signed digital certificate using
the selfcert.exe tool, since I couldn't get around this problem with
the current certificate. Unfortunately, when I tried to run
selfcert.exe, I received a most unhelpful error message of "Could not
create a certificate."
After scanning Google newsgroups, I found a solution that involves
using the makecert.exe tool directly (selfcert.exe is sort of a
"front-end" to makecert.exe). This worked and I was able to create a
new certificate and sign my VBA project.
Unfortunately, Outlook has once again "dropped" the digital signature
from my VBA project. And this time, neither selfcert.exe, or
makecert.exe will work. In fact, makescert.exe now gives me the very
odd error "Error: Can't create the key of the subject ('JoeSoft')."
And "JoeSoft" is not one of my makecert.exe parameters.
I've tried repairing and reinstalling Office XP, removing the Digital
Signature for VBA Projects component from Office XP and then
reinstalling it, and completely rebuilding my Outlook VBA project
using a new VbaProject.OTM file. I am now out of ideas. Has anyone
else had this problem, and if so, how do I fix it?
Thanks,
Sue