SSO in Microsoft Application, SQL Server 2005 & OBIEE 11g
Dear Gurus,
Any experienced how to enable SSO(Single Sign On) in OBIEE 11g, when the application platform is microsoft instead of Oracle EBS and the data source from SQL server 2005?
I am new on this.
Any help will be appreciated
Regards
JOE
Hi,
Try below link
http://sranka.wordpress.com/2008/06/06/enabling-sso-authentication-for-obiee/
http://gellio.wordpress.com/2009/10/23/enabling-oracle-single-sign-on-osso-with-obiee/
OBIEE, OAS, OID, SSO Integration
http://sranka.wordpress.com/2008/06/06/enabling-sso-authentication-for-obiee/
http://www.addidici.com/blog/?p=8
http://download.oracle.com/docs/cd/E12096_01/books/AnyDeploy/AnyDeploySSO3.html
Check the security guide here,
http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10543/sso.htm#CEGJJFED
Hope thsi help's
Thanks
Satya
Similar Messages
-
SQL Server 2005 Workgroup Edition compatibility for SAP B1 2005B
Hi Experts,
Please advise SQL Server 2005 Workgroup Edition can be used as the backend for SAP Business One 2005B.
Thanks,
ShakeelHi
Please go to:SAP service portal-product availability-supported platform-database platform
For 2005 B version we could get the following supportted information:
Microsoft?SQL Server 2005 SP2
- 32 Bit / 64 Bit (x64)
- Express (3), Workgroup (4), Standard & Enterprise Edition
Please read SAP Note 928839 on how to order SQL 2005 for upgrade purposes.
(3)SQL 2005 Express Edition is only supported with the SAP Business One Evaluation Versions and only in 32 Bit mode.
(4)SQL 2005 Workgroup Edition is only supported with Windows Small Business Server (SBS) 2003 and only in 32 Bit mode
For more detailed information regarding the supportted platform you could refer to the webpage from the above path.
Best Regards
Helen Sun
SAP Business One Forums Team -
Trouble connecting to the Microsoft SQL Server 2005 using JDBC Connection
Hi,
I am unable to connect to the Microsoft SQL Server 2005 using JDBC Connection. Kindly tell me steps to connect to the SQL Server using JDBC. The error message that I am getting while creating a data source is :
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "sap.com/JDBCConnector_KedDS.xml". [id = StartupError]
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 13169050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "KedDS".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:78)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
... 42 more
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
Found in negative cache
------------------------- Loader Info -------------------------
ClassLoader name: [library:KedDriver]
Parent loader name: [Frame ClassLoader]
No references !
Resources:
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\ext\KedDriver\sqljdbc.jar
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\core_lib\opensqlport.jar
Loading model: {parent,local,references}
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:74)
... 43 more
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
... 31 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 13169050:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "KedDS".
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:78)
at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
... 42 more
Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver
Found in negative cache
------------------------- Loader Info -------------------------
ClassLoader name: [library:KedDriver]
Parent loader name: [Frame ClassLoader]
No references !
Resources:
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\ext\KedDriver\sqljdbc.jar
E:\usr\sap\J2E\JC01\j2ee\cluster\server0\bin\core_lib\opensqlport.jar
Loading model: {parent,local,references}
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:74)
... 43 more
at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
... 33 more
at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at javax.management.MBeanException.writeObject(MBeanException.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1267)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)i'm using jcreator pro
jdk i.6
mssql server 2005
and downloaded the jdbc driver( i noticed that the msutil.jar and msbase.jar are not in the folder avalable on microsoft site Microsoft SQL Server 2005 JDBC Driver so i installed
Microsoft SQL Server 2000 Driver for JDBC 1st and just changed the jqljdb.jar file with the one available in Microsoft SQL Server 2005 JDBC Driver )
and set the path of the CLASSPATH to a folder which name has no spaces
and tried Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
and Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
and tried compiling and running with command prompt
and still have the same exception which occurs at runtime
"An exception has occured: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerDriver"
i really need help -
Required Microsoft Sql Server 2005 Server Roles for JDBC Connection
Hi!
I have developed a database in MS SQL Server 2005, to which I would require only bulkadmin server role from an external java application, because I only need to update rows, insert values or use select queries in the database.
The problem is that, using either the Microsoft JDBC Driver 1.1 or the Java JDBC ODBC Driver and the Windows XP Data Base (ODBC) configurations, I need a user with sysadmin server role inside Sql Server, otherwise JDBC won't connect to the database using the selected user. Even if I leave the sql login with setupadmin or any server role lower than sysadmin, the connection is refused.
Is there no way to connect using JDBC to MS Sql Server 2005 other than granting the connected user sysadmin rights? My code looks as follows:
String driver = "com.microsoft.sqlserver.jdbc.SQLServerDriver";
String url = "jdbc:sqlserver://FIREBLADE\\SQLEXPRESS";
String user = "username";
String password = "password$$";
Connection conn;
Class.forName(driver);
conn = DriverManager.getConnection(url,user,password);
if (conn != null)
System.out.println("\nSQL Server Connection established ...\n");
I have heard that Java JDBC connections to Microsoft require high-level access, and if that's the case I would rather migrate my database to MySql.
Any informed answer is more than welcome. Thanks for reading my post!Well i personally prefer usage of open source MS SQL SERVER 2k jdbc driver called jtds instead of the driver provided by MS themselves(which is proproteriry) as i had similar problem which i personally encountered when i was using it.
go through the below link for further info.
http://jtds.sourceforge.net/
REGARDS,
RaHuL -
Errors while migrating from Microsoft SQL Server 2005 to Oracle 9i
Hi All,
We are trying to completely move our application from Microsoft SQL Server 2005 Database to Oracle 9i. I am doing it using the latest version of Oracle SQL Developer (1.2 build 29.98).
When I right click my MSSQL server db and click "Capture Microsoft SQL server", it just shows a dialog with "Close" enabled.
Kindly help.
The migration Log has the following messages:
oracle.dbtools.metadata.persistence.PersistenceException: Unsupported feature
oracle.dbtools.metadata.persistence.PersistenceException: Unsupported feature
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Bigger type length than Maximum
oracle.dbtools.metadata.persistence.PersistenceException: Bigger type length than Maximum
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
Error ocurred during capture: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Protocol violation
oracle.dbtools.metadata.persistence.PersistenceException: OALL8 is in an inconsistent state
oracle.dbtools.metadata.persistence.PersistenceException: Bigger type length than Maximum
I cant figure out what do these messages mean.
Regards,
SandeepPasting the errors on logging page, if this is of any help:
SEVERE 150 0 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:OALL8 is in an inconsistent state
SEVERE 151 1485 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:Protocol violation
SEVERE 152 15 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:OALL8 is in an inconsistent state
SEVERE 153 10954 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:Protocol violation
SEVERE 154 15 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:OALL8 is in an inconsistent state
SEVERE 155 2688 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:Protocol violation
SEVERE 156 1140 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:OALL8 is in an inconsistent state
SEVERE 158 62172 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:OALL8 is in an inconsistent state
SEVERE 160 3672 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:Protocol violation
SEVERE 161 63 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:OALL8 is in an inconsistent state
SEVERE 162 0 oracle.dbtools.raptor.utils.NLSUtils Error loading nls:Protocol violation -
Unable to connect SQL server 2005 databse with JSF applications !
Hello guys!
Help me out to connect SQL server 2005 Databse with JSF applications using JDBC-ODBC bridge. I'm working with Netbeans 6.1 IDE.
I tried for the basic applications but instead got this error:
"unable to deploy jdbc drivers to the <project>domain/lib"
Please help me out with working sample codes that connects MS SQL server 2005 DB with JSF!!
Thank you guys!1) don't use the bridge driver
2) don't do database access from JSF
3) learn how to use your application server
4) learn how to use your IDE -
Error when creating a FDM application on SQL Server 2005
Hi,
we are getting this error when creating a FDM application on SQL Server 2005
Error: EPMCSS-07003: Failed to validate identity. Invalid identity . Check identity.[SET_ROLES_LIST]
We are using Windows System Integration although we have also tested with sa user.
Any ideas?
ThanksBased on the error message it appears to be having a Shared Services issue. Verify that the "ADMIN" account is being used for the HSS connection and that you are using "ADMIN" to create the application and see if the same error is returned.
-
Is there a way to convert Crystal Reports to Microsoft SQL Server 2005 reporting services?
Post Author: Lourdes Hernandez
CA Forum: General
Our department has always worked with and we love Crystal Reports. Unfortunately, certain reports now need to be converted to Microsoft SQL Server 2005 reporting services which from what I read I think they are *.rdl reports. Does Crystal reports have any way around this? I would have to learn this other tool when I'm already so happy with Crystal. I was thinking If I could just code the report in crystal and export it in a specific format that would be compatible Microsoft, the problem would be solved.
Any ideas would be greatly appreciated.Post Author: bettername
CA Forum: General
Ditto!
There are some software packages to convert from CR to RS, but none work 100% AFAIK, and will require manual tuning.
Seems like a big hassle and learning curve just to get reports published via another method - I know I'd put up huge resistance if they tried to take my CR away from me! -
Integrating SQL Server 2005 with OBIEE 11g
Dear Gurus,
Is there any documentation about how to using SQL Server 2005 as datasource combined with OBIEE 11g?
Clear steps with pictures will be very helpful.
Thank so much
Regards
JOEHi,
Please refer this link.
http://rnm1978.wordpress.com/2009/08/21/querying-sql-server-from-obiee-running-on-unix/
Re: How to connect Linux OBIEE repository to SQL Server 2005 database
Hope this help's
THanks
Satya -
Hi Experts,
Please let me know if we can use ODI with Mircosoft SQL Server 2005.
The Drive list is showing only MS SQL Sever 2000.
Thanks and Regards,
AndyHi,
Yes you can definitely use sql server 2005, you just need to manually enter the driver name and url.
e.g.
com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc:sqlserver://<sqls machine>:1433;databaseName=<db name>;integratedSecurity=false
Cheers
John
http://john-goodwin.blogspot.com/ -
Migrate oracle database to Microsoft sql server 2005
Hi All,
I have to migrate production oracle database to Microsoft sql server 2005. Below are the details:
Oracle database version: 8.1.7.4
Platform : Aix
Kindly help me outWell, the traditional way would be to dump out all your data from Oracle tables as comma delimited flat files and import into SQL server. Plenty of examples online, like this is one by Mark Powell: http://www.jlcomp.demon.co.uk/faq/flatfile.html
Or if you have the budget you could think about buying a data mapping tool like File-Aid
As mentioned by another poster, you will still need to figure out how to replace all your triggers, stored procedures, etc on your new platform of course. -
Hi,
I am currently working in project where we need to migrate/point batch jobs to SQL server 2005. At this moment they are pointing to Sybase. Batch jobs are in .bat and .exe format. These jobs read in an external file, does some reformatting,
and then loads it into 2 sybase tables. These jobs are auto scheduled through Control-M application.
Any idea please ?
Thanks,
Chirag PatelChange your post to type 'Question' Chirag
You would need to at least change the connection strings, and how you access SQL Server, but typically code changes are necessary.
You unfortunately don't provide enough details. But it is not as trivial to just 'point' a bunch of jobs to a new target.
Arthur My Blog -
Error during installation of Microsoft SQL Server 2005
Hello All,
During installation of Microsoft SQL Server 2005 I have got the below error message
"There was an unexpected failure during the setup wizard"
From this link http://support.microsoft.com/kb/916760 i came to know that this error occurs just because I used SQL Server 2005 installations from a folder on a network share.
After that i unstall everything & copy the installations in a local drive. But again when we restart the activity we got the same error message & the installation completed.
Any hint why this happens..
Thank You.
Kind Regards,
JitudaHello Jituda,
I think we need to focus on the error in the setup log first.
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run:
Source File Name: datastore\cachedpropertycollection.cpp
you might be able to see more detailed error information in the log.
You may check if the following links help:
http://www.sqlserverfaq.net/2008/12/17/sql-server-2005-setup-failing-to-install-on-cluster-with-unexpected-failure-while-performing-the-scc-checks/
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/f998b073-4378-4d02-95ac-c9afb31c7a60
In addition, to clarify, the SQL4SAP.VBS script does not support Microsoft Cluster Service (MSCS). If you want to run the
script in an MSCS configuration, you get an error message. In MSCS configuration need to install the SQL Server database software manually instead of using the script. Please see the corresponding SAP product installation guide under http://service.sap.com/instguides
Kind regards,
Qingqing Wang -
ODBC incompatibility with varchar type microsoft sql server 2005
Hi,
My details:
OS: Oracle Solaris 10
Oracle version: 10.2.0.3
MSSQL version: SQL Server 2005 SP2
HSODBC driver: datadirect
I configurerd the HSODBC driver on solaris to communicate from oracle to MSSQL.
Everything works fine, except he don't show the nvarchar columns of MSSQL.
Can anyone help me with that??
ThxNigel Guest wrote:
Hi,
Has anyone successfully used the Microsoft SQL Server 2005 JDBC Driver (version 1.1) with XA connections ?yes.
If so, I have the following question:
As this driver appears to support both TX & XA in the same jar file, how would I go about setting up a connection pool in weblogic to only use XA ?
Is it a connection parameter ?
thanks for any advice..
/NigelIf you want an XA pool, specify the
driver's XA DataSource as the class
to use. -
i have been tryin to dl microsoft SQL server 2005 express edition service pack 3 (KB955706) for the past 2 months and always get the same prob. it always say error code:534- window has encounter an unkown error.
i got a feelin tat it is due to the update file bein corrupted as my lenovo laptop T400 crashed once. But i m not sure. any suggestion? pls dun tell me to look at microsoft web help. totally not much help....Hello computer156,
I meant your operating system, Vista or XP? I think you problem has more to do with MS than with you machine.
Please check this site out.
Follow @LenovoForums on Twitter! Try the forum search, before first posting: Forum Search Option
Please insert your type, model (not S/N) number and used OS in your posts.
I´m a volunteer here using New X1 Carbon, ThinkPad Yoga, Yoga 11s, Yoga 13, T430s,T510, X220t, IdeaCentre B540.
TIP: If your computer runs satisfactorily now, it may not be necessary to update the system.
English Community Deutsche Community Comunidad en Español
Maybe you are looking for
-
Playback glitch on export always at same TC
Premiere CS5.5 appears to be causing a glitch/stutter at the same spot consistently. I've trashed the renders and re-rendered, I've un-nested the sequence and re-rendered + recompressed, I've exported to MPEG2 via Pr and via dynamic link using Media
-
MX 2004: CSS Layout Outlines
Hi, Doeas anybody know how to get the above in MX 2004? Macromedia introduced some additional visual aids, including the above, in DW8 [or Studio...] I find these outlines particularly useful and I would like to find a way to have MX 2004 to display
-
Error while deploying WebDynpro IViews
Hello All, I am trying to deploy webdynpro application on the remote WAS server and I am getting following error. Server <b>serverName</b> did not accept login request as admin on port XXXXX. Details: ERROR: Could not establish connection to server <
-
Does Time Machine automatically reformat a non-Mac OS Extended hard drive?
A friend has just told me something surprising he read in the "Mountain Lion Missing Manual". It apparently says that if you connect a FAT or NTFS formatted hard drive to your Mac and startup Time Machine, it will be automatically reformatted to Mac
-
XI - Receiver Determination Condition not working
I created a Condition on my Receiver Determination to stop some messages from being sent based on a field in our message. It works when using some test tools (workbench, SOAPUI, etc) but not when coming from our MDM system. The beginning of the inpu