If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Cognos Connection Permission Lost After Upgrade

Started by reneincer, 23 Feb 2015 06:53:00 PM

Previous topic - Next topic

reneincer

Hi there,
I upgraded cognos 8.3 to version 10.2.1,

What I did was a Backup of content store and audit databases from SQL2008 and restore them in SQL2012,

When I configured all in the new server, and started the Cognos Service, it asked me about updating the databases to new version so I clicked Ok,

Apparently it installed Ok, but when I entered with any user it can see all the folders, and if I enter with the admin account I only can see WorksSpace applications link, and not Cognos Administration options,

It is configured to use active directory, but It is strange, It is validating user and password against the Active Directory, but not using content store Roles correctly,

If I do a new content database it works ok, but I need my old content database, I think it has to be something with database migration, some scripts, I don't know,

Do you have some error like this?

Raghuvir

Quote from: reneincer on 23 Feb 2015 06:53:00 PM
Hi there,
I upgraded cognos 8.3 to version 10.2.1,

What I did was a Backup of content store and audit databases from SQL2008 and restore them in SQL2012,

When I configured all in the new server, and started the Cognos Service, it asked me about updating the databases to new version so I clicked Ok,

Apparently it installed Ok, but when I entered with any user it can see all the folders, and if I enter with the admin account I only can see WorksSpace applications link, and not Cognos Administration options,

It is configured to use active directory, but It is strange, It is validating user and password against the Active Directory, but not using content store Roles correctly,

If I do a new content database it works ok, but I need my old content database, I think it has to be something with database migration, some scripts, I don't know,

Do you have some error like this?


hi,

does the authentication source remain the same ?

Regards

reneincer

Thanks, that was exactly the answer,

I only change the Namespace name because we wanted a shorter name on upgradre, but this was the reason,

Thanks