Error on saving using CM Picture Field

Error on saving using CM Picture Field


After saving the logo or screenshots in a template or workspace there is an issue in the ULS log: The File with the URL "...." does not exist in this webpage


Try to open the CM Picture Library with "URLofYourRootWeb/CMPictures"
If you get an 404 Error please navigate to your Central Administration.

Navigate to the "Web Application Settings" in the Collaboration Manager sub menu and deactivte the Collaboration Manager on the specific WebApplication(s).

After that activate it again. 

Now there should be a CM Picutre Libray - please try "URLofYourRootWeb/CMPictures"


    • Related Articles

    • Field type CM_PictureField is not installed

      Problem: After creating a new list item in the workspace list to create a new site the process runs in error occured. You get this error message in the uls log: ...
    • Throw Cryptographic Exception using the CM

      Problem: System.Security.Cryptography.CryptographicException: Access is denied. at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr) at System.Security.Cryptography.Utils._AcquireCSP(CspParameters param, ...
    • CM Service Proxy not available

      Error Message: soap:ServerServer was unable to process request. ---> Unable to obtain object reference to Collaboration Manager service proxy.   Solution: Check if the Collaboration Manager Service is connected with the webapplication, where the CM ...
    • Getting "access denied" while installing Collaboration Manager (CM) or saving CM settings

      Problem: Collaboration Manager crashes during installation or storage process with the following error:  "Access denied. You do not have permission to perform this action or access this resource." Possible Reason: Most probably this behavior is ...
    • Error "Value does not fall within the expected range"

      Symptom You're using Collaboration Manager and have added multiple columns in the workspace list. Creating a workspace fails with "Error occured". When looking into the ULS Log you see an error like: ...