DI Server - Cannot connect to named instance SQL server database

Hi,
I have developed a small DI server application and want to migrate it to a production server. I keep on getting the Cannot connect to SBOCommon error on login though. I have verified all user names and passwords and the only real difference is that the production environment uses a named instance SQL server eg server\instance setup.
The production DI server will however connect perfectly to the test database (which is NOT a named instance) .
Anyone using DI server against a named instance SQL server or have some other ideas what might cause this?
I use B1WS 1.0 and the version of SBO is 8.00.181..
Jaco

I may have solved the problem, at least partially.
I created a test user with full rights on my test database server and it would also not connect, even though my test database is not a an instance setup.
Then I found this thread [Re: DI Server Always Uses SA to log into MS SQL database even if SOAP packet]
It seems that at my current patch level the user 'sa' is hard coded into the DI server as sql username! I don't have the production server's 'sa' user credentials at present but will test it on Monday. Will also test against 8.8 soon ..

Similar Messages

Cannot connect to the specified SQL Server instance

I am trying to install Microsoft System Center 2012 R2 Virtual Machine Management.
I am getting the following error:
Setup cannot connect to the specified SQL Server instance.
Ensure that the server name, isntance name, and, if speceified, port number are correct. If you are installing VMM remotely, ensure that remote connections are set up correctly, and then try Setup again.
I have installed the
Microsoft® SQL Server® 2008 R2 Command Line Utilities
but have not set up any SQL Server instances.
how should i proceed?
Edit:
The followign fields are configured:
Server Name: The name of the machine i am using
Port: <empty>
Use the following credentials <NOT ticked>
Instance name <empty> (the drop down is empty)
New Database <Ticked> : VirtualManagerDB

Is SQL server is properly installed on the system?
Are you able to connect with SQL server instance?
As per the given details looks, only client utilities installed and trying to create the database which needs SQL server.
Make sure you are able to connect with the "ServerName\InstanceName,PortNumber" and hope installing the system as per below article:
http://technet.microsoft.com/en-us/library/gg610656.aspx
Hope it help!
Please click the Mark as answer button and vote as helpful if this reply solves your problem

Setup cannot connect to the specified SQL Server instance

On a clean install domain member (Windows 2012), I am trying to setup System center 2012 VMM:
1. I installed the prerequisites as instructed during the pre-setup phase of the installation then rebooted the server (SQL Server 2012 was installed and services seem to be all started properly and SQL Configuration Manager starts as well).
2. After reboot, logged again with domain admin account and Windows update installed right away SP1 for SQL server 2012. Then I rebooted again.
3. Restarted the installation process and left default values. At the "Database configuration" step, I am leaving everything by default as well and I am getting error: "Setup cannot connect to the specified SQL Server instance. Ensure that
the server name..."
4. Tried different credentials, tried using port 1433 with no effect.
Am I missing something????
Thanks.
Benjilafouine

Definitely be sure to connect with the "ServerName\InstanceName,PortNumber". If you don't reference a port number it will try 1433 and then will connect via a dynamic port number. It is best in my opinion to always specify a specific port for each instance
to listen on in the SQL Server Configuration Manager so that you can open the fewest number of ports in the Windows firewall.

Data modeler cannot connect to non-default sql server instance

I've just started using DM, it installed and loaded fine, I got the jdbc drivers v2.0 from MS so that I can reverse engineer a couple of SQL-Server 2005 DB's.
All worked just fine until I tried to connect to a machine with a named-sql-server instance.
Normal way of doing this for sql-server is to add instance name to end of hostname in the hostname field, like this: "server10\inst01"
but this gives me a cannot-connect-to-server10 error.
I copied database over to a different server that has just a default sql-server instance and it worked fine. (both sql-server2005 and 2000!)
I also tried the older 1.2 jdbc driver from MS against the sql-server 2005 named instance, no luck!
I tried putting the instance name in front of the port number, that didn't work either.
Am I just doing something wrong? or does DM need a special way of specifying the instance name on the sql-server host?

Hello,
you don't need instance name in order to connect. It's only host and port - probably named instance is not listening on default port. It'll be unfortunate if dynamic port assignment is used - but probably that won't be the case.
I hope someone can tell you the port number.
Philip

