COGNOiSe.com - The IBM Cognos Community

Planning & Consolidation => COGNOS Planning => Topic started by: happyMD on 24 Mar 2010 10:51:08 PM

Title: can't login to cognos 8 analyst
Post by: happyMD on 24 Mar 2010 10:51:08 PM
I can't login to Cognos 8 analyst...it is a fresh install (cognos 8.3 with SP)...not sure what did wrong this is only problem pc....analyst works fine on other pcs that i installed last week...please help...the following is the error message:

[E US00055] unable to create LOGINS.LOGFILE(code =10101 8239544)  check the logins= and locks = parameters in FILESYS.INI

Thanks advance for your help:)

happyMD
Title: Re: can't login to cognos 8 analyst
Post by: EP_explorer on 25 Mar 2010 02:10:31 AM
You have to give write rights for users who will work with Analyst to the folder where filesys.ini is situated.
Title: Re: can't login to cognos 8 analyst
Post by: SomeClown on 25 Mar 2010 06:04:41 AM
Might be a different location than filesys.ini -  Inside filesys.ini, there are two lines (parameters), logins and locks.  Those folder locations are the problem (usually it's that the folder doesn't exist - Analyst won't create the subfolders).  Could also be a permissions issue to those folders as mentioned in previous post.
Title: Re: can't login to cognos 8 analyst
Post by: philwilliams on 16 Apr 2010 04:38:59 AM
Hi
We have the same issue here.  One user can onto access Analayst on her PC because of this error but someone else logging onto the PC does not encounter the issue.
I ahve done all checks with the filesys.ini and eben consulted IBM but they have not come back with an answer yet.

the user is question is the only user who has been setup on our new cognos 8.3 and all other users were imported from our cognos 7.3 version.

any help appreciated

thanks
phil
Title: Re: can't login to cognos 8 analyst
Post by: SomeClown on 16 Apr 2010 07:14:48 AM
Check AD group memberships for new user - still looks like the new user does not have permission to use the Analyst shared files location.  Have them browse to the location via windows explorer and try to create and delete a random text file inside one of the directories: this would verify they have sufficient permissions.
(assuming you are getting the exact same error message)