NAV 2009 R2 finsql.exe crashes using automation on Windows 7

CMeisersick

Hi there!

We moved a NAV 5.0 SP1 Environment to NAV 2009 R2 (6.00.33910). We use the classic client with a SQL Server database.
We use a COM dll as Automation data type to connect from NAV Classic Client to an oracle database to receive an inventory information according to an item. When the classic client connects the first time to the oracle database, it could take up to 20 seconds after the database is opened and the results are transfered to the client. If you use it the second time, you receive the result within a second. All further attempt are that quick.

The problem is, that after moving to NAV 2009 R2 some clients crash if they want to access at first time after starting their computer to the oracle database.
Microsoft Dynamics classic client executables for SQL Server funktioniert nicht mehr.

We have those problem only on OS MS Windows 7.
It seems to me, that the new classic client has a problem, if an automation control don't answers for some time. Maybe he receives a timeout?

Sometimes, if the user restart his classic client and waits some minutes, the access to oracle database works fast and fine.

Mostly at the moment the only solution is to change the compatibility mode in the properties of the link to finsql.exe.

Now what is very very strange is, that on the same machine the classic client don't crash for some days, but then crashes again. The only solution is to change the compatibilty mode back again. If finsql.exe runs on "Windows XP SP3" mode, you remove the hook at the checkbox. Else you set the hook for "Windows XP SP3" compatibility. This I cannot understand, but the cases proof that.

It would be very nice, if someone could give me a hint on that.

mohana_cse06

Did you try to run finsql as "Run As Administrator"?

stryk

Hmmm ... looks like a problem with that COM component & NAV & Win ...

What is the purpose of that COM connection to Oracle? Maybe it would be possible to get rid of that component and replace it with a direct "SQL-to-Oracle" solution, e.g. using "Linked Servers" etc.?!