Are you using RunAs aka impersonation? If yes, u need to set the Anonymous property to true (if I remember correctly).

Hi @cmdriordan,

Can you elaborate a bit more on what you are trying to achieve?  are you developing a .net or C# related application?

The customer is already using the latest IFS Access Provider for their .NET application, the issue is that the latest IFS Access Provider removed the ability to connect to IFS without using a dedicated session.

This is problematic for their existing code which uses a non-dedicated session.  Is there a way to use a “non-dedicated session” in .NET application using IFS .NET Access Provider in APP10?

For more info, customer is upgrading from APP8 to APP10.  

1. We have a .NET application that performs critical business functions some of which require IFS transactions (issuing of material, approving of purchase reqs, etc). The IFS functions must be performed in the .NET application because it executes other functions like barcode scanning, label printing, etc that can’t be done in IFS.
2. We have been using the .NET access provider to connect to IFS and perform these transactions per IFS guidance several years ago
3. We connect though some very simple C# code below using a generic login
4. <screen shot missing>
5. Then we execute the transaction with PLSQL in our code which impersonate the user logged into the application. This ensures that the user has the proper rights in IFS to perform the transaction.
6. <screen shot missing>
7. This has been working for many years
8. We are now getting errors in IFS 10 because users are not able to reuse the same connection
9. If we are forced to use a dedicated session for each connection, we need to do something like create a connection pool, because multiple users cannot reuse the same connection.

Is creating a Connection Pool the best option, is there a way to use “non-dedicated session”, or should they be doing something else?  

Hi @cmdriordan,

With new IFS releases promoting a total web architecture I think it is extremely wise if you can move your customized requirement in terms of a web application that consumes IFS App10 REST APIs. You might very well look into Apps10 IFS enterprise explorer client implementation as it is still directly calling database methods for validations/perform activities. 

as stated above, impersonation seems to be used so set the Anonymous property to true.

I also have to agree that using the projections instead is the long term future proof solution (since AccessProvider will be discontinued).