Workflow Manager: Could not parse JXL file due to error

[AllWeatherHeather]

I generated a JXL file from my JTX 9.3 environment and when I tried to import it into Workflow Manager 10.2.2 I got the following errors:

• Popup saying that The select JXL is invalid. Please see log for details.
• The log revealed a level 3 message -

  7/16/2014 13:58:45.986

  Level: 3

  Could not parse JXL file due to error -1072896760: "An invalid character was found in text content." at line 205 position 6179

  Navigating to that location in the JXL using a text editor leads me to the middle of a GUID 

     GUID="{003656DD-B777-46AB-8B3C-3A875E4643E9}"

Does anyone know of a way I could fix this issue and import my configuration? Our system has over 30 jobs and it would be a lot of work reconfiguring each one.

I should also note that I have successfully exported another instance of JTX 9.3 from our environment and imported into 10.2.2.

Thanks!

Heather

[Anonymous User]

Hi Heather,

Yes, getting your jxl to work as an import would be the desired option. We have put a task in our queue to look into it.

The issue of the queries getting overridden is my mistake, however, as it slipped my mind that it wouldn't merge the configurations.

To get yourself up and running fully please.

  - Delete the tables again

  - Run the post install with the custom config and your jxl, resolve the conflict etc.

  - Open the Workflow Manager Administrator

  - Right click on the connection and select Import/Export->Import Configuration

  - Go to C:\Program Files (x86)\ArcGIS\WMX\Desktop10.2\config\Database Configurations and pick Minimum Configuration

  - Click No to Merge

At that point the new elements will be in and nothing from your original db will be over ridden.

Apologies for the confusion, have a great weekend.

Michael

[AllWeatherHeather]

Michael,

I ran the process as you described above and I still lost my queries. Any idea why my production import will not work? Or, is there something I can check for in the WMX repository to ensure that all the 10.2.2 functionality has been added?

Also, should I be opening a support ticket to get this looked at?

Thanks,

Heather

[AllWeatherHeather]

I have also tried to copy the queries from a simple restore of our production environment to the combined restore/minimum configuration and I have been unsuccessful...