Issue of Text Qualiffier after upgrading to SQL Server 2014 Standard

Hi,
I'm facing an issue of Text Qualifier after I upgrading my system to SQL Server 2014 Standard Edition (Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
    Feb 20 2014 20:04:26
    Copyright (c) Microsoft Corporation
    Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
I have a csv file with format: Text Qualifier is double pipes ||, Vertical Bar (|) as Column Delimiter and  Row Delimiter is CRLF.
For example file:
||Col1|||||Col2||
||ABC|||||XYZ||
This file is working OK in SQL Server 2008 R2 (SP2) but it does not work in SQL Server 2014. It raised error message while running.
Error: An error occurred while skipping data rows.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on MediaAgencyGroup returned error code 0xC0202091.  The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure
code is defined by the component, but the error is fatal and the pipeline stopped executing.  There may be error messages posted before this with more information about the failure.
Any suggestion here?
Thanks,

Yes
There's a difference in the way text qualifiers are parsed from 2012 onwards
see
http://www.proactivespeaks.com/2012/06/22/my-5-favorite-sql-2012-ssis-features-so-far/
http://blog.concentra.co.uk/2013/06/24/ssis-2012-flat-files-now-greatly-improved-but-are-they-good-enough-yet/
ANyways my preferred way to do this is as below
http://visakhm.blogspot.in/2014/06/ssis-tips-handling-embedded-text.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Similar Messages

  • 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

  • SSIS packages are failing after upgrade to SQL server 2014

    Hi,
    I have some SSIS packages running on SQL server 2012 .
    After I upgraded to SQL server to 2014 from 2012 , the SSIS jobs are failing on the SQL agent.
    And i can see its related to Data source connectivity to the SQL agent. I hope it not able to identify the connection manager in SQL agent. And connection adapter is not upgraded.
    I read some articles about this and they say it not able to connect to SQL server agent job.
    And, I can see that the package is running if i run manually using SQL 2012 run time.
    Why its not running on SQL 2014 ?
    did i  miss anything while upgrading SQL server 2014 ?
    Please give me some suggestions to solve this issue. 
    And is there any way i can change the SQL server agent 2014 to adapt this and run ?
    Below is the error : 
    The Package filed to load due to error 0XC00100014 " One or more error occurres. There should be more specific errors preceding this one that expalins the details of the erroes. This message is used as a return value from functions that encounter
    errors.: This occures when CPackage::LoadFormXML fails.
    Regards,
    Vinodh Selvaraj.

    I think you have typed this error message by yourself.
    Anyway, as it says there should be more error preceeding to this. Do you have any other errors which describles the exact issue stating at what task it fails?
    If not, then there are various reasons behind this issue. 3rd party connection manager such as Oracle Attunity or it may be 32/64 bit issue.
    You may try executing package in 32 bit mode from SQL Agent Job.
    Please refer:
    http://blogs.msdn.com/b/farukcelik/archive/2010/06/16/why-package-load-error-0xc0010014-in-cpackage-loadfromxml-error-appears-while-trying-to-run-an-ssis-package.aspx
    http://www.bidn.com/blogs/timmurphy/ssas/1397/package-failed-to-load-due-to-error-0xc0010014
    -Vaibhav Chaudhari

  • Issues enabling AlwaysON in SQL Server 2014 Standard

    Hi 
    I am trying to configure AlwaysOn and having issues enabling in SQL Server configuration manager
    OS : Windows Server 2012 R2
    SQL : SQL Server 2014 Standard Edition
    Here is what i see in config manager : 
    The AlwaysOn Availability Groups feature requires the x86(non-Wow) or x64 Enterprise Edition of SQL Server 2012 (or later version) running on Windows Server 2008 (or later version) with WSFC hotfix KB 2494036 installed. This SQL Server edition and/or Windows
    Server system do not meet one or more of these requirements.
    I patched both the nodes and ran the cluster validation as well which didn't report any missing patches. Couldn't find any documentation/solution for this. 
    Can someone please help me with this ???

    Thanks. 
    Is the configuration of Always on FCI is same as Traditional WSFC ?
    Yes just think of it as a regular clustered sql instance
     An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes
    and, possibly, across multiple subnets. 
    https://msdn.microsoft.com/en-us/library/ms189134(v=sql.110).aspx

  • Upgrating SQL Server 2008 R2 SP2 to SQL Server 2014 Standard "UpgradeFeatureSpecificRules: KJRTMUpgradeBlockRule"

    I've been searching for HOURS how to resolve this issue:
    I am trying to upgrade SQL Server 2008 R2 (Express Edition with advanced services) to SQL SERVER 2014 Standard edition, my first issue was to update the 2008 R2 to Service pack 2 on the first FEATURE RULE TEST, at this time on it's keep saying this:
    ======================================================================================
    Rule Check Result
    Rule "SQL Server 2008 R2 Service pack 2 or later is requered for upgrade.: failed.
    This SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the require service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or lager to the selected instance and the shared features.
    =====================================================================================
    This is the Configuration Report issue:
    Microsoft SQL Server 2014 - System Configuration Check Report
    UpgradeFeatureSpecificRules: SQL Server 2014 Setup configuration checks for rules group 'UpgradeFeatureSpecificRules'
        KJRTMUpgradeBlockRule     
    Checks if the currently selected SQL Server 2008 R2 features to upgrade are at the supported service pack.     Failed     The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the
    required service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or later to the selected instance and the shared features.
    ====================================================================================
    I try after hours and finally did install the Upgrade Advisor and got not issues, the last choice I was to uninstall the Management Studio because in other upgrade express versions got blocked, but in this new version of SQL Server 2014 I don't see any way
    out!!!
    Thanks.

    Hi again
    This is the scenario:
    -I have installed the SQL SERVER 2008 R2 With Advanced services (version 10.50.1600.1), and now my guest decide to upgrade to an STARNDARD version which nowadays Microsoft is offering the 2014 version.
    -As all IT Support and DBA I try to upgrade to SQL 2014 to check and see with requirements were missing or updates. The first check report only ask to upgrade to SQL SERVER 2008 R2 SP2 (version 10.51.2500.0) which I found in the optional update list and
    resolved immediately with the Windows Update service.
    -Finally, I realise doing the discovery report (suggested in the last post) is that Windows update only download the service pack 2 for SQL Server 2008 instead of the 2008 R2 (I downloaded manually) then the version was upgrade to 10.52.4000.0
    Next time I might download the updates manually and not loosing a lot hours with Windows Update, another point very important is that when SQL Server 2008 R2 is installed, create the Microsoft SQL Server 2008 folder at all programas in the Startup menu:
    with the SQL Server Installation Center, but there is not one R2, when you execute this one just show the 2008 installed features.
    Now we are on 12.0.2000.8
    Thanks anyway and all of you for your interest!!!

  • SQL Server 2014 Standard, but only 2 GB RAM used

    Hello,
    I just installed MS SQL Server 2014 Standard Single x64 on a Windows 8 PC. It was bought to replace the Server Express because the RAM limitation of Express.
    I set min server memory to 500 MB and max server memory to 28672 MB. PC has 32 GB Ram.
    Now I start a very crazy procedure/query that is running for hours.
    The problem is now that task manager shows:
    - SQL Server Management Studio (32 Bit): 0% CPU and 135,4 MB RAM
    - SQL Server Windows NT - 64 Bit: 60% CPU and 2.032,6 MB RAM
    If I use: SELECT * FROM sys.dm_os_process_memory  I get:
    physical_memory_in_use_kb : 2124632
    memory_utilization_percentage : 100
    So why is there Management Studio 32 Bit if I installed it through MS SQL Server 2014 Standard Single x64 installation?
    And much more important: Why is only 2 GB RAM used if 32 GB are there and 28 GB should be used?
    kind regards
    Peter

    Hello,
    Could you try to enable Lock Pages in Memory option for the SQL Server service account?
    http://www.sqlcoffee.com/Tuning05.htm
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Windows Server 2012 Essentials and Microsoft SQL Server 2014 Standard Core Edition

    Our company is planning to buy Windows Server 2012 R2 Essentials edition (Volume license) and install it on Citrix Xenserver based virtual machine with 4 virtual processor cores. Can we install Microsoft SQL Server 2014 Standard Core Edition (2 licenses
    for 2 cores) and run it on this virtual machine?

    you can install SQL Server Standard 2014/2012 on the Essentials Windows Server but without Server core Installation while installing SQL Server 2014 is supported on the Server Core mode of the following editions of Windows Server:
    Windows Server 2012 R2 Datacenter 64-bit
    Windows Server 2012 R2 Standard 64-bit
    Windows Server 2012 Datacenter 64-bit
    Windows Server 2012 Standard 64-bit
    Windows Server 2008 R2 SP1 Datacenter 64-bit
    Windows Server 2008 R2 SP1 Enterprise 64-bit
    Windows Server 2008 R2 SP1 Standard 64-bit
    Windows Server 2008 R2 SP1 Web 64-bit
    http://msdn.microsoft.com/en-us/library/ms143506.aspx
    thanks
    diramoh
     

  • Can you replicate databases from SQL Server 2014 Enterprise Edition to SQL Server 2014 Standard edition?

    Hello,
    Can you replicate databases from SQL Server 2014 Enterprise Edition to SQL Server 2014 Standard edition? 
    Thanks. 

    Yes, you can replicate from Enterprise edition to Standard edition.  The only caveat is Peer-to-Peer Replication requires all nodes to be Enterprise Edition.
    Brandon Williams (blog |
    linkedin)

  • Reports quit working after upgrade to SQL Server 2008

    Folks,
    I'm running Visual Studio 2008 (sp1) and recently upgraded to SQL Server 2008. Reports worked fine until after upgrade. Now I get the "Login Failed" error message.
    Here is code snippets:
            CrystalDecisions.CrystalReports.Engine.ReportDocument oReport = new   CrystalDecisions.CrystalReports.Engine.ReportDocument();
            TableLogOnInfo LonOnInfo = new TableLogOnInfo();
            TableLogOnInfos crtableLogoninfos = new TableLogOnInfos();
            TableLogOnInfo crtableLogoninfo = new TableLogOnInfo();
            private Tables crTables;
            private Table crTable;
            ConnectionInfo crConnectionInfo = new ConnectionInfo();
                crConnectionInfo.IntegratedSecurity = true;
                crConnectionInfo.ServerName = Properties.Settings.Default.InstanceName + "
    Instance";
                crConnectionInfo.DatabaseName = "DATABASE";
                crTables = oReport.Database.Tables;
                for (int i = 0; i < crTables.Count; i++)
                    crTable = crTables<i>;
                    crtableLogoninfo = crTable.LogOnInfo;
                    crtableLogoninfo.ConnectionInfo = crConnectionInfo;
                    crTable.ApplyLogOnInfo(crtableLogoninfo);
                oReport.RecordSelectionFormula = xFormula;
                crystalReportViewer1.ReportSource = oReport;
    Has anyone had this problem? Any help would be appreciated.
    Terry

    CR 2008 does not support MS SQL 2008 yet, meaning we have not had time to test it completely and add it to our supported platforms.txt file.
    One thing I noticed is you are using trusted authenication:
    crConnectionInfo.IntegratedSecurity = true;
    Make sure you give access to all users, MS changed the security properties a lot since SQL 2005 and you can't simply log into any database now. If you have a DBA check with that person on how to configure NT Authentication or the Help file. You can also do a quick test and simply use MS SQL Server authentication to confirm if it's a user permission issue.
    Try creating a report that doesn't use Integrated Security, check the box off on your data logon prompt in the Designer.

  • Users using Windows Authentication unable to login after upgrade to SQL Server 2012 SP2 CU1

    We upgraded from SQL Server 2008 R2 to SQL Server 2012 SP2 CU1.  Upgrade was successful.  Users that have SQL Server Management Studio 2012 can successfully log in via Windows Authentication, but users with an older version of SQL Server Management
    Studio are unable to log in via Windows Authentication. 
    The error they receive is listed below:
    Connect not connect to XXXXXXX
    Login Failed.  The login is from an untrusted domain and cannot be used with Windows Authentication. 
    (Microsoft SQL Server, Error: 18452)
    If we switch to Mixed authentication, users can log in via SQL Server Authentication.
    Our security policy prohibits SQL Authentication. 
    Outside of having the staff upgrade to SQL Server 2012 SQL Server Management Studio, is there any setting I can set/unset to allow older version of SQL Server Management studio to connect to SQL Server 2012?
    Thanks.
    DJ

    Glad to see that you were able to resolve the issue yourself, but for the curious, could you explain what this
    Extended Protection is?
    Erland Sommarskog, SQL Server MVP, [email protected]

  • Upgrading from SQL Server 2012 Standard to SQL Server 2014 Standard Failover Cluster

    Goal: To upgrade my default instance from SQL Server 2012 to SQL Server 2014 in a failover cluster.
    Given:
    1) Operating System Windows 2012 R2
    2) 2 Virtual Machines in a cluster with SQL Server as a Guest Cluster resource.  The two VMS are called APPS08 and APPS09.  They are our development environment that is setup similar to our production environment.
    Problem:  When running the SQL Server 2014 upgrade, I started on the VM that was not running the instance.  I then moved onto upgrading on the node that was running the instance.  As soon as the install attempt to failover the running instance
    an install error occurred that it could not failover.  After many install attempts I consistently received the error
    The SQL Server Failover cluster instance name 'Dev01'
    already exists as a cluster resource.  Opening Failover cluster manager there is no record of a DEV01.
    New Strategy:  Create a SQLCluster called DEV07.  At the end of the Install I get 'Resource for instance 'MSSQLSERVER' should not exists.  Neither I nor my Windows 2012 guy understand what Resource the install may be referring to.  
    We do not see anything out of the ordinary.
    Any suggestions as to what Resource may be seeing the default instance would be greatly appreciated.

    Hi PSCSQLDBA,
    As your description, you want to upgrade the default instance in SQL Server cluster.
    >> 'SQL Server failover cluster instance name 'Dev01' already exists as cluster resource'
    This error could occur when there is a previously used instance name which may not be removed completely.
    To work around the issue, please use one of the ways below.
    1. At command prompt, type Cluster res. This command will list you all the resources including orphan resources. To delete the orphan resource, type Cluster res <resource name>/delete.
    For more information about the process, please refer to the article:
    http://gemanjyothisqlserver.blogspot.in/2012/12/sql-2008r22012-cluster-installation.html
    2. Delete DNS entries, and force a replication of DNS to the other DNS servers.
    For more information about the process, please refer to the article:
    http://jon.netdork.net/2011/06/07/failed-cluster-install-and-name-already-exists/#solution
    >> 'Resource for instance 'MSSQLSERVER' should not exist'
    This error could occur when you already have MSSQLSERVER as a resource in the cluster, which may not be removed completely. To work around the issue, you could rebuild the SQL Server cluster node.
    Regards,
    Michelle Li

  • Upgrade to SQL Server 2014

    Should there/Would there be any issue/s I might run into with upgrading from SQL Server 2008 to 2014 ?
    Or any known issue/s?
    Yes, I understand this is project server; however the SQL software was acquired (about time) and we're planning the migration/upgrade for the SQL Server for project server.
    Thank you for any and all help/suggestions/ideas
    kbwrecker

    Further to this, even Project Server 2013 isn't supported on SQL Server 2014 yet:
    http://technet.microsoft.com/en-us/library/ee683978(v=office.15).aspx see: "SQL Server 2014 is not yet supported for Project Server 2013."
    So previous versions of Project Server wont be supported.
    Paul
    Paul Mather | Twitter |
    http://pwmather.wordpress.com | CPS

  • Can't connect to remote SQL Server 2014 Standard with VS 2012

    Hi all,
    I am trying to create a development environment using SQL Server 2014 (not Express).  The SQL server instance is on a Windows 8.1 Pro machine in a non-domain environment.  I have Visual Studio 2012 installed on the same machine which can connect
    to the SQL server instance without problems.  I have another machine with VS 2012 that cannot connect.  SQL server is configured for mixed authentication.  The SSDT on the remote machine can see the SQL server networked instance, but will not
    connect with SQL authentication. 
    I have rounded up all the usual suspects;
    - The SQL server service is running
    - Remote connections are enabled on SQL server and the relevant firewall ports are open.
    - TCP/IP and named pipes are enabled
    - Remote connections are enabled in Management Studio
    - SQL Server Browser service in enabled and running
    What am I missing?  I have been out of developer mode for a few years and all of the tools have changed, but I seem to be missing something obvious.
    Many thanks in advance,
    Tim
    Tim in Dublin

    Hello,
    Have you configured the Windows Firewall on the Visual Studio computer too? Is there any other security software on those
    2 computers?
    Can you ping between both computers by computer name? If not, try connecting using the IP address. For example:
    10.0.0.10,1433
    1433 is the default SQL Server port number.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • After upgrade from SQL Server to SQL server 2012 I cannot show Query Designer ?? Please help

    Hi
    I have installed the required .Net software, but never the less I've got this message. Could you please help me out ?
    Thanx in advance
    Pia 
    TITLE: Microsoft SQL Server Management Studio
    Cannot show Query Designer.
    ADDITIONAL INFORMATION:
    Exception has been thrown by the target of an invocation. (mscorlib)
    Unable to find the requested .Net Framework Data Provider.  It may not be installed. (System.Data)
    BUTTONS:
    OK

    also check
    http://connect.microsoft.com/VisualStudio/feedback/details/652192/visual-studio-2010-add-connection-fails
    mostly machine.config is referring to .net 3.0 assemblies
    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

  • Crystal Reports XI connection problems - after updating to SQL Server 2008

    Hello!
    We have some ASP.NET 2.0 Applications that call some CR XI report files with parameters to generate PDF Files. After upgrading from SQL Server 2005 to 2008 the apps hang when trying to generate the PDFs. Some research with Fiddler showed that ever time a 401 Error is raised. Calling the reports directly from CR Designer with the same connection values and Parameter shows the appropriate data that means the log-in data iare functioning.
    I already tried switching the data source driver from OLE DB to SQL Native - no effect!
    Can it be that CR XI does not work with SQL Server 2008? Or is there an update for CR XI and SQL Server 2008?
    Because we are in a hurry I hope somebody can solve my problem(s) ...?!
    Thanks in advance,
    Frank

    Hi Frank,
    No CR XI is not supported nor is any version completely at this time. What we've found issues in so far are the Time(7) time is returned as a string value and Stored Procedure Data/time parameter SQL creation. The Time(7) field is an OLE DB driver issue with Microsoft but the Date/time SP issue is our issue and it's currently tracked and escalated. It will be fixed for CR 2008 with SP3 I believe. And I've asked that the same fix be rolled back to CR XI R2 but waiting on the reply from R&D if it can be done.
    What you need to do is download the trial version of CR XI R2 ( Release 2 ) and then use your XI Keycode to install it and it will work. Then update to the latest SP 5 Service Pack. XI is past it's end of life support which means there will be no updates or bug fixes any more.
    Next, MS SQL Server 2008 does not work with the MDAC version of the Native drivers, you must install the MS SQL Server Client. You'll see the driver name is "MS SQL Server Native client 10". This is the one you need to use.
    Another work around is to use ODBC, it seems to resolve all issues, but the client must be installed.
    Thank you
    Don

Maybe you are looking for