I’ve just started to have this problem and have no clue why…
People are able to login and bring up their document listings just fine. However, when they click on any document its just sits there and hangs for hours. Along the bottom “Retrieving your document…” scrolls by as if its thinking but nothing ever happens. Right now I have to stop and restart webi…any ideas?
Ian
Ian Humphries
Decision Support Specialist
PowerQuest Corp.
Phone : (801) 705-8527
Fax : (801) 705-4527
Email : ian.humphries@powerquest.com
Ug…The problem is is that this occurs 5-10 times a day…completely unacceptable…anyone have any other ideas on how to even track down the problem?
Ian
Ian Humphries
Decision Support Specialist
PowerQuest Corp.
Phone : (801) 705-8527
Fax : (801) 705-4527
Email : ian.humphries@powerquest.com
Tom.Nather@PENSKE.COM 03/03/00 01:29PM >>>
That is exactly what I have to do. Sometimes rebooting is necessary. I think its NT and IIS loosing something and has nothing to do with WebI.
This has been ongoing since 2.0 came out with Full client refresh.
Please get FULL UNIX here soon!!!
Ø–
I’ve just started to have this problem and have no clue why…
People are able to login and bring up their document listings just fine. However, when they click on any document its just sits there and hangs for hours. Along the bottom “Retrieving your document…” scrolls by as if its thinking but nothing ever happens. Right now I have to stop and restart webi…any ideas?
What is your setup? NT ____, service pack ____… What flavor or database for your repository? Has anything changed?
Do you run scan and repairs on your domains, often? Have you tried turning on the internal trace(s) for a while? Did you check your database, find any error messages in the dumps?
Post more info, maybe we can help.
Brent
People are able to login and bring up their document listings just fine. However, when they click on any document its just sits there and hangs for hours. Along the bottom “Retrieving your document…” scrolls by as if its thinking but nothing ever happens. Right now I have to stop and restart webi…any ideas?
I’m learning about Webi so ask me questions to help me get an answer out of you guys. We’ve been having problems with Webi in development and test lately. Of course I ask “When did the problem start and what changes were made around the same time?” Typical d’oh dunno answer(s).
I can’t get it to hang right now but I’m pretty sure when it does, we never see the login box at all. We’re fine in Production. We’re using Win2K SP2 and, believe it or not, security is set to MEDIUM in Production and is working fine. We can make dev work on the Low setting but we really want Medium. One difference between Prod and Dev is also Tivoli. I searched up the list archives and get the general impression that Tivoli is a BAAAADDD thing but the Tivoli guy says "Well, its not even turned on except on orncr03 and 05 and blah blah blah…I have no idea what he’s talking about. A guy I respect says that Tivoli just being on the network could be bothering Webi (if Webi gets bothered by Tivoli).
What should I be asking? Does anyone have security working on Medium with no problems? Can anyone tell me a bit more about Tivoli and where Tivoli would have to live and what it would be doing that would give Webi heartburn?
"
I’m learning about Webi so ask me questions to help me get an answer out of
you guys. We’ve been having problems with Webi in development and test
lately. Of course I ask “When did the problem start and what changes were
made around the same time?” Typical d’oh dunno answer(s).
I can’t get it to hang right now but I’m pretty sure when it does, we never
see the login box at all. We’re fine in Production. We’re using Win2K SP2
and, believe it or not, security is set to MEDIUM in Production and is
working fine. We can make dev work on the Low setting but we really want
Medium.
…
What should I be asking? Does anyone have security working on Medium with no
problems? Can anyone tell me a bit more about Tivoli and where Tivoli would
have to live and what it would be doing that would give Webi heartburn?
"
My experience says:
I’ve experinced several “hangings” of the WebI that do not even show the
login window, and I’ve found out one possible cause and one efective
solution for that problem.
Cause:
As my server is a lapttop computer that sometimes is connected to a LAN and
other not I’ve found out that any network unplug can realy hang the server,
even if in this case the server is on the localmachine.
Solution:
Everytime I plug/unplug the network I have to restart the IIS. After
restarting IIS (no need to restart WebI) the local WebI server on my machine
works fine, both with or without network.
I posted “8 Easy Steps to Hanging your WebI Server” at least a week ago. We
have experienced WebI hanging. I think I have narrowed down our problem.
It may be with the Visibroker ORB that is used by BusinessObjects’
WebIntelligence software.
Anytime there is a disruption in the network for three minutes or more the
WebI services can hang. We can reproduced this on several different test
and development servers.
We have intense network vulnerability scans that are done periodically and
randomly to make sure that server administrators are keeping up on the
latest virus protection and patches. We think that scans may also impact
the WebI service but don’t have any direct evidence.
I’m not so sure about the Tivoli backup software. We have been using it
regularly. We have not seen problems with Tivoli software hanging the WebI
services but then again, we may bring down the services before the backup is
started.
I’ve written a VBscript to restart the WebI services if the network goes
down and comes back up. In a post earlier today, I mentioned that I set
OSAGENT_ADDR to 127.0.0.1. I’m checking whether it’s OK to set OSAGENT_ADDR
to 127.0.0.1 or if this could cause other problems. The WebI services seem
to hang if the network goes down and up AND the OSAGENT_ADDR is set to
something other than 127.0.0.1
I hope this helps. There might be something going on with your network
connections. Maybe you could ask some questions about your network or
connectivity to the database server.
