Hi guys,
I can’t login to a system using Webi Rich client, but if i use the same system and credentials via InfoView I’m able to login with no problems.
Even more strange: I can login using the same credentials using Designer.
This happens with prodution and non-production systems.
If I try to login with the same credentials in another pc I got sucesss.
Hi,
I work in a company, and i don’t have administation access in my pc, so I would never change a registry entry, or disable/enable an access.
I’m thinkin to ask the reinstalation of webi rich client.
Just to summarize what I understand is that, you are not able to login to webi rich client from a particular client machine. If same credentials are used from a different client machine then you can successfully login to webi rich client.
-This means that its a machine specific issue.
-Lets check if the required ports are opened on the firewall particularly for this client machine (where issue is) also. 6400 to 6499
-Since you don’t have admin right to local system, try with any user who has admin right to local machine, this is just for testing purpose.
-Also you can try IP address instead of system name while trying to login.
-We can try mapping the external IP address of the BO Server(CMS machine) to the FQDN in the client machine’s host file.
I know that this thread is old but I wanted to add to it as we had the same problem today and were able to reolve it. This may help others in the future.
We deleted the following files :
1] In “My Documents\My Business Objects Documents\LocData” delete the .lsi files and the .extranet files.
2] In “C:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\config” delete the file called “cms.history”.
After that, startup InfoView and then open up a new Webi document.
Webi should open up.
Another possible solution - check you haven’t run out of space in My Documents. I had a customer today unable to sign in, when I deleted some (huge) .wid files they had in their local docs…they were able to log in fine. NB, there was no error when logging in, the user stayed stuck on the same screen indefinitely.