Virus in OBServerDLL.dll ???

Hello,
The heuristic scan from kaspersky as well as McAfee said, that OBServerDLL.dll (in Temp-Folder) is infected by a virus. Possible that it is one? A full scan of the computer found nothing.
for any hint thanks in advance
Edited by: Andreas Schlingmann on May 27, 2010 11:39 AM

Similar Messages

Error: Access violation at 02271d4a in module observerdll.dll read address

I am using Delphi 5, SAP DI API for SAP 2004.
On a users machine, when we try to connect, we get an error "Access violation at 02271d4a in module observerdll.dll read address 00000000".
Anyone know why they could be getting this error? And what I need to do to fix it?
thanks
Bill

The problem is I have not been able to reproduce the problem on any of the machines in my office, this is only happening on a client machine. They have just the SAP client, and our program that uses the DI API.
I have instructed my client to search for that dll, and try to rename it, and rerun it. Not sure whether this will fix it or not.
Here is some example code I am using, I do not at this time know the exact point where the error is returning from, I assume from the Connect function.
function TtcSAP.Connect: string;
begin
// return empty on success
Result := '';
try
    // make sure it was created
    if not Assigned(oCompany) then
    begin
      Result := 'Error creating Company object.';
      Exit;
    end;
    if oCompany.Connected then
      oCompany.Disconnect;
    // Specify the user name and password
    oCompany.UserName := sUserName;
    oCompany.Password := sPassword;
    oCompany.DbUserName := sDbUserName;
    oCompany.DbPassword := sDbPassword;
    oCompany.UseTrusted := bUseTrusted;
    // misc settins
    oCompany.language := ln_English;
    // Specify the Company database
    oCompany.CompanyDB := sCompanyDB;
    // specify the server
    oCompany.Server := sServer;
    // connect (0 = success)
    if oCompany.Connect() <> 0 then
    begin
      Result := GetLastError;
      if Trim(Result) = '' then
        Result := 'Connection failed.';
    end;
except
    on E: Exception do
      Result := E.Message;
end;
end;

Observerdll.dll not found

I have installed SB1 2004 on new computer as stand alone server. I have also installed client, server tools and DI API. But after installation I can't find observerdll.dll on my machine. Version of cliet is :
SAP Business One 2004 A (6.70.184) SP:00 PL:01
Is anyone have some idea ?

