We recently upgraded to new servers for Tessitura, and now, both test and productions servers get BCP Out failure messages when trying to do extractions. We have created a new proxy account, it is a Windows login account called MCFTA\tessproxy…it is a domain admin, an admin on the servers, and we have assigned all permissions as outlined in the documentation from Tessitura regarding creating a proxy account, setting up xp_cmdshell, etc. At the end of the document there is a test job that can be run…when I run the test job, it is successful and writes the files specified. When we try to do extractions, we get an error in the View Log that shows:
To me, the login line (highlighted) looks suspect, but I am not the staff person that runs extractions and have not viewed this log before so am not sure if this is “normal” or not.
Also, when I view the job history in SQL Agent, I see this:
I have tried everything I can think of and have had no luck. I am also working with the Tessitura Help desk but we have not been able to find the resolution yet. I wonder if anyone has run across this same issue, or might have some ideas of what to check.
Penny Tabor
IT Manager
Midland Center for the Arts
Midland, MI 48640
Hi Penny,
Is BCP only failing for this user? Total stab in the dark, but what is the default schema for the database user? I had some problems with extractions not working for a few colleagues because their default schema had somehow been changed to dbo. As soon as I changed it back to the named instance it worked fine. Of course, this was in v10 so it may not be applicable.
Patrick.