MS SQL Server 2005 Remote Database Connection

Hello Friends,
I have a database in SQL Server 2005, i installed SQL server with windows authentication. Now when I tries to connect to the server using Type 3 jdbc. I downloaded jdbc 1.2 driver from,
http://msdn2.microsoft.com/hi-in/data/aa937724(en-us).aspx
now i want to connect to the database from remote machine(different network).
How can i achieve this, and what setting i have to make to the sql server?
Any suggestion will be greatly appreciated.
Regards
Mohneesh

okey i done with some experiment.
now i am able to do it from local machine with the following code
String url="jdbc:sqlserver://LocalIP:1433;integratedSecurity=true;";
Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
Connection conn = DriverManager.getConnection("url");
now when i move to remote system and change the Local IP to remote IP(server has static IP)
it comes up with SQLException: Login failed.for user ''.
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.
please help me its kinda urgent.
Regards
Mohneesh

Similar Messages

  • How to store jpeg images in SQL server using NI database Connectivity Toolset. Can anyone please help me in this regard.

    Please tell how to store jpeg images in SQL Server using NI Database Connectivity Toolset.

    http://www.w3schools.com/sql/sql_datatypes.asp
    You setup a field as BLOB and store the binary of the picture there. Depending on the database it can be called differently as you can see in the link, in SQL server there's even a Image datatype.
    /Y
    LabVIEW 8.2 - 2014
    "Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
    G# - Free award winning reference based OOP for LV

  • 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

  • Unable to Access SQL Server 2005 Remotedly

    Not sure if this is the right forum to post this...
    After going through lot of old posts in various forums and changing lot of settings, i'm still not able to access my Server remotely.
    This is Windows 2003 Server machine with Sonicwall Firewall, i have allowed Port 1433 in both Firewall and ISA and call is getting through but i'm getting following error msg :-
    {"An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"}
    This machine is also having Sql Server 2000, and the SQL Server 2005 is installed with named instance.
    My connection string is :-
    "Data Source=192.168.0.1\MYSERVER;Initial Catalog=MyDatabase;Integrated Security=True"
    In example above, i'm showing dummy values but actual string is having the actual live IP address and correct named instance and database.
    If i use a local address like 192.168.0.1 then i'm able to connect.
    My TCP/IP Address in Sql configuration is having my Live IP Address and the port 1433.
    Any help will be highly appreciable..

    i'm still checking on this. i have changed the port now to 1434 and changed in all places.
    my connection string is also changed now, so now i'm using :- MYIP\MYSERVER,1434
    now i'm getting a different error msg
    {"An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)"}
    this can also be due to firewall or something else is blocking it, i will rechk n post back final answer.

  • Sql server 2005 and jsp connectivity

    hello everyone....am new to JSP...:-)
    i use apache tomcat server 4.1.37,SQL SERVER 2005(Studio express),dreamweaver cs3..
    this is my first page...
    <%@page contentType="text/html"%>
    <%@page pageEncoding="UTF-8"%>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>Untitled Document</title>
    </head>
    <body>
    <form id="form1" name="form1" method="post" action="new2.jsp">
    <label>
    Username
    <input type="text" name="text1" id="text1" />
    </label>
    <p>
    <label>
    Password
    <input type="text" name="text2" id="text2" />
    </label>
    </p>
    <p>
    <label>
    <input type="submit" name="button1" id="button1" value="Submit" />
    </label>
    </p>
    </form>
    </body>
    </html>
    this runs fine..coz there are only HTML codes...now the problem part...
    <%@page contentType="text/html" import="com.microsoft.sqlserver.jdbc.*, java.sql.*"%>
    <%@page pageEncoding="UTF-8"%>
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd">
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    <title>JSP Page</title>
    </head>
    <body>
    <h1>JSP Page</h1>
    <% String user = request.getParameter("text1");
    String pass = request.getParameter("text2");
    Connection con = null;
    try {
    Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
    con = DriverManager.getConnection("jdbc:sqlserver://localhost:1433;databaseName=webpage;user=Administrator");
    Statement stat=con.createStatement();
         ResultSet res =stat.executeQuery("select * from login");
    boolean l = false;
         while(res.next())
              if (user.equals(res.getString(2)) && pass.equals(res.getString(3)))
    l = true;
    if (l)
    out.println("<p>Welcome " + user + "</p>");
    else
    out.println("<p>Login Failed</p>" );
    con.close();
    } catch (ClassNotFoundException ex) {
    System.out.println("Exception: " + ex);
    catch (SQLException ex) {
    //Logger.getLogger(Main.class.getName()).log(Level.SEVERE, null, ex);
    System.out.println("Exception: " + ex);
    %>
    </body>
    </html>
    when i run this in the browser...i get JSP Pages displayed(but not the welcome...or login failed..)..which is under the html tag...
    but the tomcat server gives an error:
    Exception:com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed.java.net.ConnectException:connection refused.connect.
    Some of my questions...
    1)apache tomcat runs on port :8080 and in this code i use port :1433.Does this not have any bearing?
    when i change 1433 to 8080..it gives TDS prelogin response is incomplete.target server must be sql server 2000 or later.
    2)i use user=Administrator but when i go to Sql server management studio->object explorer->right-click->view connection properties..it gives user name as NEW-D348F33DAD2\Administrator...but if I use this it gives an error pointing to the forward slash(\).So what should be used?
    P.S. i have installed the jdbc driver and the database "webpage" has been created!

    anand_chhetri wrote:
    hello everyone....am new to JSP...:-)
    i use apache tomcat server 4.1.37,SQL SERVER 2005(Studio express),dreamweaver cs3..Tomcat is up to version 6; why are you using such an old one?
    Dreamweaver is irrelevant.
    Which JDK?
    >
    this is my first page...
    <%@page contentType="text/html"%>
    <%@page pageEncoding="UTF-8"%>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>Untitled Document</title>
    </head>
    <body>
    <form id="form1" name="form1" method="post" action="new2.jsp">
    <label>
    Username
    <input type="text" name="text1" id="text1" />
    </label>
    <p>
    <label>
    Password
    <input type="text" name="text2" id="text2" />
    </label>
    </p>
    <p>
    <label>
    <input type="submit" name="button1" id="button1" value="Submit" />
    </label>
    </p>
    </form>
    </body>
    </html>
    this runs fine..coz there are only HTML codes...now the problem part...OK.
    You don't need to import the Microsoft SQL server JDBC.
    <%@page contentType="text/html" import="com.microsoft.sqlserver.jdbc.*, java.sql.*"%>
    <%@page pageEncoding="UTF-8"%>
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
    "http://www.w3.org/TR/html4/loose.dtd">
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    <title>JSP Page</title>
    </head>
    <body>
    <h1>JSP Page</h1>Where do you think these come from? This page must be your "new2.jsp"
    <% String user = request.getParameter("text1");
    String pass = request.getParameter("text2");
    Connection con = null;
    try {
    Since you didn't get a ClassNotFoundException here, I'll assume that you got the JAR into the CLASSPATH.
    Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");Your app logs in as admin? With no password? Very bad.
    con = DriverManager.getConnection("jdbc:sqlserver://localhost:1433;databaseName=webpage;user=Administrator");
    Statement stat=con.createStatement();
         ResultSet res =stat.executeQuery("select * from login");
    boolean l = false;
         while(res.next())
              if (user.equals(res.getString(2)) && pass.equals(res.getString(3)))
    l = true;
    if (l)
    out.println("<p>Welcome " + user + "</p>");
    else
    out.println("<p>Login Failed</p>" );
    con.close();
    } catch (ClassNotFoundException ex) {
    System.out.println("Exception: " + ex);
    catch (SQLException ex) {
    //Logger.getLogger(Main.class.getName()).log(Level.SEVERE, null, ex);
    System.out.println("Exception: " + ex);
    %>
    </body>
    </html>
    when i run this in the browser...i get JSP Pages displayed(but not the welcome...or login failed..)..which is under the html tag...
    but the tomcat server gives an error:
    Exception:com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed.java.net.ConnectException:connection refused.connect.Bad connection URL. Can you write a simple class that connects without Tomcat, one that you can run on the command line?
    Some of my questions...
    1)apache tomcat runs on port :8080 and in this code i use port :1433.Does this not have any bearing?No.
    when i change 1433 to 8080..it gives TDS prelogin response is incomplete.target server must be sql server 2000 or later.No - Tomcat listens on 8080, SQL Server listens on 1433. You need both.
    2)i use user=Administrator but when i go to Sql server management studio->object explorer->right-click->view connection properties..it gives user name as NEW-D348F33DAD2\Administrator...but if I use this it gives an error pointing to the forward slash(\).So what should be used?Look at the driver docs to see how to add a password.
    P.S. i have installed the jdbc driver and the database "webpage" has been created!What does "installed" mean? The JARs should be in Tomcat's common/lib directory.
    %

  • SQL Server 2005: Monitoring Database Mirroring

    Hi All,
    I use SQL Server 2005 with mirror enable.
    Are there anyway to check/monitor/verify whether all data at principal are transit to mirror serer ?
    Regards,
    Pitou

    What is operation mode of the mirroring configuration?
    http://technet.microsoft.com/en-us/library/cc917680.aspx#XSLTsection126121120120
    /*If transaction safety (or just 'safety') is set to FULL, the principal and mirror servers operate in a synchronous transfer mode. As
    the principal server hardens its principal database log records to disk, it also sends them to the mirror. The principal then waits for a response from the mirror server. The mirror responds when it has hardened those same log records to the mirror's log disk.
    When safety is set OFF, the principal does not wait for acknowledgment from the mirror, and so the principal and mirror may not be fully synchronized (that is, the mirror may not quite keep up with the principal).*/
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • Sql Server 2005 read-only connection!

    Hi all,
    I have connected my Sql Server 2005 tables with Sql Developer 1.1.2.25, but all tables results in read-only state (I can't modify data). Connection user is administrator (SA) and no possible an user-grant problem (from Ms Server Client all work fine with same user). Same problem if I use a Windows Authenticated user. JDBC driver is from sourceforge.net .
    Can you help me?

    I have just installed Sql Developer v1.2, but haven't solved problem.
    Any ideas?

  • Replacing a SQL Server 2005 Express Database with a SQL CE 3.5 database

    I am just googling for the past few days to find out the answer to this problem..
    I have an app developed over few man-years of effort - with vb.net and SQL 2005 Express Db. Now we use VS 2010 sp1 with .net 3.5 sp1.  We have used plain T-SQL commands and the app was performing admirably well. The DB has about forty tables. The data
    volume is about 200 to 300 mb max - but mainly it stays about 50 to 60 mb in many places. We are also using XML data transfers to backup the data.
    Now we want to shift to SQL CE 3.5 or 4.0 - just to avoid the pain of SQL Express download and installation by the users. We have successfully created a 3.5 and 4.0 sdf files. But when we change the connection from a mdf file to the sdf file in the VS2010 settings
    area, it just goes fine - the connection string is accepted and the app starts. But we get the usual error no 26 - unable to locate the database file - and a five line message that it is not able to connect to the sql server.
    Are we missing something ? We have included the sqlce dll in the references.. but just not able to make the app connect to the sdf file..
    All the codes, datasets, adapters, queries are just intact in the app - but just we are not able to connect to the sdf database.
    We would appreciate help in this regard and also in doing a build with SQL Ce with Inno Setup which we have been using so long.
    Finally there is too much of SQL CEs around - but 3.5, 3.5 sp2 and now CE 4.0 seems to be ones to go in for. Which one is really the best for our app - 3.5 or 4.0 ?
    Thanks in advance.

    we change the connection from a mdf file to the sdf file ... All the codes, datasets, adapters, queries are just intact in the app...
    Agree with Erik, just changing the connection string don't work, you have to use data access components from
    System.Data.SqlServerCe Namespace instead of
    System.Data.SqlClient Namespace
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Is Oracle Client software must in Sql Server 2005 Box to connect ORACLE

    We need to connect ORACLE from SqlServer 2005
    1. We would like to know is Oracle Client Software MUST needed to be installed in SqlServer 2005 to connect ORACLE.
    2. Do we have any other means?
    3. Will Oracle OLE DB Provider for Oracle help us in establishing Linked Server to ORACLE

    Probably late in the day for this but
    The workbench cannot handle SS2K5 directly at the moment. However as long as no new SS2K5 functionality has been used with a few tweaks this can be achieved.
    1. Firstly use the SS2K offline capture scripts to build the directories for the database(s) you want to capture.
    2 Secondly edit
    (a) SS2K_SYSLOGINS.dat and take out long SS2K5 user records
    (b) SS2K_SYSINDEXES.dat change FIRST ( forth column) to a value (say hex 1).
    (c) SS2K_SYSUSERS.dat change ROLES (sixth column) to a value (say hex 1).
    This should now load into the workbench. If it does not check the error.log file in <OMWB HOME>\log.

  • PeopleTools 8.49 PeopleSoft Database Cannot Connect with MS SQL Server 2005

    Folks,
    Hello. I am working on PeopleSoft PIA. My system is Windows Server 2003, MS SQL Server Express 2005 Standard, PeopleTools 8.49. I am setting up PeopleSoft Database \PsMpDbInstall\setup.exe and got the errors as follows:
    Error: Setup fails to connect to SQL Server. The default settings SQL Server does not allow remote connection.
    Then I type in "sqlcmd" in Command Prompt and got the same error as follows:
    Name Pipe Provider: Could not open a connection to SQL Server. MS SQL Native Client: the default settings SQL Server does not allow remote connection.
    In order to fix SQL Server 2005 remote connection problem, I have done the 3 steps as follows:
    Step 1: In SQL Server Surface Area Connection, enable local and remote connection, TCP/IP and Name Pipes, SQL Server browser Startup type "automatic" and status "running".
    Step 2: Create exception for SQL Server 2005 and SQL Server browser Service in Windows Firewall.
    Step 3: Add the default SQL Server Port 1433 into Windows Firewall.
    But the above 3 steps cannot resolve SQL Server Express 2005 remote connection problem. Can any folks help to resolve this problem ?
    Thanks.

    Folks,
    Management Studio can connect with SQL Server 2005 successfully.
    I have turned off Windows Server 2003 firewall completely. But "sqlcmd" in Command Prompt still connect with SQL Server 2005 because its remote connection is not allowed.
    Is the "not allow remote connection" problem caused by Windows Firewall or SQL Server 2005 itself ?
    Thanks.

  • An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider,

    An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider,
    error: 40 - Could not open a connection to SQL Server)

    An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named
    Pipes Provider, error: 40 - Could not open a connection to SQL Server)
    Hello,
    Make sure your SQL Server service is started.
    Make sure TCP\IP and names pipes protocol is enabled
    Make sure you have made an exception in firewall for SQL Server connection
    Make sure SQL Server browser service is enabled
    Make sure you connect with correct name hostname\instance name for named instance,MSSQLSERVER for default instance and Hotname\SQLEXPRESS for express edition.
    Please make sure you use port no when connecting to SQL server listeing on different port (hostname\instance ,portno)
    http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
    Hope this helps
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Open Query issue in SQL server 2005

    I am running following query in SQL Server 2005, remote connection is Oracle. Query runs perfect in oracle.
    Any help would be greatly appreciated.
    Error is:  
    OLE DB provider "MSDAORA" for linked server "ORACLEROSTER" returned message "ORA-00911: invalid character ".
    select 
    EMPLOYEEID,
    TermDate,
    UserName,
    ACTION,
    DEPTID,
    DESCR
      from OPENQUERY(ORACLEROSTER,
    'SELECT DISTINCT substr(A.EMPLID, 1,10) "EMPLOYEEID" 
    , TO_CHAR(A.EFFDT,"yyyy-mm-dd") "Term Date"
    , SUBSTR(A.NAME, 1, 25) "User Name"
    , SUBSTR(A.ACTION, 1, 10) "ACTION"
    , SUBSTR(A.DEPTID, 1, 10) "DEPTID"
    , SUBSTR(B.DESCR, 1, 20) "DESCR" 
      FROM sysadm.PS_PERSONNEL_HIST A, sysadm.PS_EMPLMT_SRCH_QRY A1, sysadm.PS_DEPT_TBL B, sysadm.PS_SET_CNTRL_REC B2 
      WHERE B.DEPTID = A.DEPTID 
     AND B2.SETCNTRLVALUE = A.BUSINESS_UNIT 
    AND B2.RECNAME = "DEPT_TBL" 
     AND B2.SETID = B.SETID 
     AND A.EMPLID = A1.EMPLID 
     AND A.EMPL_RCD = A1.EMPL_RCD 
     AND A1.ROWSECCLASS = "DPPDIFLD" 
     AND ( A.EFFDT = 
          (SELECT MAX(A_ED.EFFDT) FROM sysadm.PS_PERSONNEL_HIST A_ED 
           WHERE A.EMPLID = A_ED.EMPLID 
           AND A.EMPL_RCD = A_ED.EMPL_RCD 
           AND A_ED.EFFDT <= SYSDATE) 
        AND A.EFFSEQ = 
            (SELECT MAX(A_ES.EFFSEQ) FROM sysadm.PS_PERSONNEL_HIST A_ES 
            WHERE A.EMPLID = A_ES.EMPLID 
              AND A.EMPL_RCD = A_ES.EMPL_RCD 
              AND A.EFFDT = A_ES.EFFDT) 
         AND A.ACTION = "TER" 
         AND A.LOCATION IN ("500","600") 
         AND A.JOBCODE IN ("SR5","SR3","ASR","ASRS","IBP5","IBP3","I53610","I53630","053610","053630") 
         AND A.EFFDT BETWEEN SYSDATE - 7 AND SYSDATE 
         AND A.ACTION_REASON <> "ZNS" 
         AND A.EMPL_STATUS = "T" 
         AND B.EFFDT = 
            (SELECT MAX(B_ED.EFFDT) FROM sysadm.PS_DEPT_TBL B_ED 
            WHERE B.SETID = B_ED.SETID 
              AND B.DEPTID = B_ED.DEPTID 
              AND B_ED.EFFDT <= A.EFFDT) )
      order by 2;')
    s

    How about if you make the query into a view on ORACLE and SELECT from the view?
    Kalman Toth SQL SERVER 2012 & BI TRAINING
    New Book: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2012

  • SQL Server Error when tryingt to install the CMS DB on SQL Server 2005 x64

    I am trying to install BOEXI R3 on w2k3 64-bit OS in a SQL Server 2005 x64 database, I am currently at the installation step where i Specify an exisiting CMS database. I created a System DSN and tested it, and it was successful. So when I got to the screen where I select my datasource I had to check use trusted connection because the datasource would not show up when Use DSN created by WOW64 option was checked. From there I could select the database I created. Oh yeah, I also made the application server local system account part of my DB admins group so it has full access to the database yet when I click next to connect I get a CMS Database Error: STU000226. here is what I have in my log:
    ThreadID     Message
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: findDFA_LLR:  (CmdLineDir) C:Documents and SettingsgsdadminDesktopBOEXI and BSM AnalyticsBOEXI R3 Full Version from SAPpackagedbcheck
    sqlrule.llr
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: Loading: database subsystem only
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: loading libary succeeded
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Init()
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:96): trace message: Creating the shared CWireObject::PropertyNameMap
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:118): trace message: Setting static property map
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:125): trace message: CWireObject::InitializeStaticPropertyMap() - reference count: 1
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: initializing subsystem succeeded
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: Loading: done loading subsystem - database subsystem only
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Connect()
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.DBConnectionManager.cpp:802): trace message: DBConnectionManager - Setting total target number of connections for pool 0 to 1.
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.SQLServerDatabase.cpp:119): trace message: SQLServer error found:  ErrorMessage( (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified), ErrorCode(0)
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.dbutils.cpp:820): trace message: Caught DatabaseSubystem Error: BusinessObjects Enterprise CMS: Unable to connect to the CMS system database "BOEXI_CMS". Reason:  (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Shutdown()
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:175): trace message: CWireObject::TerminateStaticPropertyMap() - reference count: 1
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:182): trace message: Releasing
    static property map
    How do I get past this?

    The workaround was, I installed the SQL Server Client tools and created a System DataSource  and then had to create a user DataSource  (it is a quirk in the installer I guess) to get past this point in the installation. Now I have an even bigger problem. Everything but the CMS installed and the installer hung at the "Configuring the CMS" part. The installation finished but when I tried to log into the Central managment console I got this error:
    Error: Server GSD-RRPT-RDC:6400 not found or server may be down (FWM 01003) null
    I looked at the forums for the cause of this error and came to the conclusion that BOEXI does not support an installation on SQL Server 2005 when using Integrated Authentication to the SQL Server. See the engineers here disabled SQL Authentication for the SQL Server and  will not allow it.
    Is this true? Or is there a workaround to install the CMS using Integrated Authentication in the DataSource ?
    Thanks.

  • Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

    I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
    "Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
    Nor will the query execute; I get a transport-level error 0. Any thoughts?

    Hi Davidmhjr,
    >>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
    Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
    If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
    with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
    So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
    More information about configuration requirement to run T-SQL debugger as below, please refer:
    There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
    Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
    On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
    •Add TCP port 135 to the exceptions list.
    •Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
    any named instance.
    •If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
    On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
    •Add TCP port 135 to the exceptions list.
    •Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
    Hope it is helpful.
    Regards, Amber zhang

  • MS SQL Server 2005 and JDBC

    Hi friends
    I am new in Java and for the first time I want to write a program to connect to my database on MS SQL Server 2005 to retreive data. I read the tutorial, but I couldn't find there any information about the proper driver name to connect to a SQL Server database ;(
    Could you please let me know what I should write as DriverManager.getConnection(????) to make the connection?
    Thank you in advance.

    I really thank you for your patience and accompanying me. At last I found what the problem was! It was about MS SQL Server 2005 TCP/IP connection!!!! It's disable by default, so it didn't let my java program to login. I enabled it and restart all the SQL services again. But when I executed the program another error appeared: This driver doesn't let you to have integrated secuirty .So I had to bring the 'sa' user id and its password to login to MS SQL Server. And this time it worked!! You are right, I had to cheange the connection URL to bring the port in it.
    I am writing a system for a small company in java, and I installed the MS SQL Server 2005 myself and I should manage all the problems myself! So I didn't have anyone to help me but you dear friends.
    I really appreciate all your valuable advice.
    Now the final code is:
    import java.sql.*;
    public class DBtest {
         public static void main(String[] args) {
              // Create a variable for the connection string.
              //String connectionUrl = "jdbc:sqlserver://localhost:1433;databaseName=Northwind;integratedSecurity=true;";
              String connectionUrl = "jdbc:sqlserver://localhost;databaseName=Northwind;integratedSecurity=true;";
              // Declare the JDBC objects.
              Connection con = null;
              Statement stmt = null;
              ResultSet rs = null;
                 try {
                      // Establish the connection.
                          Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
                          con = DriverManager.getConnection(connectionUrl);
                          // Create and execute an SQL statement that returns some data.
                          String SQL = "SELECT city,country FROM customers";
                          stmt = con.createStatement();
                          rs = stmt.executeQuery(SQL);
                          // Iterate through the data in the result set and display it.
                          while (rs.next()) {
                               System.out.println(rs.getString(0) + " " + rs.getString(1));
              // Handle any errors that may have occurred.
              catch (Exception e) {
                   e.printStackTrace();
              finally {
                   if (rs != null) try { rs.close(); } catch(Exception e) {}
                       if (stmt != null) try { stmt.close(); } catch(Exception e) {}
                       if (con != null) try { con.close(); } catch(Exception e) {}
    }

Maybe you are looking for