>so i have Business One 2004 (also called 6.7)
>Version A (not sure how B works into this)
B is the "version" which supports localisations in APA... Currently there are 3 different "versions":
A mostly for localizations in Europe + the US etc.
B for Asia (China, Japan) etc.
C for Eastern Europe etc.
Please check-out the coverage of the particular versions in SAP ServiceMarketplace!
The SDK is the "same" for all the localizations.
>build 188 (related to the db?)
>patch level 21 (related to the client)
depends on what you mean...
An upgrade also upgrades the blob for OBServerDLL.DLL in SBO-Common, but the DI API + DI Server are installations apart from the "Upgrader Common".
Nevertheless both use the OBServerDLL.DLL, so that it might be (in rare cases!) that there are fixes where you have to upgrade the DI* as well to make them match OBServerDLL 100%.
>so does my di-api (also build 188) need to match my
>build level or my patch level?
Sorry, you are right that the DI API must match (take it from the DI API folder in the upgrade package!).
Message was edited by: Frank Moebius
(Don't know what I was thinking yesterday re DI version vs. Company version)

DI Error - 8032 - Unable to unzip OBServerDLL.dll to

Hallo!
When I traying connect to database with DI I received Error:
"-8032 - Unable to unzip OBServerDLL.dll to C:\Users\User1\AppData\Local\Temp\SM_OBS_DLL\880234\tmpObs.zip; make sure disk is not full"
OS: Windows 7 Pro 64x
DB: MSSQL 2008
B1: SAP B1 8.8 SP00 PL16
Disk isn't full.
Mayby someone know what's happened?
Grzegorz / Gregory

Thanks Gordon
But I've reinstalled DI API, turned Off Firewall, tarned Off AntyViruses program and run AddOn as Admin.
It isn't working.
I have still Error -8032.
Maybe some permissions in Win7. I don't know... It is new for me.
Grzegorz

(-105) Unable to initialize OBServerDLL.dll

Hi All,
I have a problem with connection to SAP B1 DB on HANA in B1if. I've read the forum and tried evry solution but nothing helped.
This is an error message:
com.sap.b1i.adapter.dia.exception.ConnectionFailedException: Connect to Business One failed.
(-105) Unable to initialize OBServerDLL.dll
{b1Server=IP:PORT, company=SBODEMOPL, licenseServer=SERVER:40000, dbType=9, dbUser=SYSTEM, userName=B1i}
DI API is installed.
JCO Path i set correctly.
No SM_OBS_DLL or SM_OBS_DLL_64 folder in %temp%.
There is only SM_OBS_DLL_64 folder in C:\Windows\Temp. I changed its name but after service restart it shows again.
Any idea how to solve it?
Kind regards
Szymon

Hi Szymon,
We have the same issue. after a clean installation and double checking the B1i password + connections strings to the HANA server. we are getting the same connecting issue when testing the connection:
Hana version we are using is 9.0 PL3 HANA
Error message":
com.sap.b1i.adapter.dia.exception.ConnectionFailedException: Connect to Business One failed.
(-105) Unable to initialize OBServerDLL.dll
{b1Server=SAP:30015, company=SBO_JEROEN, licenseServer=HANA-TS:30000, dbType=9, dbUser=SYSTEM, userName=B1i}
Did you manage to find a solution?
Things we tried:
Eventsender Setup
Restarting services (integration, eventsender, proxy, proxy monitor)
Turning off Windows firewall service.
Kind Regards,
Chester van Ree

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

Obeserver dll version mismatch

This problem is with a version 2007 application that uses the DIAPI and not the UIAPI.
On the test system the application connects to the SAPB1 DB and runs perfectly. However, on a different system it fails to connect to the company object and gives the error "obeserver dll version mismatch".
The two systems seem to be the same as far as versions of OS, SQL Server and SAPB1 are concerned.
Does any one know what obeserver.dll is and what needs to be done to get the right version.
Thanks for any help.

Hi Mel,
The OBServerDLL.dll file is part of the DI API and is found in the user's SM_OBS_DLL folder in their temp directory. The first thing I would try is to delete this folder and then log in to SBO on that machine:
On the affected machine
1) Log out of SBO (other users on other machines can continue)
2) Choose Start--Run and then type %temp% and click Ok
3) You should now see a Windows Explorer window with the user's temp directory showing.
4) Find and delete the SM_OBS_DLL folder
5) Start SBO and test
When the user logs back in to SBO and starts any addon that uses the DI API (or runs a third-party application that uses the DI API) then the SM_OBS_DLL folder will be rebuilt and the dll will have the correct version.
Kind Regards,
Owen

DTW Fails to open at all

Hello,
I am using SAP Business one 2005 A Patch Level 29, I cannot get to even open DTW . It shows the icon on my task bar then crashes immediately.
It doesn't give ANY error message, or are they store elsewhere where I could check for them ??
What can I do to make it work ? What are the prerequisites for DTW ?

