When examinig the log from a backup job it is noted that a message indicating that Catalog data could not be saved for 1 or more on the vmdk files on the vm. The full text of the message is
Catalog data for [SAN1] TestVM/TestVM.vmdk volume 1 failed to save for the following reason(s): An error occurred while receiving the HTTP response to <a href='http://localhost:8000/CatalogService/service.'>Click Here</a> This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
Upon further inspection in Tools>Options>MyJobs>Catalog the Catalog Service Status shows as Unavailable despite the Quest Catalog service showing as running in Windows. Attempting to restart the Quest Catalog service results in an error from Windows that the service cannot be stopped.
From a command prompt a netstat -ab shows a non Quest/vRanger process using port 8000.
This is caused by another application on the vRanger server, such as a SAN Management Utility, or other backup utility, also attempting to use port 8000.
If the application using port 8000 was installed after vRanger either changing the port the other application is using or removing the application should resolve the issue.
If the application was installed prior to vRanger then uninstall vRanger, leaving the database, change/remove the other application, reinstall vRanger pointing to the existing Database. The catalog port 8000, is not a changable port in vRanger.
If vRanger was upgraded the Catalog database may need to be dropped and a new db created.
