"Cant edit NetworkLayer" when I choose SQL Server OLE DB

Post Author: d.tiles
CA Forum: General Feedback
Hi,I have a problem with the BO Supervisor 6.5: I can't connect to my local Microsoft Sql Server 2003 using OLE DB, but only  with ODBC...The system hangs for a while after I've choosen this option, and then I receive this error message: "Cant edit NetworkLayer" Any idea? Thank you  Daniele Tiles

Hi,
Thanks for posting here.
Connecting to Microsoft Azure SQL Database by using OLE DB or ADO is not supported on SQL Azure.
Ref: http://www.connectionstrings.com/sql-azure/
Microsoft does not announce support for OLE DB connections to Azure and there are limitations. Some required OLE DB schema rowsets are not available from an Azure connection, and some properties that identify features in SQL Server are not adjusted to represent
SQL Azure limitations. For most common connect/query/update tasks it seems to work fine.
Provider=SQLNCLI11;Password=myPassword;User ID=[username]@[servername];
Initial Catalog=databasename;Data Source=tcp:[servername].database.windows.net;
Ref: http://msdn.microsoft.com/en-us/library/azure/ee336245.aspx
You can also check
Connectivity Considerations for SQL Server in Azure Virtual Machines
Hope this helps you.
Girish Prajwal

