Home > Dynamics CRM > Microsoft Dynamics CRM 4.0 – Service msftesql was not found on computer

Microsoft Dynamics CRM 4.0 – Service msftesql was not found on computer

I created a post on this blog back in October 12th 2010 which discussed the error “Service cisvc was not found on computer”.  Now this blog post follows on from that to inform you how to fix the second error listed which was listed.

Service msftesql was not found on computer <yourcomputernamehere>. The specified service does not exist

 

msftesql

This error arises when installing Microsoft Dynamics CRM 4.0 (Enterprise or Professional) with SQL Server 2008. The msftesql is the “Microsoft SQL Server Full Text Indexing Service” which has a different name under SQL Server 2008.

To quickly fix this, do the following:

  1. Start a command prompt and type Regedit Note: This will run the Registry Editor.
  2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
  3. Rename MSSQLFDLauncher folder to msftesql
  4. Navigate to Administrative Tools > Services > SQL Full-text Filter Daemon Launcher (MSSQLSERVER) and restart the service (right-click the service to restart)
  5. Click Back on the Microsoft Dynamics CRM Setup
  6. Click Next on the Microsoft Dynamics CRM Setup to re-run the installer. Now you should be able to see the error has gone away! Note: if you still experience the error, try restarting your computer/server and running the Microsoft Dynamics CRM Setup again.
  7. All verification tasks should now succeed and we are now ready to execute the install.  Once Microsoft Dynamics CRM is installed, rename the Registry folder from msftesql  to MSSQLFDLauncher

Hope that helps.

Greg Olsen
Yellow Duck Guy

Advertisements
Categories: Dynamics CRM
  1. February 11, 2013 at 9:37 am

    Hi Greg, Thanks for the info. I found that renaming the reg key stopped the SQL Filter Daemon service from starting. Bit of a catch 22.

    The fix for me was to ensure that you do an ‘Update Installation Files’ on starting the CRM 4.0 install and the update fixed the issue.

    Hope this helps someone.

    Cheers,
    Ian

  2. Anele
    September 12, 2013 at 12:25 am

    Hi Ian. I followed Greg’s suggestion and got stuck when the service did not want to start. x
    Solution: Restart SQL and you should be good to go.

    Thanks – Anele

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: