|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Opening a signed .ade file crashes Access 2003 RuntimesHello
I have recently bought a VBA code signing certificate to sign .ade files that we distribute, in order to suppress the security warning that otherwise appears when you open the file. It works perfectly in (full) Access 2003, but opening a signed file in Access 2003 Runtimes causes the runtimes to crash immediately. Every time. With every signed .ade file I've tried. It does not make any difference if it is my Thawte certificate that I used to sign the file, or a self-generated certificate. It happens in both Windows 2000 and Windows XP. Is this a known problem? How do I fix it? Thanks ....John Hi John,
Welcome to using MSDN Managed Newsgruop! From your descriptions, I understood that you would like to add a digital signature to Access 2003 runtime. If I have misunderstood your concern, please feel free to point it out. Based on my knowledge, you could refer the Knowledge Base article below to know two methods that you can use to add a digital signature to a Microsoft Office Access 2003 run-time application. - Use the Custom Startup Wizard to add a digital signature - Add a digital signature manually How to add a digital signature to an Access 2003 run-time application http://support.microsoft.com/?id=832510 Thank you for your patience and cooperation. If you have any questions or concerns, don't hesitate to let me know. We are always here to be of assistance! Sincerely yours, Michael Cheng Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Hi Michael
> How to add a digital signature to an Access 2003 run-time application I've already done that, unless there is something I have overlooked.> http://support.microsoft.com/?id=832510 In more detail, this is what I have done: 1 Obtained a VBA code signing cert from Thawte 2 Imported it to my development PC using pvkimprt.exe (aside: this step seems to me to be poorly documented on Microsoft's website and the Access help files) 3 Used it to sign my access project file, MyApp.ade, using the procedure in the link above headed "Add a digital signature manually" 4 Copied MyApp.ade to a test machine that has Access 2003 installed and macro security configured for high security. 5 Double-click MyApp.exe to open it - it opens with no security warnings, as expected. So far all ok, but then: 6 Copied MyApp.exe to a test machine that has the Access 2003 Runtime installed. 7 Double-click MyApp.exe to open it - Access starts to launch but then there is a message that it has encountered a problem and must close, with option to mail the crash information to Microsoft. Somehow I need to stop this crash, so that I can issue signed .ade files to my customers who use the Access 2003 Runtime because they do not have a full copy of Access 2003 installed. Leaving the .ade unsigned is not an option because some customers refuse to open unsigned files. (The Access runtimes are installed from the ACCRT directory of MSDN download en_office_2003_pro.iso) ....John > 5 Double-click MyApp.exe to open it - it opens with no security warnings, as I should have said that the first time I did this there was a dialog asking > expected. if I wanted to trust this certificate. Show quote > ...John Hi John,
I understood your concern as ade is not so powerful for security issue. It's strange that your follow the steps listed in KB Q832510 and it still crashes. Would you please find the information in Event View that logs for Access crash? BTW, to find out the root cause of this issue we may need to analyze access code internal, this work has to be done by contacting Microsoft Customer Service and Support. Therefore, we probably will not be able to resolve the issue through the newsgroups. If the issue is urgent, I recommend that you open a Support incident with Microsoft Customer Service and Support so that a dedicated Support Professional can assist with this case. If you need any help in this regard, please let me know. For a complete list of Microsoft Customer Service and Support phone numbers, please go to the following address on the World Wide Web: http://support.microsoft.com/directory/overview.asp Sincerely yours, Michael Cheng Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Hi Michael
> Would you please find the information in Event View that logs for This is the text of the event for the crash when opening a signed MyApp.ade > Access crash? in Access Runtime 2003: Event Type: Error Event Source: Microsoft Office 11 Event Category: None Event ID: 1000 Date: 03/05/2005 Time: 11:11:30 User: N/A Computer: GBBHW-W-X110716 Description: Faulting application msaccess.exe, version 11.0.5614.0, stamp 3f3c8e3c, faulting module msaccess.exe, version 11.0.5614.0, stamp 3f3c8e3c, debug? 0, fault address 0x000048de. Hi Michael
SOLVED - by applying SP1 to the Access 2003 Runtime. In hindsight this was obvious, but it was not until I browsed the event log that I realised that the Access 2003 Runtime is just a crippled Access 2003, and that the service pack would apply to it. Is there an Access 2003 Runtime installation package that already has the SP1 incorporated? Where would I find it? That would make the overall installation simpler for our customers. Thanks for your help ...John Hi John,
It's great to hear that you have resolved it by applying Access 2003 SP1. For your question, I am afraid there is no Access 2003 runtime integrated with Access SP1. Sincerely yours, Michael Cheng Microsoft Online Partner Support When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. |
|||||||||||||||||||||||