TM1 Forum

Hi all,

I have just installed TM1 10.1.1 on a test server. I run Cognos Configuration as an admin and started the Admin service and Excel service, plus the TM1 instance.

Problem 1
I then use IE to access localhost/TM1Web. The login page could not display correctly i.e. there is no formatting. It appears the CSS file is not accessible when loading the page.

I looked through the old posts and process to grant Full Control access to the "inetpub\wwwroot" folder for "Everyone". I also did a IISRESET via command prompt. This did not solve the issue. I did the same for TM1Web folder under the install path, and still it did not solve the problem.

Problem 2
I followed the steps in the Installation Guide and access the Application Web (localhost:9510/pmpsvc). It detected that this is the first time I access Application portal, so it asked to set up using the TM1 instance that is currently running.

Note that I have not intention to set up workflow for the said TM1 instance. I only wanted to complete the set up in case we need to use Application in the future.

So I completed the set up by leaving all selections to the default values i.e. the three modes (Connected, Distributed and App Web) are selected.

To my horror, when I login as a normal user via TM1 Perspective and tried to open a cube, an error message showed that this user does not have access to all the dimensions in the cube. Using Admin ID, I opened Dimension Security Assignment and was shocked to see that ALL dimensions have been set to NONE for ALL User Groups!

Does this mean that I should not even set up Application in the first place as it seems to do something to the access rights in the model?

Please advice. Thanks!

harry

harrytm1 wrote:Problem 2
I followed the steps in the Installation Guide and access the Application Web (localhost:9510/pmpsvc). It detected that this is the first time I access Application portal, so it asked to set up using the TM1 instance that is currently running.

Note that I have not intention to set up workflow for the said TM1 instance. I only wanted to complete the set up in case we need to use Application in the future.

So I completed the set up by leaving all selections to the default values i.e. the three modes (Connected, Distributed and App Web) are selected.

To my horror, when I login as a normal user via TM1 Perspective and tried to open a cube, an error message showed that this user does not have access to all the dimensions in the cube. Using Admin ID, I opened Dimension Security Assignment and was shocked to see that ALL dimensions have been set to NONE for ALL User Groups!

Does this mean that I should not even set up Application in the first place as it seems to do something to the access rights in the model?

Hi Harry,

I can't comment on your first issue but the second one is something we have come across with 10.1 and 10.1.1. In all previous versions of TM1 the server was always happy not to have a }DimensionSecurity cube if no dimension security was explicitly set, all non-admin users just received the default level of read access to all dimensions. This is fine, 99% of the time it is exactly what you want since only in very rare instances would you ever want to give a user write or admin access to a dimension and there's the drawback that once you do this for one special case user/group then you have to explicitly set read access for all other groups on all other dimensions, a bit of a pain. Dimension security was therefore (traditionally) very seldom used.

Well unfortunately it seems that with v10 this has changed. Somewhere within Performance Modler or the inbuilt server settings it looks like the }DimensionSecurity cube is needed because if you delete the sucker it gets regenerated on startup. This means that you do need to set dimension security or all users will get the "no access to dimension" message and not be able to browse any cube data. But at least there is a pretty easy solution in the dimension security cube just create a rule
[ ] = S: 'READ';
and refresh security, problem should be solved.

Thanks, lotsaram.

i'm running TM1 10.1 on my local without setting up Application (although it was installed). I looked at the Data folder of those TM1 models that have been used, and I don't see any }DimensionSecurity cube. Hence, I believe Issue #2 will only occur if Application is set up, even though the workflow is not defined at all.

This means that I will have to do what you suggested i.e. using a rule to set all dims to READ, if I want to use Cognos Insight to connect to a TM1 model, while the model does not use any workflow in Application at all. I don't think CI works on a model that is not set up in TM1 Application.

Is my understanding correct?


On Issue #1, I suspect it is due to Windows 2008 not setting the Permission of the TrustedInstaller group to Full Control for the wwwroot folder. If this is true, this means the installer fails to copy the TM1Web folder from the install path to c:\inetpub\wwwroot which IIS is referencing. The question is, why didn't the installer flag this out?

On the same note, when I first installed TM1 10.1.1 on a new server, I was not aware that IIS6 was not enabled as a feature. The entire installation was "successful" without error messages. Only when I tried to run TM1 Web did I realise that. Good job, the installer.

harry

As far as number 1 goes i suspect that you are correct on the permissions. To address your question as to why, I have seen this happen when everything from a previous installation was not cleared out. The installer with copy the files but not change the permissions. If there were still TM1 folders in the web directory or the IIS Application existed then I have seen issues with security not setting automatically.

I cannot comment on the Server 2008 part which may certainly be coming into play also.