Dear ,
You need the same DI version as SAP B1.
To find out the DI version you need to check in in two places.
1. Right click on the file C:\Program Files\SAP Manage\SAP Business One
DI API\DI API 67\Object\SAPbobsCOM67.dll and go to properties, then
click on the version tab, and then in the list box find the entry
Special Build Description, this should have the same value as your B1
patch level. If it doesn't you should
uninstall the DI you have at the moment and then reinstall the DI that
is available on the latest patch.
2. The second dll you need to test is a dll that is downloaded from the
SBO-COMMON database when the add-ons connect to the server. This dll is
found in the following location
%temp%\SM_OBS_DLL\67XXXX\OBServerDLL.dll
when opening the above path note %temp% is an enviornment variable and
is unique per operating system. Also 67XXXX, there may be many of these
directories, what you need to do is select the highest one, which
represents the latest build.
When you eventually find the dll OBServerDLL.dll, Right click on it and
go to properties, then click on the version tab, and then in the list
box find the entry Special Build Description, this should have the same
value as you B1 patch level. If it doesn't what you need to do is to
delete the folder SM_OBS_DLL, this is a temporary folder so it is OK to
do this. Now restart the addon you are using (DTW, Fixed Assets e.t.c.),
fter it has initialised goto the %temp%\SM_OBS_DLL\67XXXX\ folder again
nd look at the Special build Description of the OBServerDLL.dll. If
gain it is bnot the same version then the SBO-COMMON database is not
he correct version, if this is the case please run the SBO Upgrader
tility available in the downloaded patch.
If the solution above can't solve your issue, you have reinstall DTW again.
Thanks
Apple

Regarding exception in the WebService(Business One)

Hi all,
I have installed Business One in my system.My requirement is to display the sales order details.I am using java connector and SAP NetWeaver Developer Studio for this purpose.
process:
--I've also included external jar files sboapi.jar and sbowrapper.jar
--I've written a query to get salesorder details from ORDR table.
--I am handling the IRecordSet object.
--I have written a method which returns an object array of SalesOrder class which i have created for this purpose only.
By writing normal java program it is working fine and records are displaying form that SalesOrder object which i've created.
I've created a webservice with the same code and deployed in the WAS of SAP.While testing it is showing an exception
"Exception in method getSalesOrderDetails()".
Any one please guide me in this issue.
Thanks and Regards
Madhu

Hi Madhu,
I don't know details about WAS, but regarding Java connector (JCo) for DI API please note the following:
JCo is just a thin wrapper around the DI API COM library to facilitate using DI API in a Java enviroment.
Therefore the DLL file which encapsulates the business logic (i.e. OBServerDLL.DLL) will be copied into a local temporary directory on the file system as well - ready to be loaded from the webservice then.
I could imagine that you would need to apply some settings in WAS to enable creating a directory, copying files into it + loading files from there, but this is beyond what I know.
...I assume getSalesOrderDertails() does handle the Logon as well?
For usage in a WebService, DI Server (DI API exposed as a SOAP capable Windows service = WebService to be built on top of it) may be the better alternative... - though it also works like DI API, but inside the DI Server process - not in your WebService...
...despite some limitations (no DB structure can be changed through it etc.) ...
HTH,
Frank

DB Connect failed

Hi all,
something idea about this?
When I try to connect to Business One for the first time this error appers:
- Error code: -112
- Error description: Error extracting dll from cab
My VB.NET code is:
oGui = New SAPbouiCOM.SboGuiApi
     Try
            oGui.Connect(sSBOConn)
            mSBOApp = oGui.GetApplication()
        Catch ex As Exception
            mSBOApp.MessageBox("Connessione Gui SBO fallita")
        End Try
        mDICompany = New SAPbobsCOM.Company
        mbIsConnected = False
        GetSingleSignOneConnectionParams(mSBOApp)
        oGui.AddonIdentifier = "... add-on identifier string"
        mlRetCode = mDICompany.Connect
        If mlRetCode <> 0 Then
            mDICompany.GetLastError(mlErrCode, msErrMsg)
            '**ERROR***
            '**ERROR***
            MsgBox("Connessione con db B1 fallita. Codice errore: " + CStr(mlErrCode) + ". Descrizione" + msErrMsg, MsgBoxStyle.Critical, "Interfaccia B1-VP")
        Else
            mbIsConnected = True
        End If
Private Sub GetSingleSignOneConnectionParams(ByVal App As SAPbouiCOM.Application)
        Dim sCookie As String
        Dim sConnectionInfo As String
        sCookie = mDICompany.GetContextCookie
        sConnectionInfo = App.Company.GetConnectionContext(sCookie)
        mlRetCode = mDICompany.SetSboLoginContext(sConnectionInfo)
        If mlRetCode <> 0 Then
            mDICompany.GetLastError(mlErrCode, msErrMsg)
            MsgBox("Errore " & mlErrCode & vbCrLf & msErrMsg)
        End If
    End Sub

