On a single server we carry out the below steps.
- Install CRM 2013 on a newly built server .
- Import CRM 2011 database in the system as a new org.
- Apply CRM 2013 SP1
- Upgrade existing deployment by Installing CRM 2015
- Apply CRM 2015 Update 0.2
- Upgrade existing deployment by Installing CRM 2016
- Apply CRM 2016 Update 0.1
- Uninstalled CRM 2016. Stopped all CRM related services on the box before doing this.
- Then try to install the CRM 2013 Server and you are get the error message as "Action Microsoft.CrmSetupServer.RegisterVssWriterServiceAction
failed.
Unable to Query service status.
"
We would want to be able to install the CRM 2013 again on the Server.
Comments
Mauro Lodi - Can you elaborate what do you mean by reference to CRM and VSS in the registry ?
Category: Unified Experience: Search, navigation and performance
Deleting this Registry key and clicking retry on the error worked for me: HKEY_CLASSES_ROOT\CLSID\{8D00FAB4-94D3-476C-9153-E8D7243F51CA}\InprocServer32\7.0.0.0 Like Mauro Lodi said, lingering Registry keys after uninstalling CRM 2016 messed up the second CRM 2013 installation.
Category: Unified Experience: Search, navigation and performance
I stumbled on the same issue. Somehow something from CRM 2015-2016 stays there and messes up with CRM 2013 second setup. Anyway I've solved manually deleting any reference to CRM and VSS in the registry.
Category: Unified Experience: Search, navigation and performance
Dynamics 365 Sales (administrator)
Thank you for your feedback. We are declining/closing this idea as it has been open for more than 2 years and has not received sufficient numbers of votes. If the idea is still valid, request you to re-submit the idea.