2007A: -103-Connection to SBO-Common Failed

Hi,
   I am getting the above metnioend error message when I try to connect to 2007 B1 DI API using sample code provided wiht SAP sdk.
I have verified that I have a posting period for 2007. Any help is appreciated.
globals.oCompany.Server = "TWBSLT119";
        globals.oCompany.language = SAPbobsCOM.BoSuppLangs.ln_English;
        globals.oCompany.CompanyDB="SBODemo_US";
                        globals.oCompany.DbServerType= SAPbobsCOM.BoDataServerTypes.dst_MSSQL2005;
                        globals.oCompany.DbUserName="sa";
                        globals.oCompany.DbPassword = "sa";
                        globals.oCompany.UserName="manager";
                        globals.oCompany.Password="manager";
                        globals.oCompany.LicenseServer = "TWBSLT119";
                        int x = globals.oCompany.Connect();

Hi,
Two "Maybe"'s:
1. DbPassword = "sa"; - please verify this info is correct in your DB.
2. CompanyDB="SBODemo_US"; - please note that it might be SBODemoUS (without the "_" char).
Regards,
Hagai.

Similar Messages

Add-On connection for Journal Entry - Failed to Connect to SBO Common

We have a customer (SAPBO 2005A SP01 PL29) with some specific requirements that required an add-on running in the background to monitor the addition of Goods Receipt PO's to the system. When the GRPO is successfully added, the Add-On will (behind the scenes) create an appropriate Journal Entry through the SAP DI. One of the issues that we encountered during the development of this functionality was that when it was tested by users, they weren't authorized to access the Financials module or the Journal Entry screen. What we ended up doing was creating a secondary connection (vCompany) in the DL pulling the information from the encrypted user information from SAP the Add-On used to connect, but utilizing a management level user ID and password. Once that connection has been made, the Journal Entry is added through the DI and that secondary connection is disconnected.
The problem that we're encountering is this. When the users are logged into SAP Client with an regular user, and the GRPO adds, the secondary connection fails and returns a message of "Failed to Connect to SBO-Common". However, if the user is logged into SAP as an adminitrative level user and the GRPO is added, the secondary connection is successful and the Journal Entry is created. The secondary connection is strictly used for the JE. Here's the code (VS.Net 2005) for the secondary connection:
vCompany = New SAPbobsCOM.Company
vCompany.UseTrusted = True
vCompany.language = SAPbobsCOM.BoSuppLangs.ln_English
vCompany.CompanyDB = oCompany.CompanyDB
vCompany.UserName = "XXXXX"
vCompany.Password = "YYYYY"
vCompany.Server = oCompany.Server
vCompany.DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL2005
lRetConnect = vCompany.Connect()
Where "XXXXX" would be the appropriate management level SAP User Name and "YYYYY" would be that users password.
Has anyone else had this kind of issue where you needed a secondary connection with management level access behind the scenes to accomplish something in SAP and had problems getting it to connect? Any thoughts or ideas would be greatly appreciated.

Hi Dennis,
what you can try is to make a untrusted connection
oCompany.UseTrusted = False
and set the DBUser and Pwd
oCompany.DbUserName = "sa"
oCompany.DbPassword = "insertpwd"
lg David

Connection to SBO-Common has failed

Hi!
I have a application that use SAPbobsCOM.dll version 6.7.0.0 togheter with SBO2005. Ihave no problem to read data but when i try to update i have this error "Connection to SBO-Common has failed".
What shall I do?
/Thomas

Hello Thomas,
Make sure that all components of SAP have the same Patch Level to avoid any conflict in the future. If you use SBO2005 PL02, then all the DI API, DI Server etc must also be in PL02. Hope this helps...

SBO Common Failed Error

Hi
Am facing the SBO Common Failed (-111)(fff)Error while connecting the Server thru DI API Connection Object form my Add on.

