Cannot connect to database master at SQL server at SERVERNAME

I have installed SQL 2008 R2 in a fresh win 2008 R2. I’m running the sharepoint configuration Wizard using the database server name with the correct domain
credentials but I get the following error message. “Cannot connect to database master at SQL server at
SERVERNAME. The database might not exist, or the current user does not have permission to connect”
I‘m able to login to the new SQL server using the “SQL server management studio” with no problems. I used the sa account and a domain account.
The sharepoint server is also a new installation. And both servers have the firewall disabled.
Thanks in advance for your help.
Simon

Hi,
What is your SharePoint server’s version?
Please make sure you use the farm admin account to launch SharePoint configuration wizard. If not, please log in with this account, then check the effect.
In addition, check if you create a named instance, such as, servername\sharepoint, however, you only specify the servername in the configuration wizard. If this is
the case, change to servername\sharepoint, then check the effect.
Thanks,
Rock Wang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Regards, Rock Wang Microsoft Online Community Support

Similar Messages

  • SCCM coudn't connect to database after recovering SQL server

    Hello.
    Please help to solve a problem. After crashing data storage, i have lost my SCCM and SQL server. I have restored SCCM server as virtual machine and re-install SQL server. I restored old databases to the new SQL server. Same instances and names. 
    And now i have logs smsexec.log : 
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    SMS_EXECUTIVE
    27.03.2015 10:34:19
    3268 (0x0CC4)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    SMS_EXECUTIVE
    27.03.2015 10:34:19
    3268 (0x0CC4)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    SMS_EXECUTIVE
    27.03.2015 10:34:19
    3268 (0x0CC4)
    CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
    SMS_EXECUTIVE
    27.03.2015 10:34:19
    3268 (0x0CC4)
    I found that i lost my certificate 
    i found article Certificate drop down menu empty when trying to select SSL certificate to enable SQL Server 2008 client encryption
    but i get an error when trying to execute certificate request.
    ERROR TRANSLATE ---  no information about certificate template
    I don't know what to do. Plz help. This problem sticks me. :(

    ~===================== << Starting Configuration Manager 2012 Setup >> =====================
    Configuration Manager Setup 01.04.2015 15:37:03
    8980 (0x2314)
    INFO: ConfigMgr2012 Setup was started by AV\dobrokhotov.vn.
    Configuration Manager Setup 01.04.2015 15:37:03
    8980 (0x2314)
    INFO: Command line specified was: "C:\Program Files\Microsoft Configuration Manager\bin\X64\SetupWpf.exe"
    Configuration Manager Setup 01.04.2015 15:37:03
    8980 (0x2314)
    FQDN for server SRV-SCCM is SRV-SCCM.ashipyards.com
    Configuration Manager Setup 01.04.2015 15:37:03
    8980 (0x2314)
    INFO: Target computer is a 64 bit operating system.
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Checking for existing setup information.
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Setting setup type to  1. Configuration Manager Setup
    01.04.2015 15:37:04 8980 (0x2314)
    INFO: Checking for existing SQL information.
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: 'SRV-SQL.ashipyards.com' is a valid FQDN.
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Verifying the registry entry for Asset Intelligence installation
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Found registry key for installation of Asset Intelligence full version
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 7958
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Phase is 1C7 Configuration Manager Setup
    01.04.2015 15:37:04 8980 (0x2314)
    WARNING: Failed to initialize COM to get SDK Providers. It might already be initialized. return code: 80010106.
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: SDK Provider is on SRV-SCCM.ashipyards.com.
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Setting the default CSV folder path Configuration Manager Setup
    01.04.2015 15:37:04 8980 (0x2314)
    INFO: Language: Mobile Device (INTL), LangPack: 0.
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Language: RUS, Server LangPack: 1. Configuration Manager Setup
    01.04.2015 15:37:04 8980 (0x2314)
    INFO: Language: RUS, Client LangPack: 1. Configuration Manager Setup
    01.04.2015 15:37:04 8980 (0x2314)
    INFO: Configuration Manager Build Number = 7958
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Configuration Manager Version = 5.0 Configuration Manager Setup
    01.04.2015 15:37:04 8980 (0x2314)
    INFO: Configuration Manager Minimum Build Number = 800
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Verifying Configuration Manager Active Directory Schema Extensions.
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Found DS Root:CN=Schema,CN=Configuration,DC=ashipyards,DC=com
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Verifying Configuration Manager Active Directory Schema Extensions.
    Configuration Manager Setup 01.04.2015 15:37:04
    8980 (0x2314)
    INFO: Found DS Root:CN=Schema,CN=Configuration,DC=ashipyards,DC=com
    Configuration Manager Setup 01.04.2015 15:37:05
    8980 (0x2314)
    INFO: SqlMasterDB = MSSC\master Configuration Manager Setup
    01.04.2015 15:37:05 8980 (0x2314)
    Removed SQL alias SRV-SQL.ashipyards.com\MSSC successfully.
    Configuration Manager Setup 01.04.2015 15:37:05
    8980 (0x2314)
    INFO: Registered type SRV-SQL.ASHIPYARDS.COM MSSC\MASTER for SRV-SQL.ashipyards.com MSSC\master
    Configuration Manager Setup 01.04.2015 15:37:05
    8980 (0x2314)
    INFO: Registered type SMS Master for SRV-SQL.ashipyards.com MSSC\master
    Configuration Manager Setup 01.04.2015 15:37:05
    8980 (0x2314)
    INFO: Registered type SRV-SQL.ASHIPYARDS.COM MSSC\SYSTEMCENTERCM_S01 for SRV-SQL.ashipyards.com MSSC\SystemCenterCM_S01
    Configuration Manager Setup 01.04.2015 15:37:05
    8980 (0x2314)
    INFO: Registered type SMS ACCESS for SRV-SQL.ashipyards.com MSSC\SystemCenterCM_S01
    Configuration Manager Setup 01.04.2015 15:37:05
    8980 (0x2314)
    INFO: 'SRV-SCCM.ashipyards.com' is a valid FQDN.
    Configuration Manager Setup 01.04.2015 15:37:05
    8980 (0x2314)
    INFO: Run Site Maintenance on the primary site.
    Configuration Manager Setup 01.04.2015 15:37:05
    8980 (0x2314)
    INFO: Checking for existing setup information.
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    INFO: Setting setup type to  1. Configuration Manager Setup
    01.04.2015 15:37:06 8980 (0x2314)
    INFO: Checking for existing SQL information.
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    INFO: 'SRV-SQL.ashipyards.com' is a valid FQDN.
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    INFO: Verifying the registry entry for Asset Intelligence installation
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    INFO: Found registry key for installation of Asset Intelligence full version
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    INFO: SDK Provider is on SRV-SCCM.ashipyards.com.
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    INFO: Retrieving current site control image...
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    CSiteSettings::ReadActualSCFFromDatabase: Failed to get sql connection
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    ERROR: Failed to retrieve verifiable site control data
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    INFO: Evaluating for Site Maintenance process.
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    INFO: g_SetupCmdLine.bMoveSql 0, g_SetupCmdLine.sNewSqlServer , g_SetupCmdLine.sNewSqlDatabaseName , pSetupInf->SqlMasterDB MSSC\master.
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:06
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:09
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:09
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:09
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:09
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:12
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:12
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:12
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:12
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:15
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:15
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:15
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:15
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:18
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:18
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:18
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:18
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:21
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:21
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:21
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:21
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:24
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:24
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:24
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:24
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:27
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:27
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:27
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:27
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:30
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:30
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:30
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:30
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:33
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:33
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:33
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:33
    8980 (0x2314)
    ERROR: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:36
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:36
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:36
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:36
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:36
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:39
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:39
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:39
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:39
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:42
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:42
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:42
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:42
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:45
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:45
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:45
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:45
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:48
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.2015 15:37:48
    8980 (0x2314)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS.
    Configuration Manager Setup 01.04.2015 15:37:48
    8980 (0x2314)
    INFO: SQL Connection failed. Connection: SMS ACCESS, Type: Secure
    Configuration Manager Setup 01.04.2015 15:37:48
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]SSL Provider: The certificate chain was issued by an authority that is not trusted.
    Configuration Manager Setup 01.04.2015 15:37:51
    8980 (0x2314)
    *** [08001][-2146893019][Microsoft][SQL Server Native Client 11.0]Client unable to establish connection
    Configuration Manager Setup 01.04.

  • Cannot connect to database after change of server ip

    hi gems..
    the ip of our database server has got changed.
    Windows server, 11gr2 database version, archivelog mode.
    i have changed the tnsnames.ora and the listener.ora manually with the new ip.
    I am able to connect to sqlplus "/as sysdba" (since authentiacetion services is NTS)
    But i am not able to connect to 'sqlplus sys/password@sid as sysdba'
    it is throwing the error of
    ERROR:
    ORA-12560: TNS:protocol adapter error
    pls help...

    tnsping sid:
    E:\>tnsping ORCL
    TNS Ping Utility for 32-bit Windows: Version 11.2.0.1.0 - Production on 28-FEB-2
    012 19:11:53
    Copyright (c) 1997, 2010, Oracle. All rights reserved.
    Used parameter files:
    E:\app\product\11.2.0\dbhome_1\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 10.184.1
    32.101)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl)
    TNS-12560: TNS:protocol adapter error
    E:\>
    lsnrctl status
    E:\>lsnrctl status
    LSNRCTL for 32-bit Windows: Version 11.2.0.1.0 - Production on 28-FEB-2012 19:13
    :13
    Copyright (c) 1991, 2010, Oracle. All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.184.132.101)(PORT=152
    1)))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
    TNS-00511: No listener
    32-bit Windows Error: 61: Unknown error
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
    TNS-12541: TNS:no listener
    TNS-12560: TNS:protocol adapter error
    TNS-00511: No listener
    32-bit Windows Error: 2: No such file or directory
    listener.ora
    # listener.ora Network Configuration File: E:\app\product\11.2.0\dbhome_1\network\admin\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = CLRExtProc)
    (ORACLE_HOME = E:\app\product\11.2.0\dbhome_1)
    (PROGRAM = extproc)
    (ENVS = "EXTPROC_DLLS=ONLY:E:\app\product\11.2.0\dbhome_1\bin\oraclr11.dll")
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.184.132.101)(PORT = 1521))
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    ADR_BASE_LISTENER = E:\app
    ipconfig
    E:\>ipconfig
    Windows IP Configuration
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    IP Address. . . . . . . . . . . . : 10.184.132.101
    Subnet Mask . . . . . . . . . . . : 255.255.252.0
    Default Gateway . . . . . . . . . : 10.184.132.1
    i have changed the ip 10.184.132.101 manually as per the new ip.

  • Connect Oracle Reports to Ms Sql Server DB

    Is it possilbe to Connect Oracle Reports to Microsoft Sql Server database. If yes then how. Please advice.
    Thanks
    Sami.

    It is possible to connect Oracle database to MS Sql server database using the Oracle Transparent Gateway for MS SQL Server.
    You can use the following links to configure such connection:
    Oracle Transparent Gateways - General Description - Part I
    http://oracle-apps-dba.blogspot.com/2008/04/oracle-transparent-gateways-general.html
    Oracle Transparent Gateway for MS SQL Server - Part II
    http://oracle-apps-dba.blogspot.com/2008/04/oracle-transparent-gateway-for-ms-sql_16.html
    Aviad

  • How to connect labviewv database toolkit to SQL CE server

    Dear sir,
                      i am using labview 8.2.1 and Database Connectivity 8.2.i need same simple  concept of how to connect  LV database toolkit to SQL CE Server.

    When opening the database connection, you will need to provide either a connection string, or a path to a UDL (which will contain a conenction string). The easiest way to get a connection string is to go to (no I am not kidding) www.ConnectionStrings.com. Once there you enter the type of DBMS you are trying to connect to, and the system will list connection strings that you can use based on the drivers that you're using.
    How much experience do you have with LV and/or databases?
    Mike...
    PS: you might also want to check out a series I did a bit ago on database connectivity in my blog. See the link in my signature...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Run Reporting services 2005 with databases housed on SQL Server 2012?

    Hi, I have a RS 2005 install in which the ReportServer and ReportServerTempDB databases reside on a different SQL Server 2005 server. I am planning to upgrade DB server to 2012 and would like to keep SSRS as 2005.As a second phase I will upgrade SSRS2005
    to SSRS 2008. So I would be running something like this:
    Server A: SQL 2005 Reporting Services
    Server B: SQL 2012 database engine - housing ReportServer and ReportServerTempDB
    Is this configuration supported? 

    Hello,
    According to the
    BOL, Report Server service checks the database version at startup. If the report server is connected to a database that is an earlier version, the report server will update the database during startup.If you have a newer report server database, you
    cannot use it with an earlier version of a report server instances.
    In that case, the earlier versions of SQL Server Database Engine that can be used to host the SSRS report server databases. For example, In SQL Server 2005 Reporting Services, we can use either SQL Server 2000 or SQL Server 2005 to host the databases, for
    SSRS 2012, we can use SQL Server 2012,2008 R2,2008,2005.
    Based on my test, In the Reporting Services 2005 Configure Manager, we can create a new database on a remote SQL Server 2012 database engine and the Initialization is successful.
    In this way, the databases are created from the script file which installed with the Reporting Services instance, you can find the Catalog.sql and CatalogTempDB.sql  under folder C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer.
    However, when upgrade the existing ReportServer database and ReportServerTempDB database on the SQL Server 2012 by restore from a backup, we cannot use this existing database for Reporting Services 2005 and get the following message:
    The database version (162) does not match your reporting serivces installation.And the initialization failed.
    In your case, you can host the ReportServer database and ReportServerTempDB database of SSRS 2005 on SQL Server 2012 database enginer by create a new database from Reporting Services 2005 Configure Manager. But you cannot use the existing
    database which upgrade to SQL Server 2012.
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click here. 
    Fanny Liu
    TechNet Community Support

  • Cannot connect to database host...

    Hello,
    First, I want to say i'm not so good in english that's why i'm apologies for this.
    I try to use Sun VDI, my computer doesn't work in 64 bits that's why i use this product in 32 bits so I'm in a product envionnement.
    I've installed A mysql 5 server in a 2003 server with php, phpmyadmin to see database, and when i install sun vdi in my solaris 10 i have this error message:
    Cannot connect to database host...ip:3306 as user root, but when i've install mysql i've just root for user and i use this he work, and i use this login to connect in my database.
    What can Have to do now? My port is really 3306 when i install mysql and the two machine is in the same network, ping work.
    Thanks for yours futur answers
    Regards,

    Select (1/2/0) : 1
    Specify an administrator password: (in my case) xxxxxxxx _(password of my sql)_ <------ This is wrong. This can be any desired admin password.
    specify a cluster signature: 7727kkkk
    again
    you can only connect to a remote MYSQL database in a 32-bit system.
    Continue? (y/n): y
    Enter the dns name of mysql server: _192.168.168.165_ <------- This is wrong. This is an IP address and not a DNS name (not sure if that is really a problem here).
    Enter the port of mysql server : 3306
    enter mysql priviliged administrator: root_ <------- This is wrong. Here you have to enter the admin user name of your database.
    enter mysql priviliged administrator password: xxxxxxxx_ <------- Here you enter the corresponding password for this user (so password of your MySQL account)
    Do you want to use a Socket secure layer (ssl) connection for '192.168.168.165'? (yn): n
    Cannot connect to database host 192.168.168.x:3306 as user 'root'
    Please make you shure connexion daitels you have provided are correct
    Where i have wrong please?

  • Cannot connect to Database attempts hang (no errors)

    hi, i have oracle 9.2 on solaris 5.8
    weirdly, today we could not connect the db anymore. even these does not work on the server:
    sqlplus /nolog
    SQL> connect /as sysdba
    sqlplus "/ as sysdba"
    sqlplus system/**
    ALL attemps just hang , no errors.
    what can i do?
    i think the only way is reboot the machine?
    any ideas?

    here is the output
    bash-2.05# vmstat 2 20
    kthr memory page disk faults cpu
    r b w swap free re mf pi po fr de sr f0 m0 m1 m2 in sy cs us sy id
    0 0 0 1940080 1012952 9 25 51 0 0 0 0 0 7 5 7 729 777 245 15 3 82
    0 0 0 1828840 855200 0 4 0 0 0 0 0 0 386 7 387 5626 62112 3614 25 40 35
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 384 7 384 5611 62299 3786 23 40 37
    0 1 0 1828840 855200 0 0 0 0 0 0 0 0 372 6 373 5582 63459 3754 24 39 37
    0 2 0 1828840 855200 0 0 0 0 0 0 0 0 391 7 391 5640 63245 3976 23 38 40
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 374 18 374 5789 61626 3760 24 37 3
    9
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 373 7 373 5536 62333 3888 20 47 34
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 376 7 376 5585 62463 3594 24 42 35
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 354 8 354 5364 61787 3396 24 41 36
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 378 7 378 5616 61667 3777 18 47 35
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 364 11 364 5494 63075 3616 24 40 3
    6
    0 2 0 1828840 855200 0 0 0 0 0 0 0 0 388 8 388 5733 62161 3947 22 39 39
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 388 8 388 5702 61873 4142 22 43 35
    0 1 0 1828840 855200 0 0 0 0 0 0 0 0 383 7 383 5584 63365 3815 28 33 40
    1 0 0 1828840 855200 0 0 0 0 0 0 0 0 387 7 387 5643 63920 3846 29 29 41
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 378 10 378 5650 61793 3914 23 40 3
    6
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 388 7 389 5644 62798 4064 24 36 40
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 377 11 377 5592 62206 3941 23 47 3
    0
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 379 8 380 5605 61121 3959 21 50 29
    kthr memory page disk faults cpu
    r b w swap free re mf pi po fr de sr f0 m0 m1 m2 in sy cs us sy id
    0 0 0 1828840 855200 0 0 0 0 0 0 0 0 379 7 379 5511 61964 3549 19 46 35
    Also, i cannot connect the database, i dont have any active connections, cannot run any sql statements..

  • How to connect from Oracle 11g to SQL Server 2008 R2

    Hi,
    Is it possible to connect from Oracle 11g on AIX to SQL Server 2008 R2? If so, what is the preferred method?
    SQL Server has the original table. From Oracle 11g, we want to access data which is in SQL Server real time.
    Thank You
    Sarayu

    Hi,
    Have a look at these Oracle notes for the full information on the gateways -
    Master Note for Oracle Gateway Products (Doc ID 1083703.1)
    Functional Differences Between DG4ODBC and Specific Database Gateways (Doc ID 252364.1)
    Gateway and Generic Connectivity Licensing Considerations (Doc ID 232482.1)
    How to Setup DG4MSQL (Oracle Database Gateway for MS SQL Server) 64bit Unix OS (Linux, Solaris, AIX,HP-UX) (Doc ID 562509.1)
    How to Configure DG4ODBC on 64bit Unix OS (Linux, Solaris, AIX, HP-UX Itanium) to Connect to Non-Oracle Databases Post Install (Doc ID 561033.1)
    The Database Gateway for SQL*Server (DG4MSQL) needs a separate license but the Database Gateway for ODBC (DG4ODBC) is included in your RDBMS license. You only need to provide the third party ODBC driver needed by DG4ODBC.
    Regards,
    Mike

  • Connecting and Accessing Oracle with SQL Server

    In Oracle and SQL Servers I'm Updating the data manually. But I want make it Automated Process(Updating required columns automatically) in SQL Server by using trigger during manual update in Oracle's table with respect to column .
    Is this possible?
    Im using Oracle 11g in linux and SQL Server 2005 in windows.
    Both Servers are in different locations , but are in same network and not connected with ODBC , dblink .
    I need your Valuable assitance and Helpful guide for succesfully completing my task.
    Useful Replies are Highly Appreciated.

    Hi,
    Yes, you can update SQL*Server tables from Oracle using triggers if you install and use the Database Gateway for SQL*Server (DG4MSQL). You need to use DG4MSQL because it supports distributed transactions so that the Oracle and SQL*Server commits can be synchronised and both will be rolled back if there is an error.
    You could use the Database Gateway for ODBC (DG4ODBC) but you would have to write your own error routines to handle problems if the commits fail in either Oracle or SQL*Server.
    There is more information about the gateways in this note available in My Oracle Support -
    Master Note for Oracle Gateway Products (Doc ID 1083703.1)
    Regards,
    Mike

  • How can I connect NetBeans 6.1 with SQL Server 2005?

    Hello guys...
    how can i connect NetBeans 6.1 with SQL Server 2005?
    there is no SQL Server in Server list when we create a new Web Project and choose Server.
    I'm new to NetBeans and this is my first time of posting.
    If has some errors and unwanted disturbing,pls understand me. Thanks.
    (If you have references or some snippets, i'll be glad if u can share.)
    scsfdev

    The JDBC-ODBC bridge wasn't recognizing any of the primary keys I had set up in SQL Server. After lots of head banging, here's the solution I came up with:
    1. Download the appropriate driver. SQL Server 2000 requires the SQL Server 2000 JDBC driver (http://www.microsoft.com/downloads/details.aspx?FamilyId=07287B11-0502-461A-B138-2AA54BFDC03A&displaylang=en).
    SQL Server 2005 download: (http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en)
    3. After installing, right-click on "Libraries" in your project, and choose "Add Library...". Next, give it a name (i.e. SQLServer2000), and select "Class Libraries".
    4. On the next screen, find the JAR files (should be in C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\), and add them under the "Classpath" tab. It will now be available under "Libraries" for future projects.
    5. You can now create a connection to a specific database under the "Services" tab (next to "Projects" and "Files" in the top left of the screen). Select "Microsoft Sql Server 2000 (Microsoft Driver)" and format the "Database URL" like this:
    jdbc:microsoft:sqlserver//YOURSERVER:1433;DatabaseName=YOURDATABASE
    1433 is the default port, though your DBA may have changed it.
    I posted a simpler version of this on the NetBeans.org FAQ page - they had the following title with no content on the answer page:
    "Cannot Select Tables From MsSql 2000 Because It Says No Primary Key Next To Each Table But The Tables DO Have A Primary Key. What Do I Do?"

  • Remote Connection from SAP to MS-SQL server

    Hello Experts,
    We have been following 2 options so far and we have come across some issues
    The first Option is to call a stored procedure (this is our preferred method) which does the data transfer for us
    We have been able to test this scenario successfully from SQL Server side
    However, while calling the stored proc via native SQL from ABAP we have come across an issue which is due to SQL 2005 changes (Schema implementation and difference in the security context)
    While calling the stored procedure from the ABAP Code we have an error
                The program short dumps with runtime error DBIF_DSQL2_SQL_ERROR, exception CX_SY_NATIVE_SQL_ERROR. The database error code is 15274, and the error text is
                 "Access to the remote server     is denied because the current security context is not trusted."
    This issue is new after the SQL Server 2005.
    We are trying to resolve that.
    Secondly we have been trying the DBCON option as well as per OSS Note 323151
    We have a few things thatu2019s impacting our scenario:
    The remote servers are in a different domain
    The remote servers are located  in DIZ
    Remote server is a named instance
    Remote server has been configured with a different port than standard (1565) u2013 All Connection strings will need port in there
    The Database name starts with a numeric value
    Due a combination of factors as mentioned above the standard approach does not work
    Have any of you used this approach while connecting from SAP to MS-SQL server? Do you know of any successful methods to connect to SQL using ABAP (or not) from SAP.
    Thanks in advance,

    Yes,
    DBConnect & UDConnect.
    Works like a charm.
    We write data into a MS-SQL database via DBConnect & an ABAP program (using open sql).

  • Assigning database roles on SQL Server db

    I am trying to set up a SQL Server adapter (not a database table adapter for SQL tables) to manage role assignment on a database 'test1' on my sql server ( 2000) 'sqlserver1' using IdM 7.1. I am trying to assign role1 to user tuser1 on test1. I am using 'sa' account so permissions should not be an issue.
    Per resource reference document, I mapped:
    userNametest1 <-> userNametest1
    rolestest1 <-> rolestest1
    My login for user 'tuser1' gets created on the SQL server. However the database and role assignment is not happening. I do not get any errors in the IdM admin pages from where I am testing this. Hence I am assuming I am not setting something right in the resource schema. I have tried different ways such as
    userNametest1 <->userName
    rolestest1 <-> roles
    and some more combination but none seem to work. How can i find out what my resource attribute mapping should be? If anyone has done this, can you please share how you got it work?
    Thanks in advance.

    Some more info.
    I have set up the out of the box MS SQL server adapter to connect to MSDE version of SQL server running on my local machine. I used the MSSQLServer Form provided in the samples folder and assigned it to an admin user and turned on the trace.
    I am able to create logins by assigning the resource to a user. Using the admin user I am able to see in the trace that the server Roles are also being retrieved fine. What I am not able to get is assigning a database to the user and then assigning db roles.
    Following the documentation (Resource Reference guide for IdM 7.1) I have created following attributes on the left hand side of schema.
    defaultDB,serverRoles,domain, userNameMyTestDb,rolesMyTestDb.
    No matter what I map the last two attribute I am not able to assign a db and dbroles to a user. I turned on sql profiler and then again used the admin user to view a test user using MSSqlServer form and it appears that the procedure sp_databases is not being called at all. I have decompiled the sql server class file and it appears there might be an issue with the way list of databases is being retrieved.
    Has any one seen this before? If you were able to get it to work, can you please give me information on the resource schema and any other settings you had to make to get it to work?
    Thanks in advance.

  • Problem with "Database Gateway for SQL Server"

    Hello,
    i am testing the different technologies for connecting an oracle database with a sql-server database.
    The way using 10g-generic-connectivity with ODBC works fine, but the 11g-DG4MSQL makes problems.
    Environment:
    Server PEGASUS (32bit Windows Server 2003 R2 SP2) with Oracle Database 10g Release 10.2.0.4.0
    Server OBELIXUS (32bit Windows 2000 Sp4) with MS-SQL-Server 2005
    On PEGASUS i have installed the gateway in a new oracle home directory:
    "D:\oracle\product\10.2.0\db_1" => home directory of 10g
    "D:\oracle\product\11.1.0\tg_1\" => home directory of the gateway
    D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\tnsnames.ora:
    MSSQLDG =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = PEGASUS)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = DG4MSQL)
    (HS = OK)
    MSSQL =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = PEGASUS)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = MSSQLTEST)
    (HS = OK)
    D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora:
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
    (PROGRAM = extproc)
    (SID_DESC =
    (GLOBAL_DBNAME = INTEGRAT)
    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
    (SID_NAME = INTEGRAT)
    (SID_DESC =
    (SID_NAME = MSSQLTEST)
    (PROGRAM = D:\oracle\product\10.2.0\db_1\bin\hsodbc)
    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
    (SID_DESC=
    (SID_NAME=DG4MSQL)
    (ORACLE_HOME=D:\oracle\product\11.1.0\tg_1)
    (PROGRAM=D:\oracle\product\11.1.0\tg_1\BIN\dg4msql)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (ADDRESS = (PROTOCOL = TCP)(HOST = pegasus.cursor.de)(PORT = 1521))
    D:\oracle\product\11.1.0\tg_1\dg4msql\admin\initDG4MSQL.ora:
    HS_FDS_CONNECT_INFO=OBELIXUS/MSSQLSERVER/testuju
    HS_FDS_TRACE_LEVEL=DEBUG
    HS_FDS_RECOVERY_ACCOUNT=RECOVER
    HS_FDS_RECOVERY_PWD=RECOVER
    D:\oracle\product\10.2.0\db_1\hs\admin\initMSSQLTEST.ora:
    HS_FDS_CONNECT_INFO=DSN_MSSQL
    HS_FDS_TRACE_LEVEL=OFF
    HS_LANGUAGE=AMERICAN_AMERICA.WE8MSWIN1252
    HS_FDS_FETCH_ROWS=100
    HS_RPC_FETCH_REBLOCKING=OFF
    How mentioned above, the access from oracle to sqlserver using MSSQL(10g hsodbc.exe) works fine.
    But when trying to acces the sqlserver using MSSQLDG (11g dg4msql.exe) I get the following error:
    ORA-28500: Verbindung von ORACLE zu Fremdsystem gab diese Nachricht zurück:
    [Oracle][ODBC SQL Server Driver][DBNETLIB]Ungültige Verbindung.
    [Oracle][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (ParseConnectParams()).
    [Oracle][ODBC SQL Server Driver]Ungültiges Attribut für die Verbindungszeichenfolge
    ORA-02063: vorherige 2 lines von DBL_MSSQL4
    Here the contect of the file "DG4MSQL_agt_2332.trc":
    Oracle Corporation --- FREITAG AUG 22 2008 16:17:42.198
    Heterogeneous Agent Release
    11.1.0.6.0
    Oracle Corporation --- FREITAG AUG 22 2008 16:17:42.198
    Version 11.1.0.6.0
    Entered hgogprd
    HOSGIP for "HS_FDS_TRACE_LEVEL" returned "DEBUG"
    Entered hgosdip
    setting HS_OPEN_CURSORS to default of 50
    HOSGIP returned value of "RECOVER" for HS_FDS_RECOVERY_ACCOUNT
    HOSGIP returned a value for HS_FDS_RECOVERY_PWD
    setting HS_FDS_TRANSACTION_LOG to default of "HS_TRANSACTION_LOG"
    setting HS_FDS_TRANSACTION_ISOLATION to default of "READ_COMMITTED"
    setting HS_NLS_NCHAR to default of "AL16UTF16"
    setting HS_FDS_TIMESTAMP_AS_DATE to default of "TRUE"
    setting HS_RPC_FETCH_REBLOCKING to default of "ON"
    setting HS_FDS_FETCH_ROWS to default of "100"
    setting HS_FDS_RESULTSET_SUPPORT to default of "FALSE"
    setting HS_FDS_PROC_IS_FUNC to default of "FALSE"
    setting HS_FDS_CHARACTER_SEMANTICS to default of "FALSE"
    setting HS_FDS_MAP_NCHAR to default of "TRUE"
    setting HS_NLS_DATE_FORMAT to default of "YYYY-MM-DD HH24:MI:SS"
    setting HS_FDS_REPORT_REAL_AS_DOUBLE to default of "FALSE"
    setting HS_LONG_PIECE_TRANSFER_SIZE to default of "65536"
    setting HS_SQL_HANDLE_STMT_REUSE to default of "FALSE"
    setting HS_FDS_QUERY_DRIVER to default of "FALSE"
    setting HS_CALL_NAME_ISP to "gtw$:SQLTables;gtw$:SQLColumns;gtw$:SQLPrimaryKeys;gtw$:SQLForeignKeys;gtw$:SQLProcedures;gtw$:SQLStatistics"
    Exiting hgosdip, rc=0
    ORACLE_SID is "DG4MSQL"
    Product-Info:
    Port Rls/Upd:6/0 PrdStat:0
    Agent:Oracle Database Gateway for MSSQL
    Facility:hsa
    Class:MSSQL, ClassVsn:11.1.0.6.0_0006, Instance:DG4MSQL
    Exiting hgogprd, rc=0
    Entered hgoinit
    HOCXU_COMP_CSET=1
    HOCXU_DRV_CSET=178
    HOCXU_DRV_NCHAR=2000
    HOCXU_DB_CSET=178
    HOCXU_SEM_VER=102000
    Entered hgolofn at 2008/08/22-16:17:42
    RC=-1 from HOSGIP for "PATH"
    PATH from environment is "d:\oracle\product\11.1.0\tg_1\bin;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Programme\IBM\Informix\Client-SDK\bin"
    Exiting hgolofn, rc=0 at 2008/08/22-16:17:43
    HOSGIP for "HS_OPEN_CURSORS" returned "50"
    HOSGIP for "HS_FDS_FETCH_ROWS" returned "100"
    HOSGIP for "HS_LONG_PIECE_TRANSFER_SIZE" returned "65536"
    HOSGIP for "HS_NLS_NUMERIC_CHARACTER" returned ".,"
    Exiting hgoinit, rc=0 at 2008/08/22-16:17:43
    Entered hgolgon at 2008/08/22-16:17:43
    reco:0, name:testuju, tflag:0
    Entered hgosuec at 2008/08/22-16:17:43
    uencoding=UTF16
    Entered shgosuec at 2008/08/22-16:17:43
    Exiting shgosuec, rc=0 at 2008/08/22-16:17:43
    shgosuec() returned rc=0
    Exiting hgosuec, rc=0 at 2008/08/22-16:17:43
    HOSGIP for "HS_FDS_RECOVERY_ACCOUNT" returned "RECOVER"
    HOSGIP for "HS_FDS_TRANSACTION_LOG" returned ""HS_TRANSACTION_LOG""
    HOSGIP for "HS_FDS_TIMESTAMP_AS_DATE" returned "TRUE"
    HOSGIP for "HS_FDS_CHARACTER_SEMANTICS" returned "FALSE"
    HOSGIP for "HS_FDS_MAP_NCHAR" returned "TRUE"
    HOSGIP for "HS_FDS_RESULT_SET_SUPPORT" returned "FALSE"
    HOSGIP for "HS_FDS_PROC_IS_FUNC" returned "FALSE"
    HOSGIP for "HS_FDS_REPORT_REAL_AS_DOUBLE" returned "FALSE"
    using testuju as default value for "HS_FDS_DEFAULT_OWNER"
    HOSGIP for "HS_SQL_HANDLE_STMT_REUSE" returned "FALSE"
    Entered hgocont at 2008/08/22-16:17:43
    HS_FDS_CONNECT_INFO = "OBELIXUS/MSSQLSERVER/testuju"
    RC=-1 from HOSGIP for "HS_FDS_CONNECT_STRING"
    Entered hgogenconstr at 2008/08/22-16:17:43
    dsn:OBELIXUS/MSSQLSERVER/testuju, name:testuju
    optn:
    Entered shgogohn at 2008/08/22-16:17:43
    ohn is 'OraGtw11g_home1'
    Exiting shgogohn, rc=0 at 2008/08/22-16:17:43
    Entered hgocont_OracleCsidToIANA at 2008/08/22-16:17:43
    Returning 2252
    Exiting hgocont_OracleCsidToIANA at 2008/08/22-16:17:43
    ##>Connect Parameters (len=223)<##
    ## DRIVER=Oracle 11g dg4msql-OraGtw11g_home1;
    ## SERVER=OBELIXUS\MSSQLSERVER;
    ## Database=testuju;
    #! UID=testuju;
    #! PWD=*
    ## AnsiNPW=Yes;
    ## QuotedId=Yes;
    ## IANAAppCodePage=2252;
    ## ArraySize=100;
    ## PadVarbinary=0;
    ## SupportNumericPrecisionGreaterThan38=1;
    Exiting hgogenconstr, rc=0 at 2008/08/22-16:17:44
    Entered hgopoer at 2008/08/22-16:18:00
    hgopoer, line 159: got native error 14 and sqlstate 08001; message follows...
    [Oracle][ODBC SQL Server Driver][DBNETLIB]Ungültige Verbindung.[Oracle][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (ParseConnectParams()).[Oracle][ODBC SQL Server Driver]Ungültiges Attribut für die Verbindungszeichenfolge
    Exiting hgopoer, rc=0 at 2008/08/22-16:18:00
    hgocont, line 1890: calling SqlDriverConnect got sqlstate 08001
    Exiting hgocont, rc=28500 at 2008/08/22-16:18:00 with error ptr FILE:hgocont.c LINE:1910 ID:Something other than invalid authorization
    Exiting hgolgon, rc=28500 at 2008/08/22-16:18:00 with error ptr FILE:hgolgon.c LINE:612 ID:Calling hgocont
    Entered hgoexit at 2008/08/22-16:18:00
    Exiting hgoexit, rc=0 at 2008/08/22-16:18:00
    Many thanks in advance for any help!
    Regards Hartmut

    At first your configuration is not really correct.
    =====================================================
    In the LISTENER.ORA from 10g, you must only refer to the database and hsodbc 10g
    D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora:
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
    (PROGRAM = extproc)
    (SID_DESC =
    (GLOBAL_DBNAME = INTEGRAT)
    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
    (SID_NAME = INTEGRAT)
    (SID_DESC =
    (SID_NAME = MSSQLTEST)
    (PROGRAM = D:\oracle\product\10.2.0\db_1\bin\hsodbc)
    (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (ADDRESS = (PROTOCOL = TCP)(HOST = pegasus.cursor.de)(PORT = 1521))
    ===========================================================
    Then you have to create a new listener (new name) in the gateway oracle_home on a different port than instance database:
    D:\oracle\product\11.1.0\tg_1\network\admin\listener.ora
    SID_LIST_LISTENERGTW =
    (SID_LIST =
    (SID_DESC=
    (SID_NAME=DG4MSQL)
    (ORACLE_HOME=D:\oracle\product\11.1.0\tg_1)
    (PROGRAM=D:\oracle\product\11.1.0\tg_1\BIN\dg4msql)
    LISTENERGTW=
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = pegasus.cursor.de)(PORT = 1522))
    To start it, use the command below:
    D:\oracle\product\11.1.0\tg_1\bin\LSNRCTL start listenergtw
    ===========================================================
    D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\tnsnames.ora:
    match the DG4MSQL with the listener on 1522 port
    HSODBC match with binary10g on listener 1521 port
    MSSQLDG =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = PEGASUS)(PORT = 1522))
    (CONNECT_DATA =(SERVICE_NAME = DG4MSQL))
    (HS = OK)
    MSSQL =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = PEGASUS)(PORT = 1521))
    (CONNECT_DATA =(SERVICE_NAME = MSSQLTEST))
    (HS = OK)
    Try to configure and let me know your feedback
    regards,
    Mireille

  • Cannot connect to database via TNS

    Hello!
    I installed XE with default settings and have some trouble. I cannot connect to database via TNS. Two symptoms:
    1. I can connect with SQLPLUS system/pwd (locally, without tns name input), but CANNOT connect with SQLPLUS system/pwd@EX (WITH TNS NAME input).
    2. I cannot start Database Home Page.
    How to avoid this problem? Any ideas?
    DETAILS:
    PC configuration: Win2k+SP4, 512Mb, Outpost Firewall (disabled!), No another Oracle products being installed.
    TNSNAMES.ORA file:
    ************* BEGIN TNSNAMES *****************************************
    XE =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = pz)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = XE)
    EXTPROC_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
    (CONNECT_DATA =
    (SID = PLSExtProc)
    (PRESENTATION = RO)
    ORACLR_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
    (CONNECT_DATA =
    (SID = CLRExtProc)
    (PRESENTATION = RO)
    ************* END OF TNSNAMES *****************************************
    Listener status:
    ************* BEGIN STATUS *****************************************
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Prod
    ction
    Start Date 22-MAR-2006 17:27:15
    Uptime 0 days 1 hr. 8 min. 53 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Default Service XE
    Listener Parameter File D:\oracle\ora10xe\app\oracle\product\10.2.0\server\ne
    work\admin\listener.ora
    Listener Log File D:\oracle\ora10xe\app\oracle\product\10.2.0\server\ne
    work\log\listener.log
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC_FOR_XEipc)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=pz)(PORT=1521)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=8080))(Presentation
    HTTP)(Session=RAW))
    Services Summary...
    Service "CLRExtProc" has 1 instance(s).
    Instance "CLRExtProc", 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...
    Service "XEXDB" has 1 instance(s).
    Instance "xe", status READY, has 1 handler(s) for this service...
    Service "XE_XPT" has 1 instance(s).
    Instance "xe", status READY, has 1 handler(s) for this service...
    Service "xe" has 1 instance(s).
    Instance "xe", status READY, has 1 handler(s) for this service...
    The command completed successfully
    ************* END OF STATUS *****************************************
    NETSTAT -an results:
    ************* BEGIN NETSTAT *****************************************
    Proto Local Address Foreign Address State
    TCP 0.0.0.0:1521 0.0.0.0:0 LISTENING
    TCP 0.0.0.0:2298 0.0.0.0:0 LISTENING
    TCP 127.0.0.1:2455 127.0.0.1:8080 ESTABLISHED
    TCP 127.0.0.1:8080 0.0.0.0:0 LISTENING
    TCP 127.0.0.1:8080 127.0.0.1:2382 CLOSE_WAIT
    TCP 127.0.0.1:8080 127.0.0.1:2455 ESTABLISHED
    TCP 192.168.200.49:1521 192.168.200.49:2298 ESTABLISHED
    TCP 192.168.200.49:2298 192.168.200.49:1521 ESTABLISHED
    <truncated>
    ************* END OF NETSTAT *****************************************
    I found following error in SQLNET.LOG:
    *************** START LOG *********************************************
    Fatal NI connect error 12570, connecting to:
    (LOCAL=NO)
    VERSION INFORMATION:
         TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
         Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 10.2.0.1.0 - Production
         Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 10.2.0.1.0 - Production
    Time: 22-MAR-2006 17:28:59
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12570
    TNS-12570: TNS:packet reader failure
    ns secondary err code: 12560
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
    *************** END OF LOG *******************************************

    I successfully connect with XE client to another Oracle databases from LAN, including 8i and 9i databases.
    But cannot connect from another machines to my XE.

Maybe you are looking for