UI error "The requested lookup key was not found in any active" workaround

Question

Hi All.
Some of you might have this problem when making a UI-Connection "The requested lookup key was not found in any active activation context"
Talking to SAP Support and Gianluigi Bagnoli about the problem here is a sum of the problem and the workaround to prevent it (at least untill SAP development fix the problem)
Some facts:
- The error is present in SBO2005A SP01 and SBO2005B SP00, SBO2007A should not be affected
- The error occur because the SAP client fail to provide the correct/entire connection-string
- The problem is actually an underlying problem from Microsoft (try searching google with the error message)
- Normally after the error occur, you can go to Administration > Add-ons and start the add-on manually without problems
Some additional observations
- The error mostly happen just after startup of a windows machine
- We have had a couple of customers that have had the problem, then upgraded the SAP client to a new patchlevel and got rid of the problem (but we have also had customers where this did not help)
- Seem to be happening more often of slower machines
Workaround
Knowing that this problem is tied to and incorrect connection string is also the "workaround"... What you could do is to create exception handling around the UI connection, and if it fails connection using the development connection string (like you do during development) The connection string is: 0030002C0030002C00530041005000420044005F00440061007400650076002C0050004
Using this method, you will be able to establish a connection even if the client is unable to provide you a correct connectionstring, but the draw-back of this workaround is that the add-on will be indicated as failed in the Add-on Manager and the user is not able to stop the add-on in any way other than disconnection from the company.

Answer 1

Hi,
I am looking for a solution to the error "The requested lookup key was not found in any active activation context" too.
In our add-on we do two SboGuiApi.Connect(sConnectionString), one from MyAddon.exe and the other one from MyAddon.dll. The .exe catches messages and .dll interacts with UI to paint forms etc. It is since the .exe and .dll are not in the same thread. The first connection works fine in the .exe, then that connection string is passed to the dll and the error is raised. The rare thing is why it works fine from the development enviroment, but doesn't work when SAP is starting the Addon?
Is it possible connect twice?
Can we connect in the .exe using the connection string received from SAP and in the .dll using the development connection string?
It is over
Windows XP 2002 SP2
SBO2007A patchlevel 15
VS 2005 C#
SQL Server 2005
Thank you