You should also check the OBSCommon user in the SQL Enterprise manager. This error also pops up when the OBSCommon user's loginname is not the same as the Name. Both should be OBSCommon. If this is not the case delete the OBSCommon user and add it again with the right name and loginname. Just make sure that you also give this user the db_owner role.
Hope this helps...
yogesh

Error while connecting to SBO-common

hi,
I m getting started with the sap business one , i installed :
    sql server on machine1
    SAP business one server on machine 1
    SAP business one client on machine 2
Im trying now to apply samples provided as is by the sdk...samples concerning COM UI execute without any problems..However , COM DI samples, when executed ,return an error :
    Connection to SBO-common has failed..
plz help..
thank you

Hi,
I've had this error when the user which connects through DI has no license for DI-connections. Maybe this is the case for you also?
Hope this helps,
Jacco

2007A Install - Cannot connect to SBO-COMMON db

Towards the end of the Server install, after building the databases, a message displays that the Install is testing the connection to the SBO-COMMON db. It then tells me that it is unable to connect and displays the MSSQL log on screen for me to enter the sa password. When I enter the correct password and press ok I get the "Cannot Connect" message again.
Before running the Install I have made sure that the required MSSQL services are running (MSSQL, Agent and Browser)

Hello Tony,
Please take a look at SAP Note 979081, it may be related.
Hope it helps,
Regards,
Willy
SAP Business One Forum's team

2007 B Upgrade - Cannot connect to SBO-COMMON db

Hi,
Trying to upgrade SBO 2005B PL43 to SBO 2007B PL07.
The SBO -Common database exist
The SQL Express <TCP and Pipes> enable
In the SBO Common Upgrade, when I enter the correct server name, user, password and press OK, i get the follow error:
"The Connection to the specified server has failed"
"Check your password and the that server exist on the network"
Any idea?
Tanks

Hi Marcio
In 2007 you must specify the server type as SQL or SQL_2005 (Type 1 or Type 4). There are also limitations in 2007 with respect to SQL Express. The best is to check the supported databases on the portal or check with your local SAP office.
Kind regards
Peter Juby

Sbo common error - test connection

Hello, Im trying to connect the B1DI in SBO common, but I can't:
This error appears:
XCE001 Nested exception: java.rmi.RemoteException: com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: java.net.MalformedURLException: invalid authority: rmi://license_server_name:2099/DiaAdapterProxy_XXX
If I write the IP address, is another error: -8012... I checked the note "Troubleshooting on B1ic Version 8.81" but the patch level are correct...
Can somebody help me??
Thank you!
Sorry for my english!!
Paulina

Hi Paulina,
You cannot successfully connect to SBO-Common via the B1DI test connection since its actually not like a normal Business One database. Therefore you should only test connections to normal B1 databases. If they do not exists in the SLD then you can create one.
Cheers,
Lisa

SBO-Common error when Using oRecordSet = oCompany.GetCompanyList

Good Day
Experts:
I am having a bit of trouble running the code in the COM DI\05.OrderAndInvoice sample.
On the line --> oRecordSet = oCompany.GetCompanyList
An error appears "Connection to SBO-Common has failed".
I would like to do the same thing in one of my screens but I cannot even get the sample to work. I am not sure
what connecting to SBO-Common does but appearently I need that since the sample or my application does not work.
Can anyone help?
Thanks,
EJD

oCompany = New SAPbobsCOM.Company
' Init Connection Properties
oCompany.Server = "servername" ' change to your company server
oCompany.DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL2005
oCompany.DbUserName = ""
oCompany.DbPassword = ""
oCompany.UseTrusted = True
lRetCode = oCompany.Connect()
If lRetCode <> 0 Then ' if the connection failed
oCompany.GetLastError(lErrCode, sErrMsg)
MsgBox("Connection Failed - " & sErrMsg, MsgBoxStyle.Exclamation, "Default Connection Failed")
End If
'Create a list of companies...
oRecordSet = oCompany.GetCompanyList ' get the company list

SBO COMMON Upgrade

