x64: ERR -111: Failed to Connect to SBOCommon

[Former Member]

Hi

does anyone have experience with that error on x64 Systems?

starting position

1) B1 2007 A SP00 PL42 installed on a virtual machine 1 (win 2003 server)

2) Our Application - only using DI-API - installed on machine 2 (win 2003 server) compiled for x86

3) Our Application - only using DI-API - installed on machine 3 (win vista ultimate 64) compiled for x86

Running our application on machine 2 works fine. Runnig our application on machine 3 produces the error -111.

Binaries and configurations of our application are equal on machine 2 and 3 (same deployment).

Are there any known problems with access rights on vista, e.g. for writing into %temp% folder?

Are there any known problems with x64 native sql client?

I have installed a B1 client on machine 3 and it works correctly.

Thanks

Flo

[Former Member]

Hi Flo,

Although all of them might not relate to your issue, it would be no harm to check:

Thanks,

Gordon

[Former Member]

Hi Gordon

thanks for the reply. During the last three days, I have read everything I could find here already and double checked. It must be another problem.

The application is running fine in all other environments with exactly the same configuration. Even with older versions of DI-API. It is also running fine on x64 environments at our customers (Windows Server 2003 and Windows Server 2008).

I assume, that it is a problem of my Vista environment ( e.g. there is no SM_OBS_DLL-Directory) or SQL client.

Is there a way to trace the DI-API (I dont want to write a wrapper). I have seen, that the DI-API accesses a file called 'C:\Program Files (x86)\SAP\SAP Business One DI API\DI API 2005\DoDiLogging' and if this file exists, it writes the following messages to a file called 'C:\Program Files (x86)\SAP\SAP Business One DI API\DI API 2005\DiLogger.txt':

28/10/2009 16:21:28 *** DI new running ... ***

28/10/2009 16:35:42 *** DI new running ... ***

28/10/2009 16:42:01 *** DI new running ... ***

28/10/2009 16:42:29 *** DI new running ... ***

28/10/2009 16:49:12 *** DI new running ... ***

28/10/2009 17:15:49 *** DI new running ... ***

28/10/2009 17:29:37 *** DI new running ... ***

28/10/2009 17:31:11 *** DI new running ... ***

28/10/2009 18:32:28 *** DI new running ... ***

28/10/2009 18:33:57 *** DI new running ... ***

28/10/2009 18:35:40 *** DI new running ... ***

Unfortunately not that much of information - but eventually, there is a way to tell the DI-API to log more detailed information...

Regards

Max

[Former Member]

Hi Gordon

I installed our app on another Vista environment and it ist running fine.

I will continue examining the problem if there is some time left.

Kind regards

Flo