Observer.dll nightmare...

Hi, : Failed to extract OBServer.dll from Cab file.
Here's the scenario :
1 Server with SAP 2007 p35 installed
2 Web server with SAP 2007 p35 client only installed.
Now on the web server, the connection is made successfuly and works great.
EXCEPT, every now and then, we get Failed to extract OBserver.dll from Cab file
What's the problem guys ? Is it trying to get a version of OBServer.dll from the server 1 which it can't for an unknown reason ?
Is there anyone capable to explain what's the problem with this think and why its randomly not working ?
I don't even know what all that means for me and what do I have to check for. I dont know this file. And even know we would explain it to me I wouldn't understand. All I need is to avoid having a problem with it because this makes the customer using my app starting to ***** very hard on me and I have no clue what to do
Things I already tried without any success :
1) Uninstall SAP CLIENT
2) Deleted SM_OBS_DLL directory
3) Reinstalled client
Even this was making my app working well, until a afew minutes then POW, the connection problem again
Is this all because of the way I'm using the DI API on a server that have just the client ?
Also, people on other threads was taking about installing DI API which I never really needed since it works without it. Also, I already installed it and this never made any different.
I'm now really out of idea on this.
The user using the app has FULL RIGHTS on the server which means he's the administrator of the system
HELP.. Really....
Oh and I've looked at the dll's versions and everything is all the same, everywhere. SapBobsCom, The interropt. Realy, I repeat agian. It works every now and then but suddently, it stopped for the error mentioned above
It can be anything that is causing it but if only I would understand what is it and why do we get this error exactly I could probably find a way to avoid it

>
Yatsea Li wrote:
> Ok, your IIS is 6.0 version, and working with IIS_WPG or NetworkService, try to grant the read/write permission of the following folders for IIS_WPG:
> <<C:\Documents and Settings\LocalMachineName\IIS_WPG\Local Settings\Temp>>
> <<C:\Documents and Settings\NetworkService\Local Settings\Temp>>
>
> if it still doesn't work, try to copy SM_OBS_DLL into the folders above by manual.
> If you are working with DI, you don't need to grant IIS_WPG with read write on windows\temp
>
> Please let us know the update. Thanks.
>
> Kind Regards, Yatsea
Hi,
I've looked and these directory<ies do not exist. However, I saw that the only TEMP directory used on this server is the WINDOWS\TEMP
Now I did add the rights to NETWORK SERVICE and IIS_WPG and during the day I'll see if this helps.
I'll let you know.
If I had to copy this directoy it would have cause a version mismatch in case they would have upgraded to PL42 and for every upgrade I would have had to copy this directory isn't it ?
Hope I will not have to do such thing.

Similar Messages

Observer.dll version Mismatch with DI API when connecting to company

Please help!
I recently upgraded to patch 47 from 45, I entered the company through the di api, and I got an error that said something about external component threw an exception, I closed my program and tried to enter again, now I'm getting this Observer.dll Mismatch, when trying to connect to the company.
I saw another post, and verified the DI API dll SAPbobsCOM with THE SCAB table in SBO-COMMON, and both are 800181.
Iam using the SAPbobsCOM dll that its under C:\Program Files\SAP\SAP Business One\DI API\2007, although I have to say, I was using another dll from the examples folder in the SDK, when I started getting the error I changed to the one above. Ive tried deleting the SBO-COMMON database and then executing the upgrade patch 47 to rebuild, but Im getting the same error.
More Info: I took a look at this temp folder:
C:\Documents and Settings\username\Local Settings\Temp\SM_OBS_DLL\800148
Ive noticed that the version is diferent, but where does it come from?
Thank you!
Edited by: Josu00E9 Inu00E9s Cantu00FA Arrambide on Mar 31, 2009 7:51 PM
Edited by: Josu00E9 Inu00E9s Cantu00FA Arrambide on Mar 31, 2009 8:02 PM

My Bad, I was connecting to the wrong server.

Observer Dll Version Mismatch

Hi,
I have a project, which works fine for a client in SAP 2007 PL30.
I'm trying to connect the same project (in debug mode) to another client, who is in 2007A SP00 PL15.
But, I'm getting the error - Observer DLL version mismatch, when I'm trying to connect.
oCompany.SetSboLoginContext(ocookiecontext)
If oCompany.Connect <> 0 Then
'Error
I guess it is something to do with the version of SAPBOUICOM.Dll, SAPBOBSCOM.DLL in my application.
I tried using both as 2007, also I tried using DI as 2005 and UI as 2007.
Nothing is working.
Please help me with this.
Thanks.
-Geetha

