Error call AP_BCP_FILE Procedure

Former Member
Former Member $organization

 

Hi,

Maybe somebody can help me. I have my Store procedure where I call to AP_BCP_FILE  procedure with those parameters

EXEC  AP_BCP_FILE
     @file_name    = '\\Server\t-import\import\TestData.txt',
     @format_file  = '-c',
     @table_name   = 'lt_hf_custom_data_staging',
     @db_login     = '-T',
     @bcp_in_out   = 'IN'

and I get the error message

Msg 50000, Level 11, State 2, Procedure AP_BCP_FILE, Line 218
\\server\import\TestData.txt is not a valid file or the process is
unable to access the file.

Any Idea how I can fix it?

 

Thanks

 

Adrian

 

 

  • The user you are running SQL service as - has to have access to \\server\t_import folder.  If you are running SQL as a local user or system account, this won't work (someone can mention proxy accounts here).  If you run SQL as a domain user, you can add this domain user to be allowed to access the share (windows security is stopping you)

    A more simple approach could be to create a hidden share on the SQL server (c:\mysharedfolder\) and drop the import file on there, then your @file_name would be c:\mysharedfolder\testdata.txt.  

    For simplicitys sake (tighten back up later) set the folder security to "Everyone" group.

    Try this and see how you get on.



    [edited by: Wayne Evans at 8:58 AM (GMT -6) on 26 Nov 2013]
  • Former Member
    Former Member $organization

    Hi Wayne,

    I created a folder inside of sql server, after that  I copied the file into it, I gave full control to "Everyone" and after that I opened the SQL Managment Studio in the SQL server and run the store procedure and I get the same error 

    Msg 50000, Level 11, State 2, Procedure AP_BCP_FILE, Line 218
    c:\Myfolder\v11test1.txt is not a valid file or the process is unable to access the file.

    Do you have any other idea?


    Thanks

    Adrian

    A more simple approach could be to create a hidden share on the SQL server (c:\mysharedfolder\) and drop the import file on there, then your filename would be c:\mysharedfolder\testdata.txt.  

    For simplicitys sake (tighten back up later) set the folder security to "Everyone" group.


    On 11/26/2013 10:15 AM, Wayne Evans wrote:

    The user you are running SQL service as - has to have access to \\server\t_import folder.  If you are running SQL as a local user or system account, this won't work (someone can mention proxy accounts here).  If you run SQL as a domain user, you can add this domain user to be allowed to access the share (windows security is stopping you)

    A more simple approach could be to create a hidden share on the SQL server (c:\mysharedfolder\) and drop the import file on there, then your filename would be c:\mysharedfolder\testdata.txt.  

    For simplicitys sake (tighten back up later) set the folder security to "Everyone" group.

    Try this and see how you get on.

    From: Adrian Karmel <bounce-adriankarmel8286@tessituranetwork.com>
    Sent: 11/26/2013 7:34:20 AM

     

    Hi,

    Maybe somebody can help me. I have my Store procedure where I call to AP_BCP_FILE  procedure with those parameters

    EXEC  AP_BCP_FILE
         @file_name    = '\\Server\t-import\import\TestData.txt',
         @format_file  = '-c',
         @table_name   = 'lt_hf_custom_data_staging',
         @db_login     = '-T',
         @bcp_in_out   = 'IN'

    and I get the error message

    Msg 50000, Level 11, State 2, Procedure AP_BCP_FILE, Line 218
    \\server\import\TestData.txt is not a valid file or the process is
    unable to access the file.

    Any Idea how I can fix it?

     

    Thanks

     

    Adrian

     

     




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

    No virus found in this message.
    Checked by AVG - www.avg.com
    Version: 2012.0.2247 / Virus Database: 3629/6368 - Release Date: 11/26/13