Author Topic: Content Store Export Error: CM-REQ-4248 Unable to access the account "CAMID...  (Read 243 times)

Offline Magdalina08

  • Full Member
  • ***
  • Join Date: Oct 2019
  • Posts: 33
  • Forum Citizenship: +0/-0
We are upgrading from Congos 10.2 to 11 and are starting with our QA enviroment.  When I export the Content Store, I get a warning that certain CAMIDs were not able to be copied over.  There are about 45 of them.  I am getting this warning for each CAMID:

CM-REQ-4248 Unable to access the account "CAMID("LDAP_STAGE:u:d43d83c0-a603-1037-8575-ccee154c4fb8")" in an external security system.

I am guessing this means these specific users will not have their personal files transferred as Cognos was not able to access them.  Is there a way to find the user based on the CAMID or is there something I am overlooking here and it means something totally different? Do I need to make sure something is set up differently?  We need to make sure all users have their personal files and schedules moved over successfully.

Offline MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 11,202
  • Forum Citizenship: +662/-10
  • Cognos Software Muppet
We are upgrading from Congos 10.2 to 11 and are starting with our QA enviroment.  When I export the Content Store, I get a warning that certain CAMIDs were not able to be copied over.  There are about 45 of them.  I am getting this warning for each CAMID:

CM-REQ-4248 Unable to access the account "CAMID("LDAP_STAGE:u:d43d83c0-a603-1037-8575-ccee154c4fb8")" in an external security system.

I am guessing this means these specific users will not have their personal files transferred as Cognos was not able to access them.  Is there a way to find the user based on the CAMID or is there something I am overlooking here and it means something totally different? Do I need to make sure something is set up differently?  We need to make sure all users have their personal files and schedules moved over successfully.

Hi,

A couple of questions:
1. Do you have more than one authentication provider? If so, you will need to log into all namespaces before creating the deployment archive. Log into the first provider, then use the Log In option to log in a second time to the second provider. Then create the deployment.
2. Is it possible you have content still present in your Cognos instance that is owned by users no longer present in your authentication provider? You can run a Content Maintenance task to look for this content if so - and either assign it to a new user or remove it.

Cheers!

MF.
Meep!

Offline Eric.Pleiss

  • Administrator
  • Full Member
  • ******
  • Join Date: Jun 2016
  • Posts: 31
  • Forum Citizenship: +2/-1
1. Do you have more than one authentication provider? If so, you will need to log into all namespaces before creating the deployment archive. Log into the first provider, then use the Log In option to log in a second time to the second provider. Then create the deployment.
2. Is it possible you have content still present in your Cognos instance that is owned by users no longer present in your authentication provider? You can run a Content Maintenance task to look for this content if so - and either assign it to a new user or remove it.

MF pretty much nails it here.  If you have a third party tool, like MetaManager, you can easily search for unowned (or orphaned content) and assign it all to a user in bulk, or move it all to an area to be reviewed by relevant SMEs. 

The MetaManager free tools will allow you to find orphaned content in just a couple of clicks - https://www.bspsoftware.com/products/metamanager/Download/

Offline Magdalina08

  • Full Member
  • ***
  • Join Date: Oct 2019
  • Posts: 33
  • Forum Citizenship: +0/-0
Thanks MFGF.  I was able to run the Cognos Maintenance task and found the users were no longer active.  That's what I needed to know.  Thanks!