We recently completed our upgrade to v15 and have come across the following error message when running the Constituent Import utility in TLive:
The text reads: Operating system error code 5(Access is denied). This error only occurs in the Live version of Tessitura, we have no issues running the import in TTest.
Has anyone else come across this issue? Any ideas as to why this is specific to the Live version of Tessitura?
I had this problem in v15 when using windows authentication. Once I switched back to a normal login everything was fine.
Interesting. Once SSMS access went to Windows Auth for RAMP I could no longer do any filesystem access (i.e. BCP).
Thank you! We aren't a RAMP client, but it seems strange that the utility would run in TTest but not in Live. We use the windows login for both.
Gawain, with all the recent SSMS access changes do you know if BCP processes are getting blocked regardless of whether a user has Windows Auth set up or not? I've been trying to troubleshoot a utility that came with our iWave integration and realized that Windows Auth was causing an issue, but even after taking authentication off of my profile it seems like it's still giving me trouble. I'm butting up against the limits of my technical knowledge so thought I'd ask if you've unearthed more! And I sympathize with everyone in the thread, we've also had plenty of our own custom procs that are breaking with authentication being the culprit.
With RAMP, the SSMS access is via separate (not Tessitura client) accounts. Those have been switched to using Windows Auth for years now. For a while, and I ran into the filesystem permissions issues the moment they did it. For a while they allowed me to keep a SQL Server Authenticated account in parallel with my windows auth account (again, neither of these are Tessitura accounts), but after a while they wouldn't let me, and now I'm struggling with a customization that requires BCP. It's really weird to me, to be honest, that Windows Auth is the one that has trouble with filesystem access, but it sounds like they haven't figured out how to the fix the issue. It's good to know, however. It sounds like for admins we're going to have to suck it up and keep our old SQL auth accounts when we upgrade to v15. Sucks, I was really looking forward to having one fewer password (I have to enter 5 in a row before entering the Tessitura client currently).