Failed to Connect to SBOCommon

Hello,
I created a simple program to get the Session ID from the di server using the VB6.0, I supplied all the valid entries but i still can't get the session id. Here is the SBODI_Server.log response given to me.
<?xml version="1.0"?><env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"><env:Body><env:Fault><env:Code><env:Value>env:Receiver</env:Value><env:Subcode><env:Value>-111</env:Value></env:Subcode></env:Code><env:Reason><env:Text xml:lang="en">Failed to Connect to SBOCommon</env:Text></env:Reason><env:Detail><Command>Login</Command></env:Detail></env:Fault></env:Body></env:Envelope>

Have a look at this thread
Can't connect to Company Database w/ SOAP

Similar Messages

Solution Error #: -111 Failed to Connect to SBOCommon.

Good morning.
We are representatives of SAP Business One
I have a problem in the sap.
We have a web application working properly and where a trial basis to validate the changes delivered to the customer.
But when the application will make the communication with the sap returns me the following error.
Unable to save the quote
Error #: -111 Failed to Connect to SBOCommon.
I wonder if anyone can help me in this doubt.

Hi,
Welcome you post on the forum.
You mat check this first: http://forums.sdn.sap.com/search.jspa?threadID=&q=111&objID=c44&dateRange=thisyear&numResults=15&rankBy=10001
Thanks,
Gordon

-111 Failed to Connect to SBOCommon

I am getting an occational error when I am trying to connect to one of our test databases with the DI API.
This is what the code looks like:
oCompany = New SAPbobsCOM.Company
        oCompany.Server = "192.168.123.76"
        oCompany.CompanyDB = "Feb19_ForAuditors"
        oCompany.UseTrusted = True
        oCompany.UserName = "maanger"
        oCompany.Password = "manager"
        '** Disconnect from DB if connection present
        If (oCompany.Connected = True) Then
            oCompany.Disconnect()
        End If
        Try
            '** Attempt connection to DB
            lRetCode = oCompany.Connect
        Catch ex As Exception
            MessageBox.Show("Error upon connecting to " & oCompany.CompanyDB & Environment.NewLine & _
                        ex.Message, "SAPbobCOM Error", MessageBoxButtons.OK, MessageBoxIcon.Error)
            Close()
        End Try
        If lRetCode <> 0 Then
            '** If there was a code other than 0 (connected) state why
            oCompany.GetLastError(lErrCode, sErrMsg)
            MessageBox.Show(sErrMsg)
        End If
Now normally my SAP B1 setup for the application itself is set to Used Trusted. I started off using .UseTrusted = True but it would never let me connect until it supplied .Username and .Password
Now it seems it seems to fail more often now with both the username and password as well as being a trusted connection.
I can use SAP fine, but when I try to run my little app it says Failed to Connect to SBOCommon
Is there anything wrong in the above code? I would like to use the trusted connection because I don't want to have people type in their username/password each time they run this little middleware app nor do I want to store it on each machine.
Could it possible be an issue if my program crashes and the connection to the SAP database was not closed properly and it has to wait to timeout??
Just looking to figure this out

Tyler,
You state that you get the error "occasionally". Does that mean that you do not get it all of the time?   If you do not get it all of the time, what is the difference/what has happened between the time that you do not see the error and the time that you do? What version of Business One and patch level are you using?
Here is a note from the SAP Notes database that may help, but it has to do with db ownership and also may not pertain to your issue ...
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0000979081
Eddy

ERR: SynchManager's Try Connection Button: "Failed to Connect to SBOCommon"

When running SynchManager and testing the connection, I get the same error every time:
SBO Error #-111: Failed to Connect to SBOCommon
I can see both the B1 SQL Server and the Web Tools SQL Server, but it doesn't see the SBOCommon database. It's clearly there, though - why would this happen?
Edited by: Michael Foss on Jan 22, 2008 3:48 PM - Updated Subject to make problem clearer