Dear All,
Currently I am using SAP B1 2007 B PL00, I want to upgrade with PL 08,
When I am upgrading SBO COMMON, system giving one error The connection to the specified server has failed. Check your password and that the server exists on the network
I verified SQL Server ID an Password It is correct, I am doing this task on server where SQL server has installed
Thanks,
Siddique Shaikh.

Hi Siddique,
Check the thread
Installation issues - Connection to the specified server has failed
2007 B Upgrade - Cannot connect to SBO-COMMON db
*Close the thread if issue solved
Regards
Jambulingam.P
Edited by: Jambulingam P on Aug 10, 2009 11:58 AM

DTW - SBO Common is failed

Hi Experts,
I am getting an error while connecting to the server through Data Transfer Workbench. the error is "SBO Common is failed". Why I am getting this error.
Edited by: Darius Heydarian on Mar 18, 2008 3:13 PM

Hi Douglas,
I am getting this error when I open DTW to import the data from Excel files. Before that I need to log on to server., right , at the beginning of the log on when I am mentioned the username and password and server name... then the error SBO-Common has failed is displayed
venkat

DTW- "Connection to SBO Commeo has failed"

Dear All
After the installation of DTW in Client (Not in Server) machine i am trying to log on to DTW i am getting following message
Connection to SBO Commeo has failed
I filled In Server name = OC-SAP (Server Name)
License Server = OC-SAP:30000
What could be the reason and how can i solve the issue
Regards
Rashid

Dear Rashid,
Please check the below information is entered while login
1. Click on the "Options >>" button.
2. Tick the "Choose Database" CheckBox
3. Select "SQL Server" or SQL Server 2005 in the DBType combobox.
4. Set the DBUser (e.g. sa) and its password.
5. Click on the "Refresh" button in order to fill the Company list.
Regards
Vijay kumar

Sbo-common sbo 2007A

Hi,
i've a problem. i want to copy my sbo-common 2007A PL45 in my computer to another server because i've a problem with terminal server installation. Can i do it without problem? Thanks a lot

Yes u could do it, but you also could use the SBO-Common from the installation CD.

SBO COmmon Upgrad Error

hello all,
im doing an upgrade from SBO 2007a SP01 PL09 to SBO2007a SP01 PL12, but when i upgrade the sbo common database it gives me this error. [see Image|http://s264.photobucket.com/albums/ii184/abing430/SAP/?action=view&current=CommonError.jpg]. base on this error i have found this sap note 1379089, but when i get to the service manager - Event Sender my computer hangs up...
please help..
best regards,
Fidel

Hello Fidel,
Have you checked the forum?
You may start from the follows:
Unable to install 8.8 client
Upgradation Failed - SAP b1 8.8 PL 12
Thanks,
Gordon

RFC_ERROR_COMMUNICATION: Connect to message server failed

Hi,
I think this is the most common error that one can face and have seen quite a few threads in the forum. Still, i couldn't resolve my problem.
I am getting the following error when i tried to connect to SAP using SAP JCO connector with load balancing.
(102) RFC_ERROR_COMMUNICATION: Connect to message server failed
Connect_PM MSHOST=sapserver, R3NAME=D11, GROUP=Group1
LOCATION    CPIC (TCP/IP) on local host
ERROR       partner not reached (host sapserver, service sapmsD11)
TIME        Wed Jun 24 16:05:49 2009
I added the service sapmsD11 in the services file of my client as well as in R/3 server.
I got the above error when i tried to connect using load balancing. Without load balancing, i was able to connect to R/3 server successfully. Can any one tell how to figure out the message server host name ?
Can the application server host name and message server host name be same ?
PS: I am able to ping my R/3 server from my client.
Thanks,
Prasad.

Hi,
Check that you have configured properly using the below document. And check the message server of R/3 is configured properly in the SLD.
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5
Function module to get the message server host name and port in R/3.
SLDAG_GET_MESSAGE_SERVER_INFO
See this thread also..
Re: Jco Destination
Regards,
Charan

2007A: -103-Connection to SBO-Common Failed

Similar Messages

Maybe you are looking for