on 10-17-2014 2:18 AM
Hello,
We recently upgraded from XI 3.1 FP4.2 to FP7.1. Since then we have intermittently had issues where users log into Desktop Intelligence using the 3-tier cluster name and the list of "Available Universes" is blank. This affects all users, and it is only fixed by logging into Desktop Intelligence with the Administrator account, which somehow refreshes the connection.
"Use in Offline Mode" is NOT being ticked, when this occurs.
SAP Knowledge Base Article "1998841 - Cannot view Universes list when using Desktop 3-tiers mode for Administrator users", actually details the opposite problem to what we have. In our case its the non-adminstrators that cannot see the "Available Universes" list.
One thing we did do when upgrading the fix pack was to turn on auditing for Desktop Intelligence.
Any ideas on troubleshooting/resolving this issue would be appreciated.
Thanks
Stuart
This problem continues to randomly plague our system. Can anyone advise any suggestions for troubleshooting this situation, I'm assuming this "Available Universes" list is generated from the CMS database. Is there a particular server/s that enabling tracing on would give specific information around this particular problem ?
Thanks
Stuart
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
When tracing is turned on and using Desktop Intelligence 12.7.1 this is the content of the log file generated when the "Available Universes:" list does not appear. I was incorrect this problem is occurring for Administrator accounts too.
LsiFileHandle.cpp:93:class bo_utf8string __thiscall LSIFileHandle::getClusterGuid(void) throw(struct Deploy::Zip::ZipException): TraceLog message 1
2014/10/20 21:58:26.973|>>|E| | 708|3836| |||||||||||||||**ERROR:LSIFileHandle:invalid LSI format : no domain folder [LsiFileHandle.cpp;93]
.\ceRepoProxyUniverse.cpp:1701:void __cdecl CEBORepoProxyMaster::GetRepoProxyError(class RepoAccessException &,long,bool): TraceLog message 2
2014/10/20 21:58:43.198|>>|E| | 708|3836| |||||||||||||||RepoProxy Error : [repo_proxy 36] UniverseFacade::getAllLightUniverseList - com.crystaldecisions.sdk.exception.SDKRuntimeException$UnexpectedCause: An unexpected error has occurred. The exception originally thrown was: A problem occurred while operating on file store, eg. while checking if a file exists cause:com.crystaldecisions.sdk.exception.SDKException$GenericFileStoreError: A problem occurred while operating on file store, eg. while checking if a file exists cause:com.crystaldecisions.thirdparty.org.omg.CORBA.IMP_LIMIT: can't create new thread minor code: 0x4f4f0002 completed: No detail:A problem occurred while operating on file store, eg. while checking if a file exists can't create new thread detail:An unexpected error has occurred. The exception originally thrown was: A problem occurred while operating on file store, eg. while checking if a file exists A problem occurred while operating on file store, eg. while checking if a file exists can't create new thread [repo_bridge - BridgeUniverseFacade::getAllLightUniverseList]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Stuart,
Are ALL the Deski Clients also running same version as server, BOE XI 3.1 w/ SP7 + FP1.
Did you try to un-install the Clients tools and re-installed Clients tools w/ SP7 and then update to FP1.
Also try to lower the level of Audit for DeskI client to see if it helps, Auditing could be causing a delay.
Regards,
Ajay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the quick reply Ajay, the staff that have initially reported this issue were running the FP7.1 version of the client tools. There are many people still running the older version though. I might turn off the Deski auditing, we were just trying to collect statistic to plan for a 4.1 upgrade.
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.