Jay, I've checked on the things you mentioned and am still stuck. Here're my results:
> 1) Is the DI-API at the same patch level as the patch level of the database?
How would I check this? Where would I go to view the DI-API patch level and the DB patch level?
> 2) Can you log into SBO normally?
...yes, but for some reason it blows up on me when I do certain things. This is not the first time this has happened, either. I have a backup of my SAP DB from over a month ago (same version as the current), and I restore it to the same SQL server under a different name. When I log in to it via SAP B1, it tells me that my password is expired and I need to change it. I change it to something else quick and it lets me in, but as soon as it finishes loading up it crashes. Upon trying to go in again, I use the new password and get in successfully. I'd prefer it if all of the manager passwords stay the same, so I go into Users and change the password back. When I Update the password dialog it goes through OK, but when I Update the user dialog it blows up again, password unchanged. This might be related to a different problem.
> 3) Sometimes there is a copy of an old version of SBOBobsCOM2005.dll in the windows\temp folder, do a search on the computer and if you find a SBOBobscom dll in the temp directory, delete it, it will be recreated the next time the di-api is accessed.
No such file exists anywhere in \Windows.
> 4) Are you using SA to access the SQL server? Does the SQL user have access to all of the databases?
Yes.
Any further help would be fantastic. Thanks for your time.

111 Failed to connect to SBOCommon Login - DI server

Hi,
I have developed a website that uses DI Server. I am able to successfully execute the B1 logic in my development machine. After hosting it on a server, i am getting "111 Failed to connect to SBOCommon Login" error.
Any clues?
Thanks & Regards
Amudha

You may check these threads:
Error -111 "Failed to Connect to SBOCommon" MSSQL2008
dtw error
Thanks,
Gordon

SBO Error #-111: Failed to Connect to SBOCommon

I have recently moved my databases to a SQL 2008 server on a 64bit platform. When doing so, I installed the SQL Native Client to support the client access. I can go into SAP/b1 and access everything as I did before. (Previously SQL 2005.)
When I moved the databases, I went into the Synch Manager to change my settings. I was able to enter my SQL connection information and select my databases, but when I clicked "Try Connection", I get the error message.
I have seen where others have found that reinstalling the Synch Manager has helped... this did not work for me.
I have seen where others have deleted items from the TEMP folder... this did not work for me.
I have also seen where others stated that the 64bit SQL platform is not supported with WebTools. If this is the case, then this is a problem... However, I'm begining to think that this is an issue with the support of SQL 2008.
Can someone give me some direction to help correct this issue?
Thanks!

Ugh... yes that helps, thank you.
I will update to p04 and see if that fixes my problem.
FYI for others:
zed E-Commerce 7.0.1 is now available for download to all zedIT Solutions partners for implementation.
Additions:
Express Checkout Service Tab on Business Partner detail screen Previously Purchased Item view Special Pricing view SQL 2008 compatibility New version numbering scheme Fixes and changes Credit Card data encrypted when synchronized to Business One Able to sort quotes by column heading Text label width expanded on admin homepage to display correct amount of text New instance will contain default ticket types Synch no longer fails when using stored credit card for payment method Phone number now displayed on prospect detail License request page link correct on installation using domain name and no virtual directory Initialize synch operation no longer incorrectly clears web userid UDF field when choosing UserID as the Business Partner Contacts Synch Field in the Synch Manager u2013 settings screen Correct default data populated on new instances for General mail template Single quotes and apostropheu2019s in Web Userid UDF no longer throws synch error Editing of closed service call disabled About page now shows overall product version number u201CAttentionu201D field on shipping and billing screen renamed to u201CNameu201D and moved to top Parent level category on category list page now displays links to sub categories and category description Able to sort tickets by Project and Queue Renamed u201CSupportu201D menu option in admin to u201CServiceu201D All fixes from SAP Business One E-Commerce and WebCRM(Web tools) Patch 4 merged
Edited by: Terry Oplinger on Oct 21, 2009 7:41 PM

2008-07-29 16:23:42Z - SBO Error #-111: Failed to Connect to SBOCommon

