We can go through a lot of potential differences to try and find your
issue, but I think it is faster to think about the issue this way:
What configuration is required by the specific Windows application to
trigger the exception dialog box?
There are a gazillion possible issues to sort through, but only one
exact list of requirements, so it is usually easier to gather the
requirements than reverse engineer the requirements through issues
observed through experimentation.
For example, user logon from IIS are considered non-interactive and
cannot be changed. Default Windows login is interactive. If the
exception dialog triggers only on interactive use, then it won't be
triggered from IIS and will actually be considered "by-design" by both
IIS and the other Windows application.
Of course, I think the issue is within the particular Windows
application's definition and support of "unattend", but you've got to
obtain that definition before you start on your development.
On Dec 27, 1:25m, David Lloyd < XXXX@XXXXX.COM >
> through the accounting application user interface the first time. >>
>> I am able to activate this exception dialog box through a Windows
>> application, however, calls to my web service results in an error,
>> essentially telling me that I don't have the necessary exception, but not
>> activating the exception dialog box in order to grant the exception. nce I
>> have the exception, the web service can access the application without user
>> Something is preventing the web service from activating the necessary
>> accounting application exception dialog box. have attempted numerous
>> configurations including the following: unning the application pool under
>> an administrative account (for testing purposes), setting the "Allow service
>> to interact with the desktop" property for the World Wide Web Publishing and
>> IIS Admin Service, verfiying the ACLs of the appropriate folders, and
>> changing app pool uesr accounts. n addition, there is a configuration where
>> I can use an out-of-process COM server supplied by accounting application to
>> perform the same operation. his configuration yields the same error.
>> What other configuration issues might prevent the web service from
>> successfully activating the exception dialog box? s there an issue that
>> would prevent the web service from interacting with the desktop? gt;
> Alternatively, Is there a way to configure a specific security context for>
> the accounting application? would appreciate any insights. >
> Thank you.