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

Similar Messages

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

Urgent please - Error Testing connection pool

I have a connection pool and datasource working fine, but when I click at the testing hyperlink on the weblogic console/jdbc/testing, the following message apear at the Unix console.
Caused by: javax.management.MalformedObjectNameException: bad object name,property Location has multiple values in Name=hom59DataSource,Type=ApplicationRuntime,Location=cbdHom,ServerRuntime=cbdHom,Loc
ation=cbdHom,Type=JDBCDataSourceRuntime
at java.lang.Throwable.<init>(Throwable.java:57)
at java.lang.Throwable.<init>(Throwable.java:68)
at weblogic.management.WebLogicObjectName.extractProperties(WebLogicObjectName.java:571)
at weblogic.management.WebLogicObjectName.<init>(WebLogicObjectName.java:326)
at weblogic.management.WebLogicObjectName.setParentFromObjectName(WebLogicObjectName.java:934)
at weblogic.management.WebLogicObjectName.populate(WebLogicObjectName.java:851)
at weblogic.management.WebLogicObjectName.<init>(WebLogicObjectName.java:328)
at weblogic.management.WebLogicObjectName.<init>(WebLogicObjectName.java:822)
at weblogic.management.jmx.MBeanServerInvocationHandler.getWebLogicObjectName(MBeanServerInvocationHandler.java:80)
Somebody please could help me?
Message was edited by:
Denimar

Have figured this out. Need to set the "Test Connections" settings under Configurations
(Advanced Options) for the Connection Pool.
Thanks for your help :)
Joe Weinstein <[email protected]> wrote:
Everbright wrote:
Hi,
I've just started working on the Avitek Tutorials.
Encountered the following error message when testing the connectionpools for
both the XA and non-XA connections.
Warning! Connectivity to backend database not verified. This is eitherbecause
required connection pool attributes "TestConnectionsOnReserve" or "TestConnectionsOnRelease"
have not been enabled, or an invalid value has been specified for attribute"TestTableName".
Please check the server log for more details..
Any ideas what might be wrong?It is likely that some part of the information you specified about how
to connect to
your database was incorrect, so weblogic was unable to make a pool of
connections.
We will know more if you show us the server log file, which will contain
messages
about any errors it suffered during startup...
Joe
Thanks!

Error testing connection pools

Hi,
I've just started working on the Avitek Tutorials.
Encountered the following error message when testing the connection pools for
both the XA and non-XA connections.
Warning! Connectivity to backend database not verified. This is either because
required connection pool attributes "TestConnectionsOnReserve" or "TestConnectionsOnRelease"
have not been enabled, or an invalid value has been specified for attribute "TestTableName".
Please check the server log for more details..
Any ideas what might be wrong?
Thanks!

Have figured this out. Need to set the "Test Connections" settings under Configurations
(Advanced Options) for the Connection Pool.
Thanks for your help :)
Joe Weinstein <[email protected]> wrote:
Everbright wrote:
Hi,
I've just started working on the Avitek Tutorials.
Encountered the following error message when testing the connectionpools for
both the XA and non-XA connections.
Warning! Connectivity to backend database not verified. This is eitherbecause
required connection pool attributes "TestConnectionsOnReserve" or "TestConnectionsOnRelease"
have not been enabled, or an invalid value has been specified for attribute"TestTableName".
Please check the server log for more details..
Any ideas what might be wrong?It is likely that some part of the information you specified about how
to connect to
your database was incorrect, so weblogic was unable to make a pool of
connections.
We will know more if you show us the server log file, which will contain
messages
about any errors it suffered during startup...
Joe
Thanks!

ERROR TEST CONNECTION B1DI

HI friends,
My case is the following:
I have to implement Cockpit, i've installed Java 5.0_22, Integration Service, Di Api, EventSender all it's OK, but I tested from Integration Framework show the next error:
com.sap.b1i.adapter.dia.exception.ConnectionFailedException: Connect to Business One failed.
(-129) Connection with license server failed
{b1Server=SERVIDOR, company=SBO_CPB, licenseServer=SERVIDOR:30000, dbType=6, dbUser=sa, userName=B1i}
The test JDBC it's OK
Thanks for yours help!
Christian

Maria Trinidad:
Thanks I already actived 3 dashboard but if I could modify this? or create other.. dashboard
Other question...
I have my Ipad, now the cockpit works fine and i have configure all, do you have somethings tips for SAP BO work in the ipad?
In the Settings for my Ipad Sap 1.2 i have: <IP>:8080 UserCode: Manager PhoneNum: 123456 (the same configured in SAP)
Thanks

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

Please help! Error when testing connection, (-111) Unable to access SBO-Com

