cancel
Showing results for 
Search instead for 
Did you mean: 

Could not save document to the repository [repo_proxy 30] (WIS 30567)

Former Member
0 Kudos

Hello,

My environment is:

Windows Server 2003 SP2

BusinessObjects XI3.1 SP3

Apache/Tomcat 5.5.20

I am starting to receive these intermittent errors when trying to save Web Intelligence documents.

"Could not save the document to the repository for the following reason: [repo_proxy 30] InfoStore::ObjectExport::commit - (Helpers::InfoStore::ObjectExport::commit) File Repository Server error: Could not save the file <filename>.wid to the File Repository Server. File already exists. (hr=#0x80042a4a)(Error #-2147210678 (WIS 30567)"

I have checked the settings of the Temp folder for the Input File Repository and this is set to %BOB%\FileStore\Temp (where %BOB% is my BusinessObjects installation directory.

Please can anyone advise.

TIA

Julian

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

please see note 1934933:

Cause

The "detail" Webi report infoObject has somehow become corrupted.

Resolution

  1. Save the "detail" Webi report to the enterprise to a different location or to the same location with a different name.  This will create a new infoObject within the BI Enterprise.
  2. When this new Webi report is opened and then saved, there will not be any issues.
  3. Since the GUID of the Webi report has changed, the "master" Webi report will need to be remapped to point to the new "detail" Webi report.
Former Member
0 Kudos

Have you check if your server dick is full?

Regards

Former Member
0 Kudos

Interesting idea Oscar, but I'd also suggest checking the disk.

denis_konovalov
Active Contributor

lets keep it professional please ;):)

On the subject - what this error is telling you is that when report was being saved into Input FRS, another report with the same ID was found there and the product couldn't overwrite it.

Possible reasons :

1. you have no rights to overwrite docs in the BOE

2. there are OS issues with restrictios on IFRS

3. Drive space issues