QAM Launcher service doesn't start because mapped drive isn't available
Cluster failover failed because the QAM_Launcher is mapped to a F:\ drive on the cluster that doesn't exist at the time of the failover. The F:\ drive is automatically mapped shortly after the QAM_Launcher service is started.
Sign In Required
You need to be signed in and under a current maintenance contract to view premium knowledge articles.