Results 1 to 2 of 2
  1. #1
    Join Date
    Mar 2016
    Posts
    1

    Unanswered: cannot import a text file using the import / export wizard for sql server 2014 expres

    hi. a blind it student, and now trying to import a text file into sql server 2014 64 bit express. i use a screen reader jaws for windows from http://www.freedomscientific.com, and using windows 10 64 bit pro on a toshiba satellite pro laptop. will paste the report file and the table below. says the file could not be opened, does it need to be opened. did able to import this when i had windows 8.1 last year and got my certificate iv programming from http://www.upskilled.edu.au. can any one help me out. what stupid thing am i not doing right. also did try the bulk import, but had mismatch errors. and then rolled back to windows 7 from windows 8.1, and then upgraded to windows 10. can any one help. will paste the report and the table below. any help. marvin from australia. SQL Server Import and Export Wizard
    Initializing Data Flow Task Operation stopped...

    - Initializing Data Flow Task (Success)

    - Initializing Connections (Success)

    - Setting SQL Command (Success)

    - Setting Source Connection (Success)

    - Setting Destination Connection (Success)

    - Validating (Success)
    Messages
    * Warning 0x80049304: Data Flow Task 1: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
    (SQL Server Import and Export Wizard)


    - Prepare for Execute (Success)

    - Pre-execute (Error)
    Messages
    * Information 0x402090dc: Data Flow Task 1: The processing of file "C:\DailyNames.txt" has started.
    (SQL Server Import and Export Wizard)

    * Information 0x402090dc: Data Flow Task 1: The processing of file "C:\DailyNames.txt" has started.
    (SQL Server Import and Export Wizard)

    * Warning 0x80070005: Data Flow Task 1: Access is denied.
    (SQL Server Import and Export Wizard)

    * Error 0xc020200e: Data Flow Task 1: Cannot open the datafile "C:\DailyNames.txt".
    (SQL Server Import and Export Wizard)

    * Error 0xc004701a: Data Flow Task 1: Destination - DailyNames_txt failed the pre-execute phase and returned error code 0xC020200E.
    (SQL Server Import and Export Wizard)


    - Executing (Success)

    - Copying to C:\DailyNames.txt (Stopped)

    - Post-execute (Stopped)
    Messages
    * Information 0x402090dd: Data Flow Task 1: The processing of file "C:\DailyNames.txt" has ended.
    (SQL Server Import and Export Wizard)

    * Information 0x402090dd: Data Flow Task 1: The processing of file "C:\DailyNames.txt" has ended.
    (SQL Server Import and Export Wizard)

    * Information 0x4004300b: Data Flow Task 1: "Destination - DailyNames_txt" wrote 0 rows.
    (SQL Server Import and Export Wizard)

  2. #2
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Your problem is with Windows Permissions. Be patient for a moment, then this ought to make sense.

    The Windows concept of "context" describes what Windows login is running a given process combined with the Windows ACL Permissions that login had at the time the Windows task began. The SQL Server process runs using the context of the Windows Service Credentials as they existed when the Windows Service running SQL Server started... Most of the time, the SSIS process runs under the same context which is actually inherited from the Windows Service running the SQL Server Integration Service. Each step or package within SSIS can specify the Windows Credentials that it wants to use, and when SSIS creates those credentials a new context is established for that step or package using the specified credentials.

    The context that was being used to read the C:\DailyNames.txt file and the context being used to write the destination file did not have the appropriate permissions to read or write the file or files. You have two choices:

    The easy answer is to move the files (they may both be one file) to a place where the existing context will work. The backup folder is often an easy choice for testing purposes.

    The better answer is to:
    1. Create a new folder where the work will be done.
    2. Create a new Windows Login for the step or package to use
    3. Grant the Windows login permission (via ACL) to read and write to the file
    4. Modify the SSIS steps or package to use the credentials of this Windows Login

    -PatP
    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •