Anyone got this error :
OLE DB Provider instance properties are in conflict with another Provider instance properties using the same Session ID
Thanks for this information.
I would recommend that
Let us know how it goes.
I've made this question its own thread so it has greater visibility. The error appears when there are at least two provider instances using the same Session ID and have conflicting properties. To have each session manage their own server connections and cache, you can set Session ID = -1 in the Provider Connection String. Can you provide the OLEDB connection string? What is the consumer application (SSMS, PowerPivot, etc.)? Performance can be improved (parallelized) if each session maintains its own objects, but the downside is if they need to share the cache. In any case, Session ID = -1 should resolve the error, but a better understanding of the use case would help determine if it's the appropriate long-term solution. Has the error appeared before or is it a new application? You can refer to the PI OLEDB Provider 2010 R3 guide (pg. 15) for details/use cases regarding the Session ID keyword.
I m already using Session ID = -1. There are many query using my Linked server from different process. It was specific SQL account that got this error and other wasn't. I did try yesterday to switch authentification for all user of this linked server to use the same credential. (user not defined in list connection will be made with this security context)
@provstr=N'Always Return Rowset=True;SessionID=-1;Integrated Security=SSPI;'
I should add to this also, we using this linked server to query PI with SQL OPENQUERY.
Hello Mr. Marcil,
Are you having several linked servers for the same PI Server?
This error can occur if you have several linked server using the same connection string.
The easiest approach it to use only one linked server per PI Server.
If you don't, you need to have a different connection string for each linked server.
Yes we had several linked server for the same PI Server. Trouble did start last week when i added new query using this linked server for another process. Few day after that when I saw this error, I did make sure all query were using the same linked server, I did expect that could be the root cause too. But I didn t delete the extra one. We had 2 setup to try with or without security context, kind of test to set this up a month ago. Everything was fine even if we had 2 linked server on same PI server, until last week when i added more query.
So problem did happen again this week. That s when I posted here. I did delete extra linked serevr yesterday to keep only one. With Session ID = -1 on both I though that wouldn t be a problem.
I didn't find a way to unlock a user stuck with this error. I had to change the security context to use a different user. Now I fear all my process get jam with this error since they all using the same one. I did switch some critical operation on these linked server, it was looking pretty solid until last week.
Yes, good call Patrice, I ll go ahead and reboot this SQL Server too.
Hope everything go well after this.
Coming from SQL world, having access to this Linked server to query PI make my life so much easier. I must stabilise this path!
I have seen that you marked the answer as correct.
I am glad that things worked for you!
Thanks for coming to PI Square
Retrieving data ...