Trouble Turneing on FileStream/Ad Hoc Query with new SQL Server 2014 64-BIt Version

SQL Server Help,
I have recently installed SQL SERVER 2014 on my Window 7 SP1 Acer laptop.
I am trying to do a simple upload of an Excel file into SQL Server using the OPENROWSET command:
Which I found requires some configuration change I attempted below.
When I execute this:
execute sp_configure 'show advanced options', 1;
RECONFIGURE;
execute sp_configure 'Ad Hoc Distributed Queries', 1;
RECONFIGURE;
GO
I get this message
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 5593, Level 16, State 1, Line 2
FILESTREAM feature is not supported on WoW64. The feature is disabled.
Msg 15123, Level 16, State 1, Procedure sp_configure, Line 62
The configuration option 'Ad Hoc Distributed Queries' does not exist, or it may be an advanced option.
Msg 5593, Level 16, State 1, Line 4
FILESTREAM feature is not supported on WoW64. The feature is disabled.
When I go to the SQL Server Services and Properties on the Server and try to change the FileStream options to be on..I get the error:
"There was an unknown error applying the FILESTREAM settings.  Check the parameters are valid (0x80070002)."
Perhaps my issue is with the Windows Share Name:  .  I have put in a local driver C:\A_Excel....also the computer name, my user ID.   Is there a special format or way to define a Share Name that I am unaware of?
Is there a way to fix this?  Can I not load Excel files with a 64-Bit system?  Or what is the easiest way that I can do this with my configuration?
Thanks for any help.

