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

Similar Messages

  • 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

  • 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

  • -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

  • 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

  • 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.

  • Adobe Reader 9.1 - Fatal Error : Acrobat failed to connect a DDE server

    Hi Everyone,
    I have some users telling me that when they try to open a pdf attachment in Outlook 2007. Nothing happens. The system just sits there as if you did not click on the attachment. If you wait long enought a popup box from adobe reader comes up and says:
    Fatal Error
    Acrobat failed to connect a DDE server.
    All the PDFs are very simple, just simple scanned images or converted over from a document into a PDF.
    I've tried repairing the install and still had no luck - same behaviour. The only way the pdf opens is if we go into task manager and close the AcroRd32.exe process or logoff and log back in.
    If it helps, the most recent system change was the upgrade to IE7 and a new anti-virus software.
    Thanks,
    KEvin

    No solution I am afraid but same problem, running full version of AVG and problem hit immediately after Adobe Reader 9.1 upgrade.  Pretty darn sure problem is in the upgrade but the relevant Restore Point was overwritten before I figured it out.  Any advice welcome.

  • 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

  • What do i do when I receive Fatal Error Acrobat failed to connect to a DDE Server

    Can I get some help? I can't get the Acrobat XI Pro to open...I get the Fatal Error Acrobat failed to connect to a DDE server.

    You already setup a discussion for this, no need to create more. It has only been an hour since your last post. Considering this is Sunday, you may have to wait a while, though it really comes down to when someone with an answer happens to stop by. We are just users, not employees of Adobe (that is why it is called a user-to-user forum). I remember seeing posts on this in the past and suggest you do a forum search for past posts. I do not have the solution at hand.
    There are several posts under "DDE Server Acrobat Installation" search.

  • Adobe Reader won't open pdfs. Message : Fatal Error: Acrobat failed to connect to a DDE server.

    What can I do to restore my Adobe Reader to working order. Worked fine yesterday. Today, won't open any pdf  docs in Adobe or saved on the computer. Message keeps popping up: Fatal Error: Acrobat failed to connect to a DDE server.

    DDE stands for Dynamic Data Exchange, check this threat
    http://forums.adobe.com/message/1877300#1877300

  • Windows 7- Adobe Reader X 10.1.4- "An Internal Error Occurred"-"Fatal Error, Adobe Failed to connect

    I downloaded Adobe Reader X 10.1.4  lately and I could not open any pdf file I have and gave a message, "An Internal Error Occurred. I tried to change it under the Program Features for updates and fixes  and re-started my computer. Then I tried to open again a pdf file and a message " Fatal Error", Adobe failed to connect to DDE Server. What do I need to do to fix this up? Is Adobe even aware of this?

    If all things fail and you are not getting a resolution to this. Delete the Windows 7 User profile.   C:\Windows\Users\<user name>
    Reboot, then recreate the user profile by logging on as the User.   You are not done yet.
    Logoff and log back as Administrator and go to Regedit and manually delete the user profile from the Registry.
    Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\[SID]    look for the User name.bak
    Delete it.   Then reboot and go back and log on as the user.  That should fix it.
    If you get lost with those instructions on how to delete user profile.  Go to this link:
    The best way to delete the user profile from a domain joined Windows PC - fixedByVonnie

  • Fatal Error Acrobat failed to connect to a DDE server?

    Need help, Adobe Acrobat Pro 11 will not open.  Fatal Error Acrobat failed to connect to a DDE server.

    Hi joanne36657607,
    I a sorry that you are experiencing this issue & will be happy to help you.
    Please provide some more information in order to diagnose the issue correctly.
    1) Which Operating System you are using.
    2) Exact version of Acrobat.
    3) What were you doing when this problem start occurring.
    4) Have you tried re-installing the product, if not, then please try it.
    Regards,
    Aadesh

  • When I try to open a pdf I get the following error "Acrobat failed to connect to a DDE server" what should I do?

    When I try to open a pdf I get the following error "Acrobat failed to connect to a DDE server" what should I do?

    I have not had this error before, but Google has numerous examples. Here are a couple:
    https://forums.adobe.com/thread/847438
    http://community.spiceworks.com/topic/134868-adobe-acrobat-fatal-error-failed-to-connect-t o-a-dde-server

  • Error OCCURRED: Failed to connect to LiveCycle server via RMI. Make sure that the server is running

    I have installed LifeCycle trial version .
    and trying to convert pdf to rtf
    using following initialization
    Properties connectionProps = new Properties();
    connectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_EJB_ENDPOINT, "jnp://localhost:1099");
    connectionProps.setProperty(ServiceClientFactoryProperties.DSC_TRANSPORT_PROTOCOL,Service ClientFactoryProperties.DSC_EJB_PROTOCOL);
    connectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE, "JBoss");
    connectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_USERNAME, "administrator");
    connectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_PASSWORD, "password");
    //Create a ServiceClientFactory instance
    ServiceClientFactory factory = ServiceClientFactory.createInstance(connectionProps);
    but i am getting error like following though i have started jboss which is inside lifecycle folder by run.bat
    ERROR IS:Error OCCURRED: Failed to connect to LiveCycle server via RMI. Make sure that the server is running and accessible to this client.

    May be you could use "netstat" or other tools like "ActivePorts" to ensure that ports established are correct.
    Also try if jnp://127.0.0.1:1099 works or not, if ports are correct.

Maybe you are looking for

  • Possible Bug When Binding Data to ContentPresenter ToolTip Attribute

    Hello everyone, I'm developing a small application using WPF. I have a custom ListBox control which contains a number of CheckBox entries paired up with a ContentPresenter object which displays some text obtained from a custom generic object. If I bi

  • Ipad2 not connecting to itunes anymore

    I have had my ipad2 for about 3 or 4 months, and havent had any problems until now. Now, I can't seem to connect to itunes, which has always worked in the past. Also, It doesnt say it is charging, but it does seem to be. It did connect once for about

  • Problem opening secondary screen (add file, change info, add folder, etc)

    Whenever I open a secondary scren it automatically moves behind the itunes main window and it disables my ability to use itunes. My temporary solution is to press alt + tab to bring up the secondary creen. However the screen will intermitantly move b

  • Want answer from experts tables used in cost raw material

    hi friends, how do i know about diff fico tables involved in diff batches. actullay i want to know f status of diff batches under diff materials. kindly help me out if any body have answer.                                      OR which table are used

  • Starting JWS on a remote linux Machine

    how can i start an application through JWS, running as a daemon in the background, without using X11 as my application doesnt need one