Similar Messages

  • What are the advantage of using Oracle Database when compare to SQL SERVER

    Hi all
    Please tell anyone about
    what are the advantage of using Oracle Database when compare to SQL SERVER
    Thanks in advance
    Balamurugan S

    user12842738 wrote:
    Hi,
    There are various differences between the two.
    1. SQL Server is only Windows, but Oracle runs on almost all Platforms.
    2. You can have multiple databases in SQL Server, but Oracle provides you only one database per instance.Given that the very term 'database' has s different meaning in the two products, this "difference" is absolutely meaningless.
    3. SQL Server provides T-SQL for writing programs, whereas Oracle provides PL/SQLWhich means what? Both products have a procedural programming language. They named them differently, and the languages are not interchangeable. Means nothing in comparing the features/strengths/weaknesses/suitability to purpose.
    4. Backup types in both are the same. (Except Oracle provides an additional backup called Logical Backup.)You make that sound like "Logical Backup" is something more than it is. It is nothing more than an export of the data and metadata. Many experts don't even consider it a backup. I'm sure SQL Server provides the same functionality though they probably call it by some other name.
    5. Both provide High Availability.Well, I guess they both have a suite of features they refer to as "High Availability". But what does that really mean? The devil is in the details. Remember, the two products don't even agree on what constitutes a "database".
    6. Both come in various distributions.???
    >
    If you are going for an Implementation, you can try SQL Server Express Edition and Oracle XE which are free to use.
    Then you can choose whichever is comfortable for your needs.
    Thanks.

  • I get one or the other error when i install SQL server 2012 SP1 in my Lab server

    I get multiple errors when i install SQL server 2012 SP1 In my lab server.
    Not sure why i keep getting different errors all the time when i install SQL server 2012 & 2012 SP1.
    Below are error codes, screen shots and also a log of the error.
    1.  Eror code 0X84B40000
    Also dint understand any thing from this article related to the above error 
    http://social.technet.microsoft.com/Forums/sqlserver/en-US/5b6cc928-0db8-4fe4-a5d3-21672225f0ca/i-get-error-code-0x84b40000-when-trying-to-install-sql-server-mgmt-studio-to-an-existing-sql?forum=sqlexpress
    2. Eror code 0x851A001A
    Can any one plz help as i always get one or the other error.
    ====================================
    Screen shot: 
    Please note the below screen shot has given the error code 0x851A001A which is same in case of failure of all the other features which have failed during this installation. Hence i have uploaded only one screen shot.
    2. Log file content.
    =================================
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893606
      Start time:                    2014-05-04 21:15:35
      End time:                      2014-05-04 21:51:45
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  SERVER1
      Machine processor count:       2
      OS version:                    Windows Server 2008 R2
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Database Engine Services                 1033      
              Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            SQL Server Replication                   1033      
              Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                
    Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Data Quality Services                    1033    
                Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSAS11.MSSQLSERVER             Analysis Services                        1033  
                  Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012      MSSQLSERVER          MSRS11.MSSQLSERVER             Reporting Services - Native              1033        
            Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Management Tools - Basic  
                  1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Management Tools - Complete  
               1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools Connectivity  
                 1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools Backwards Compatibility
        1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Client Tools SDK      
                      1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Integration Services    
                    1033                 Enterprise Edition   11.0.2100.60    No        
      SQL Server 2012                                                          Reporting Services - SharePoint
                                                       11.0.2100.60    No        
    Package properties:
      Description:                   Microsoft SQL Server 2012 Service Pack 1
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      SPLevel:                       0
      Installation location:         F:\x64\setup\
      Installation edition:          Enterprise
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 ms\sql
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                true
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SCOM
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SCOM
      INSTANCENAME:                  SCOM
      ISSVCACCOUNT:                  NT AUTHORITY\Network Service
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              DefaultSharePointMode
      RSSVCACCOUNT:                  NT Service\ReportServer$SCOM
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 ms\sql
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           MS\Gautam, MS\SCOM Users
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
    Detailed results:
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A001A
      Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\SystemConfigurationCheck_Report.htm

    Sorry about the error in the path, but you find the files that's the main thing.
    Indeed it is a certificate problem:
    2014-05-04 21:47:43.56 spid12s Error: 17190, Severity: 16, State: 1.
    2014-05-04 21:47:43.56 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-05-04 21:47:43.56 spid12s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
    2014-05-04 21:47:43.57 spid12s Error: 17826, Severity: 18, State: 3.
    2014-05-04 21:47:43.57 spid12s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-05-04 21:47:43.57 spid12s Error: 17120, Severity: 16, State: 1.
    2014-05-04 21:47:43.57 spid12s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    I've recall that I've tried to help people with this error before, but I'm sure they were able to sort it out.
    Anyway, this blog post,
    http://blogs.msdn.com/b/sqljourney/archive/2012/10/09/sql-2008-service-fails-to-come-online-with-a-valid-certificate-could-not-be-found-and-it-is-not-possible-to-create-a-self-signed-certificate.aspx
    suggests the issue is a corrupted user profile, and you should try to use a different service account.
    This blog also seems to have a simple solution, but I cannot vouch for that it will work:
    http://www.beejblog.com/2012/02/sql-server-solved-unable-to-initialize.html
    Erland Sommarskog, SQL Server MVP, [email protected]

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

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

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

  • Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager

    Will the reports developed in sql server 2008 r2 BIDS work when deployed on sql server 2012 reporting manager?
    when I check on Microsoft site it says
    Reports are not upgraded when you upload a report definition file directly to the report server
    or SharePoint site. Upgrading a report definition in SQL Server Data Tools is the only way to upgrade the .rdl file.
    When you open an .rdl file in Report Designer in SQL Server Data Tools (SSDT), if the report was
    created for a previous namespace, Report Designer automatically creates a backup file and upgrades the report to the current namespace.
    This is the only way you can upgrade a report definition file.
    Now here is another confusing statement which says
    You can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server
    2012 report server and it is automatically upgraded on first use. The report server stores the report definition file in the original format. The report is automatically upgraded the first time it is viewed, but the stored report definition file remains
    unchanged.
    All I want to know is if I deploy a rdl made in 2008 r2 to 2012 will it work on the report manager of
    2012?
    <o:p>
    </o:p>
    Mudassar

    I have tested this fucntionality and can confirm that ssrs 2008 r2 reports work when you deploy them on new ssrs 2012 report manager .
    No Migration is required .
    I didnt even moved report server dbs .All I did is just deployed reports on the report manager and it worked .
    "You
    can upload an .rdl file created in an earlier version of Reporting Services to a SQL Server 2012 report server and it is automatically upgraded on first use. "
    Microsoft needs to correct this the documentation is misleading
    Mudassar

  • Resource Breaks When Upgrade from SQL Server 2000 to 2005 - Help!

    I have a resource that connects to mutiple databases:
    <ResourceAttribute name='Databases' displayName='com.waveset.adapter.RAMessages:RESATTR_DATABASES'
    description='com.waveset.adapter.RAMessages:RESATTR_DATABASES_HELP' multi='true'>
    <value>dbOne</value>
    <value>dbTwo</value>
    <value>Employee_Info</value>
    </ResourceAttribute>
    It all works fine when the backend SQL server is 2000, but since we've upgraded it to 2005, the connection fails with this error:
    Test connection failed for resource(s):MenuSQL: Required database dbOne not found.MenuSQL: Required database dbTwo not found.MenuSQL: Required database Employee_Info not found.
    I'm using the MS SQL JDBC driver for 2005 and I've verified that my connection url is good:jdbc:sqlserver://%h:%p;databaseName=%d;integratedSecurity=true; where %h and %p are the correct host and ports.
    I turned on tracing of com.waveset.adapter.MSSQLServerResourceAdapter and com.waveset.adapter.JdbcResourceAdapter and I don't see any errors or issues reported.
    If I set it back to connect to the SQL 2000 databases, it works. If I change it to only connect to one database, rather than 3 it works. However, I need this working on 2005 with all three databases. Any ideas on what I can look at or how I can further troubleshoot this?
    Thanks in advance for any help!

    Turns out the driver I'm using is fine (sqljdbc.jar). The problem is that the IdM source code executes "sp_databases" to list the databases. In SQL versions prior to 2005 this would work by default. But with 2005 a user has to be granted permissions to do so.
    To fix it you need to either grant the IdM ID you're using VIEW DEFINITION permission at an appropriate scope: object level, database level or server level or modify the stored procedure so that it executes under the credentials of the owner.
    Here's some info: http://msdn.microsoft.com/en-us/library/ms187113.aspx

  • 3._What components do you install when you install SQL Server?

    3. What components do we  install when  we  install SQL Server?

    http://msdn.microsoft.com/en-us/library/ms144275.aspx
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • Cant create connection Pool for MS SQL Server 2000 with Microsoft Driver

    i am using bea weblogic server 6.1, i cant create connection pool while using MS
    SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft website. when
    i give the following class name for JDBC driver and the connection url and click
    apply while selecting the available server, a number of exception appears in default
    server (that is the connection pool cannot be created..... cannot load the driver
    class).
    URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
    Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
    when i use the above setting in a JDBC simple application in Jbuilder
    7.0 the application runs successfully and fetches the data deom MS SQL database
    but in at Bea connection Pool is not created with these settings. i do give appropriate
    username and password in properties field in connection pool. Thankx for any help!

    khabbab wrote:
    That was the original code part from "startweblogic" :
    :runWebLogic
    echo on
    set PATH=.\bin;%PATH%
    set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;
    echo off
    and i changed it to :
    :runWebLogic
    echo on
    set PATH=.\bin;%PATH%
    set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;D:\Program Files\Microsoft
    SQL Server 2000 Driver for JDBC\lib\msbase.jar;D:\Program Files\Microsoft SQL
    Server 2000 Driver for JDBC\lib\msutil.jar;D:\Program Files\Microsoft SQL Server
    2000 Driver for JDBC\lib\mssqlserver.jar;I suggest moving or copying the three ms driver jars to a directory that has no blanks
    in it so the classpath doesn't have blanks in it. Ie:
    go to the "D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib"
    directory and do this:
    mkdir D:\microsoft_jdbc_driver
    cp *.jar D:\microsoft_jdbc_driver
    Then make the classpath include D:\microsoft_jdbc_driver\msbase.jar etc.
    Joe
    >
    >
    echo off
    when i save and run the bat file, server appears then disappears.
    Joseph Weinstein <[email protected]_this> wrote:
    khabbab wrote:
    The class path which is echoed at server startup does not include thepaths to
    driver jar files. when i edited the "startweblogic.bat" file and includedthe
    driver class paths to jar files, now the server doesnot even run. tellme what
    to do now???Show me what change you made to the startweblogic file.
    Joe
    Joseph Weinstein <[email protected]_this> wrote:
    khabbab wrote:
    kindly tell me how can i check that the class paths for driver jarfiles are included
    in that string? thanks. also tell me can not i use the jdriver forsql server
    2000?.The startup script will echo what it's doing, including printing out
    the classpath
    it will use. Yes you can use the jDriver for MS SQL2000. It is sufficient
    for
    basic JDBC, but the MS drivfer is preferable in some ways.
    Joe
    Joseph Weinstein <[email protected]_this> wrote:
    khabbab wrote:
    i am using bea weblogic server 6.1, i cant create connection
    pool
    while
    using MS
    SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft
    website.
    when
    i give the following class name for JDBC driver and the connectionurl and click
    apply while selecting the available server, a number of exception
    appears
    in default
    server (that is the connection pool cannot be created..... cannot
    load
    the driver
    class).The server startup script creates a string that will become the
    classpath
    for the server.
    This string is part of the java call to start the server with a-classpath
    argument. You need to
    make sure the MS driver jars are part of that classpath string.
    Joe
    URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
    Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
    when i use the above setting in a JDBC simple applicationin Jbuilder
    7.0 the application runs successfully and fetches the data deom
    MS
    SQL database
    but in at Bea connection Pool is not created with these settings.
    i
    do give appropriate
    username and password in properties field in connection pool.
    Thankx
    for any help!
    khabbab wrote:
    The class path which is echoed at server startup does not include thepaths to
    driver jar files. when i edited the "startweblogic.bat" file and includedthe
    driver class paths to jar files, now the server doesnot even run. tellme what
    to do now???
    Joseph Weinstein <[email protected]_this> wrote:
    khabbab wrote:
    kindly tell me how can i check that the class paths for driver jarfiles are included
    in that string? thanks. also tell me can not i use the jdriver forsql server
    2000?.The startup script will echo what it's doing, including printing out
    the classpath
    it will use. Yes you can use the jDriver for MS SQL2000. It is sufficient
    for
    basic JDBC, but the MS drivfer is preferable in some ways.
    Joe
    Joseph Weinstein <[email protected]_this> wrote:
    khabbab wrote:
    i am using bea weblogic server 6.1, i cant create connection
    pool
    while
    using MS
    SQL Server 2000. i have installed JDBC Driver SAP1 from microsoft
    website.
    when
    i give the following class name for JDBC driver and the connectionurl and click
    apply while selecting the available server, a number of exception
    appears
    in default
    server (that is the connection pool cannot be created..... cannot
    load
    the driver
    class).The server startup script creates a string that will become the
    classpath
    for the server.
    This string is part of the java call to start the server with a-classpath
    argument. You need to
    make sure the MS driver jars are part of that classpath string.
    Joe
    URL= jdbc:Microsoft:sqlserver://127.0.0.1:1433;DatabaseName=MyDB
    Driver= com.microsoft.jdbc.sqlserver.SQLServerDriver
    when i use the above setting in a JDBC simple applicationin Jbuilder
    7.0 the application runs successfully and fetches the data deom
    MS
    SQL database
    but in at Bea connection Pool is not created with these settings.
    i
    do give appropriate
    username and password in properties field in connection pool.
    Thankx
    for any help!

  • Error when upgrading from SQL Server 2005 to SQL Server 2014

    Hello everyone,
    Could you help me, i have an error when i try to upgrade my SQL Server 2005 Enterprise Edition to SQL Server 2014 Enterprise Edition,
    All of prerequisits are available and i dont have a problem,
    before the end of migration process, i have this error: The group name could not be found (0x84BB0001)
    File log:
    Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
    command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x84BB0001
      Error description:             The group name could not be found.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
    command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x84BB0001
      Error description:             The group name could not be found.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
    command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x84BB0001
      Error description:             The group name could not be found.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
    Best regards,
    Guiga Hafedh

    There are more detailed logs for the various components. The one of interesting is the one for the engine or possibly the one for full-text.
    These logs are extremely verbose, and the errors are rarely crystal clear, but at least give them a try. If you have problems, find a place to upload them (Dropbox, Skrydrive etc), so that we can look.
    The closest at hand is that "group" that cannot be found is an AD group.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Error when DBLOGIN into SQL Server

    Hi,
    I'm using Oracle GoldenGate for SQL Server. I successfully created a DNS ODBC connection to SQL Server and named it as HRSQLSRV.
    When I tried to use DBLOGIN command in gg, I got the following:
    E:\ggs>GGSCI
    Oracle GoldenGate Command Interpreter for SQL Server
    Version 11.2.1.0.1 OGGCORE_11.2.1.0.1_PLATFORMS_120423.0230
    Windows (optimized), Microsoft SQL Server on Apr 23 2012 06:55:51
    Copyright (C) 1995, 2012, Oracle and/or its affiliates. All rights reserved.
    GGSCI (server5) 1> dblogin sourcedb HRSQLSRV
    Source Context :
      SourceModule            : [ggdb.mssql.util]
      SourceID                : [../gglib/ggdbmssql/mssqlutil.c]
      SourceFunction          : [MSSQLCollation::getProperties]
      SourceLine              : [1818]
    2012-08-29 11:28:28  ERROR   OGG-00868  Fetching error for select operation Data
    base error 0 ([Microsoft][SQL Server Native Client 10.0]Invalid cursor state
    2012-08-29 11:28:28  ERROR   OGG-01668  PROCESS ABENDING.
    E:\ggs>The database is SQL Server 2008 R2 in Windows 2003 32-bit.
    Thanks in advance.

    Finally, I got the solution:
    Control Panel ->Regional and Language Options-> Advanced-> Language for non-Unicode programs-> from the drop list of languages, I selected the English (United States)-> Reboot the box
    I also removed any Keyboard added to Windows other than the US English one.

  • I Cant connect to Localhost after installing sql Server 2012 r2 Sp2

    Hi,
    I can't connect to localhost after installing ssms. Also, I can't find SQL on Services. Do you have any ideal? Thanks!

    where can i download the database engine component?
    You can download Express or Evaluation edition which are free to download. here is the download link for SQL 2012
    Microsoft® SQL Server® 2012 Express
    http://www.microsoft.com/en-us/download/details.aspx?id=29062
    Microsoft® SQL Server® 2012 Evaluation
    http://www.microsoft.com/en-us/download/details.aspx?id=29066
    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

  • SSIS fails to load files from network when executed via SQL server Agent (SQL server 2008 R2 SP 2)

    Hi All,
    I have a simple SSIS package that reads a flat file and copies it into a SQL Server table.
    When the flat fiel is on the C drive I have no problem runnign this package from SQL Server Agent, but as soon as I update the path to a network location the package only works when I run it manually, but fails when is executed via the SQL Server agent job.
    The error says "cannot open the datafile", while the datafile location is valid.
    Is this a kind of limitation of a SQL Server Agent that only local files are allowed to be processed?
    Thanks,
    Andrei
    SSIS question

    Hi All,
    Thanks for your responses.
    I configured the SQL agent service to use my domain account with which I have no porblems accessing the folder. However the issue persisted.
    Thanks,
    Andrei
    SSIS question

  • ODBC Error when migrating from SQL Server 2008 to SQL Anywhere 12

    Hello community,
    i have the following requirement:
    I need to migrate a Database with some Demo data into a SQL Anywhere 12 Database. The SQL Anywhere 12 Database is part of the SAP BusinessObjects Enterprise XI 3.1 SP7 installation and came with the same as OEM Product.
    The Environment looks like the following:
    DB1 is a MS SQL Server 2008 R2 64 Bit running on Windows Server 2008 R2 64 Bit.
    DB2 is the SAP BusinessObjects Enterprise XI 3.1 SP7 installation with the shipped SQL Anywhere 12 (12.0.1.3873) Database running on SLES 11.3 64 Bit
    CL1 is my Windows 7 64 Bit Client where Sybase Central is installed in 64 Bit. On CL1 i have a 64 Bit System ODBC Connection connecting to DB1 successfully.
    Basically i followed the following (pretty straight forward) tutorial:
    Migrating a SQL Server Database to SQL Anywhere White Paper-Technical: Mobile Enterprise, Database Management iAnywhere …
    When i want to test the connection from inside Sybase Central (During the migration process) i receive the following error:
    From inside Sybase Central my connection looks as follows:
    And from the ODBC Manager the connection looks as follows:
    Personally i found is strange that the Sybase ODBC Driver Manager drops the error. I would expect that the MS SQL ODBC Driver Manager pops the error it its related to the ODBC DSN to DB1.
    Any ideas?
    Thanks and Regards
    -Seb.

    Hi Sebastian,
    The data from the SQL Server database must be migrated to an existing SQL Anywhere database.  Could you please tell me where this SQL Anywhere database resides and how are you connecting to it?
    The error message is saying that the connection to the SQL Anywhere remote database server is failing, as opposed to the connection to the SQL Server database.

  • $$$$ License Exception when connecting to SQL Server for Weblogic 7.0

    Hi,
    I downloaded Weblogic 7.0, and installed and uninstalled a few times,
    When I tried to connect SQL Server 2000 using the samples in ..\examples\jdbc\mssqlserver4,
    I got the error:
    Exception was thrown: java.sql.SQLException: $$$$$$$$$$$$$$$$ License Exception
    $$$$$$$$$$$$$$$$
    jDriver/MSSQLServer4: license signature validation error!
    $$$$$$$$$$$$$$$$ License Exception $$$$$$$$$$$$$$$$
    I checked the classpath, c:\bea is in there!!
    Is any problem for installing and uninstalling a few times on the same computer?
    Thanks a lot!!
    JH

    Hi,
    As mentioned in the following configuration article, for earlier versions of SQL Server where MARS was not an option, the way to configure is to have server-side cursors configured.
    (check out the tabulated column next to MARS_Connection for details)
    http://www.easysoft.com/products/data_access/odbc-sql-server-driver/manual/configuration.html
    To use server-side queries in the connection URL, pls go through this link
    http://www.oracle.com/technology/products/jdev/howtos/bc4j/bc_psqlserverwalkthrough.html
    But please note that server-side cursors does have a performance overhead.
    Let me know if you need more information.
    HTH,
    Lakshmi.

  • ODBC Slow resonse time when connecting to SQL SERVER on Azure VM

    Hello,
    I have extra small AZURE VM with SQL Server Express 2008.
    I managed to connect to the SQL Server by ODBC connection (from access).
    The problem is that the response time is very slow and it is not usable.
    How can I improve the response time?
    If I will use bigger VM or use AZURE SQL SERVER (instead of installing SQL SERVER on VM)
    will the response time be better?
    Thank you for your help

    Hello,
    In addition to resoure of the windows Azure VM, the network and the query may also result to the slow response. When create a Windows Azure SQL Database, it also share resources with other services.
    You can refer to the following blog about manage connections in Windows Azure SQL Database:
    http://social.technet.microsoft.com/wiki/contents/articles/1541.windows-azure-sql-database-connection-management.aspx#GeneralBestPractices
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

Maybe you are looking for