Problem solved.
Customer has a Business One terminalserver installation, where there is a flag manages the TEMP folder containing OBServerDLL.dll.
If it's true the folder is emptied each time the client ends his connection.
So every time the client try to connect to Business One, there is the exception error -112.
Setting the flag to false this error ends.

Errors connecting to 8.8

I have a VB DI-API program for 8.8 which works at a client site, but gives connection errors on my local machine when using the Trusted mode. I recently installed SQL 2008 and SBO 8.8 on my laptop and may have missed a setting. On the connect, I get "Error -8031: Unable to retrieve OBServerDLL.dll from serverl table SINF is missing". The original error was -111, which I resolved by adding my user login in SQL. The code is quite simple:
Cmp = New SAPbobsCOM.Company
With Cmp
   .Server = "DEC214"
   .CompanyDB = "SBODemoUS"
   .UserName = "manager"
   .Password = "master"
   .language = ln_English
   .DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL2008
   .UseTrusted = True
   lRetCode = .Connect
Program references include "SAP Business One DI API Version 8.8". I get same message, regardless of target database. SBO itself launches fine with the passwords provided.
Note: if I set useTrusted = FALSE and include the DbUserName and DbPassword parameters, the connect works fine.
Thanks for any pointers.

Hi David,
If you log in to SQL Studio Management using your Windows login are you able to access both the SBO-COMMON and your company database? Can you query the SINF table in SBO-COMMON while logged in to Studio Management using your Windows login?
In SQL 2008, unlike 2005, any local admins on the server do not automatically get sysadmin privileges in SQL Server. You'll need to check what security roles your login has for the SBO-COMMON and company databases. The minimum that SAP recommend is dbOwner. You could also try adding your account to the sysadmin role.
Kind Regards,
Owen

Temporary files created by SBO

SBO 6.5 SP:01 EF:07 with the SDK UI/DI creates files in the temp folder ...\Local Settings\Temp\SM_OBS_DLL
The subfolder "650097" contains multiple copies of a dll (2.4 MB), like "OBSdll080904070408.Dll"
Another subfolder called "GUI" contains LRF files for every supported language (in total 15 mb)
This all adds up to at least 20 MB, but on my system to several 100 MB additional files on the harddrive.
The folder contains the file CleanupHist.xml but SBO doesn't seem to remove these files after shutting down the applicaton.
Does anyone know why SBO creates these files or to prevent it?
Thanks,
Gerold

The OBS.....dll files are copies of OBServerDLL.dll. Each time you run an add-on that uses the DI, it creates a copy of this DLL and works with this copy.
There is a known issue about these being left behind. SAP Note 722338 details it.
John.

Regarding Exception in WebService

Hi all,
I have installed Business One in my system.My requirement is to display the sales order details.I am using java connector and SAP NetWeaver Developer Studio for this purpose.
process:
--I've also included external jar files sboapi.jar and sbowrapper.jar
--I've written a query to get salesorder details from ORDR table.
--I am handling the IRecordSet object.
--I have written a method which returns an object array of SalesOrder class which i have created for this purpose only.
By writing normal java program it is working fine and records are displaying form that SalesOrder object which i've created.
I've created a webservice with the same code and deployed in the WAS of SAP.While testing it is showing an exception
"Exception in method getSalesOrderDetails()".
Any one please guide me in this issue.
Thanks and Regards
Madhu

