none
Error during preprocess of trace file RRS feed

  • Question

  • I'm working to get Distributed Replay 2017 working in my environment.

    So far I've installed the Controller and Client on the same machine and configure then to run under a domain service account.  I've verified that the DCOM permissions have been set for both my domain user and the service account that the controller and client run under.  I've also verified that the service account is a member of the "Distributed COM Users" group.

    After all this I've verified that the controller and client start, and that the client log states that it is connected to the local controller.

    My problem is this:

    I used the "TSQL_Replay" template in SQL Server Profiler v17.8 to create a script for a server side trace.  Then used that script to create a small 1 gig trace file from one of my SQL 2017 servers.  I then tried to preprocess the file as directed in this post:

    https://docs.microsoft.com/en-us/sql/tools/distributed-replay/preprocess-option-distributed-replay-administration-tool?view=sql-server-2017

    However when I run the command: dreplay preprocess -i c:\Traces\test.trc -d c:\Traces

    I get this output:

    2018-06-28 17:05:16:153 Info DReplay    Preprocessing pass 1 of 2 in progress.
    2018-06-28 17:05:16:215 Error DReplay   Unexpected error occurred!

    And the controller log says this:

    2018-06-28 17:05:16:106 OPERATIONAL  [Controller Service]  Preprocess started. Detailed options:
    2018-06-28 17:05:16:106 OPERATIONAL  [Controller Service]  Input Trace File: [c:\Traces\test.trc].
    2018-06-28 17:05:16:106 OPERATIONAL  [Controller Service]  Controller Working Directory: [c:\Traces].
    2018-06-28 17:05:16:106 OPERATIONAL  [Controller Service]  Include System Session: [No].
    2018-06-28 17:05:16:106 OPERATIONAL  [Controller Service]  Max Idle Time: [-1]
    2018-06-28 17:05:16:122 CRITICAL     [Controller Service]  **** Critical Error ****
    2018-06-28 17:05:16:137 CRITICAL     [Controller Service]  Machine Name: XXXXXXXXX
    2018-06-28 17:05:16:137 CRITICAL     [Controller Service]  Error Code: 0x00000000

    I've tried to get Informational log messages from the controller but it didn't give me any useful information:

    2018-06-28 17:13:50:635 INFORMATION  [Controller Service]  Start Preprocessing ......
    2018-06-28 17:13:50:635 OPERATIONAL  [Controller Service]  Preprocess started. Detailed options:
    2018-06-28 17:13:50:635 OPERATIONAL  [Controller Service]  Input Trace File: [c:\Traces\test.trc].
    2018-06-28 17:13:50:635 OPERATIONAL  [Controller Service]  Controller Working Directory: [c:\Traces].
    2018-06-28 17:13:50:635 OPERATIONAL  [Controller Service]  Include System Session: [No].
    2018-06-28 17:13:50:635 OPERATIONAL  [Controller Service]  Max Idle Time: [-1]
    2018-06-28 17:13:50:651 INFORMATION  [Preprocess]          Shutdown IR file manager.
    2018-06-28 17:13:50:651 CRITICAL     [Controller Service]  **** Critical Error ****
    2018-06-28 17:13:50:651 INFORMATION  [Controller Service]  Preprocessing - Done.
    2018-06-28 17:13:50:651 CRITICAL     [Controller Service]  Machine Name: XXXXXXXXX
    2018-06-28 17:13:50:651 CRITICAL     [Controller Service]  Error Code: 0x00000000

    I've also double checked the permissions on the c:\Traces folder to make sure the service account had access to read and write to the folder.

    Finally I tried to collect a trace from an older 2008r2 sql server and got the same message in the error log.

    I've tried to google/bing the error message but given that it's Error Code: 0x00000000 it's not very helpful.

    Any ideas on where I can look to resolve this issue.

    Thanks

    Thursday, June 28, 2018 11:16 PM

All replies

  • try change folder path other than C drive

    https://social.technet.microsoft.com/wiki/contents/articles/37872.sql-server-installation-on-centos-linux.aspx

    Thursday, July 5, 2018 7:41 AM
  • Also double check that you have at least CU1 installed for SQL Server 2017. 

    https://support.microsoft.com/en-us/help/4045678/fix-unexpected-error-when-you-use-the-dreplay-feature-to-replay-a

    Wednesday, September 19, 2018 6:47 PM
  • After working with Microsoft support it appears that this is an issue with 2017, installing the latest CU resolved the error.
    Monday, November 26, 2018 10:51 PM