Hey guys,
I'm getting this error message when I try to connect to the company SAP database on another server. When I refresh the list of databases, I can see all of the B1 databases that are on that server, but it continues to give me this error message and prevents me from connecting to the database or editing any of the other configuration tabs.
Thanks,
Kevin

Hey Bryce,
So I was using the sa user and so I created a new SQL Server user with administrative rights. I assigned that user to the database and it seemed to have no impact on this error message I was having.
However, I did notice that the synchmanager tools is referring the SBOCommon, not SBO-COMMON as it appears in SQL Server. Is it possible that the synch manager is looking for SBOCommon when it should be looking for SBO-COMMON?
Thanks,
Kevin
Edited by: Kevin Lee on Jul 30, 2008 3:50 PM

Webserver - "Failed to Connect to SBOCommon -111"

hi, i have a little web-application, that connects to the SAP-Db via DIApi.
it worked fine on the test-server, but now in the live-environment it crashes from time to time (i can't login and get the error message mentioned above).
After a restart of the IIS it works again.
What can it be? Has anyone had the same problem?
best regards
Philipp

So,
Sorry, i did not have so many time to think this over...
Now it is better. I have thinked and ....
I am would continue the authorization line, because my experience (i have written web applications for B1 and webshops) says this. Even in the development environment it is going fine, and in the go live environment could be different from tests....
If your test environment was your PC and IIS, or VS2005, in this case the IIS was running under your account.
Now the iis is running in the name of localsystem or network service account, so it must have to be also enabled to access license and configured for dcom security.
This means, that Network service / Interactive / Self and SYSTEM users must have to be accessed to DI API in DCOM config of the running machine. Without this, it will not work.
I have found my documentation:
1.2.1 Configuring COM Security
Follow the outlined steps below to configure COM Security to work with the Business One DI API.
1.2.1.1 Windows 2003 Server Instructions
(For Windows XP or Windows 2000 instructions see section 1.2.1.2)
     In Windows, click on Start > Control Panel > Administrative Tools > Component Services.
     Under Console Root click once on Component Services.
     A folder called Computers will appear on the right. Double-click on it.
     An icon labeled My Computer will appear in the same window. Right click on it and select Properties.
     Click on the Default COM Security tab.
     Under the section labeled Access Permissions click on Edit Default.
u2022     Within the Group or User Name area, the following groups should appear: Network Service, Interactive, Self, and System. Click on each of these groups to assure that Allow is selected for everything under the Permissions area. If any of these groups are missing, follow the directions below:
u2022     Click Add.
u2022     Type "YOUR MACHINE NAME\network service". (Substitute "YOUR MACHINE NAME" with the webserveru2019s name. Do not use quotes.)
u2022     Click Check Names.
u2022     Click OK.
u2022     Click Add.
u2022     Type "interactive" (without quotes).
u2022     Click Check Names.
u2022     Click OK.
u2022     Double-check to make sure Allow is checked for all permissions. Click OK when finished.
     Select Edit Default in the Launch Permissions section.
     Under Group or User Names, the selections Network Service, Interactive, Self, and System should be available. If any are not, follow these steps:
u2022     Click Add.
u2022     Type "YOUR MACHINE NAME\network service". (Substitute "YOUR MACHINE NAME" with your the webserveru2019s name. Do not use quotes.)
u2022     Click Check Names.
u2022     Click OK.
u2022     Click Add.
u2022     Type "interactive" (without quotes).
u2022     Click Check Names.
u2022     Click OK.
u2022     Double-check to make sure Allow is checked for all permissions. Click OK when finished.
     Select each user in the Group or User Name window and assure Allow is selected for all Permissions in the window located below them.
     Back in the My Computer Properties screen select the Default Properties tab.
     Place a check in the Enable Distributed COM on this Computer selection.
     Place a check in the Enable COM Internet Services on this Computer selection.
     Under Default Authentication Level, click the drop-down arrow and select Connect.
     Under Default Impersonation Level, click the drop-down arrow and select Identify.
     Click OK.
     Close the Component Services window and reboot your system.
1.2.1.2 Windows XP and 2000 Installation
     In Windows, click on Start > Control Panel > Administrative Tools > Component Services.
     Under Console Root click once on Component Services.
     A folder called Computers will appear on the right. Double-click on it.
     An icon labeled My Computer will appear in the same window. Right click on it and select Properties.
     Click on the COM Security tab.
     Under the section labeled Access Permissions click on Edit Default.
     Within the Group or User Name area, the following groups should appear: ASP.NET, Interactive, Self, and System. Click on each of these groups to assure that Allow is selected for everything under the Permissions area. If any of these groups are missing, follow the directions below:
u2022     Click Add.
u2022     Type "YOUR MACHINE NAME\ASPNET". (Substitute "YOUR MACHINE NAME" with the webserveru2019s name. Do not use quotes.)
u2022     Click Check Names.
u2022     Click OK.
u2022     Click Add.
u2022     Type "interactive" (without quotes).
u2022     Click Check Names.
u2022     Click OK.
u2022     Double-check to make sure Allow is checked for all permissions. Click OK when finished.
     Select Edit Default in the Launch Permissions section.
     Under Group or User Names, the selections ASP.NET, Interactive, Self, and System should be available. If any are not, follow these steps:
u2022     Click Add.
u2022     Type "YOUR MACHINE NAME\ASPNET". (Substitute "YOUR MACHINE NAME" with the webserveru2019s name. Do not use quotes.)
u2022     Click Check Names.
u2022     Click OK.
u2022     Click Add.
u2022     Type "interactive" (without quotes).
u2022     Click Check Names.
u2022     Click OK.
u2022     Double-check to make sure Allow is checked for all permissions. Click OK when finished.
     Select each user in the Group or User Name window and assure Allow is selected for all Permissions in the window located below them.
     Back in the My Computer Properties screen select the Default Properties tab.
     Place a check in the Enable Distributed COM on this Computer selection.
     Place a check in the Enable COM Internet Services on this Computer selection.
     Under Default Authentication Level, click the drop-down arrow and select Connect.
     Under Default Impersonation Level, click the drop-down arrow and select Identify.
     Click OK.
     Close the Component Services window and reboot your system.
regards,
J.

X64: ERR -111: Failed to Connect to SBOCommon

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

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

Failed to connect Error - Need Help, Please

I installed , created the simple "Hello" program and it ran fine on the simulator.
Then, I click the run OTA and now I'm in deep yogurt!
I get the message:
*** Error ***
Failed to connect to device 0!
Reason:
Emulator 0 terminated while waiting for it to register!
BUILD SUCCESSFUL (total time: 4 seconds)
I just want to restore things to what they were before I selected Run OTA. I've been reading for the past 3 hours and haven't found out to restore. I even deleted and re-installed but, still get the same meassge (probably some saved java pref file...). Anyway, HOW TO RESTORE to a virgin setup????
Thanks

... I read somewhere I need to reboot - I did and it took care of it.

Remote app on ipod fails to connect to itunes 10

After upgrading to iTunes 10, my remote app on the ipod touch 4G fails to connect. I've reauthorized, which times out most times, but eventually when it works, it only continues to connect to iTunes until I close and restart the program. I've disabled all firewalls and still have the issue. iTunes 10/iPod Touch 4G/iOS 4.1/ancient remote.app do not play well together.
Anyone else unable to get the remote app working reliably with this combination?

Hello all,
I would like to get more details from people who are still having trouble getting Remote 2.0.1 to connect. If you are unable to connect, please email me <[email protected]> with the following information:
- A detailed description of the specific issue you are seeing.
- What OS is on the host computer? (the one with iTunes on it)
- What OS is on the affected iOS device(s)?
- A description of your network topology. Please be as detailed as you can, including hardware and firmware versions, if possible. Also please explain how everything is connected.
- Is the base station running default settings, or do you have any non-standard settings enabled? If so, please elaborate.
- Do you have the built-in firewall enabled on the host computer?
- Do you have any other firewall or Internet protection (anti-virus, etc) installed on the host computer?
- Were you able to connect with versions of Remote prior to 2.0?
- If you have multiple computers, can you get Remote to connect to any of them?
- Does Home Sharing work between computers on your network?
- Do you see any messages in Console (in Applications/Utilities) on the host computer that seem to coincide with the connection failures?
Thanks,
Roy
<[email protected]>

My iphone 5 won't make a call when i fail to connect to the internet via 3g

My iphone 5 won't call when i fail to connect to the internet via 3g.
At work i dont have wifi i have 3g, if i launch say the sky go app,or the iplayer, sometimes they work and everything is fine...sometimes they wont load as 3g for whatever reason cant get a connection at that particular time........ if i then try and make a call the call will fail. I've experimented 25 + times and this is definately the cause.
(note: when the 3g connection does work, the phone has absolutely no problem calling people)
Anyone had this problem?
Even better has anyone got a solution?
Thanks,
Nick.

Are you sure that the carrier's signal is strong where you are having this problem? Certain building structures and locations have poor cellular signal strength and this often results in the "No Service" indication. Are other users able to get service in the same locations where you have problems?

On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

I have a new install of Windows 2012.  I have two physical servers. One is a W2012 std Domain Controller ("DC"). The Second is configured as W2012 HyperV  ("HV"). Under HV I have
two VMs. One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS"). All systems are behind a firewall appliance. Exchange is working via Outlook and OWA internally and externally. The self
created SSL must be installed manually on external machines since it comes up as an untrusted certificate. Once installed remote outlook works and OWA works. I have configured the terminal server and I am able
to login remotely as various users under my "TS group". The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
for alias@ domain, then fails the logging on to the mail server) The error reads: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The
connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC. I have
tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command. I have also tried to use the guid via "Get-Mailbox
ALIAS | fl name, exchangeguid. Keep in mind all desktop users on the network are connecting to Outlook without issue.
I would appreciate any thoughts on solving this issue.

