• Replies 7 replies
  • Subscribers 337 subscribers
  • Views 312 views
  • Users 0 members are here
Related

Constituent Import Utility problem

Tanya Hoffmann
$organization

Hello,   I am trying to run the Constituent Import utility from the client.  I have the text file and the format file prepared and it runs perfectly on our Test system.  However when I try to run the same files from the same location on our production system, I get the following errors:

....... may not be a valid directory or the process is unable to access the filepath.

.......file1.txt is not a valid file or the process is unable to access the file.

Error reading format file........ You do not have permission to use the bulk load statement.

As I said, the same files work in our test system so I do not believe it is the files.  In trying to problem solve, I added the bulkadmin Server Role to my user on production (although my user in Test does not have this role.)

I've been looking at what differences in permission there might be between production and test and have not found anything. 

Does anyone have any hints about what might possibly be wrong?

Many thanks,

Tanya

 

 

  • $organization

    Does the file live within a directory that is specifically for TEST? In other words, are you certain the LIVE environment can access that location? If you are on RAMP you may need to check with them regarding file access locations. Hope you find a solution. 

  • $organization

    Hi Tanya,

    From what I remember, that error is usually related to some permissions issue, most likely in the file system not in SQL Server. I can probably help, but I need some more information... Are the files stored in a folder local to the production database server or are they in a shared folder on another server? If on a shared folder elsewhere, am I correct in assuming that you are using a UNC path (i.e. \\servername\sharename\...) to specify the location?

    David

  • $organization

    Hi,

    The files are on a shared folder that both Tessitura and the users can access.  I’ve changed some of the exact names to protect the innocent but here are the file paths.  If it were a permissions issue on the folder – what should I be looking for?

     

    \\jfkc\MIS_APPS\TESSITURA\Tessitura\ImportGroupon\file1.txt

     

    \\jfkc\MIS_APPS\TESSITURA\Tessitura\ImportGroupon\format\GrouponFormat.xml

     

    Many thanks!

    Tanya

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Thursday, December 03, 2015 5:15 PM
    To: Hoffmann, Tanya
    Subject: Re: [Tessitura Technical Forum] Constituent Import Utility problem

     

    Hi Tanya,

    From what I remember, that error is usually related to some permissions issue, most likely in the file system not in SQL Server. I can probably help, but I need some more information... Are the files stored in a folder local to the production database server or are they in a shared folder on another server? If on a shared folder elsewhere, am I correct in assuming that you are using a UNC path (i.e. \\servername\sharename\...) to specify the location?

    David

    From: Tanya Hoffmann <bounce-tanyahoffmann4570@tessituranetwork.com>
    Sent: 12/3/2015 9:48:55 AM

    Hello,   I am trying to run the Constituent Import utility from the client.  I have the text file and the format file prepared and it runs perfectly on our Test system.  However when I try to run the same files from the same location on our production system, I get the following errors:

    ....... may not be a valid directory or the process is unable to access the filepath.

    .......file1.txt is not a valid file or the process is unable to access the file.

    Error reading format file........ You do not have permission to use the bulk load statement.

    As I said, the same files work in our test system so I do not believe it is the files.  In trying to problem solve, I added the bulkadmin Server Role to my user on production (although my user in Test does not have this role.)

    I've been looking at what differences in permission there might be between production and test and have not found anything. 

    Does anyone have any hints about what might possibly be wrong?

    Many thanks,

    Tanya

     

     




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!



    This e-mail message is intended only for the recipient(s) named above. This message may contain trade secrets, attorney-client communication, or other privileged and confidential information. Any review, re-transmission, dissemination, reproduction or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the Sender and delete the material from any computer.
  • $organization

    Hi Tanya,

     

    When we set this up, I had to grant the account we use for the SQL Server database service access to the folder via NTFS permissions. We used Modify permissions.  You would also want to confirm that the share permissions for the MIS_APPS share either allows Everyone or includes that same account.

     

    It didn’t work properly until we did that from what I remember…

     

    Thanks,

    David

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Tanya Hoffmann
    Sent: Friday, December 4, 2015 6:44 AM
    To: David Frederick <DFrederick@scfta.org>
    Subject: RE: [Tessitura Technical Forum] Constituent Import Utility problem

     

    Hi,

    The files are on a shared folder that both Tessitura and the users can access.  I’ve changed some of the exact names to protect the innocent but here are the file paths.  If it were a permissions issue on the folder – what should I be looking for?

     

    \\jfkc\MIS_APPS\TESSITURA\Tessitura\ImportGroupon\file1.txt

     

    \\jfkc\MIS_APPS\TESSITURA\Tessitura\ImportGroupon\format\GrouponFormat.xml

     

    Many thanks!

    Tanya

     

  • $organization

    Hi David,

    Thank you so much.  I feel like we are so close.  Can you give me an example of the account you use for the SQL Server database service? 

     

    Tanya

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Friday, December 04, 2015 2:21 PM
    To: Hoffmann, Tanya
    Subject: RE: [Tessitura Technical Forum] Constituent Import Utility problem

     

    Hi Tanya,

     

    When we set this up, I had to grant the account we use for the SQL Server database service access to the folder via NTFS permissions. We used Modify permissions.  You would also want to confirm that the share permissions for the MIS_APPS share either allows Everyone or includes that same account.

     

    It didn’t work properly until we did that from what I remember…

     

    Thanks,

    David

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Tanya Hoffmann
    Sent: Friday, December 4, 2015 6:44 AM
    To: David Frederick <DFrederick@scfta.org>
    Subject: RE: [Tessitura Technical Forum] Constituent Import Utility problem

     

    Hi,

    The files are on a shared folder that both Tessitura and the users can access.  I’ve changed some of the exact names to protect the innocent but here are the file paths.  If it were a permissions issue on the folder – what should I be looking for?

     

    \\jfkc\MIS_APPS\TESSITURA\Tessitura\ImportGroupon\file1.txt

     

    \\jfkc\MIS_APPS\TESSITURA\Tessitura\ImportGroupon\format\GrouponFormat.xml

     

    Many thanks!

    Tanya

     




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!



    This e-mail message is intended only for the recipient(s) named above. This message may contain trade secrets, attorney-client communication, or other privileged and confidential information. Any review, re-transmission, dissemination, reproduction or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the Sender and delete the material from any computer.
  • $organization

    Hi Tanya,

     

    When we deployed SQL Server, we set up the SQL Server database service to run under a domain account rather than a local account. It is just a standard AD account (we’re not yet using a managed service account for this purpose) – i.e. domain\username.

     

    Thanks,

    David

     

  • $organization

    Hi David,

    Thank you so much for all of your help!  We got this working today in production.  It did seem to be some file permission issues.  We are still a little stumped because it wasn’t working yesterday.  But last night we applied windows patches and rebooted the servers so our theory is that something got stuck somewhere and the reboot reset things.

     

    Thanks again,

    Tanya

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of David Frederick
    Sent: Friday, December 04, 2015 5:24 PM
    To: Hoffmann, Tanya
    Subject: RE: [Tessitura Technical Forum] Constituent Import Utility problem

     

    Hi Tanya,

     

    When we deployed SQL Server, we set up the SQL Server database service to run under a domain account rather than a local account. It is just a standard AD account (we’re not yet using a managed service account for this purpose) – i.e. domain\username.

     

    Thanks,

    David

     




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!



    This e-mail message is intended only for the recipient(s) named above. This message may contain trade secrets, attorney-client communication, or other privileged and confidential information. Any review, re-transmission, dissemination, reproduction or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the Sender and delete the material from any computer.