Where can find the OBServer.Dll

[Former Member]

Hi partners, I have this trouble, when I try to connect to SAP, I receive this message “Failed to Extract OBServer.dll from Cab File”, I don’t have this problem in my computer, the problem is when I try to run the program in another computer, I was read about a directory in Windows\Temp, that contains this dll, but I don’t know how can install this in the client computer…

I regard any help about this

Thanks

[rasmuswulff_jensen · Accepted solution]

The file you are reffering to is in the SM_OBS_DLL forlder in your temp-folder (Go to start > Run and type in %temp% and you will get into it)... The problem might be a corrupted SM_OBS_DLL forlder, so try to rename it to oldSM_OBS_DLL and restart SAP Business One and your add-on (the SAP wil recreate it from the SBO_Common database wich actually have the files embedded)

If the machine doesn't have a SM_OBS_DLL folder you might need to install the DI-API, or you might need to reinstall it if you have a wrong version installed (DI-aPI should always be the same patch as the SAP Client)...

[rasmuswulff_jensen · Accepted solution]

btw. The file itself is called OBServerDLL.dll and not OBServer.dll as statet wrong in the error message by SAP

[Former Member]

The problem was generate by a bad update, I were re-install all, because, some computers can’t be established a connection with SAP, I don’t know if I would fixed this problems without re-install but I worried about to resolved this problem, because, my client is in production.

Thanks and regard to Rasmus Jensen and Owen Slater

[former_member201110]

Hi Karlo,

The OBServer.dll file is stored in the SM_OBS_DLL folder in the user's temp directory. There are a number of causes for this error message (if you've got a S User account then you can search through SAP Notes for this error message).

Here's a few things to try:

1) Try running SBO using an account with full admin rights on the machine. If SBO runs fine under this account then its a Windows user privileges issue.

2) It could be a damaged CAB file. You can correct this by rerunning the upgrader common utility from your current patch to rebuild the CAB file (caution: don't take this step on a production system unless you are sure of what you are doing and have full recovery).

3) Check that your user profile on the workstation has a temp folder defined and there is sufficient disk space.

You can also try deleting the SM_OBS_DLL folder in your temp directory while logged out of SBO as this is rebuilt the next time you try and use the DI API.

Kind Regards,

Owen

P.S. Doh! Rasmus beat me to it