Hi,
According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
Regards,
Winnie Liang
TechNet Community Support

My new i phone 5 wont sync with my laptop, keeps saying failed to connect to sync services. any help?

I just purchased a new i phone 5. when i go to connect with my laptop it says 'failed to connect to sync services, try again later' it shows my phone, and i can see my app screens, however it wont let me sync, back up or make changes. this is my first apple product, any help would be greatly appreciated.

Hello there, load dogg.
The following Knowledge Base article provides some in-depth steps to help troubleshoot the issue you are descibing:
iTunes for Windows: "Unable to load data class" or "Unable to load provider data" sync services alert
http://support.apple.com/kb/ts2690
Thanks for reaching out to Apple Support Communities for answers to your question.
Cheers,
Pedro D.

OBIEE 11g agents are failed to connect to Essbase

OBIEE 11g agents are failed to connect to Essbase. We are using :USER & :PASSWORD (SSO) in connection pool setting to connect to Essbase.
User account exists in both OBIEE and Essbase. OBIEE dashboards which are based on Essbase are working fine. Essbase variables in RPD are upto date.
Only agents are failing and error says invalid credentials, but dashboard pages are running without any issue.
OBIEE: 11.1.1.5 (BP4)
Essbase: 11.1.2.1
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Login fails due to invalid login credentials (HY000)
Essbase and OBIEE services are up and running.
Any help will be appreciated.

We finally implemented CSS Token option and ended up with this error. We are unable to connect to essbase with CSS Token option.
We followed the Oracle document to implement this.
[nQSError: 43119] Query Failed: EPMCSS-00301: Failed to authenticate user. Invalid credentials. Enter valid credentials. (HY000)
We did update this property:
JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME} -Dweblogic.home=${WLS_HOME} -Didstore.identityAttribute=objectguid"
Any help will be appreciated!

Failed to Connect to SBOCommon

Similar Messages

Maybe you are looking for