I think you may check the configuration of VersionManagerService and ensure that it has all the correct repository mappings defined under the versionedRepositories property which maps repository names to their respective component paths. It should have correct catalog and pricelist repository mappings along with any of your custom repository that is versioned and you are managing it through BCC. Check that you have SecureProductCatalog and SecurPriceLists mapped in it correctly if you are using those.
Thanks for your reply.
We tried to use the SecureProductCatalog and SecurPriceLists in the versionedRepositories of the VersionManagerService component. However, we were facing other issues like our BCC itself not functioning properly and getting many errors and unable to deploy any project. So that we are using the /atg/commerce/catalog/ProductCatalog for CustomProductCatalog and /atg/commerce/pricing/priceLists/PriceLists for PriceLists in the versionedRepositories of VersionManagerService. With this all the things working fine in BCC except the above mentioned issue.
I'm not sure if there was any issue during your environment setup or while setting up your CA deployment target in BCC and what error you were encountering which made you change the VersionManagerService configuration. But you must remember that by default product catalog repository is secured only when you use ATG Business Commerce module while the PriceLists repository is secured by default. I think you can probably recheck your source/destination repositories and their mappings that you would have defined within your target site configuration in the BCC Admin Console. See if they are in synch with the secured repository instance present in VersionManagerService.