cancel
Showing results for 
Search instead for 
Did you mean: 

WIS 00001 as well as Slow Universe Loading Problem

Former Member
0 Kudos

Using Business Objects XI Release 2 on Windows XP.

After completing a large universe and exporting it, we've been having difficulties with loading the universe in Web Intelligence. In most cases, the users can't seem to get the loading bar past 3/4 of the bar, even after a full half-hour of waiting. After about 1 minute of loading, it reaches 3/4, then hangs for eternity.

For the times when it does open (slightly more of a rarity), anytime a query is run the error message "WIS 00001" claims that the data is no longer available. Nothing has been deleted in the universe, and the error message seems to come up for every query, including small queries of a single field. As far as we've tested, it seems that all data in this particular universe is unretrievable, though no data has been deleted or changed.

If more information is needed, just ask.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Try clearing out the document and universe caches on your server. The directory for that is:

C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Data\[SYSTEM]\storage

Also, I wonder if it's related to Java memory usage. Through your XP system's control panel, you can set the Java runtime parameters (eg. '-Xmx512m') for applets. How large is the universe?

Answers (2)

Answers (2)

Former Member
0 Kudos

I tried both suggestions, and I don't think either worked. Mine has always loaded decently quickly, but the other users could never seem to even load it, let alone quickly (I figure it has to be something to do with me being the Designer). I set the Java on their computer and deleted the Caches on the server, and it still won't load up for them, and still won't allow me to make a query.

Do you think Service Pack 4 might help with this problem? I saw something about FixPack 3.5 possibly correcting this, but I couldn't locate it. I figured it would be in a Service Pack now, but haven't downloaded it yet.

Former Member
0 Kudos

I'll take another stab. Maybe JVM cache? Go to Control Panel-> Java Plugin, then select on the 'cache' tab and clear the cache and perhaps increase the max size too.

Is everything else pretty much equal? Are you located on the same network segment as your users? Can you log in through their systems with your user and see what is the behavior? Are other reports and universes working?

Former Member
0 Kudos

>

> I'll take another stab. Maybe JVM cache? Go to Control Panel-> Java Plugin, then select on the 'cache' tab and clear the cache and perhaps increase the max size too.

I'll try that.

> Is everything else pretty much equal?

Not quite sure what you mean, but I assume it's answered by the other questions.

> Are you located on the same network segment as your users?

Yes.

> Can you log in through their systems with your user and see what is the behavior?

Both physically, and remotely.

> Are other reports and universes working?

Yes. Only the two that I have recently completed (by Murphy's Law, they are also the only really important ones) don't seem to work... Prior to that, I made small universes that seemed to work fine, but they didn't quite have the complex schema or universe that these have. The others load as fast as you would expect, and give proper reports... Just nothing important.

Former Member
0 Kudos

I'll try those two points, but to answer your last question, the universe contains about (estimating) around 100 - 150 tables (give or take, and including copied tables), while the schema itself contains about 700 - 1000 tables. Not sure if that helps any. Also, I'm running JRE Version 1.5.0_07 as well as 1.5.0_11... Which one should I change the parameter on? I'm not quite sure which one is run by Web Intelligence.

Former Member
0 Kudos

150 tables doesn't seem unreasonable, but it could be memory related. I would just add the setting to both versions of the JRE. -Xmx is for the maximum memory allocation. You can also set a '-Xms128m' or some lower value to set the minimum memory allocation. The -Xmx value is also variable. You'll have to adjust it to how much free memory that you have on your workstation.