I cannot connect to my basic SQL server from Visual Studio Ultimate 2013? Error 40 - Cannot establish connection

I just started learning ASP.NET through a book, and it asks to connect to "your" SQL server and explore a .mdf file. I've been trying to install SQL, but I only just now got a working installation, and even then it won't let me install the Management
Software. Whenever I try to connect, I get this error: http://puu.sh/7F2JY.png
This is exactly what I do to connect:
1) Open project
2) Navigate to the Server Explorer
3) Click on connect to database
4) In this menu, I can see me Machine name on the top part, which I think means that it's picking up my server runningh
5) On the bottom, it wants me to enter a database name. I think this may be my problem, as I have no idea what to do here.
Also, when I double click on the database file, I get this errpr (52): http://puu.sh/7F2Yw.png
I really don't know what to do here, so post any tips down below

Hi,
Did you choose the correct Server name? It should be the machine name where you installed SQL Server on.
Is it empty when you open select or enter database name drop box in the Add connect dialog box in the Visual Studio 2013?
“Update: I re-installed, and then used both installers. Now I have the Server Management tools, but I still cannot connect.”
The screenshots indicates that the SQL Server is not accessible.
Do you mean that you are not able to connect SQL Server by using SQL Server Management Studio?
If so, make sure that SQL Server Services is started.
Please check out the following articles for details:
How to: Start an Instance of SQL Server (SQL Server Configuration Manager)
http://technet.microsoft.com/en-us/library/ms190699(v=sql.105).aspx
Connect to Any SQL Server Component from SQL Server Management Studio
http://technet.microsoft.com/en-us/library/ms173871.aspx
Thanks.
Tracy Cai
TechNet Community Support

Cannot connect to newly created SQL 2008 R2 instance. Login failed for user...

I'm not a SQL guy, just figuring my way around here...
I just created a new instance on an existing SQL server. The original instance works fine. On
Database Engine Configuration > Account Provisioning
I selected Windows authentication mode and added several users, myself among them.
Tried to log in with one my account and getting:
TITLE: Connect to Server
Cannot connect to SERVERNAME\INSTANCE.
ADDITIONAL INFORMATION:
Login failed for user 'domain\myusername'. (Microsoft SQL Server, Error: 18456)
Guidance/suggestions?
Thanks,
Scott

http://sqlserver-help.com/2014/07/08/help-how-to-find-cause-of-login-failed-for-user-error/
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Sql server 2012 express - tcp/ip connection to named instance using dynamic port not working

I have a named instance on a SQL 2012 Express server that won't connect via TCP/IP when wanting to connect off of the dynamic port. I can connect via shared memory locally on the server.   I can connect to the namespace when specifying the
dynamic port listed in the configuration manager.
This is the only named instance on the server and it is not the default.
TCP/IP is enabled
Allow Remote connections is enabled
the server browser service is running
I can connect via the dynamic port number
I am testing the connection locally on the server, so I don't believe a firewall is the issue. I get the same results if I test it from a remote computer.
When using the sqlcmd (sqlcmd -S tcp:SQLSRVR\NAMEINST -E) I get the message that "the requested protocol isn't supported [xfffffffff]".   The command (sqlcmd -S tcp:SQLSRVR\NAMEINST,59992 -E) works.
Through SSMS, I get the message "the connection was actively refused".
On other boxes, I can connect with the named instance without having to specify the port.
I have looked through the sql logs and nothing much shows up. The log does show that is listening on the port # for ipv4 and ipv6.   There is also a line in there talking about the SPN not being registered and not to worry about it if
you are not using Kerberos. I logged in through shared memory and it said I was using NTLM.
Any help would be appreciated.
thanks.

