Link to home
Start Free TrialLog in
Avatar of Darrin Moore
Darrin Moore

asked on

File <filename>.wid not found on File Repository Server error on Crystal Report jobs that were migrated from different server.

Working with SAP Business BI Platform 4.2 SP 5 (2016)

Migrating from a Windows 2012 Server to a Windows 2019 Server using the Promotion Management Wizard. 

Was able to successfully export the configuration from the old server and import them in using the PMW on the 2019 server. Everything came up and looks fine but whenever a job that is scheduled to run actually runs it fails with the error:


File <filename>.wid not found on File Repository Server


When this job is ran manually within Central Management Server it completes successfully. Whenever the job is rescheduled to run it will complete successfully. Only the jobs that have been brought over will fail with this error. 


I've seen a couple other issues on EE similar to this, but nothing that resolves my issue.

Avatar of Mike McCracken
Mike McCracken

From SAP


First try to restart the tomcat and SIA and then try.If not working then follow below steps.


1. Launch Central Management Console (CMC).

2. Log in to CMC with Administrator account.

3. Click on Servers.

4. Right click on InputFileRepository server.

5. Click on Properties from Context menu.

6. Set correct Temporary Directory path. (e.g.: <installation directory of BOE>:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\FileStore\Input\Temp)

7. Set correct File Store Directory path. (e.g.: <installation directory of BOE>:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\FileStore\Input)

8. Click on Save & Close.

9. Restart the InputFileRepository server.

10. Apply step 4 to 9 for OutputFileRepository server.


Note: Correct paths for OutputFileRepository server are:



  • Temporary Directory path. (e.g.: <installation directory of BOE>:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\FileStore\Output\Temp)


  • File Store Directory path. (e.g.: <installation directory of BOE>:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\FileStore\Output)




Avatar of Darrin Moore
Darrin Moore

ASKER

Good morning Mike,

Thank you for the suggestions. Late yesterday i managed to track down an article on SAP's website regarding this.  Basically, it is a bug in the version that we were going to on the destination server. The "fix" is to install the 2020 version instead of 2016. I am going to try that and report back.  I don't believe i can link to it since it is behind their portal, but here's a cut n paste:


2625500 - Promoted recurring instances fail with error, "Could not open the file [filename].wid"

Version 6 from 17.04.2018 in EnglishShow Changes


Component:BI-BIP-LCMPriority:Correction with medium priorityCategory:Program errorRelease Status:Released for CustomerCorrections:0Manual Activities:0Entry successfully validatedPrerequisites:0

DescriptionSoftware ComponentsSupport Package PatchesThis document refers toAttributesLanguagesActivate item to go to section in page

Symptom

  • Promoted recurring instances fail with the error:
    Could not open the file [filename].wid
    File [filename].wid not found on file repository server
  • Issue is not specific to any report type -- Crystal Reports, Web Intelligence, and even Analysis for Office instances can be affected

Other Terms

Promotion,biar,recurrence, BI BIP 4.2,wid,webi, web intelligence, AO

Reason and Prerequisites

Environment:

  • SAP BusinessObjects Business Intelligence Platform 4.2 Support Pack 04 and newer

Steps to Reproduce:

  1. In the Source environment, create a recurring instance of some test report, e.g. Comparative Income Statement / hourly, and ensure the instances run successfully.
  2. Still in the Source environment, use the Query Builder to execute the following query:
    select si_files from ci_infoobjects where si_name='Comparative Income Statement' and si_schedule_status=9
    ***Note that the Input filename referenced is in the correct format and has the correct extension (.rpt)***
  3. Use Promotion Management to create a lcmbiar of the report and its Recurring instance.
  4. Import the lcmbiar into the Destination environment.
  5. In the Destination environment, the imported instance will run to a Failed state
  6. Running the same Query Builder query as before, now in the Destination environment, reveals the filename is no longer in the correct format and now ends with .wid
  7. Rescheduling the Recurring instance in the Destination environment will correct this issue.

Solution

  • This issue is fixed in the patches listed in the "Support Packages & Patches" section below.

    The "Support Packages & Patches" section will be populated with the relevant patch levels once they are released.

    For Business Intelligence Platform maintenance schedule and strategy see the Knowledge Base Article 2144559 in References section.

ASKER CERTIFIED SOLUTION
Avatar of Darrin Moore
Darrin Moore
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial