Carl Moeller on Mon, 18 Mar 2013 15:41:20
When I run the DReplay.exe preprocess command on many trace files, I get:
2013-03-18 12:29:09:179 Error DReplay The input trace file is not valid. Make sure that the trace file exists on controller(not on the Universal Naming Convention (UNC) path) and that the file is not corrupt.
In the controller log, I find this:
2013-03-18 12:29:09:174 CRITICAL [Controller Service] [0xC8200022] The input trace file is not valid. Make sure that the trace file exists on controller(not on the Universal Naming Convention (UNC) path) and that the file is not corrupt.
The trace file is local (C: drive) to the same server that is running the controller. I have created trace files using the TSQL_Replay template and they all can be loaded back into the SQL Server Profiler without error. I have also created trace
files using SQL Server 2005, 2008 and 2012 with exactly the same results. My command line on the server running distributed replay (SQL Server 2012 SP1) looks like:
dreplay preprocess -i "c:\tracefiles\testtrace.trc" -d c:\tracefiles\preprocess
Has anyone seen this error before? Anyone know what I am doing wrong? I haven't found anyone else seeing this error.
tomonowak on Sat, 18 May 2013 16:52:38
You can see here: http://connect.microsoft.com/SQLServer/feedback/details/700114/distributed-replay-dreplay-exe-preprocess-xsd-does-not-exist
Carl Moeller on Tue, 21 May 2013 12:37:14
Thanks tomonowak! That was a good idea; however, I am running the DReplay in the proper working directory. The error I am seeing seems related to the input trace files rather than the xsd.
On the other hand, when I put the trace file into the same folder, I no longer get the error. I got an OS error 5 (i.e. access is denied). I needed to change some permissions on the folder specified in my -d parameter. Once that was done, the preprocess worked without error.