by ·Comments Off on Invalid user when starting Cognos Controller

Product:
Cognos Controller 10.3.1
Microsoft Windows 2012 R2 Server

Issue:
Error when you try to login to Cognos Controller client, after you have selected the database to use, and you have been logged in as a CAM user.

Error message:
System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.Exception: invalid_user

at Cognos.Controller.Proxy.SoapExtension.ServerExtension.ValidateCAMUser(SoapMessage& message)

at Cognos.Controller.Proxy.SoapExtension.ServerExtension.ProcessMessage(SoapMessage message)

at System.Web.Services.Protocols.SoapMessage.RunExtensions(SoapExtension[] extensions, Boolean throwOnException)

at System.Web.Services.Protocols.SoapServerProtocol.CreateServerInstance()

at System.Web.Services.Protocols.WebServiceHandler.Invoke()

at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()

— End of inner exception stack trace —

at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)

at Cognos.Controller.Common.RaiseErrCli.RaiseError(Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)

at Cognos.Controller.Direct.ServerInfoD.GetServerInfo()

at CCR.AppContext.InitServerInfo()

at CCR.AppContext.Login()

Solution:
Login to your windows computer as a user who have rights to use Cognos Controller.
Then it will work. This user is not added inside Cognos controller, and therefor can not login.

Other solutions:
http://www-01.ibm.com/support/docview.wss?uid=swg21692450

by ·Comments Off on An error occurred while trying to access the server

Product:
Cognos Controller 10.3.1
Microsoft Windows 2012 R2 Server

Issue:
An error occurred while trying to access the server when you start the Cognos Controller client and try to login.

Error message:
System.Web.Services.Protocols.SoapException: Server was unable to process request. —> System.ArgumentException: Requested registry access is not allowed.

at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)

at ControllerServerCommon.RaiseErrSrv.RaiseError(String sUser, Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)

at FrServerB.LocalConnectionBusiness.SetSelectDb(String sGuid, String sUser, Boolean bSelectDb)

at FrServerB.ConnectionBusiness.SetSelectDb(String sGuid, String sUser, Boolean bSelectDb)

— End of inner exception stack trace —

at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object Source, Object Description, Object HelpFile, Object HelpContext)

at Cognos.Controller.Common.RaiseErrCli.RaiseError(Int32 lErrNo, String sErrSource, String sErrDesc, String sErrHelpFile, Int32 lErrHelpContext)

at Cognos.Controller.Direct.ConnectionDirect.SetSelectDb(Boolean bSelectDb)

at CCR.AppContext.SelectDb()

at CCR.AppContext.Login()

Solution:
In the IIS manager change the user account used by the Application pool that Controllerserver is using.

Start Internet Information Servers Manager
Go to Application pools
Select NET v4.5
Click on Advance Settings
Change Application pool identity to LocalSystem from ApplicationPoolIdentity
Click OK
Restart IIS services.

More information:
http://www-01.ibm.com/support/docview.wss?uid=swg21691747

by ·Comments Off on No route to host in PAW

Product:
Planning Analytics 2.0.3
Planning Analytics Workspace  (ipa_workspace_local_2.0.29.1080.2.zip)
Microsoft Windows 2016 server
Red Hat Linux server

Problem:
When inside PAW, and you try to expand a node of a TM1 instance, you get a error message.

Error:
Session can not be established for server proven_techniques 500 (internal server error) “code” “explorer” “refID” “message” .”Failed to get children for server cubes”. “cause”.”java.net.NoRouteToHostException: No route to host”.

paw39
Solution:
In one case this is because of DNS and routing problems in network. The PAW server and PA server have both two network cards, and can only communication on one of them.
You must in TM1S.CFG tell Tm1 instance what network card it should use.

Add the line
IPAddressV4=”10.200.30.40″
in TM1S.CFG and restart the TM1 instance.

Replace the ip number with the correct ip address of your Planning Analytics server.
Important that the IP address are inside ” double quotation mark.

by ·Comments Off on User is not admin in Planning Analytics Workspace

Product:
Planning Analytics Workspace
Planning Analytics 2.0.3
Microsoft Windows 2016 Server

Problem:
When user surf to the PAW, they are not administrator and can not add other users.
Surf to http://pawservername.domain.com
Click on the user — and see there is not a option for Administration.
This is a new PAW setup with CAM authentications.

Solution:
The first users that you add in a TM1 instance as ADMIN will be admin in paw when you login to paw. Therefor you must add CAM users to a native TM1 instance first.

Open up a Tm1 application in Native mode. Like Proven_Techniques.
Open C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\tm1s.cfg in notepad++.
Add the lines;
IntegratedSecurityMode=2
ServerCAMURI=http://caservername.domain.com:9300/p2pd/servlet/dispatch
ClientCAMURI=http://caservername.domain.com:80/ibmcognos/bi/v1/disp
Close TM1 architect.
Update the C:\Users\%username%\AppData\Roaming\Applix\tm1\tm1p.ini file with
AllowImportCAMClients = T
CognosGatewayURI = http://caservername.domain.com:80/ibmcognos/bi/v1/disp

Start PAW administration console and surf to http://pawservername.domain.com:8888
Setup like this (change to your servers name);
TM1 Admin Server URI: https://paservername.domain.com:5898
TM1 Application Server Gateway URI: http://paservername.domain.com:9510
Authentication Mode: TM1
TM1 Login Server URI: https://paservername.domain.com:5011
Click validate and update.

(This TM1 instance you point out with the HTTPport number is the instance that will define the first ADMIN in paw, even if you use security mode 5).

Start TM1 Architect and login to Proven_Techniques as Admin.
Go to Security – Client/Groups. From menu Clients select Add New Client.
Add your CAM user from your AD domain, that you want to be ADMIN in paw.
Mark the user to be ADMIN in TM1 Architect. Click OK.
Exit Tm1 Architect.

Open C:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\tm1s.cfg in notepad++.
Change; IntegratedSecurityMode=5
Save the file and restart the TM1 instance.
Now TM1 instance is using CAM authentication.

Update PAW admin console by surf to http://pawservername.domain.com:8888
TM1 Admin Server URI: https://paservername.domain.com:5898
TM1 Application Server Gateway URI: http://paservername.domain.com:9510
Change to Authentication Mode: CAM
Set IBM Cognos BI Gateway URI: http://caservername.domain.com:80/ibmcognos
Set IBM Cognos BI Dispatcher URI: http://caservername.domain.com:9300/p2pd/servlet/dispatch
Set IBM Cognos BI Authentication Namespace ID: AD
Click Validate and update.
Click on status tab – wait until CPU usage is below 1%.

Surf to http://pawservername.domain.com
Login as the CAM user you have given ADMIN rights in Proven_Techniques.
This user should now have a ADMINISTRATOR option under its name.

The list will only show name for people who have already try to login.

More Information:
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/c_paw_administration_top_level.html