July 24, 2008 at 1:43 pm
I have two linked servers. 1st server is like an admin sql server dd1 and the other one also is a sql server for eg dd2 . On this one i have a stored proc database. I have some sql jobs, calling those stored procs, that run everyday that use trace files that trace activity on the dd2 server. The jobs are on the admin server dd1. For the past couple of days when i am running the job it is failing saying:
This part seems to be not working in the script:
select * from ::fn_trace_gettable ('TraceFile.trc', default)
when i run this on dd1, it gives me the above error. However when i run this on dd2, it returns some result. So this shows that the trace file does exist. I can even open it, so it is not corrupted in any way.
This used to work before. What might be causing this to fail? Can anyone please help? I am desperately trying to figure out something 🙁
July 24, 2008 at 2:00 pm
If the trace is running on server dd2 then the trace file is being created on that server so it does not exists on dd1. You could set the traces to save the file on dd1 across the network, or you could pass the network path to the files on dd2 when calling the function on dd1.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
July 24, 2008 at 3:09 pm
That is what i am doing. I pass the network path in the function when running the job on dd1. This has been working fine for months....i don't understand what got wrong now. It seems more like a permission or security issue. I am running the jobs as SA. How can i check what might have affected the permission of SA etc? This is only a guess.....i have no clue...but only guesses for now.
Thanks
Priya
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply