-
1. Re: "Unspecified Error" or "Runtime Error" 7 when launching application with AcroPDF on Secured Vista PC.
lrosenth Jun 10, 2009 2:59 AM (in response to Matthew Snapp)You need to consider low rights issues according to Vista development rules.
-
2. Re: "Unspecified Error" or "Runtime Error" 7 when launching application with AcroPDF on Secured Vista PC.
Matthew Snapp Jun 10, 2009 5:51 AM (in response to lrosenth)"Low Rights" seems to apply to Internet Explorer. This is not an Internet Explorer application. The browser I refer to is the Acrobat browser that the AcroPDF control places on the form, and it is used by the Windows application we wrote to view the PDF files we are processing.
The application is installed into Program Files, and the error occurs on the initialization of the form, before any code that we wrote even executes. This also occurs with accounts that are in the Administrator group, and have some elevated priviledges.
-
3. Re: "Unspecified Error" or "Runtime Error" 7 when launching application with AcroPDF on Secured Vista PC.
Matthew Snapp Jun 10, 2009 2:17 PM (in response to Matthew Snapp)I have done the following on my Vista Business VM and I still have not been able to duplicate the error that I see at the client site.
1. Enabled UAC.
2. Implemented Software Restriction Policies.
3. Set the Default Security Level to Basic User (except for Local Administrators).
4. Lowered the Integrity Level on my AcroTest1.EXE and on my actual executable to "Low".
The sample application and the user application loaded the form and initialized the AcroPDF control when logged in as a normal user account (the account is only a member of the "Users" group on the local Vista PC).
Since this application is an actual Windows application (not an Internet Browser plug in), the default integrity level should be "Medium".
-
4. Re: "Unspecified Error" or "Runtime Error" 7 when launching application with AcroPDF on Secured Vista PC.
Matthew Snapp Apr 9, 2010 2:28 PM (in response to Matthew Snapp)This issue was resolved by reinstalling Acrobat 9.x on the client machine. The client's IT had created a "custom" Acrobat install that was put in their images by default. When the "stock" Acrobat 9.x install was run for that user, this issue disappeared.


