Missing VSP, see error message
Me too! I frequently see this message. I reported it, and support folks told me how to manually start the service, which I can do, but it is only a workaround. The problem seems to be related to delays with Windows startup on a "big" machine with lots of things to do during boot up. Even setting the service startup to "retry" several times does not always solve the problem. The message to affected users seems to be that SSDR CAT is only a bridging strategy until the world catches up to native SSDR interfaces. That's fine, but it doesn't help in the here and now.