I’ve got another question for you folks, in case anyone else has run into this problem as well. When starting the WebI server, I noticed the icon in the system tray continues to flash, and reads “Server is starting” or something of that sort like it’s still starting up continuously (even after the server has been on for days). The odd part is that all system modules/processes (whatever we’d like to call them this week) seem to have actually started already according to what I’m seeing in the admin console, as well as in Windows task manager.
I looked at the trace files after boot, and saw something kind of troubling about the BOManager module/process, but as I said, I can see a BOMgr.exe process actually running in the task manager even though it seems to indicate in the trace log that it wasn’t able to start. I checked the permissions of the user ID being used to run/launch server processes, and that’s not the problem. Anyone have any other thoughts on this or prior experience with 6.1.3 to this effect?
Yup, it’s a stand-alone machine, and it’s been rebooted repeatedly. The only other problem I’ve having is with a limited number of wqy reports that don’t want to open in 6.1.3, but I’d think that to be a separate problem given its fairly limited scope. I was kind of the same mindset as you about just the flashing icon when the task manager, services list, and BO admin console all told me that server processes were running fine, but that trace file gave me a bit of doubt after checking it. Otherwise I’d just ignore it too.
Good thought. I got a bit of the tunnel vision on the BOMgr.exe process when I saw that in the log, and forgot to look for the two minimum spawned busobj.exe processes, which are mysteriously absent. Thanks for the suggestion, that was my oversight. We’ll do some poking around and see why those aren’t coming up.
Hmm. Well I re-ran the configuration utility, making certain that the user ID and password for the ORB configuration were correct, and after a restart my busobj.exe processes did spawn this time (and automatically respawn if I kill them via the task manager). The BOManager trace file looks cleaner now too, but that danged icon is still blinking. It does make me wonder… something’s just not quite right.
I did think it was odd that whe starting or stopping the server that there is both a regular user name and domain, and a BO user name and domain displayed. What is the significance of these two settings? They both reflect the same values presently, but the service account information put into the ORB configuration has nothing to do with any BusinessObjects credentials…
set name=infoAdvantage
set type=PRIMARY
set service=yes
set mode=AUTO
set userType=USER
set domain=<machine name of server>
set userName=<service account name on server>
set boUserType=USER
set boDomain=<machine name of server>
set boUserName=<service account name on server>
Are you using RDC? Every session (such as RDC) gets it’s own winotify.exe process and icon and can’t see any others. Check it out in the task manager - the session id column should be different for each instance. I’ve noticed that sometimes the ones instantiated by user sessions instead of the WebIntelligence service startup fail to update with the current status. If you have a way to view the actual/local desktop, the icon should be accurate.
I’ve come to believe they update via a periodic call to wasfadm.exe. wasfadm sometimes hangs, although you won’t see an error except in the Windows logs and a pop-up on the local console. wasfadm should not be active for more than few seconds. If you see one hanging around, it probably blew up. If you’re not ready to give up and ignore the icon yet, there are some KB articles about calling wasfadm interactively: Resolution entries 13506 & 17517.
Perhaps a big fat “nevermind” on this one. Our application was deployed on WebSphere without configuring the infoview instance via the BusinessObjects configuration tool, but rather just using WDeploy it would seem… so all the pieces and parts were there. Once I just created a new InfoView instance in the configuration utility (didn’t configure the web server or app server for that instance though, so as not to booger up the currently working deployment) that annoying little icon in the system tray stops blinking, and says properly that the system is started. It must just continue to blink forever when you haven’t created any instances of InfoView via the configuration tool so it’s smart enough to know it’s actually present and accounted for. Thanks for the ideas.
(BOB member since 2003-07-01)