Hi Geetha
To solve this issue please do the following:
1. Go to Start -> Run and type in %temp%.
2. Locate the folder SM_OBS_DLL .
3. Delete this folder (if you cannot delete it rename it)
When you connect again the correct version of the ObserverdLL will be
downloaded from the SBOCommon Database.
Regards,
Syn Qin
SAP Business One Forums Team

DI Webservice - Response not well-formed XML & OBServer.dll failed extract

Hi,
My company just implement SAP B1 this year.
So far, we encounter 2 issue :
1. Every month we encounter "Response is not well-formed XML" using DI Server Webservice.
2. Failed to extract OBServer.dll from CAB file (encounter also once a month)
For issue 1, restart DI Server service will not help.
I need to reboot the Windows OS to make it work again.
For issue 2, restart DI Server service will help to solve the problem.
But the question why this happening ?
Please help.
Thanks.

Hi,
To begin troubleshooting, you may check any monthly applications' running like update or anti-virus.
Thanks,
Gordon

Where can find the OBServer.Dll

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 dont 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 dont know how can install this in the client computer
I regard any help about this
Thanks

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

Interop.sapbobscom.dll compatibility

I'm having a compatibility issue, I think, with the patch-level of my interop.sapbobscom.dll that is installed with my addon compared to the patch level that is installed at my customer's location. I'm developing on SP00 PL49, but the customer is at 48. (They are getting a "server threw an exception" error at random places in the code that seem to be related to recordset.doquery.)
I want to create an installer for my addon that will contain the appropriate interop dlls but I want to make sure that I'm giving them the right ones. How do I tell what patch level the interops were created for? The SAPBOBSCOM.DLL object in C:\Program Files\SAP\SAP Business One\DI API\2007 has a special build description property in the version tab that lists the PL, but the interop file does not contain that property. I have different addons created for different customers all at different levels, so finding the right version of the interop files is quite challenging without any real identifying numbers.
Thanks!

Hello John
Basically the interop dlls are just containg the functions, as library but the business logic is coded in observer.dll which is downloaded to %TEMP%SM_OBS_DLL. By this logic the SAP B1 DI API can support the compatibilty between patch levels.
You cannot determine the interop versions, because only the major version number is stored there.
So in your case the Business Logic of PL 48 not knows the logic of PL49 if i understand you problem well.
When i had problems with recordset queries i was able to dicover 2 reasons
- cleaning up the %TEMP%SM_OBS_DLL was solving the problems
- on huge databases the transactions was generated this kind of errors.
I hope i has able to help you.
Regards
János

Error -8003 u201CObeserver dll version mismatchu201D.

I have an SBO installation sitting on a server called SVR. The SBO version is 2005 PL44 sitting on SQL 2000 to reflect one of our current customers. On my laptop I have a VS2005 C# DI-API project that attempts to connect to the companies on SVR. I also run an SBO installation on my laptop (SBO version 2005 PL50).
I get the error -8003 u201CObeserver dll version mismatchu201D.
To try and resolve this I made sure that:
1. the reference in my C# DI-API project was to a valid SAPbobsCOM2005.dll (i.e. a PL44 version)
2. I removed %TEMP%/ SM_OBS_DLL so that it would refresh with the Observer.dll from the SVR machine (I think it downloads from SBO_Common on SVR)
3. I stopped the licensing manager service (set it to manual) on my laptop and rebooted just so I could clear any in process references to my PL50 version.
I then retried to connect and got the same error.
I checked the OBServerDLL.dll that went back into the %TEMP%\SM_OBS_DLL directory and the version was PL44.
I canu2019t understand why; if I am referencing a PL44 SAPbobsCOM2005.dll in my DI-API C# project, and the Observer.dll that gets loaded from the SVR machine is a PL44 version that I get a version mismatch.
Does anyone know the reason or can anymore explain the architecture concerning the versioning so I can resolve my issue?
Thanks