Hi Madhu,
I don't know details about WAS, but regarding Java connector (JCo) for DI API please note the following:
JCo is just a thin wrapper around the DI API COM library to facilitate using DI API in a Java enviroment.
Therefore the DLL file which encapsulates the business logic (i.e. OBServerDLL.DLL) will be copied into a local temporary directory on the file system as well - ready to be loaded from the webservice then.
I could imagine that you would need to apply some settings in WAS to enable creating a directory, copying files into it + loading files from there, but this is beyond what I know.
...I assume getSalesOrderDertails() does handle the Logon as well?
For usage in a WebService, DI Server (DI API exposed as a SOAP capable Windows service = WebService to be built on top of it) may be the better alternative... - though it also works like DI API, but inside the DI Server process - not in your WebService...
...despite some limitations (no DB structure can be changed through it etc.) ...
HTH,
Frank

Performance Comprisment between DI API & DI Server

Hello
Has anyone ever checked the speed differences between DI API & DI Server? I am talking specifically about documents creation - for instance, creating 100,000 invoices as a batch, 5 lines as invoice. Using DI API I'd say it will take around 2 days on an average server - any idea if this is faster using DI SERVER?

Hi Ron,
Since noone replied in the last 2 days I decided to let you at least know that an Italian partner told me recently that his experience with DI Server would be that it is "a lot" faster - whatever that means...
However, the logical checks are the same (i.e. the number of queries sent to the DB should be the same basically) since both DI API and DI Server are using OBServerDLL.DLL in the background.
I think there will be an ideal number of records put into an envelope based on system configuration (RAM, CPU, HDD, DB settings).
...maybe just modify the DI Server sample from the SDK samples accordingly and give it a try?
...but maybe someone else can come up with concrete experiences?
HTH,
Frank

SBO-Common_log grow up to 10 Gig!

Hi friends!
how can i drop/decrease log of SBO-Common DB?
at one of our clients SBO-Common_Data.mdf is of 64Mb, but SBO-Common_Log.ldf is up to 10Gb!
i've read many other forums and i didn't find there any agreement between points of view. Someone tolds that it should be done by LogBackUping and then LogShrinking, others say that it can be done by DB-detaching, deleting ldf-file and then attaching..
could u publish here your methods of decreasing SBO-Common log size?
P.S.: i've done it by 2nd method described before
thanx!

Hi Zsolt & Alexey,
Just to mention (mainly for other readers in this forum):
The SBO-Common database is - as you certainly already know - only used to store binaries like the OBServerDLL.DLL, upgrade package for the SAP Business One client, the Add-On installers and some additional things (info which license server to use, cahced list of DBs in this DB server etc.).
I.e., there's absolutely no need to keep the log information...
Besides using SQL Server Enterprise Manager you can simply run SQL queries to apply suitable settings re size of the logfile:
/* Reduce size of the logfile to xxx MB.... */
/* Please note the particular commands need to be run one-by-one... */
<b>/* Please replace "TMPE-Common_Log" with the "filename" of your logfile (in the DB properties; not the name in the filesystem...)*/</b>
PRINT 'Process <Shrinking Databases> starts'
USE "SBO-Common"
GO
DBCC SHRINKFILE ("TMPE-Common_Log", 1)
GO
/* Limit the max. size of the logfile to e.g. 500 MB
(only works, if current size is less than 500 MB); not sure also about dependencies on number of logged on users etc... */
ALTER DATABASE "SBO-Common"
MODIFY FILE
NAME = "TMPE-Common_Log",
MAXSIZE = 500MB
GO
/* Sets the size of the logfile to 500 MB
(no growth needed, if max. size is 500 MB => no fragmentation)*/
ALTER DATABASE "SBO-Common"
MODIFY FILE
NAME = "TMPE-Common_Log",
SIZE = 500MB
GO
/* Prevent logfile growth */
ALTER DATABASE "SBO-Common"
MODIFY FILE
NAME = "TMPE-Common_Log",
FILEGROWTH = 0MB
GO
PRINT 'Process <Shrinking Databases> has finished'
However, you will need to get rid of the existing 10 gig logfile first, but as I mentioned regardless how you do that, you won't loose real "data"...
HTH,
Frank
Message was edited by: Frank Moebius

Virus in OBServerDLL.dll ???

Similar Messages

Maybe you are looking for