Hi clw,
I’m writing to follow up with you on this post. According to your description, I do a test, if you configure the database engine to listen on a specific TCP port (59992), and
the port is opened in the firewall. If you want to connect to the SQL Server instance, you 'd better to
use the port number.
In my opinion, by default, the default instance of the Database Engine uses port 1433, usually, if you have configured the server to listen on a non-default port number, when an instance of SQL Server uses dynamic port allocation, the connection string that
is built at the SQL Server client does not specify the destination TCP/IP port unless the user or the programmer explicitly specifies the port. Therefore, the SQL Server client library queries the server on UDP port 1434 to collect the information about the
destination instance of SQL Server.
If UDP port 1434 is disabled, the SQL Server client cannot dynamically determine the port of the named instance of SQL Server. Therefore, the SQL Server client may be unable to connect to the named instance of SQL Server. In this situation, the SQL Server
client must specify the dynamically allocated port where the named instance of SQL Server is listening.
For more information about configuring an instance of SQL Server to listen on a specific TCP port or dynamic port, you can review the following article.
https://support.transfrm.com/entries/503111-How-to-configure-an-instance-of-SQL-Server-to-listen-on-a-specific-TCP-port-or-dynamic-port
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

JDBC Connection String for MS Sql Server 2000 with Instance Name

Hi All,
I am having problems connecting to a MS Sql Server 2000 database using MSSqlServer4
driver when the database server has an Instance Name. If the database server has
no instance name then I am able to connect using the connection string
connection=jdbc:weblogic:mssqlserver4:hansa:1433
But when I have the MS Sql Server DB with an instance name such as "TestInstance",
then I am unable to connect with any of the connection strings given below
connection=jdbc:weblogic:mssqlserver4:hansa\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa\\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:1433:TestInstance
Can anybody help me in resolving this issue. Appreciate your help.
Thanks in advance.
Vikram

Vikram wrote:
Hi All,
I am having problems connecting to a MS Sql Server 2000 database using MSSqlServer4
driver when the database server has an Instance Name. If the database server has
no instance name then I am able to connect using the connection string
connection=jdbc:weblogic:mssqlserver4:hansa:1433
But when I have the MS Sql Server DB with an instance name such as "TestInstance",
then I am unable to connect with any of the connection strings given below
connection=jdbc:weblogic:mssqlserver4:hansa\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa\\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:1433:TestInstance
Can anybody help me in resolving this issue. Appreciate your help.Hi. No type-4 jdbc driver is going to be able to use a name for a DBMS instance.
Let's assume you have two DBMS instances running on the machine hansa. One
of them may be listening for tcp connections on port 1433, but the other must not.
The other most be listening on some other port number you have chosen.
Therefore, to choose which DBMS instance you want to connect to, use the
working URL you have, and switch the port number as desired.
Joe Weinstein
>
>
Thanks in advance.
Vikram

Connection failed: SQLState:'01000' SQL Server Error:67 [Microsoft]ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). Connection failed: SQLState:'08001' SQL Server Error:17 [Microsoft]ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist o

Help,
setup a new sql server 2012 on a windows 2012r2 server to replace old sql server 2005 on an old windows server 2003 machine. When i test the ODBC connection locally on the server it works fine, however when i try to connect via windows 7 client machine
i get the following error:
Connection failed:
SQLState:'01000'
SQL Server Error:67
[Microsoft]ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect()).
Connection failed:
SQLState:'08001'
SQL Server Error:17
[Microsoft]ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied
I think it must be a permissions thing, I've turned off the firewall for now and still no difference, 've also made sure remote connection is enabled. I can connect to the other sql server in studio manager on the new machine however, i can't go do
the same in the old server, says:
cannot connect to hbfsqlpro1\hbfsqlpro1
Additonal information a network related or instance specifc error occured while establising a connection to SQL server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL server is configured to
allow remote connections. (provider:SQL Network Interfaces, error 26 - error locationg server/instance specified) (Microsoft SQL server)
the instance is def correct, as that is what i use to connect locally on the new machine and what it comes up on the studio manager on the new machine. STarting to pull my hair out somewhat, i'm sure it's something really simple!

Hello,
You are trying to connect to a named instance. Make sure the SQL Server Browser service is started on the SQL Server computer.
Make sure TCP/IP is enabled.
http://msdn.microsoft.com/en-us/library/ms191294(v=sql.110).aspx
Try to disable Windows Firewall or security software on both, SQL Server instance and client computer.
Test basic connectivity too. Try to ping from the client computer to the SQL Server computer.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

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