Thanks Jitin,
Very helpful but I still have the problem. I tried the folowing as the link suggested...
1. Locate the Temp folder by going to Start -> Run and type %temp%.
2. Locate the SM_OBS_DLL folder here and delete it.
3. Uninstall the DI API from Add/Remove Programs.
4. Reboot your PC
5. Install the DI API from your current patch. (Download patch, extract it and then browse to Packages\DI API and run setup.exe)
6. Run the Upgrader Common again (From the same patch as above - very important!). Browse to Packages\Upgrader Common and run setup.exe. This will update the SBO-COMMON to this patch level again. You will not lose any data.
... which makes a lot of sense - and I would have thought would have solved my problem. A colleague in the office CAN connect using the same DIAPI application. He is running a laptop with Version 2007 on it. Perhaps the major difference in versions is working to his advantage.@^%#$!
I would like to understand the architecture so I can methodically troubleshhot the process.
I have a Backward and Forward compatibility guide that shows the OBServer.dll getting downloaded from the Server and into process memory - but it's a bit lighton detail.
Are there any more comprehensive documents that can be accessed from SAP or from other sources. I've been trawling the internet but no cigar as yet...
Thanks

Error while importing data with DTW

Hi Guys,
I received an error when i try to upload data with DTW
method '~' of object '~' failed65171
When i click on run simulation again,
I received another error 65172.
There's two different error.
Can anyone help?

Hi,
This error means that your Obscommon user is corrupt and you cannot connect to the SBO-Common database to download the OBServer.dll that is stored in the temporary directory.
For more information, see SAP Note 858475, 642564, or 614946.
Thanks & Regards,
Nagarajan

Error in running Extract Definition Upload from Data File concurrent.

Hi all,
Am trying to upload the 834 Extract Layout from the data file by running the concurrent program, Extract Definition Upload from Data File.
After running this concurrent program am getting the Extract Layout definition with Record layout and Data elements within it.
But some record layouts has the changes at their repeating level in that.
Please suggest me how do i get the same repeating levels for the record layouts when i move the 834 benefit extract layout definition
from one instance to another instance.

Hi,
We have exactly the same error in IBolt. This error happens sometime and we don't find the reason.
IBolt has been upgraded to Version 3.1 SP1 and a fix has been developed by the support. After installation, we've work hardly during 2 days for testing all the flows by the customer without having this error.
Ibolt works as a service and when this error occurs, the service stopped and must be restarted.
In our flows, we have put a delete of the observer.dll file just before the rest of the flow but it doesn't solve the problem.
Deleting the directory can be temporarly a solution but the error come back another day.
Each time the SBO client or DTW is started, the %temp%\SMS_OBJ_DLL directory is created...
When you just delete the observer.dll file and leave the rest of the directory like it is, the file is re-created when you start and log to SBO. I would say that this file is a copy of another file observer_800178.dll (800178 depending of the version of SBO yoi have). 800178 corresponds to SBO 2007 A PL 42.
Do you have more information since your post has been send ?
Thanks in advance for your help.
Best regards.

The specified resource name cannot be found in the image file.

Dear Experts,
I have developed an import too and it imports many of the Business Objects from a temporary data base to SAP B1. It was running fine for more than 6 months now.
Currently when the Tool is importing Credit Notes in to SAP B1, the following error is thrown.
The specified resource name cannot be found in the image file.
And I have no Clue about the error. Any one had any experience regarding the above error???
Thanks in Advance,
Vasu Natari.

Hello VAsu,
Somethimes this unexpected, ununderstandable eroor messages caused by corrupted observer dll.
Do a clean up (delete %TEMP%SM_OBS_DLL) folder, and see the result ! (i had several issues in the past with some strange messages...)
Regards
János

Add-on connection error (-105) Access to company database is not permitted

Good day,
One of our clients have upgraded to 8.8 PL 11 (from 2007A PL 41).
Somehow the SBO-Common became corrupt and SAP suggested that we reinstall the SBO-Common.
The problem is that now the add-on (developed by us) is not connecting.
The add-on connects to UI API and DI API, but when trying to connect to the company with SAPbobsCOM.Company, an error is returned (error code: -105).
I am also confused about what the error actually is, bacause according to the SDK Help file, error -105 is "The observer.dll init has failed.", but the error message returned by the add-on is "Access to company database is not permitted; log on to SAP Business One and sign end user license agreement (EULA)"
I have tried resigning the EULA, but no success.
I have also tried deleting the content of the %temp%\SM_OBS_DLL, as suggested in another post.
The version of the OBServer.dll is 8.80.229.0 - I believe that this is the correct version for 8.8 PL 11?
Please advise.
Kind regards,
Rikard

Good day all,
My apologies.
I have discovered what the problem was - and it was me.
I did not realise that the connection I was making was not to the same database that I was connected to.
Therefore, I had to log onto the other database and sign the EULA.
The error explained exactly what I needed to do, but I wasn't paying attention.
Regards,
Rikard

