We have a trace set up to collect long running transaction data. This is part of our admin database and runs on each monitored instance in our environment. We are seeing that while our 2005 instances can stop then close and delete the trace, then read the .trc into a database table then restart the trace, our 2008r2 instances can only stop, then close and delete. Or Start the trace when it has already been stopped. When they try to read the .trc file using sp_trace_gettable, we receive the following error:
File '\\UNCPath\trace\TransactionTraceServername_5.trc' either does not exist or is not a recognizable trace file. Or there was an error opening the file.
The UNCPath is defined inside the procedure using a variable and the whole process is run through a SQL Agent Job. The services for SQL and SQL Agent both have rights on the shared drive. We have attempted to send these .trc files to a separate shared drive with the same rights and have been successful. Has anyone else run into this type of problem trying to read trace files across a network share using sp_trace_gettable? If so, do you have any recommendations for resolving the issue?