Dave's Adventures in Business Intelligence

Not too long ago I had a very frustrating run where certain events (and I was never quite sure what the connection was) would cause my designer session to crash. For a while it was just exporting a universe. The universe would get exported successfully and then Designer would immediately crash. Then I started having problems with Desktop Intelligence where I could not edit documents related to a specific universe. The universe itself was fine, as I verified by going into the Infoview portal and creating documents. And others were able to use the universe just fine.

Ultimately I found a post on BOB that pointed me in the right direction. The seemingly “random” events all had to do with accessing the security areas of the repository, and that pointed to a corrupted .lsi file. These files have been around for many versions of the Business Objects software. Although I don’t remember ever getting a confirmation one way or another I have always called them the “local security information” files. This file is what lets Desktop Intelligence users work in offline mode as it contains a list of universes and documents and so on that the user has rights to. It makes sense that exporting a universe works because that’s not related to security. It’s only after the export was complete that the local security information file was updated, and since my file was corrupted in some fashion that update failed.

Removing the .lsi file for that particular environment solved the problem. There’s no harm in removing this file as Business Objects will automatically regenerate it the next time it’s needed when the program realizes that it is missing.

Where are the .lsi files? The location may be different based on how the software is installed, but they should be within the application folder that is contained within the Documents and Settings parent folder. Here’s the path for me under XI 3.1:

D:\Documents and Settings\username-here\Application Data\Business Objects\Business Objects 12.0\lsi

Once I deleted the .lsi file for the offending environment – I could have removed them all because they’re automatically regenerated if they’re missing – everything worked again. That being said, there are two files in that folder that should not be deleted, and those are pdac.lsi and sdac.lsi. Those files are used to store information related to personal (pdac) and shared (sdac) connections that have been defined on the client computer.

If you’re wondering what ABEND means, it’s short for “abnormal ending” and dates back to mainframe days. 🙂