Here is an issue for Business Objects/Winframe users: We have encountered severe difficulty with implementing Business Objects on a Winframe server. The issue is the usage of objects.lsi which is part of the local install of Business Objects on the server. (Since we are invoking Winframe using an internet browser, local copies of objects.lsi are not an option).
When multiple customers attempt to login to the application (nearly simultaneously), the objects.lsi becomes locked/corrupted almost immediately. This requires an administrator to restore the file and in the meantime Business Objects is not available.
Any advice on a patch or workaround for this situation would be greatly welcomed - regards,
Ralph Chapman
Sandia Labs rlchapm@sandia.gov
We have encountered this problems thru all releases of 4.x, including 4.1.2.
We had a shared install with the Objects.ssi file shared on the server, so when it became corrupted, all users on that server could not log in.
The problem occurs (reproducable) when a user logs in, becomes impatient with lack of response to the login, and reboots their PC. This immediately corrupts the ssi/lsi file (shared or local install). This problem was reported
to Bus Obj prior to 4.1. Response was that it will be fixed in a future release.
It is still broken!
Our solution/workaround (shared install) was to install the ssi file local on the
desktop (to a personal LAN drive). When the file becomes corrupted, it only affects
a single user & can be more easily dealt with than the situation with all users on
the server being down.
I know this may not help your particular install, but maybe you can use this info
derive another solution until Bus Obj can fix it!!