Addon connect problem when connecting from client machine

[NeerajAgarwal]

Dear All

Have you ever faced this error? This error is coming when trying to connect the Addon from a client. When running from Server the add on connects without problem. The DI API is from the latest patch and is installed on the client also. There is no mismatch of the DI API

"Error in Function: GetBusinessObject You are not connected to a company

[Gianluigi]

Well it looks like you are not connected ... did you set the correct server / password / user ? did you check for error values and exceptions ?

[NeerajAgarwal]

Actually, we are able to connect SAP Business One from the client machine. The problem occurs only when connecting the add on. What do you mean when you say you are not connected..?

[Former Member]

I am getting this error message as well. Weird thing is, it was working up until 2 days ago and then started getting this error. Any ideas what may have changed? I know my code has not changed and the company names have not changed.

Thanks in advance.

Rhonda

[former_member201110]

Hi Rhonda,

Try deleting the SM_OBS_DLL folder in your local temp directory (that will be C:\Documents and Settings\<user>\Local Settings\Temp on a Windows XP workstation). This folder is rebuilt the next time you use the DI. I found that rebuilding this folder resolves a number of issues with connecting.

Hope this helps,

Owen

[NeerajAgarwal]

Hi Rhoda

The problem occured because the SBO Common version didn't match with DI API version. This could have happened during upgrade to a higher patch where becasue of some reason, the mismatch happened. 3 of our partners were able to solve this issue by bringing both the SBO common and the DI API to the same version level.

If your SBO comon is of lower version compared to DI API, upgrade your SBO common. If your DI API is of lower version uninstall teh DI API and install again

I hope this will be of help

[Former Member]

Hi,

Sometimes I wonder this can cause the serious problem,just because if you upgrade the server

patch 65,and remember to upgrade diapi 65,

but you forget to do upgrade diapi 65 on

every client machine.

The poor mis will have many complain phones

from many corners of the offices,and I think the

solutions will be challenged by many users again!

By the way,I still want to thank to

this article,because I have spent 2 days to find

the strange problem of b1 and this is the answer.

Andrew Chu