Hi sap connection problem

hi
when i m going to connect to the sap server by giving, login information , it gives an error mesage saying
"-112-Failed to Extract OBServer.dll from CAB File"
this machine i didnt install sap b1. i'm using DI API and enter Login information .
can you help me to solve this problem.
regards,
chaminda ratnayake

Hi Cahaminda,
How many space is left on your system drive (where %TEMP% is located)?
You need about 40- 50 mb minimum
Regards
Ad

DTW Update price error - Method '~' of object '~' failed65171

Hi,
We recently updraded from SBO 8.82 to SBO 9.0 PL 08 HF1
Before the upgrade we never had this issue, but now I get this error message while trying to update prices through DTW (version 88.1.4): Method '~' of object '~' failed65171
ParentKey LineNum PriceList Price Currency AdditionalPrice1 AdditionalCurrency1 AdditionalPrice2 AdditionalCurrency2
ItemCode LineNum PriceList Price Currency AddPrice1 Currency1 AddPrice2 Currency2
135109-1 28 29 40 SEK
Itemcode is 135109-1
Linenum is 28
PriceList is 29
Price is 40
Currency is SEK
I have done this several times before the updrage without any problems, but now I'm stuck.
Any ideas what we can try?
Regards
Kjetil Sandvik

Hi,
Please check:
This error means that your Obscommon user is corrupt and you cannot connect to the SBO-Common database to download the OBServer.dll that is stored in the temporary directory.
For more information, see SAP Note 858475, 642564, or 614946
Thanks & Regards,
Nagarajan

Addon Strange behavior lately.

Hi,
I have a code that I never modified since the begining and now it start poping a message in SAP which is
"Failed connecting to the company\'s Data Base".
this message comes from this :
private void ConnectDIAPI()
    if (!System.Convert.ToBoolean(SetConnectionContext() == 0))
        SBO_Application.MessageBox("Failed setting a connection to DI API", 1, "&Ok", "", "");
        System.Windows.Forms.Application.Exit();
    if (!System.Convert.ToBoolean(ConnectToCompany() == 0))
        SBO_Application.MessageBox("Failed connecting to the company\'s Data Base", 1, "&Ok", "", "");
        System.Windows.Forms.Application.Exit();
And this is because this method returns something else then 0 :
private int ConnectToCompany()
    int returnValue;
    //// Make sure you're not already connected.
    if (oCompany.Connected == true)
        oCompany.Disconnect();
    //oCompany.AddonIdentifier = "blablabla the huge number you know about";
    //// Establish the connection to the company database.
    returnValue = oCompany.Connect();
    return returnValue;
But now you wanna read the strangest thing ? The addon works perfectly even tought.
So I'm all confused on this. OH and also another weird thing is that if I'm the administrator of the
machine on which the addon runs, the message doesn't pop. and if I'm just a user I have the message...

I'm still wondering what is SM_OBS_DLL and why do we have to delete this to solve problems.
Any detail information on what it is and its purpose.
All I know is that there's the observer.dll in it and DI API connections but I don't understand what it is
and why it gets corrupted and why since a long time this never been fixed by SAP !

2007A: Comments on GetDICompany method

According to the help center:
"When running several DI add-ons performance may degrades significantly, because each additional connection to the DI API loads a new DI and ObServer DLLs.
You can improve performance using a new connection interface to DI API. This method is recommended when running multiple DI add-ons connected to the same Company database.
You must handle shut down events properly, otherwise add-on process remains in memory"
I'd like to ask SDK Architects two simple questions before i test it by myself:
1. Wll GetLastError, GetNewObjectCode and other process-specific methods work properly? Imagine you have 2 addons and 2 connections returned by GetDICompany as well. What will be the result of GetNewObjectCode method executed by 2nd addon: will it be the the code of the latest object added by 2nd addon's DI connection or will it be the code of the latest object added by 'joined' processes of 1st and 2nd addons?
2. Should we keep in mind anything while coding the shut-down events?
These questions are the cause and effect of the lack of GetDICompany-mechanism's descriptions and comments. Detailed comments on its core are appreciate.
Regards,
Alexey

Hi Alexey,
Re 1. Of course that should work per Add-On!
...I just double-checked it with GetNewObjectCode - to have seen it myself before replying ;-)!
Re 2. I am not aware of anything you should keep in mind so far...; we'll double-check with R&D and let you know in case there is something!
Thank you very much for raising this!
Regards,
Frank

Observer.dll nightmare...

Similar Messages

Maybe you are looking for