Issues with SSIS in named instance SQL 2014

I have a SSIS job that runs without any issues with native mode. But for named instance, I get these errors:
Any suggestions?
Failed to decrypt protected XML node
"DTS:Password" with error 0x8009000B "Key not valid for use in specified state.
You may not be authorized to access this
information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2015-04-22 15:20:01.67     Code: 0xC0016016
Source: xxx Description: Failed to decrypt protected XML node "OraPassword" with error 0x8009000B
"Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a
cryptographic error. Verify that the correct key is available. End Error Error: 2015-04-22 15:20:02.22     Code:
0x000002BD     Source: xxx Connection manager "yyy"     Description:Oracle Home not found. End Error Error: 2015-04-22
15:20:02.22     Code: 0x0000020F    Source: mmm[96]
Description: The AcquireConnection method call to the connection manager yyy failed with error code 0x80004005. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error
Thanks

Hi LaxUdas,
If I understand correctly, the package is developed with Protection Level set as "EncryptSensitiveWithUserKey". When you execute the package via a SQL Agent Job in a Named Instance, the account that job step using is not the user that create the
package. So it cannot be able to connect to the Oracle DB with invalid connection string.
This behavior is by design. In an Integration Services package, the following information is defined as sensitive:
The password part of a connection string.
The task-generated XML nodes that are tagged as sensitive.
Any variable that is marked as sensitive.
EncryptSensitiveWithUserKey uses a key that is based on the current user profile to encrypt only the values of sensitive properties in the package. Only the same user who uses the same profile can load the package. If a different user opens the package,
the sensitive information is replaced with blanks and the current user must provide new values for the sensitive data.
To work around this issue, please refer to the following suggestions:
Change the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword. This setting uses a password for encryption. To open the package in SSIS Designer (SSDT), the user must provide the package password.
Change the Named Instance SQL Agent Service account to the user that create the package, like your Default Instance.
Use SSIS Package configuration files to store sensitive information, and then store these configuration files in a secured folder. You can then change the ProtectionLevel property to DontSaveSensitive so that the package is not encrypted and does not try
to save secrets to the package. When you run the SSIS package, the required information is loaded from the configuration file. Make sure that the configuration files are adequately protected if they contain sensitive information.
The following two documents are for your references:
https://msdn.microsoft.com/en-us/library/ms141747.aspx
https://support.microsoft.com/en-us/kb/918760
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Reporting Services server cannot connect

Hi,
I am trying to install the SAP BPC MS version and so far been hit with many issues. The latest issue is that the installer cannot connect to the Reporting Services server, in which from the installation documentation this should come as standard with MSSQL.
Any idea how to activate this manually?
Thanks.

Hi,
In that case, I believe, the reporting service was not installed. When you are installing SQL server, you need to check the reporting services from the list. If thats not selected, then it wont be installed.
I guess, you have to run the installation once again. While doing the installation, please check the required services from the list, including reporting services.
Hope this helps.

Reporting Services Server cannot connect to the DPM database. ( dpm 2010 )

Reporting Services Server cannot connect to the DPM database.
To repair the configuration, follow steps for repairing DPM from DPM Setup Help.
ID: 3001
i can not try the Recommended action from error codes catalog because i did not found Change reporting
password

