Maintian Libraries in Analyst 10.1

[vitki]

Hey all, total newb system admin here that got pulled into a new Cognos 10 install.

We have the server up and running and Analyst seems to connect. The issue we are having is that when I go into Maintain Libraries and Users and try to Add a Library, it just seems to refresh the demo libraries and never adds the new one to the list. It will create the folder if I specify one and adds the LIBACCES.BAK and TAB files, it just never shows up in the list of libraries.

Every time I try to add one, I get a small window pop up in the foreground that says "Connecting Analyst Demo Libraries" and the bottom left goes through the Rebuilding index for type...

I am a member of the Planning Rights Administrators group.

What do you think could be the case here?
I'm not sure what information would be of use for you, so:

Windows 2008 R2 64 bit server, IIS7, SQL 2008 database
Everything is on one server right now, except the SQL DB.

[SomeClown]

First guess would be file-system privileges.  If you didn't move Analyst, then system files are inside Program Files (x86) somewhere.  Even with UAC turned off and local admin rights, Windows 2008 R2 doesn't let you easily update files in those directories.  I'd recommend trying to move the system files (filesys.ini and the *.tab mentioned inside filesys) to a location outside of Program Files (if not done already).

[skinners666]

Yes - likely filesys.ini specifically is read only.

[ericlfg]

Hey Vitki,

My 2 cents:

The filesys.ini only stores the path reference to the libs.tab file, which actually houses the various libraries that you've added to an environment.  When you add a library it uses the path specified in the filesys.ini to update the libs.tab file.  I will agree with the others on this thread and you should try either opening the permissions up on the ..\bin directory (if you're using the default install location of the filesys.ini and various .tab files), or move the files off to another location and open it up.  I would do it in this order:

1. Give the Everyone group Full Control of the ..\bin directory to start.  Test.
2. If still unsuccessful move the fileys.ini and .tab files over to another location.  Update the filesys.ini with the new path items (only the top most items in the file, don't worry about all the sample libraries included).  Make sure you create the ..\Locks directory in the root of wherever you move the files).  Make sure you open up sharing permissions and file system permissions.  Test.

Good luck!

[vitki]

That looks like that may have done it!

Even though I installed to the D drive in a new folder, once I gave the everyone group to the bin folder, everything started working.
The Filesys.ini file was not read-only, so it must have needed the added access.

Thanks for your help. I'm sure I will have more questions as this process goes on  :)

[vitki]

OK, one more question :)

Deploying Analyst to a terminal server, I'm running into the problem in this article:
http://www-01.ibm.com/support/docview.wss?uid=swg21472649
Problem(Abstract)After installing Analyst, only the user that performed the installation can use Analyst.
All other users, even local administrators, cannot use Analyst

Is there a fix floating around for this scenario other than having every user click on a few reg files the first time they log on?

[ericlfg]

At this point in time there is no fix available.

Unfortunately this issue lies between an OS security level change for the registry and Analyst's 'old' method of doing things.  Have a look at the below TN as it also addresses the same behavior, but at a policy level.

http://www-01.ibm.com/support/docview.wss?uid=swg21577430

There might be some other more automated ways to address this issue:
1. Startup script that runs the first time the user logs onto that server that effectively executes the import of the keys.
2. Replace the 'default' profile that is used when a new profile is created for the first time.
*Note: this would require that the existing user profiles, if this is an existing terminal machine, be deleted so that they're recreated when the user logs on.

Good luck!

[vitki]

OK, has anybody seen this issue?

I have analyst installed on a Windwos 2008 R2 TS and running for my admin user. I have exported the registry keys mentioned before and a nomal user logs in and adds them. The user then adds the Cognos app server to the local intranet zone for SSO purposes.

The user launches Analyst and the Splash Screen flashes up and then nothng else ever happens. The application shows it is started in the Task Manager and I get dyalog32.exe and epOpHost.exe listed in the processes. It will just sit like that for a long time. If I end epOpHost.exe an error message pops up on the screen about being unable to reach the gateway URI.

This does not happen every time, just the majority of the time.
Any ideas? I installed it using the Citrix option from the complete installer. All users have modify access to the bin folder on the server. Do users need expanded rights, like the Power Users group? The administrators group is out of the question for this :)

Thanks for all the help you have been with my earlier questions

[ericlfg]

Hi Vitki,

I would start, to rule out permissions, by giving one user admin privs on the box itself and test.  This would help to immediately identify any security issues that you may be able to work backwards from with this particular user.

Just thinking off the top of my head:
1. Typically after the splash screen you would get the security HTML page dialog to provide credentials.  If this is getting suppressed or something, then maybe there's another IE custom security setting that needs to be looked at?
2. Was the security challenge screen appearing before SSO was enabled?  I would disable it, to remove complexity, and then try getting in.
3. Anything showing up in the planningerrorlog.csv?  I would search on the system for this file and archive it.  Then reproduce the issue, but don't kill the dyalog or epOpHost before having a look at it.  If nothing is present in the log, close out of it and then kill the 2 exes and then take another look at the log.

Hopefully something will point you in the right direction.

[SomeClown]

Try setting Compatibility option for Analyst so program is Run As Administrator for all users  (right-click, properties on main menu, Compatibility, Change settings for all users)

You may also want to look at this:
http://www-01.ibm.com/support/docview.wss?uid=swg21590673&myns=swgimgmt&mynp=OCSS9S5U&mync=R

May also want to consider antivirus exclusions, turning off DEP and pop-up blockers.

I've seen it before but I don't remember what I did to fix it.

[vitki]

Turning off DEP was the ticket here.
I had a few other issues with the filesys being set up incorrectly. I had the Analyst pointing to a local filesys that had the unc paths for all files. This got the Locks mixed up. Once I used the tool to modify the filesys and set it correctly and turned off DEP. Everything worked correctly.

Thanks for all the help you all have been to me.