Hello,
I am running an ASP.NET application in C#, and running a simple interface to PI via OLEDB calls. Desirably, this .net application will run under the identity of a process account (ie., on the domain). This domain account was added to a trust on the PI server in question. When installed however, I encounter strange behavior; the first few calls against the SDK
will return succesfully, then proceed to generate the following 2 errors consistently (typically the first one):
Quote:No error message available, result code: E_FAIL(0x80004005).
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.OleDb.OleDbException: No error message available, result code: E_FAIL(0x80004005).
Quote:[PI SDK] Unable to access SCM Manager. 5
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.OleDb.OleDbException: [PI SDK] Unable to access SCM Manager. 5
Interestingly, for the sake of testing, I switched my application to run under a local account on the web server (NETWORK SERVICE) and added the web server to the trust - this worked 100% of the time.
Any thoughts regarding why the connections would fail when the application runs under the process account identity? Could this have something to do with connection pooling? Is some additional permission needed on the web server to get the SDK to consistently work with the process account identity?
Thanks in advance.
