FormAutomation AFORMAUTLib's AFormApp() Method throws COMException when running under an account wit

Question

Hi,
I've a VB application that uses the AFORMAUTLib library to create buttons in a PDF document. To do that I can use the AFORMAUTLib's AFormApp method to create an object that allows me to add the button using the following code (for example):
Line 1: formApp = New AFORMAUTLib.AFormApp()
Line 2: acroForm = formApp.Fields
Line 3: field = acroForm.Add("Simple Button", "button", 0, x1, y1, x2, y2)
I've this written as a console application and when I run it (an account having administrator privilege) I have no problem and the button is added to the PDF document.
The problem comes with I am trying to run it using a custom account (without admin privilege) and the system is throwing COMException and it fails exactly at Line 1. Having it to run without admin privilege is more like a technical rule that I need to follow.
I've already granted all possible permissions for the custom account to launch/activate all Acrobat related DCOM objects (those I can tell: AcroDistX, AcroExch.AVDoc, AcroExch.PDBookmark). But I am still having COMException when I run the code using the custom account.
Is there a DCOM object for the AFORMAUTLib or any DCOM object indirectly controls the access permission of the AFORMAUTLib library? I cannot find it so far.
I've no problem opening the PDF document but it just fails on that line when I'm about to do some form operations.
Any idea? Thanks in advance on any comment.

Answer 1

> Also thanks for your input on the legal info, although that doesn't get me anywhere on solving my problem.
You're welcome, always better to have the information than get sued.
You never mentioned in your first post that it was running as a service. That's why this didn't come up until you were asked and responded that it was indeed a service. While a lot of people on here are smart, they're not mind readers - we didn't know it was running as a service, and that changes a lot of things.
> "Please use LiveCycle instead. Don't bother with using FormAutomation in SDK, adobe prohits that kind of usage. Please also post questions in LiveCycle forum. Thank you."
If you want to be snide about it, sure. The fact is there is no solution using the Acrobat SDK for your issue because it was not designed to be used in the manner - in fact, it was explicitly designed to NOT be used in this manner. While I can certainly understand that you're frustrated over putting in work on this project just to find out it won't work, had you done sufficient research before hand you wouldn't have had this problem. You can take it out on me all you want trying to make me look like I deliberately designed the SDK to prevent you specifically from doing your work but that simply isn't the case. It's not possible with the Acrobat SDK (and if you find a workaround, it's still illegal, so I won't be helping you break the law).
This is a forum for Acrobat SDK development. I never said you couldn't post your LiveCycle question here, but as I said my knowledge of LiveCycle is limited - as it is with most people who frequent here - so you would have a BETTER chance asking in the LiveCycle forum (since that seems the logical place for people with LiveCycle knowledge to visit).
You can be as mad as you want and scream about wanting an answer, but I think you'll find very few people here will be willing to help anybody (not just you specifically) violate the licensing agreement. If anybody wants to help you break the law, that's entirely up to them, but you're right - I'm personally not going to help you break the law.