I created a data source on my local WAS.The database I am trying to connect is on a dev sql server 2012 host.When I do a test connection it fails with below error :
java.sql.SQLException: Login failed for user ''.
ClientConnectionId:c1c4d500-ad7c-4014-b9c2-96e8f54e4a3f DSRA0010E: SQL
State = S0001, Error Code = 18,456 [7/18/18 13:18:51:387 IST] 00000061
SystemErr R at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
[7/18/18 13:18:51:387 IST] 00000061 SystemErr R at
com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:254)
[7/18/18 13:18:51:387 IST] 00000061 SystemErr R at
com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:84
Any help in how can I resolve this?
The error message indicates that you are trying to connect without a user name specified.
Check your configuration to see if you have specified user/password on the data source or a valid authentication alias. The following
knowledge center doc lists the precedence for determining the user/password that are used for test connection operations.
Related
Good day, all.
I've currently facing issue with creating a connection to HIVE datasource from Oracle Business Intelligence.
When i enter my db credentials i get this error :
Failed to save connection.Cannot create a connection since some errors occured. Fix them and try again.
And nothing more.
Meanwhile in Weblogic Console log :
|Unsupported property passed in properties: fixedString=true|
|Unsupported property passed in properties: oracle.jdbc.J2EE13Compliant=true|
|BEA-000000| |java.sql.SQLException java.io.IOException: execute query failed[nQSError: 43113] Message returned from OBIS.
[nQSError: 16001] ODBC error state: S1000 code: 1202 message: [Oracle DataDirect][ODBC Apache Hive Wire Protocol driver]Error switching to requested database (default)..
[nQSError: 16001] ODBC error state: S1000 code: 1 message: [Oracle DataDirect][ODBC Apache Hive Wire Protocol driver][Hive]Invalid method name: 'execute'.
oracle.bi.jdbc.AnaJdbcStatementImpl.executeQuery(AnaJdbcStatementImpl.java:387)
oracle.bi.jdbc.AnaJdbcStatementImpl.execute(AnaJdbcStatementImpl.java:268)
oracle.bi.jdbc.AnaJdbcPreparedStatementImpl.execute(AnaJdbcPreparedStatementImpl.java:507)
oracle.bi.jdbc.AnaJdbcPreparedStatementImpl.executeQuery(AnaJdbcPreparedStatementImpl.java:204)
oracle.bi.datasource.jdbc.connector.BIJDBCConnector.execute(BIJDBCConnector.java:173)
oracle.bi.datasource.jdbc.connector.BIJDBCConnector.execute(BIJDBCConnector.java:93)
oracle.bi.datasource.jdbc.connector.BIJDBCProvider.getObjectList(BIJDBCProvider.java:217)
oracle.bi.datasource.service.DatasourceServiceProcessor.getObjectsList(DatasourceServiceProcessor.java:1057)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
|Error| |oracle.bi.datasource.trace| |BEA-000000| |SQL_EXCEPTION 0 : java.io.IOException: execute query failed[nQSError: 43113] Message returned from OBIS.
[nQSError: 16001] ODBC error state: S1000 code: 1202 message: [Oracle DataDirect][ODBC Apache Hive Wire Protocol driver]Error switching to requested database (default)..
[nQSError: 16001] ODBC error state: S1000 code: 1 message: [Oracle DataDirect][ODBC Apache Hive Wire Protocol driver][Hive]Invalid method name: 'execute'.
Cause - SQLException is thrown from the datasource
Action - Check the log
oracle.bi.datasource.jdbc.connector.SQLExceptionMapper.convert(SQLExceptionMapper.java:40)
oracle.bi.datasource.jdbc.connector.BIJDBCConnector.execute(BIJDBCConnector.java:215)
oracle.bi.datasource.jdbc.connector.BIJDBCConnector.execute(BIJDBCConnector.java:93)
oracle.bi.datasource.jdbc.connector.BIJDBCProvider.getObjectList(BIJDBCProvider.java:217)
oracle.bi.datasource.service.DatasourceServiceProcessor.getObjectsList(DatasourceServiceProcessor.java:1057)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
|
|Error| |oracle.bi.datasource.trace| |BEA-000000| |java.util.concurrent.ExecutionException oracle.bi.datasource.exceptions.DatasourceException: 0 : java.io.IOException: execute query failed[nQSError: 43113] Message returned from OBIS.
[nQSError: 16001] ODBC error state: S1000 code: 1202 message: [Oracle DataDirect][ODBC Apache Hive Wire Protocol driver]Error switching to requested database (default)..
[nQSError: 16001] ODBC error state: S1000 code: 1 message: [Oracle DataDirect][ODBC Apache Hive Wire Protocol driver][Hive]Invalid method name: 'execute'.
Cause - 0 : java.io.IOException: execute query failed[nQSError: 43113] Message returned from OBIS.
[nQSError: 16001] ODBC error state: S1000 code: 1202 message: [Oracle DataDirect][ODBC Apache Hive Wire Protocol driver]Error switching to requested database (default)..
[nQSError: 16001] ODBC error state: S1000 code: 1 message: [Oracle DataDirect][ODBC Apache Hive Wire Protocol driver][Hive]Invalid method name: 'execute'.
java.util.concurrent.FutureTask.report(FutureTask.java:122)
java.util.concurrent.FutureTask.get(FutureTask.java:206)
oracle.bi.datasource.service.adf.server.DatasourceServlet.doGet(DatasourceServlet.java:442)
javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
|
|Error| |oracle.bi.web.datasetsvc| |BEA-000000| |getObjectList failed for 'weblogic'.'HiveDS'|
|Error| |oracle.bi.tech.services.dataset| |BEA-000000| |Failed to create connection. : Bad Request - {"code":400101,"message":"JDS - Invalid syntax","subMessage":"oracle.bi.datasource.exceptions.DatasourceException: 0 : java.io.IOException: execute query failed[nQSError: 43113] Message returned from OBIS.\n[nQSError: 16001] ODBC error state: S1000 code: 1202 message: [Oracle DataDirect][ODBC Apache Hive Wire Protocol driver]Error switching to requested database (default)..\n[nQSError: 16001] ODBC error state: S1000 code: 1 message: [Oracle DataDirect][ODBC Apache Hive Wire Protocol driver][Hive]Invalid method name: 'execute'.\nCause: SQLException is thrown from the datasource\nAction: Check the log"}|
can anyone point me to possible solution?
Looks like an incorrect port number is being specified for the hive server in the database connection. Here is a similar error reported from the the same connector, but branded for IBM: http://www-01.ibm.com/support/docview.wss?uid=swg21671761
And here are connection option descriptions and default values for reference.
I am trying to make an ssl based oci connection to Oracle 11g ssl enabled database using OBIEE BI server and Admin tool. The wallet and all required configurations are in place. However the connection establishment fails and in the sqlnet trace file I get the following error.
(12184) [25-OCT-2015 12:45:21:521] ntzcsgtab: INTERNAL ERROR - unknown cipher suite 157.
(12184) [25-OCT-2015 12:45:21:521] ntzcsgtab: failed with error 543
(12184) [25-OCT-2015 12:45:21:521] ntzcsgtab: exit
(12184) [25-OCT-2015 12:45:21:521] ntzini: Could not initialize Cipher Suite table.
(12184) [25-OCT-2015 12:45:21:521] ntzini: failed with error 543
I am not specifying any particular cipher suite in sqlnet.ora either in client or database, and using the default ones.
Next I tried to create jdbc connection using oci driver (using oracle instant client) and using same wallet, in a simple java client program. I was able to successfully establish the SSL enabled connection.
So it seems like Oracle client inside OBIEE might be missing some feature to handle SSL based connection. Any idea how to fix this?
Thanks in advance
Trying to diagnose a MobileFirst server error. v6.3, Liberty, Windows.
We have two supposedly identical servers, one is fine, one fails.
Symptom: server starts but console reports a server error when trying to populate the initial list of runtimes. Investigating further we see an attempt to call an admin service.
So we attempt to call that service directly from a browser. On the working server we see
{"projects":
[{"name":"DM","link":"https://shqomfas01.dm.gov.ae:9443/wladmin/management- apis/1.0/runtimes/DM","numberOfAdapters":16,
"numberOfApplications":2,"synchronizationStatus":"ok",
"numberOfActiveDevices":0,"numberOfDecommissionedDevices":0,
"running":true}],"productVersion":"6.3.0.00-20141127-1357"}
On the other server we get an error response and see these exceptions in the logs.
[6/16/15 11:42:23:284 GST] 000000ec RuntimeServic > RuntimeService getAllRuntimes ENTRY uri=https://shqomfas02.dm.gov.ae:9443/wladmin/management-apis/1.0/runtimes/ securityContext=org.apache.wink.server.internal.contexts.SecurityContextImpl_83263026 httpRequest={Loc=en_US, Locs=(en_US,), User=admin, RemoteUser=admin} null
[6/16/15 11:42:23:284 GST] 000000ec SystemErr R 1832175 WorklightManagementPU-oracle INFO [LargeThreadPool-thread-164] openjpa.Runtime - Starting OpenJPA 1.2.2
[6/16/15 11:42:23:284 GST] 000000ec SystemErr R 1832175 WorklightManagementPU-oracle INFO [LargeThreadPool-thread-164] openjpa.jdbc.JDBC - Using dictionary class "org.apache.openjpa.jdbc.sql.OracleDictionary".
[6/16/15 11:42:23:331 GST] 000000ec LibertyRuntim I Establishing REST connection to service:jmx:rest://localhost:9443/IBMJMXConnectorREST
[6/16/15 11:42:24:097 GST] 000000ec RuntimeServic > ResponseUtil error ENTRY
[6/16/15 11:42:24:112 GST] 000000ec RuntimeServic E FWLSE3000E: A server error was detected.
com.ibm.worklight.admin.common.util.exceptions.SystemException: FWLSE3000E: A server error was detected.
at com.ibm.worklight.admin.services.RuntimeService.addMBeanProperties(RuntimeService.java:1112)
at com.ibm.worklight.admin.services.RuntimeService.getAllRuntimes(RuntimeService.java:306)
...
Caused by: java.io.IOException: CWWKX0214E: An unexpected Throwable object was returned from the server.
at com.ibm.ws.jmx.connector.client.rest.internal.RESTMBeanServerConnection.getAttribute(RESTMBeanServerConnection.java:758)
at com.sun.jmx.mbeanserver.MXBeanProxy$GetHandler.invoke(Unknown Source)
at com.sun.jmx.mbeanserver.MXBeanProxy.invoke(Unknown Source)
at javax.management.MBeanServerInvocationHandler.invoke(Unknown Source)
at com.sun.proxy.$Proxy163.getDevicesSummary(Unknown Source)
at com.ibm.worklight.admin.services.RuntimeService$RuntimeMBeanProperties.<init>(RuntimeService.java:1021)
at com.ibm.worklight.admin.services.RuntimeService$3.call(RuntimeService.java:1050)
at com.ibm.worklight.admin.services.RuntimeService$3.call(RuntimeService.java:1048)
at com.ibm.worklight.admin.util.RuntimeMBeanRoutingCaller.call(RuntimeMBeanRoutingCaller.java:66)
at com.ibm.worklight.admin.services.RuntimeService.addMBeanProperties(RuntimeService.java:1045)
... 73 more
Caused by: javax.management.RuntimeMBeanException: java.lang.RuntimeException: Runtime synchronization failed. Cannot get devices summary from runtime
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(Unknown Source)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(Unknown Source)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(Unknown Source)
suggestions?
We were seeing this issue today. We had recently made configuration changes to the server.xml file, and we received the "Server ERROR" message after login to the Worklight Console.
Reinstalling the runtime fixed our issue.
We are facing an issue on our PROD environment where it shows the following error message:
The home page shows that the runtime contains the project files:
There error on the WAS is:
[5/1/15 12:38:29:901 EDT] 0000009f ApplicationMa E
com.worklight.mgmt.impl.ApplicationManagementImpl getApplicationRuntimeInformation FWLSE0023E: application 'MobileBanking' not found, please redeploy. [project MobileBanking]
[5/1/15 12:38:29:947 EDT] 0000009f DMAdapter I com.ibm.ws.ffdc.impl.DMAdapter getAnalysisEngine FFDC1009I: Analysis Engine using data base: /wl62/profiles/node1/properties/logbr/ffdc/adv/ffdcdb.xml
[5/1/15 12:38:30:069 EDT] 0000009f FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /wl62/profiles/node1/logs/ffdc/server11_wl_3e94673b_15.05.01_12.38.29.9336586937544274552029.txt com.ibm.ws.management.AdminServiceImpl.invoke 693
[5/1/15 12:38:30:573 EDT] 00000100 ApplicationSe E FWLSE3000E: A server error was detected.
java.lang.IllegalArgumentException: FWLSE0023E: application 'MobileBanking' not found, please redeploy. [project MobileBanking]
at com.worklight.mgmt.impl.ApplicationManagementImpl.getApplicationRuntimeInformation(ApplicationManagementImpl.java:165)
at com.worklight.core.jmx.ProjectManagementMXBeanImpl.getApplicationRuntimeInformation(ProjectManagementMXBeanImpl.java:673)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:76)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:607)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:75)
at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:607)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:279)
at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193)
at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117)
at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:1335)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:1228)
at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:181)
at com.ibm.ws.management.connector.ipc.CallRouter.route(CallRouter.java:247)
at com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink.doWork(IPCConnectorInboundLink.java:360)
at com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink$IPCConnectorReadCallback.complete(IPCConnectorInboundLink.java:602)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1862)
We have reinstalled the runtime more than once, and it says successful, we also recycled the dmgr, node, cluser, server and the runtimes and all shows green arrows with successful start up message.
Same WAR file is used on our Dev, QAT and UAT and they all running up with no issues.
Worklight Version 6.2.0.1
WAS version 8.5.5.1
Any help to resolve it, thanks.
We were able to resolve both the application issues and the Worklight service issue. There were multiple pieces that needed to be fixed. For the most part, these issues were a result of having the complexity of the how Worklight implements security. All the environment is up and running now.
Steps we followed to resolve the issue:
Make sure the exact same configuration are running on both Nodes.
Make sure that the JVM configuration are matching.
Review the security configuration on each node (SSL certificate - SLL alias and SSL keystore).
I have two applications, one is deployed in jboss as 7, another is a java application (Camel).
The camel has an exposed JMX service:
service:jmx:rmi:///jndi/rmi://172.20.30.85:19999/jmxrmi/camel
now, I need to access it from a EJB(jboss as 7). I have tried the following two ways, but both are fialed.
A) works well with jboss as 5.x:
JMXServiceURL target = new JMXServiceURL("service:jmx:rmi:///jndi/rmi://" + host + ":" + port.toString() + "/jmxrmi/camel");
JMXConnector connector = JMXConnectorFactory.connect(target);
got exception:
Caused by: javax.naming.NameNotFoundException: rmi://172.20.30.85:19999/jmxrmi/camel -- service jboss.naming.context.java.rmi:."172.20.30.85:19999".jmxrmi.camel
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:103)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197)
at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:241)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:183)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:411)
at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1929)
at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1896)
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:286)
B)
JMXServiceURL target = new JMXServiceURL("service:jmx:remoting-jmx://172.20.30.85:19999/jmxrmi/camel");
got exception:
ERROR [org.jboss.remoting.remote.connection] (Remoting "endpoint" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000202: Abrupt close on Remoting connection 79f4a60c to sha-lri-pc-161/172.20.30.85:19999
11:33:44,415 WARN [com.lombardrisk.reform.process.api.ProcessInspectorBean] (http-/127.0.0.1:8080-29) Could not connect to integration MBean server: java.lang.RuntimeException: Operation failed with status WAITING
at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:235)
at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:148)
at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:99)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:268)
at com.lombardrisk.reform.process.api.ProcessInspectorBean.getIntegrationMBeanServerConnection(ProcessInspectorBean.java:328)
at com.lombardrisk.reform.process.api.ProcessInspectorBean.getRoutes(ProcessInspectorBean.java:486)
Is there anyone who can guide me? Thanks in advance.