Hi,
We have had several customers report this after installing DPM 2012 R2.
To get past the below error while scheduling reports to be mailed.
Reporting Services Server cannot connect to the DPM database.
To repair the configuration, follow steps for repairing DPM from DPM Setup Help.
ID: 3001
Perform the following steps as necessary:
1. Created a new local group called "DPMDBReaders$<DPMServerName>"
2. Created a new user called, "DPMR$<DPMServerName>" and added this user to DPMDBReader group that we created on step 1.
3. Open SQL management studio and add the DPMDBReaders$<DPMServerName group to Logins under Security in SQL Management Studio.
4. Modify the properties and under General – change the default database to the current DPMDB name.
5. Under User Mapping – select the current DPMDB name and check the db_datareader checkbox.
6. In SQL Management Studio, navigate to the Databases > DPMDB > Security > Users > and select the DPMDBReaders$<DPMServerName>" group.
Right-click the DPMDBReaders$<DPMServerName>" group and select properties. Under the
Securables section, click on Search. On the add objects dialog, click OK.
On the Select Objects dialog, click the Objects type, then check the
stored procedure checkbox. Browse and add the following two stored procedures
“Prc_MOM_Heartbeat_Get” and “prc_MOM_ProductionServer_Get”.    Grant the Execute permission for both of the stored procedures added.
7. In SQL Reporting Services Configuration manager, under Report Manager URL - click on the link to open the portal (http://localhost/Reports)
      i. Click on the DPMReoprts_GUID to open the DPM reports.
      ii. Click on the DPMReporterDataSource
      iii. On the poperties page, enabled "Credentials stored securely in the report server" on DPMReporterDataSource configuration page and added “DPMR$<DPMServerName>” user account that we created in step 2.
      iv. tick "Use as Windows credentials when connecting to the data source."
      v.   Click ‘Test connection’ on the same page to verify whether it can connect successfully.
8. In SQL Reporting configuration manager - change the Service Account to use build-in account: Network Service
9. Reboot the DPM Server.
10. You should then be able to schedule e-mailed reports.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
posting is provided "AS IS" with no warranties, and confers no rights.

DPM 2012 R2 Rollup 1 x64.. cant save scheduled report.. gives error: "Reporting services server cannot connect to the dpm database"

The error also has "to repair the configuration, follow steps for repairing dpm from DPM setup help ID: 3001
I tried the solution outlined here:
http://social.technet.microsoft.com/Forums/en-US/8be919ee-f358-47a4-9cc3-d23eb05d3f18/system-center-2012-r2-dpm-smtp-issue-reporting-services-server-cannot-connect-to-the-dpm?forum=dataprotectionmanager
and also the graphical depiction here: http://www.ms4u.info/2014/01/reporting-services-server-cannot.html
I tried these steps, but everytime i try to change it, it tells me:
"The permissions granted to user 'domain\userid' are insufficient for performing this action rsaccessdenied..
Nothing seems to work..
I thought if i went into sql management studio and made sure my userid had admin rights to the db it would work.. but i cant change it there (via integrated security).. i believe i need to login as SA, but i dont recall the password for SA, though it appears
i can change the SA password from within sql management studio.. i'm unsure if doing so will break DPM though or is even needed to fix the reporting integration issue..
Any thoughts on this?
Thanks
Tech, the Universe, Everything: http://tech-stew.com

Using:
data source="servername\MSDPM2012";persist security info=False;initial catalog=DPMDB
I used the domain sqlservice account and test connection was ok.
However.. accessing reports still crashes in the MMC
Tech, the Universe, Everything: http://tech-stew.com
When i recreated the db.. i called it Reporting2 or similiar..
Then the reports folder i created called "Reports Folder"
Then datasource name "reports datasource"
The issue here is that the DPM reports in the reporting web interface are gone, since this is a new DB.. how do i redeploy them
Tech, the Universe, Everything: http://tech-stew.com
i went back into the sql reporting services area.. hit change db.. chose the original .. then back to the url.. went to the OLD reporting services folder and datasource.. added the connect string and now reporting area works.. so does scheduling..
Problem now solved
Tech, the Universe, Everything: http://tech-stew.com
Oops spoke too soon.. the first time i set it to do "status" as a schedule.. it seemed to work (clicked ok, no error).. went back and added an email notification..
Now i'm getting.. "an error occurred causing the reporting job to fail" "system files may be corrupt".
Seems to only occur if i try to add the email address portion
Tech, the Universe, Everything: http://tech-stew.com
rechecked the datasource.. i think there was an error in the connect string.. now everything seems to be working.. email notifications and all.
Tech, the Universe, Everything: http://tech-stew.com

Connecting from Oracle to SQL Server

Hi
I am now tring to connect from oracle to sql server using database link.
Created database link
but when connecting to remote db getting the floowing error
select * from region@mysqlserverdsn
ERROR at line 1:
ORA-28545: error diagnosed by Net8 when connecting to an agent
Unable to retrieve text of NETWORK/NCR message 65535
ORA-02063: preceding 2 lines from MYSQLSERVERDSN
Can anyone help
My Listener File
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
(PROGRAM = extproc1)
(SID_DESC =
(GLOBAL_DBNAME = ORCL.DOMAIN.COM)
(ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
(SID_NAME = orcl)
(SID_DESC =
(GLOBAL_DBNAME = NORTHWIND.DOMAIN.COM)
(ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
(SID_NAME = MYSQLSERVERDSN)
(PROGRAM=hsodbc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST=
(ADDRESS = (PROTOCOL = TCP)(HOST = SALIHKM.DOMAIN.COM)(PORT = 1522))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
My Tnsnames Entry
MYSQLSERVERDSN =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.xxx)(PORT=1522))
(CONNECT_DATA=(SID=MYSQLSERVERDSN))
(HS=OK)
Lsnrctl is working fine.
c:\>lsnrctl start
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 18-MAY-2006 18:53
:13
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting tnslsnr: please wait...
TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
System parameter file is D:\oracle\product\10.2.0\db_1\network\admin\listener.or
a
Log messages written to D:\oracle\product\10.2.0\db_1\network\log\listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=SALIHKM.DOMAIN.COM)(POR
T=1522)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROCipc)
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=SALIHKM.DOMAIN.COM)(POR
T=1522)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Produ
ction
Start Date 18-MAY-2006 18:53:16
Uptime 0 days 0 hr. 0 min. 3 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File D:\oracle\product\10.2.0\db_1\network\admin\listener.o
ra
Listener Log File D:\oracle\product\10.2.0\db_1\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=SALIHKM.DOMAIN.COM)(PORT=1522)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROCipc)))
Services Summary...
Service "NORTHWIND.DOMAIN.COM" has 1 instance(s).
Instance "MYSQLSERVERDSN", status UNKNOWN, has 1 handler(s) for this service..
Service "ORCL.DOMAIN.COM" has 1 instance(s).
Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
But Tnsping show no listener
C:\>tnsping MYSQLSERVERDSN
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 18-MAY-2
006 18:56:27
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
D:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.xxx)(P
ORT=1522)) (CONNECT_DATA=(SID=MYSQLSERVERDSN)) (HS=OK))
TNS-12541: TNS:no listener
Services
C:\>lsnrctl services
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 18-MAY-2006 19:00
:04
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=SALIHKM.DOMAIN.COM)(POR
T=1522)))
Services Summary...
Service "NORTHWIND.DOMAIN.COM" has 1 instance(s).
Instance "MYSQLSERVERDSN", status UNKNOWN, has 1 handler(s) for this service..
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "ORCL.DOMAIN.COM" has 1 instance(s).
Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "orcl" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:1 refused:0 state:ready
LOCAL SERVER
Service "orclXDB" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1002 state:ready
DISPATCHER <machine: SALIHKM, pid: 2080>
(ADDRESS=(PROTOCOL=tcp)(HOST=SALIHKM.DOMAIN.COM)(PORT=1070))
Service "orcl_XPT" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:1 refused:0 state:ready
LOCAL SERVER
The command completed successfully
I am very much confused with this situation.
Thanks & Regards
Salih Km

Hi ,
Thanks for your reply.
Contents of my initMYSQLSERVERDSN.ora file is
# This is a sample agent init file that contains the HS parameters that are
# needed for an ODBC Agent.
# HS init parameters
HS_FDS_CONNECT_INFO = MYSQLSERVERDSN
HS_FDS_TRACE_LEVEL = 0
HS_FDS_TRACE_FILE_NAME = hsmsql.trc
# Environment variables required for the non-Oracle system
#set <envvar>=<value>
set ODBCINI=c:\WINDOWS\ODBC.INI
SALIHKM.DOMAIN.COM is my system in which Oracle Test DB is Installed.
SQL Server is in another location.
In Tnsnames i specified ip address.
One more doubt.
I am using 10g Release 2 demo version.
whether it will support Hetrogeneous Services?
How to know whether a database supports HS or not?
Thanks & Regards
Salih Km

DI Server - Cannot connect to named instance SQL server database

Similar Messages

Maybe you are looking for