I wrote:> Having been in a hurry, I did not notice which of the> following solved the problem:>> 1. clear the temporary directory SM_OBS.> 2. restart the license server,>> Sorry for taking your time. The problem returned this morning, and the above solution no longer helps. I think it was a mere conicidence that it seemed to have worked, because the error is intermittent and is caused by other factors. Johan Hakkesteegt: > One test you may perform, is to create a blank addon that> does absolutely nothing else than connect to the company,> and run it on the affected machine.>> This test helped me in the past, to determine that an open> .NET sqldatareader object in my project was somehow> blocking the company object's connect method. I did it, but to no avail, for the B1 client itself connects to its company databases with the same delay, which I have meaured to be 90 seconds. > There are others users connected in the same instance that> you trying connect? If yes, try connect in an instance> that have no users, and tell us about your results. I checked it with no other users on the whole server and found no difference. > I have saw this problem when some Add-on, has some routine> that call StartTransaction() in DI API in another machine,> and delay to call EndTransaction(), during this period,> any other user in any machines can't connect in the> company. An SQL-Profiler trace shows no long-running quieries, so I suppose it is not SQL that is causing the delay.
↧
Re: Di connection taking to long
↧