Hi everyone,
I have set up and installed the integration component on a customers site because they would like to use the dashboards and mobile solutions.
I set up a company in the SLD but I cannot get the connection to work, i only get the following message
com.sap.b1i.adapter.dia.exception.ConnectionFailedException: Connect to Business One failed.
(-111) Unable to access SBO-Common database
{b1Server=10.14.75.110, company=SAP_INUIT_AB, licenseServer=10.14.75.110:30000, dbType=6, dbUser=sa, userName=B1i}
I have used the ip-adress instead of logical names.
I cannot figure out whats wrong, I have been searching for hours..
Any ideas??
Thanks
Br
Anders

You have to install Integration tool first and then the DB. Try this , via sql take all the companies offline and refresh your SAP B1 login. The companies will not be visible. Restart integration services. Make the companies Online.
In the SAP DB change the B1i password. It should be same as the B1i admin password.
Go to SLD, change B1user password.
Logout
Refresh Integration service.
Check the SLD connection.

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

Error on testing connection in IDT

Hello,
I got a BI 4.1 SP03 over SBO. Connection is to MS SQL 12.
got a strange error while trying to create measure inside IDT, after a while that evertyhing was working fine.
Continued the 'investigation' and found out the connection in the BO to the DB fails - while pressing "EDIT" on the connection and pressing "Test" inside the popup - succeed.
Important: This is happening since upgrade from BI 4.0 to 4.1 SP03 3 days ago.
The file attached is the error I get while creating a measure on IDT.
Webi working fine, dashboards working fine. data is coming from DB fine. only IDT and DS runs into error (same error in all actions)
Couldn't find in similar case around - anyone have any idea?
Thank you,
Or.

Hi,
I have seen the BI4.1 SP03 IDT test connection failed while the test of the same connection succeed in edit connection in IDT.
It seems that the connection I created, which is an Oracle JDBC connection, in BI4.1 SP03 universe designer is somehow not compatible with IDT test although the JDBC connection works in BI Launchpad and in Webi rich client.
The workaround is to delete this problem JDBC connection IDT does not like, and recreate it in IDT instead of universe designer. After that, this recreated JDBC connection works successfully on both universe designer and IDT connection test.
Hope this helps,
Jin-Chong

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

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

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

DTW error "Unable to access SBO-Common database " for sap hana

Hi.. Experts
I am working on SAP Hana Pl 04 64 bit, On which I got the error "Unable to access SBO-Common database " While using DTW.
also company databases are also not presents,For more details for more details find out attachment.
I have also check out all services & Restart them.
Please give me proper solution.

Hi,
Please check:
1.Ensure you have the correct DB Type selected under the Login options.
2.Verify that all connection information is correct (for example, the correct user name and password or the user has enough right to connect to the database server in case Windows Authentication is used).
3. Check whether the database is running properly, make sure that the COMMON and company databases are not suspended or stopped.
4. Ensure there is no DI API version mismatch.
Thanks & Regards,
Nagarajan

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

Error while Test Connection with Connector

hi all:
     there is an error while Test Connection with Connector , I also test it through sys administration->sys configuration->
suport -> sap transaction, I got all errors, I put these two errors as folows, could you please tell me how to sovle it
***************ERROR 1 while *error while Test Connection with Connector ******************************************************
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this
system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
************error sys administration->sys configuration-> suport -> sap transaction        ********************** 1.5 #0025B3E02892006100000A0800001798000487530FB0122E#1274690722265#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt
.runtime#guodongdong#47472##n/a##690347f0670e11df98cc0025b3e02892#SAPEngine_Application_Thread[impl:3]
9##0#0#Error##Java###04:4524/05/10_0077_6087550
[EXCEPTION]
#1#com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Application URL
&\#39;:///sap(ZT1KVXBWektldldTeV9QQXBXRjNaWTRBLS1OZmRvZzBRWWY2QmN0WThNUmgqdUlRLS0=)/bc/gui/sap/its/webgui&\#39; is not valid!
Please check the protocol and host entries for system &\#39;sapdev&\#39;.
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass
(AbstractIntegratorComponent.java:123)
     at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:523)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:412)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Hi,
As per this part of the trace:
Exception in SAP Application Integrator occured: Application URL &\#39;:///sap(ZT1KVXBWektldldTeV9QQXBXRjNaWTRBLS1OZmRvZzBRWWY2QmN0WThNUmgqdUlRLS0=)/bc/gui/sap/its/webgui&\#39; is not valid! Please check the protocol and host entries for system &\#39;sapdev&\#39;. at ...
You can clearly see that the system object 'sapdev' is not configured correctly/at all - you are trying to launch transaction iView
(WEBGUI) and in order to do so you should configure the 'internet transaction server' category of the system object
with the hostname of the ITS server.
Generally the template is
<System.Access.ITS.protocol>://<System.Access.ITS.hostname>/sap<ESID>/bc/gui/sap/its/webgui?\....
So that's why you got
Please check the protocol and host entries for system ..

Sbo common error - test connection

Similar Messages

Maybe you are looking for