FILESTREAM feature is not supported on WoW64. The feature is disabled.
By the error message it seems you have a 64 bit OS, but have installed a 32 bit SQL Server and here in WoW64 mode filestream seems to be not supported. Install a 64 bit SQL Server instead.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Similar Messages

  • Licensing question for AD enterprise with new SQL Server

    Hi!
    We have Server 2008 R2 STD where our AD is located and it has enough User CAL's. Additionally we have Terminal server with TS licenses.
    Now we're purchasing a Server 2012 where we plan to install SQL Server 2012 STD where we will install our third party program and this program is going to be used through Terminal server. 
    Now the question is do I only need SQL CAL's or will I have to get both SQL CAL's AND User CAL's for the new server? I'm thinking AD servers User CAL's is enough for the whole enterprise, but I'm not 100% sure and need help with this!
    Thanks!

    Licensing questions should be directed to trained Microsoft licensing specialists instead of a technical forum. 
    www.microsoft.com/licensing. 
    That said, SQL CALs and operating system CALs are sold separately.  Talk with the vendor from whom you are purchasing your licenses.  They should be able to help you sort out the CAL questions.
    . : | : . : | : . tim

  • Issue with applying SQL Server 2014 CU6

    Anyone had an issue like this when applying CU6... I have a single server/single instance 2014 installation running SQL SRVR, SSAS, SSRS, SSIS...
    SSAS, SSRS, and SSIS all upgraded to 12.0.2480.0, but SQL Server did not.  The summary file has the generic failure message below:
    Instance MSSQLSERVER overall summary:
      Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
      Exit code (Decimal):           -2061893565
      Start time:                    2015-03-13 10:56:18
      End time:                      2015-03-13 10:59:59
      Requested action:              Patch
    After reboot everything came up fine, but now I am left wondering how to troubleshoot this.  The detail log is huge and doesn't show a clear indication of what the issue might be.  Anyone have any guidance on troubleshooting?  I have searched
    the web and found some results for earlier versions... but nothing terribly helpful.

    To close this out, I'd like to note that I finally was able to get to a meaningful error message:
    "The User Data directory in the registry is not valid. Verify DefaultData key under the instance hive points to a valid directory. Error code: 0x851A0043"
    The error resulted from an earlier relocation of the default data location.  A registry entry for DefaultData in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQLServer was incorrectly pointing to an obsolete drive
    letter.  Correcting the drive letter was all that was needed.  I am now successfully at version 12.0.2480.0.

  • SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

    We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.)  Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
    anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
    specifically listed as a SQL DB user tries to use the front end they get an error of:
    Microsoft SQL Server Login
    Connection failed:
    SQL State: '28000'
    SQL Server Error: 18456
    [Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
    After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
    to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
    Thanks a billion in advance ----

    Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
    all other roles, as well as allowing select only, and still have no access for the guest account.
    The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
    and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
    thru MS Access ACCDB, using a (by default) read only OCDB connection.
    This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
    levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
    since the result set would involve hundreds of thousands if not millions of records.
    So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
    as well as running our network on Microsoft's network software.

  • Query Analysis Services DMV (DISCOVER_LOCKS) with OPENQUERY SQL Server 2012

    Hi, I'm having trouble with a specific DMV, $SYSTEM.DISCOVER_LOCKS, while querying it using T-SQL OPENQUERY.
    For example, this query will run just fine:
    select * from openquery(OLAP_SERVER, 'SELECT * FROM $SYSTEM.DISCOVER_CONNECTIONS')
    But when I try:
    select * from openquery(OLAP_SERVER, 'SELECT * FROM $SYSTEM.DISCOVER_LOCKS')
    I get the following error:
    OLE DB provider "MSOLAP" for linked server "OLAP_SERVER" returned message "Internal error: An unexpected error occurred in conversion.".
    OLE DB provider "MSOLAP" for linked server "OLAP_SERVER" returned message "An error occurred while parsing the 'C5' element at line , column ('urn:schemas-microsoft-com:xml-analysis:rowset' namespace) under Envelope/Body/ExecuteResponse/return/root/row/(any).".
    Msg 7320, Level 16, State 2, Line 3
    Cannot execute the query "SELECT * FROM $SYSTEM.DISCOVER_LOCKS" against OLE DB provider "MSOLAP" for linked server "OLAP_SERVER".
    Similar problems [*] were present on SQL Server 2008, but the author obviously managed to execute queries to all DMV-s. Could the linked server properties play a role in this?
    [*] I am not able to post links or images at the moment until my account is verified, but I was referring to an article by Vidas Matelis, "SSAS 2008 DMVs – querying from the
    SQL Server and database diagrams"

    Hi Frodik,
    Generally, the reason for the error “Cannot execute the query "XX" against OLE DB provider "XX" for linked server "XX"” can be lack of sufficient memory on server. Also possibly running into an SSAS issue which could
    be bringing lots of data into cache. So in your scenario, if you server is X86 server, you can migrate it to X64 server which should help. If you server is X64 server, you can avoid this issue by increasing available memory.
    Hope this helps.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Problem using DG4ODBC with named SQL Server instance

    I am running DG4ODBC on a 64 bit LINUX machine with the Microsoft SQL Server driver installed. I have successfully tested this with a SQL Server instance that was not named (GENERALI_DSN).The named instance gives the following when trying to query:
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [unixODBC][Microsoft][SQL Server Native Client 11.0]Login timeout expired {HYT00}[unixODBC][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].  {08001,NativeErr = -1}[unixODBC][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. {08001,NativeErr = -1}
    ORA-02063: preceding 2 lines from DEVMISC
    odbc.ini
    [GENERALI_DSN]
    Driver                  = SQL Server Native Client 11.0
    Server                  = CLTDMJCWBYZ.eu.scor.local
    User                    = everest
    Password                = everest
    Database                = Everest_Generali
    [DEVMISC_DSN]
    Driver                  = SQL Server Native Client 11.0
    Server                  = [USVCLTDEVSQL02\DEVMISC]
    User                    = link_user
    Password                = password1
    Database                = DBA
    initDG4ODBC2.ora
    # HS init parameters
    HS_FDS_CONNECT_INFO = DEVMISC_DSN
    HS_FDS_TRACE_LEVEL = DEBUG
    HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
    # ODBC specific environment variables
    set ODBCINI=/home/oracle/.odbc.ini
    listener.ora
    SID_LIST_LISTENER_GW =
       (SID_LIST =
          (SID_DESC =
           (SID_NAME=DG4ODBC)
          (ORACLE_HOME=/home/oracle/product/11.2.0)
          (ENV=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micro
    soft/sqlncli/lib)
          (PROGRAM=dg4odbc)
          (SID_DESC =
           (SID_NAME=DG4ODBC2)
          (ORACLE_HOME=/home/oracle/product/11.2.0)
          (ENVS=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micr
    osoft/sqlncli/lib)
          (PROGRAM=dg4odbc)
    LISTENER_GW =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = usvcltprdoragw)(PORT = 1521))
    tnsnames.ora
    DG4ODBC =
       (DESCRIPTION=
          (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
          (CONNECT_DATA=(SID=DG4ODBC))
          (HS=OK)
    DG4ODBC2 =
       (DESCRIPTION=
          (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
          (CONNECT_DATA=(SID=DG4ODBC2))
          (HS=OK)
    I can't figure out why the named instance does not work but the other one does. Any help would be greatly appreciated!

    Did you check with the ODBC test utility isql (it is installed by default when you install the unixODBC Driver manager) if your ODBC driver can connect at all to that named instance? I have some doubts that it will work either as there was a blog commented by a MS engineer:
    Introducing the new Microsoft ODBC Drivers for SQL Server - Microsoft SQLNCli team blog - Site Home - MSDN Blogs
    who states that named instance connections are not supported using that driver.
    - Klaus

  • SQL Server 2014 with AGs - Over 6 million DONE tasks in dm_os_tasks

    Hello,
    We've noticed that our SQL Server deployment has a very high number of tasks in the done state.  On our 5 node cluster we have values in the millions on most servers (depending on last restart time), with our highest server returning over 6 million
    for the following query:
    select count(*)
    from sys.dm_os_tasks
    where task_state = 'done'
    We also track the count daily, and we have never seen the number of tasks decrease.  The average growth per day is 50,000.  The servers are all running SQL Server 2014 Enterprise Edition CU2 (build 12.0.2370).  The servers host between 4 and 8
    availability groups each, with 1 to 3 databases per AG.
    We're a little concerned that this behaviour is very reminiscent of that noted in the Memory Leak in 2012 KB 2877100), and wondered if anyone else is having a similar experience with 2014 AGs?
    We did open a product support case for a separate issue where we mentioned this, but were told that until we could provide a memory dump of a crashing instance we wouldn't be able to investigate if this was actually a leak.
    Any advice or discussion that suggests this behaviour is actually 'worked as intended' would be appreciated.
    Kind Regards,
    Tim

    Hi Tim,
    This does indeed look quite reminiscent of 2877100 and this behavior does certainly seem abnormal, particularly if you can establish memory consumption growth over time. I'd recommend providing MSFT additional statistics regarding memory usage via DMVs and
    perfmon if you haven't already.
    Product support is still definitely the recommended route - and you might try escalating or asking for another engineer.  I understand why they are asking for this information, but perhaps ask if they can provide less invasive methods for root cause
    analysis.  If the answer is still "no" - hopefully you have a prod-like environment where you can reproduce this?  And if so, then the memory dump is less of a risk in non-prod.
    Best Regards, Joe Sack, MVP, SQL MCM | SackHQ.com

  • What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?

    What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?
    Are these the same as software product keys, or just some pieces of paper the company needs to have on hand?
    In which case, when we install SQL Server 2014, (and when looked for videos) - there is only 1 product key value to be put in, is there some other screen in the setup to input the License bought ( in our case will be Core licenses).
    So in addition to the Core Licenses do will a Product key be needed? Would product key from an msdn work, as it is the licenses that we will buy to indicate that we bought to run the software on server X?
    Thanks for any indications.

    1. What will I do with the SQL Server (2012/2014) (Standard/Enterprise) Licenses?
    Are these the same as software product keys, or just some pieces of paper the company needs to have on hand?
    2. In which case, when we install SQL Server 2014, (and when looked for videos) - there is only 1 product key value to be put in, is there some other screen in the setup to input the License bought ( in our case will be Core licenses).
    3. So in addition to the Core Licenses do will a Product key be needed? Would product key from an msdn work, as it is the licenses that we will buy to indicate that we bought to run the software on server X?
    Thanks for any indications.
    I will answer your question point wise
    1. Keeping license key is good idea it helps you during audit and you have proof that you are using a valid Microsoft License. Plus in scenario of disaster where whole box gets damanged you might need to install SQL Server again in that case during
    reinstallation on setup page where you need to enter key you might need need it. If you are missing your paper then you are in trouble.
    2. Only on product key page license key is required and it is not required anywhere else during installation. Unless you enter valid product key installation will not proceed further.
    3 License makes you a valid owner of Microsoft product with restrictions on how much hardware resource you can use how much max connections you can make etc. Key lets you install it on Windows machine making sure that you are using valid Microsoft product.
    This was just a general idea please speak to your licensing specialist for more details. This is technical forum and we generally ask user to speak to licensing expert for such queries.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • How to get JDev 10.1.2/ADF working with MS SQL Server Identity Column

    Hello JDevTeam & JDevelopers,
    I want to use JDev/ADF with a MS SQL Server 2005 database that contains tables employing IDENTITY Columns.
    Using JDev/ADF and DBSequence with an Oracle database employing before triggers/sequences accomplishes what I am trying to do except I want to accomplish the same thing using a MSSQL Server 2005 database. Unfortunately I cannot change the database.
    I have been able to select records but I am unable to insert records (due to my lack of knowledge) when using MS/SQL Server Identity Columns with JDev/ADF.
    The following are the steps taken thus far.
    Step1: Create table named test in the 2005 MSSQL Server (see script below).
    Step2: Register 3rd Party JDBC Driver with JDeveloper; Using use Tools/Manage Libraries. Create a new entry in User Libraries with the following;
         Library Name     = Ms2005Jdbc
         Class Path     = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu\sqljdbc.jar
         (note: Latest TYPE 4 JDBC driver for Microsoft SQL Server 2005 - free at http://msdn.microsoft.com/data/ref/jdbc/)
    Step3:Create New Database Connection;
         Connection Name = testconn1
         Type = Third Party JDBC Driver
         Authentication Username = sa, Password = password, Check Deploy Password
         Connection
              Driver Class = com.microsoft.sqlserver.jdbc.SQLServerDriver     
              Library = Ms2005Jdbc     
              Classpath = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu
              URL = jdbc:sqlserver://192.168.1.151:1433;instanceName=sqlexpress;databaseName=test
         Test Connection = Success!
    Step5: Create a new application workspace using Web Application default template
    Step6: In Model project, Create new Business Components Diagram.
    Step7: Create new Entity Object. Goto to connections/testconn1, open tables and drag table test onto the diagram.
    Step8: Generate Default Data Model Components by right-clicking on Entity Object. Except all the defaults.
    When I test the Appmodule I select the view object and can scroll through all the records without error. If I try to insert a record, I get JBO-27014: Attribute testid in test is required.
    Going back to the EntityObject I deselect the Mandatory attribute and re-run the test. Now when I try to insert it accepts the value for testname but it does not update the PK testid like it would using an "JDev/ADF/DBSequence/Oracle database/before trigger/sequence" solution.
    Going back to the EntityObject and selecting refresh on insert does not solve this problem either. Changing the URL connection string and adding "SelectMethod=cursor" did not help and changing the SQl Flavor to SQLServer produced errors in the Business Components Browser. I've tried overriding isAttributeChanged() and other things as well.
    I am totally stuck! Can anyone provide a solution?
    Thanks for you help,
    BG...
    Create table named test
    use [testdb]
    go
    set ansi_nulls on
    go
    set quoted_identifier on
    go
    create table [test](
         [testid] [int] identity(0,1) not null,
         [testname] [nvarchar](50) collate sql_latin1_general_cp1_ci_as not null,
    constraint [pk_test] primary key nonclustered
         [testid] asc
    )with (pad_index = off, ignore_dup_key = off) on [primary]
    ) on [primary]

    Figured it out!
    When using the MS SQL Server 2000 Database with the MS JDBC 2000 Driver you specify the SQL Flavor to SQLServer. However setting the SQL Flavor to SQLServer with MS SQL Server 2005 Database and the MS JDBC 2005 Driver will *** fail ***.
    When working with the MS SQL Server 2005 Database and the MS JDBC 2005 Driver you set the SQL Flavor to SQL92 and the Type Map to Java.
    If using a named instance like I am you would specify the URL = jdbc:sqlserver://<db host ip address>:<listening port>;instanceName=<your instance name>;selectMethod=cursor;databaseName=<your database name> (note: leave out the < >)
    The 2005 Driver Class is different then the 2000 and is specified as com.microsoft.sqlserver.jdbc.SQLServerDriver
    Note: In a default MS SQL Server 2005 installation the listening port will change *** everytime *** the host is restarted! You can override this though.
    For the primary key you need to deselect the Mandatory attribute in the EntityObject editor.
    Set Refresh on insert/update = no.
    Set Updateable = never.
    Now my Primary Keys which get their values from the Identity Column are working with ADF in a predictable way.
    Simple enough but I have been away from this stuff for awhile.
    BG...

  • Sharepoint Foundation 2010 compatibility with SQL Server 2014

    Due to a requirement to use Sharepoint without Active Directory access.  I am trying to find explicit confirmation whether Sharepoint Foundation 2010 is compatible with SQL Server 2014.  I have seen that Sharepoint Server 2010 and 2013 are compatible
    with SQL Server 2014 as of CU 1 (released in April).  But there is no mention of Sharepoint Foundation.
    This chart is great except it doesn't mention whether the Foundation versions are supported.
    http://msdn.microsoft.com/en-us/library/gg492257.aspx
    Thanks.

    Note that that is for the Reporting Services component, but not necessarily for the SQL Database Engine component (which comes from the SharePoint Product Group, rather than the SQL Product Group). I haven't seen any confirmation that SharePoint 2010 is
    supported at all with SQL 2014 as a Database Engine.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Sql server 2005 reports with sql server 2014

    Can i upload SSRS 2005 reports as it is on SSRS 2014 and use it without doing anything extra or without changing anything ??
    I can use SSRS 2005 reports as it is with SSRS 2012. But for SSRS 2014 not sure.
    h2007

    You can upgrade the the RDL schema will be upgraded.
    Report definition (.rdl) files are automatically upgraded in the following ways:
    When you open a report in Report Designer in SQL Server Data Tools (SSDT), the report definition is upgraded to the currently supported RDL schema. When you specify a SQL Server 2008 or SQL Server 2008 R2 report server in the project properties, the report
    definition is saved in a schema that is compatible with the target server.
    When you upgrade a Reporting Services installation to a SQL Server 2014 Reporting Services (SSRS) installation, existing reports and snapshots that have been published to a report server are compiled and automatically upgraded to the new schema the first
    time they are processed. If a report cannot be automatically upgraded, the report is processed using the backward-compatibility mode. The report definition remains in the original schema.
    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.
    After a report is upgraded locally or on the report server, you might notice additional errors, warnings, and messages. This is the result of changes to the internal report object model and processing components, which cause messages to appear when underlying
    problems in the report are detected. For more information, see Reporting Services Backward Compatibility.
    For more information about new features for SQL Server 2014 Reporting Services (SSRS), see
    What's New (Reporting Services).
    Check the below Microsoft link for more information
    http://msdn.microsoft.com/en-us/library/ms143674.aspx
    Mudassar

  • Is it possible to Deploy a SSIS package to catalog with a Sql Server Identity in SQL Server 2012 programmly ?

    Hi,
    how can I deploy a SSIS package with a SQL SERVER identity to the catalog in SQL Server 2012 programmly?
    I tried to use the [SSISDB].[catalog].[deploy_project], but the error said that it could only be used with a WINDOWS identity.
    This question has worried me for days.
    Is there any way to make the catalog.deploy_project available for a SQL SERVER identity ?
    Or just an new solution instead of using the catalog.deploy_project?
    best wishes from Qingyuan Lee.

    Sorry, my description may be confusable.
    I use EXECUTE AS , not EXECUTE WITH, to solve the problem.
    In fact,  I don't care about the authority.
    I want to execute the stored procedure using a SQL SERVER Authentication Account , since my codes run on a linux OS and it is hard to connect to SSIS using a Windows Authentication Account.
    so, using EXECUTE AS to change the execution context is accaptable.
    The requirement for a Windows Authentication Account makes sense.
    I consider that the SSIS executes outside the context of SQL Server and as part of an OS process, which means that a Windows account is necessary in order to deploy a package.
    Thanks very much for your help.

  • SQL Server 2014 Express (32 bit) issues with Microsoft OLE DB Provider for Visual FoxPro

    Hello, I am trying to create a sample data warehouse and some reports etc to demonstrate SQL server and subsequent automation to a company I am working for.  I am trying to import data from the company's VFP based software into a new SQL Server database.
     (please note, this is not custom developed software, so i am unable to push the data from VPF)
    I keep getting errors and SQL server crashes when i try to access the Microsofl OLE DB Provider for Visual Fox Pro similar to this thread https://social.msdn.microsoft.com/Forums/en-US/88296548-553e-4402-93e3-6f26f5de343d/dtswizard-importexport-utility-error-trying-to-use-vfp-oledb-provider?forum=sqldataaccess
     however, the solution outlined in that thread will not work, as i cannot create an SSIS package in Express.
    I have also attempted to use the OLE DB in Excel as well to test it, and it crashes Excel the same way.  
    results of the following query Exec master.dbo.xp_msver
    Index Name
    Internal_Value Character_Value
    1 ProductName
    NULL Microsoft SQL Server
    2 ProductVersion
    786432 12.0.2000.8
    3 Language
    1033 English (United States)
    4 Platform
    NULL NT INTEL X86
    5 Comments
    NULL SQL
    6 CompanyName
    NULL Microsoft Corporation
    7 FileDescription
    NULL SQL Server Windows NT
    8 FileVersion
    NULL 2014.0120.2000.08 ((SQL14_RTM).140220-1752)
    9 InternalName
    NULL SQLSERVR
    10 LegalCopyright
    NULL Microsoft Corp. All rights reserved.
    11 LegalTrademarks
    NULL Microsoft SQL Server is a registered trademark of Microsoft Corporation.
    12 OriginalFilename
    NULL SQLSERVR.EXE
    13 PrivateBuild
    NULL NULL
    14 SpecialBuild
    131072008 NULL
    15 WindowsVersion
    131072008 6.1 (7601)
    16 ProcessorCount
    8 8
    17 ProcessorActiveMask
    255 000000ff
    18 ProcessorType
    586 PROCESSOR_INTEL_PENTIUM
    19 PhysicalMemory
    4055 4055 (4252094464)
    20 Product ID
    NULL NULL
    Any guidance is appreciated.  thanks!

    No, I attempted to use the Microsofl OLE DB Provider for Visual Fox Pro to access the .dbf from Excel,
    and it behaved identically to the way it did in SQL Server.
    I can use the Microsoft Excel Data source in SQL Server to link an excel file to SQL Server perfectly fine. 

  • Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

    Hello everyone.
    We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
    packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
    Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
    MCP

    Hi. Yes...
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="SQLISServer" /> 
      <EventID Qualifiers="0">1</EventID> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" /> 
      <EventRecordID>469950</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>abtru1a11.oneabbott.com</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
    exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
    runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
    Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
    Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
    behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
    at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data> 
      </EventData>
      </Event>
    MCP

  • Why can't I log into my "Local" sql server (sql server 2014) with my Sql Server Authentication UID ?

    I just got a new work station (win7 Pro) which has the following sql server
    SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
    returns
    12.0.2254.0     RTM     Developer Edition (64-bit)
    Select @@version
    returns
    Microsoft SQL Server 2014 - 12.0.2254.0 (X64)
     Jul 25 2014 18:52:51
     Copyright (c) Microsoft Corporation
     Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    I added/created a new (random) user account to this server [joe123] and made him sa and mapped him to everything, the password never expires, ...
    when I try to login to this local server the login fails, but I can log into this server with my windows integrated account (also sa).  What do I need to do so that the joe123 account can login to the server
    Rich P

    Check if both "SQL Server and Windows Authentication mode" is set (not just Windows Authentication mode). Server-->right click and select properties -->  Security
    Satish Kartan http://www.sqlfood.com/

Maybe you are looking for