This content has been marked as final. Show 3 replies
Never encountered this. But it could be the repercussion of another exception or error so putting in some general thoughts. Check in the server logs about any other exceptions or errors reported before you encounter this. Also, check if your server startup (specifically the ATG repositories, services and other components which are started) is clean. If all is fine then look at the complete stacktrace of the exception. It can give you an idea of involved component and then you may check at the config layers which are coming into picture for that component on your BCC server for any unwanted configuration.
Are you still getting the same error or was it just one off thing? Another observation I have is if you look at the module reported in the error posted:
AssetManager web-app is part of the ATG's AssetUI module which contains the stuff related to managing versioned repository assets. Some of the main functionality it provides are like asset picker, different type of property editors etc. AssetManager won't be containing anything related to the target creation because that is based on ATG's portal framework and is served from bizui and PubPortlet. So we first need to know the exact scenario where you are encountering this issue because to me the exception doesn't seem to be related to the problem reported. You might want to check if there are multiple BCC sessions to the same server which you are connected and something went wrong in any of those.