John McCormack DBA

SQL Server Databases and Cloud

  • Personal
    • About
  • Free Training
    • SQL Server on Amazon RDS (Free Course)
    • Free practice questions to help you pass DP-900
  • Save money in Azure
    • Azure IaaS SQL Backups – Stop burning money
    • Your Azure SQL Database and Managed Instance is too big
    • Turn the cloud off at bedtime to save 70%
    • Your Azure SQL Virtual Machine might be too big
    • Save money with Azure SQL DB serverless
    • Save up to 73% with reserved instances
    • Delete unused instances to save money in Azure
  • Hire me
    • 60 minute cost optimization
    • Let me solve your SQL Server problems
    • Take a look at my Sessionize speaker’s profile

Error DReplay Could not find any resources appropriate for the specified culture or the neutral culture

13th October 2016 By John McCormack 3 Comments

When you finally resolve that errorError DReplay   Could not find any resources appropriate for the specified culture or the neutral culture

2016-10-12 08:26:15:865 Error DReplay   Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure "Microsoft.SqlServer.Management.DistributedReplay.ExceptionTemplates.resources" was correctly embedded or linked into assembly "Microsoft.SqlServer.Management.DistributedReplay" at compile time, or that all the satellite assemblies required are loadable and fully signed.

This is a short post to hopefully save any readers some time. Like many people, I was receiving this error when trying to use distributed replay with SQL Server 2016. There are a number of causes but the error message can throw you off course. In my experience, you will get this error when the controller and client cannot communicate with each other.

How can you check if there is a communication issue?

  • Check that the SQL Server Distributed Replay Controller service is running on the controller machine you wish to use.
  • Ensure that the SQL Server Distributed Replay Client service is running on each client machine you wish to use.
    • This was the cause of my problem. I had restarted the client machines but services were set to manual rather than automatic so had not restarted.

To quickly turn on the services without logging on to each server, you could run the command below. Just change the server name for your client server name.

SC \\Distributed_Replay_Client1 start "SQL Server Distributed Replay Client"
SC \\Distributed_Replay_Client2 start "SQL Server Distributed Replay Client"
SC \\Distributed_Replay_Client3 start "SQL Server Distributed Replay Client"
SC \\Distributed_Replay_Client4 start "SQL Server Distributed Replay Client"
SC \\Distributed_Replay_Client5 start "SQL Server Distributed Replay Client"
  • Check for this line in your dreplay client log file: Registered with controller “name_of_controller”. The name of controller is whatever you have used such as Distributed_Replay_Controller. You will find the file at C:\Program Files (x86)\Microsoft SQL Server\130\Tools\DReplayClient\Log for SQL Server 2016. If the service is running and the log does not say registered with controller, you have an issue.

How to fix the communication issue.

Assuming services are running and log does not say Registered with controller

  • Check your firewall has been opened up (on every client machine) to allow incoming connections for DReplayClient.exe. Also, ensure that incoming connections are allowed for DReplayController.exe on your controller machine. Check section 6 of the post-installation steps on this technet article for more info. If you prefer to use the GUI, open the snap in for Windows Firewall with Advanced Security, open command prompt or start, then type wf.msc
  • Ensure your DCOM settings have been changed to allow communication between the controller and client machines. DCOM is used for the RPC communications between controller and clients as well as controller and administration tool.

You should go through this msdn page and check you have done everything required. In my experience, the DCOM setting are something that DBAs do not generally mess with so you wouldn’t necessarily have thought to do this unless you saw it in the configuration guide.

Share this:

  • Tweet
  • Email

Related

Filed Under: front-page, Guides

About John McCormack

John McCormack is an experienced SQL DBA with extensive knowledge of the two largest public clouds: AWS and Azure.

Comments

  1. Narayana Swamy says

    19th April 2020 at 6:16 pm

    Hi.. Nice article .. I have similar issue.. in logs i see Registered with controller “xxxx” but i get below error
    2020-04-19 10:12:03:830 Error DReplay Could not find any resources appropriate for the specified culture or the neutral culture. Make sure “Microsoft.SqlServer.Management.DistributedReplay.ExceptionTemplates.resources” was correctly embedded or linked into assembly “Microsoft.SqlServer.Management.DistributedReplay” at compile time, or that all the satellite assemblies required are loadable and fully signed.

    Reply
    • John McCormack says

      1st May 2020 at 11:30 am

      Hi.

      This is the same error thats posted at the top of the blog post. If you’ve been through all the steps,I don’t think I could help any further.

      What I would say though is that I no longer use distributed replay as I always found it a hassle. I now use WorkloadTools by Gianluca Sartori and I find it an excellent piece of software. Take a look here: https://github.com/spaghettidba/WorkloadTools/wiki

      Thanks
      John

      Reply

Trackbacks

  1. Distributed Replay Error: Failed to set proper database for the connection - John McCormack DBA says:
    3rd May 2019 at 3:45 pm

    […] https://johnmccormack.it/2016/10/error-dreplay-could-not-find-any-resources-appropriate-for-the-spec… […]

    Reply

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

John McCormack · Copyright © 2023

loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.