I have a master setup on our file server. Shared files are on the file server. The file server setup is read only for normal users. When a normal user performs a Shared setup I get an error writing to Business Objects\ShData\Objects.ssi. Is this by design? Do all users need to have write rights on Business Objects\ShData?
I have a master setup on our file server. Shared files are on the file server. The file server setup is read only for normal users. When a normal user performs a Shared setup I get an error writing to Business Objects\ShData\Objects.ssi. Is this by design? Do all users need to have write rights on Business Objects\ShData?
The shdata directory on the server should be read/write. However, I had similar errors with this file when doing workstation installs. I was getting contention messages. BO support said to skip the file; they thought that the setup program itself may have locked the file. Skipping it doesn’t hurt the install. I eventually changed the setup to copy objects.lsi to the local directory.
All user need to be able to write to the obejcts.ssi file, so they will need write access to that directory.
Business Objects actually suggests that you use a local objects.lsi file because the shared objects.ssi can get corrupted very easily. We had this problem, and ended up putting the objects.lsi file locally.
hans.kingma@UNISOURCE-UCS.COM 09/23/1998 01:09pm >>>
I have a master setup on our file server. Shared files are on the file server. The file server setup is read only for normal users. When a normal user performs a Shared setup I get an error writing to Business Objects\ShData\Objects.ssi. Is this by design? Do all users need to have write rights on Business Objects\ShData?