WebI Troubleshooting Tips

system · January 24, 2000, 2:26pm

Here are some trouleshooting tips that I put together in working with Business Objects tech support to get WebI up and running. I think I encountered every error not in the Error Guide. So, here they are and good luck!

Jodie

Prior to installation:

Get an NT id setup in the domain that is a member of the local

Act as part of the operating system
Back up files and directories
Log on as a batch job
Log on as a service
Log on locally
Restore files and directories
This id will be used in the installation so you must have the Id set up with the correct permissions before installing.

Web Intelligence must be installed on a stand-alone server. Do not
install Web Intelligence on a Backup Domain Controller or Primary Domain Controller. Business Objects does not support it and it simply will not work. To determine if the server is a BDC: * Go to Start…Programs…Administrative Tools (common)…Server
Manager. The Server Manager lists all the computers in the domain and gives their type: Backup Domain Controller, Primary Domain Controller or stand-alone.

Verify the machine(s) used for WebIntelligence are stand-alone
servers.

(Informix users only) Install the database client first and then Web
Intelligence. If Web Intelligence is uninstalled or reinstalled, the database client must be uninstalled as well.
Install the Cluster Manager first and then the nodes.
For each machine, Cluster Manager or Node, choose the NT id on the
local domain during installation. This will configure the Web Intelligence services to start under that id on the local domain.
Check the C:\Program Files\Business Objects\Server\Business Objects
Manager 5.0\bin\servconf.exe to make sure it is configured to run using the NT id defined in installation on the local machine. Also, make sure the DCOM config has the id configured to allow access, allow launch and full control.
When setting up the virtual directories in IIS Manager for Web
Intelligence, set them up as virtual directories under the Default Web Site. Make sure you have a virtual directory for wi, wiadmin and bin. They should be set using the following local paths:

wi: C:\Program Files\Business Objects\WebIntelligence
2.5\http-server
wiadmin: C:\Program Files\Business Objects\WebIntelligence
2.5\http-server\classes\bo\w2\adm
bin: C:\Program Files\Business Objects\WebIntelligence 2.5\http-server\admin

Troubleshooting Tips after Installation: Cannot retrieve time reference for security domain when logging into WebI The database client was not installed before Web Intelligence. Uninstall both WebIntelligence and the database client. Reinstall the database client, then Web Intelligence.

Cluster Manager does not have privileges to login The NT id does not have the appropriate privileges to login or the services are running under the wrong id.

Check the privileges listed above for the NT id and make sure you
are logged into the correct domain.
Try logging into the local domain and then try to login the
Administrator module.
Go to Control Panel…Services and click on each WebIntelligence
service (WebIntelligence Manager and WebIntelligence ORB) and click on Startup. Make sure that both services are using “This Account” and browse for the NT administrator id in the local domain you identified in the installation. Then stop and restart the WebIntelligence services.

Login Failed when trying to refresh the BCA list in the Administrator module.
A General Supervisor login must be used to refresh the BCA list. * Make sure the bomain.key is valid. (i.e. Can you login to
Supervisor from the server)

Check your id in Supervisor to assure it is not disabled.
Make sure you have a BCA defined in Supervisor
Open the C:\Program Files\Business Objects\Server\Business Objects
Manager 5.0\bin\servconf.exe. Make sure it is configured to use the NT id defined in installation on the local machine.

Three login prompts and the login fails when attempting to login to WebIntelligence.
This occurs when the directory security in the IIS manager is set up with NT Challenge Response and Allow Anonymous Access. * Go to Start…Programs…Windows NT4.0…IIS…IIS Manager. Right
click on the wi virtual directory set up under the Default Web Site and go to Properties. Click on the Directory Security Tab and only check Allow Anonymous Access. Go to Edit of Allow Anonymous Access and make sure it is using the IUSER_ id and has password synchronization checked off.

Repeat this procedure for the wiadmin and bin directories in IIS.

Unable to set user password 0x0000007a when trying to apply servconf.exe changes or during installation.
This error occurs when you have installed WebIntelligence on a Backup Domain Controller. The installation will be successful even though this error appears during the installation. Reformat the server to be a stand-alone server.

When the Login button is clicked from the WebIntelligence home page, the following error is displayed: Server Application Error The server has encountered an error while loading an application during the processing of your request. Please refer to the event log for more detail information. Please contact the server administrator for assistance. This error occurs when the virtual directories are set up incorrectly in the IIS manager. Check to make sure the wi, wiadmin and bin directories are set up with the correct local paths and under the Default Web Site.

Cannot Create New Documents when clicking on the Create New Documents button This error occurs when the Navigation Bar is pointing to the wrong frame. * Put the mouse pointer above the “create document” option. You can
see the URL adress “DefaultNoNewFrame.wis” This is not normal, you should have the following target “DefaultNewFrame.wis” * You have to modify the NavigationBar.wis (located in the
WebIntelligence/WiGenerator/Wi folder)

Edit it with Notepad and change the “DefaultNoNewFrame.wis” (In the
part <T$NEW… part) links to “DefaultNewFrame.wis”. * Stop and start WebIntelligence.

General Tips
If WebIntelligence is not functioning properly and there are Cluster Nodes online, stop the WebIntelligence services on the Cluster Nodes and try to get the Cluster Manager fully functional first. Then start the services on a Cluster Node one at a time to help isolate and identify the problem.