XI 3.1:
When I try to delete an object from CMS (e.g. a Crystal report), I am getting the following error in the event log:
System problem encountered: Failed to remove file \filestore\Input\a_193\004\000\1217\ from the file system. Please check for permissions or sharing violations
Although the object is no longer listed in the CMC, the actual file still exists on the filestore. The service account (NT id) has full access to the Filestore.
There are event log messages every second when the fileserver is returning the above mentioned error.
The installation document specifies specific port numbers, 6404 (input) and 6406 (Output) for the FRSs. Do I need to specify these as I currently have ‘Auto Assign’ for port number for both services. If there was a communication issue, I would assume it would be a problem while creating the files too.
I tried pointing the input/ouput FRS back to the local drive on the server and everything worked fine without any event log errors with deleting the folder.
Reconfirmed that the fileshare permissions are set correctly to allow ‘Everyone’ full access. I am able to delete the folder manually but BusinessObjects_fileserv is still throwing the above mentioned error attempting to delete the object.
This is supposed to be straight forward and I have done this a million times in R2. Anybody with similar issues or successful experience pointing the FRS to a file share in XI 3.1?
Case opened with SAP and they have successfully recreated the issue:
In XI 3.1, when an Input FRS is pointed to a file share using UNC path, and an object is deleted in the CMC, the file and the corresponding folders are not deleted in the FRS and a sharing violation error is recorded in the server event log.
It doesn’t matter where the file share resides. It can be on the application server itself with the same behavior.
SAP will notify us when they have officially logged this as a bug.
Anybody who has successfully setup an XI 3.1 Input FRS on a file share and are not seeing the above behavior?
I’m using XIR2SP2 and have the FRSs shared out. With XIR2 the key is to use a DOMAIN acct not system acct. I then add the domain acct to the share, where the Input/Output is housed and give that acct the necessary permissions. I have never had an issue using this method where the files are not deleted from the FRS. Good luck.
Thanks for the heads up. I had just moved my FRSs to a file server and was planning to apply the 3.1 update to my 3.0 installation on Friday. I guess I’ll wait for a bit now.
Hi Chaps
has anyone got hold of fix pack 1.1 for BOXi 3.1 yet.
The support desk are insistant that it doesn’t exist, and their software dist web pages are less use than an umbrella on the moon!
I received a script(BO TECH SUPPORT) for the delete of the files that are out of Synch with the repository database.
Had to run it multiple times to clean up the entire set of outdated files.
The reason i had to run multiple times was because each batch can collect only 1000 files.
I applied Fix Pack 1.1. I do not see the ADAPT you reference here in the release notes. I was still getting the same FRS error until I changed the SIA to run under a domain account rather than a machine account.
Works without error now.