Error: "Could not export instance: RWI 00200"

Error: "Could not export instance: RWI 00200"

Introduction

This article explains how to resolve export failures with 360Bind or 360Cast when the following error is returned:

Warning
Could not export instance: (RWI 00200)

Environment

  • Products: 360Bind, 360Cast
  • Product version: not version-specific
  • Dependency: SAP BusinessObjects (BOBJ) Java libraries used by 360Suite

Symptoms

  • Export fails in 360Bind or 360Cast.
  • Task logs show the error in phase 3 for both products.

Error Message

Warning

Could not export instance: (RWI 00200)

Cause

The root cause is a compatibility mismatch between:

  • the BOBJ Java libraries currently used by 360Suite, and
  • the actual version of the BOBJ environment.

Typical scenarios include:

  • The BOBJ environment was upgraded, but the 360Suite BOBJ libraries were not refreshed.
  • The 360Web Platform setup references a path containing libraries that do not match the current BOBJ version.

Resolution

After any BOBJ upgrade, rerun the 360Suite setup and provide the path to the BOBJ libraries matching the upgraded environment.

This step is required even when the platform version itself is not changing.

Example

If BOBJ is upgraded from 4.2 SP4 to 4.2 SP9, update the BOBJ libraries folder used by the 360Suite setup, then rerun setup with the updated path.

Setup screen for BOBJ libraries path

Note: as with any upgrade operation, stop the Tomcat server hosting 360Suite before running setup. The setup process then restarts Tomcat automatically.

Additional Information

Rerunning the same setup version as your 360Suite does not upgrade the application itself. It refreshes and recopies the filtered BOBJ libraries into the application's lib directory.