I'm running TBSM4.2.1 advanced installation.
I've created model and page with ServiceViewer in it showing desired model.
Everything works fine for tipadmin user.
But when I log in as user I've created, to which I gave all roles, ServiceViewer in page can not be opened. I get error:
The selected default service instance 19 failed to load with the following error: java.lang.RuntimeException: Could not initialize soap stub for user: KorisnikPalic: CTGBF0012E An error occurred while establishing a session. The user ID KorisnikPalic is not valid.
Also, this user get this same error when try to open ServiceAvailability page, but when I click on desired service instance in ServiceTree, model apear in ServiceViewer.
I've tried with some other user, but get the same mistake.
Has anyone any idea what is wrong ? Why any created user is not valid ?
This topic has been locked.
4 replies Latest Post - 2013-03-14T20:26:46Z by IsaacGraf
Pinned topic TBSM 4.2.1 problem with ServiceViewer
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-14T20:26:46Z at 2013-03-14T20:26:46Z by IsaacGraf
SystemAdmin 110000D4XK172 Posts
dmcclure 0600011K8N54 Posts
IsaacGraf 2700044PSD34 PostsACCEPTED ANSWER
Re: TBSM 4.2.1 problem with ServiceViewer2013-03-14T20:26:46Z in response to Maja_GIf you have file based repository and create a new user in TIP I don't think it will get migrated to data server if it is running in a separate ewas. Alternatively this could happend if you're using an external repository that is somehow misconfigured on the data server.
The best workaround is to configure the property impact.sla.dataserver.bypassvalidation=true in TBSM_sla.props in data server (RAD_sla.props in tbsm 421) and restart the data server.