View Full Version : Frustrating error - Unable to Open Show Export File - when trying to play show

01-02-2014, 12:09 AM
Hi Joe.

First of all: Happy New Year!
As I am adding more songs to my show (currently 4) I started to run to a weird error: "Unable to Open Show Export File".

I have started to experience it couple weeks ago after I added 3rd song. I was able to overcome it by trying to start over again ("Play a Specific Playlist") and it sporadically worked (after 2nd or 3th try).
I added 4th song to my display today and it became almost permanent. I spent 1 hour to persuade HLS player to play my show. :ohwell: It's just frustrating. I don't think I'll be able to add 5th song. I am getting stuck now.
More info:
After today's battle I discovered that it has to be song's quantity/file size related. I tested it and started the show with 1 or 2 sequences without issue.
- I have 4 sequences with size of hlsIdata files : 498MB, 403MB, 395MB and 301MB.
- I tried to restart HLS or machine and still the same.
- I tried it on a different machine => no difference (both machine with 8GB of RAM and WIN7).
- The HLS folder is placed directly on C drive

How to reproduce it:
- create a play list with 4 songs
- go to "OutPut" and pick "Play a Specific Playlist"
- select the created 4 songs playlist
- upon almost 30 sec window with NIC card option appears
- select IP and click OK --> HLS starts to process/compile the list ...
- after a while I get this error:

The problem is that it happens sporadically. i.e. I have just run it 1st time -> error (after 3 minutes), 2nd time -> worked (after 7minutes), 3d time -> error (after 3 minutes)
I am getting frustrated from this issue.
Please, what should I do to avoid this error?

here is my playable show (https://app.box.com/s/hxemds2ox631u0mhwfar) for easy reproduction

Thank you

01-02-2014, 09:26 AM
The error occurs with the Read XML file process (hlsidata).

I have released version 19K that added additional debug info to the error message --- filename and error code.

Not sure of how you are defining random since HLS only reads those files at the very start of a Show Playlist. The XML file is read, processed, and saved as binary so that delays in the show are minimized.

Once you find which file is causing your issue - you can check the error code to the list below:

101 Invalid attribute index.

102 No attributes available.

103 Invalid namespace index.

104 No namespaces available.

105 Invalid element index.

106 No elements available.

107 Attribute does not exist.

201 Unbalanced element tag.

202 Unknown element prefix (can't find namespace).

203 Unknown attribute prefix (can't find namespace).

204 Invalid XML markup.

205 Invalid end state for parser.

206 Document contains unbalanced elements.

207 Invalid XPath (http://doityourselfchristmas.com/forums/XMLp_p_XPath.htm).

208 No such child.

209 Top element does not match start of path.

210 DOM tree unavailable (set BuildDOM (http://doityourselfchristmas.com/forums/XMLp_p_BuildDOM.htm) to true and reparse).

302 Can't open file.

Let me know what you find.


01-02-2014, 01:03 PM
Joe, thank you for the quick turnaround on this issue.
We are "almost" there. I got error 200 which is not in your error list.
Any idea what it could cause that?
FYI: The file is not read only.

01-02-2014, 01:46 PM
I use a XML component from nsoftware - I will email them and ask what the error is.

Can you open the file with a good editor?

Check the end and make sure it is a complete XML file.


01-02-2014, 03:10 PM
The XML looks good to me. All the tags are properly closed.
Could it be the file size?
This file is only one which has almost half a gig. The others are around 0.4 GB. Could it be that the XML component simply chokes on it under certain conditions?

01-02-2014, 03:16 PM
I know size is an issue.

When I first started HLS -- I had the HLS file constructed using XML and found the upper end size limit - that is why I switched to a binary format.

If it were a size limit - then it would failed every time that file was parsed -- but you posts states that sometimes it works and sometimes it doesn't.

I place a support question into nsoftware on the meaning of error 200. I will let you know when I get their reply.

I did not write my own XML parser ... looks like I might have to.


01-02-2014, 03:32 PM
Thank you Joe for your help.

01-02-2014, 06:11 PM
I just released 19L.

The component supplier could not explain error 200.

They provided me with a way to acquire a Text Version of the error which is what version 19L does.

Break it again and report back the error message.



01-02-2014, 08:14 PM
Hi Joe,

here is the detailed error: 22317

I watched the Memory usage and average usage is around 1 GB. Sometimes it jumps to 1.7GB. But the crash occurs even around 900MB.

01-02-2014, 09:10 PM
I'll have to ponder on how to address this one.

I suspect I will write my own that puts data onto the disk since this component implementation uses all ram.

I only use XML for Library and export data.


01-02-2014, 09:21 PM
Can you send me that hlsidata file so I have something to test with?



01-02-2014, 09:31 PM
Thank you Joe for trying to help me out.
In the initial post there is a link with my whole show in case you need it.

01-03-2014, 08:38 AM
I slept on this all night --- that is where I solve a ton of issues.

I should have this resolved by days end.


01-03-2014, 12:33 PM
I just released 19M.

This release removes any and all size related constraints with the HLS export file.

Your file in question was almost 500Meg in size.

Most XML readers consider 100Meg an VERY LARGE XML file.

HLS can easily read a 2 to 4 GIG Export file now.

Your 500 meg export file contained 73 Universes -- each having anywhere from 450 to 510 channels per Universe.

Let me know how it works for you.



01-03-2014, 12:43 PM
Thank you Joe very much.
I'll give it a whirl tonight and keep you posted.

01-03-2014, 01:02 PM
500 meg export file contained 73 Universes -- each having anywhere from 450 to 510 channels per Universe.

WOW! I feel very inadequate right now with my 26KB file.

01-03-2014, 04:03 PM
I know I went a little overboard. Thanks to Joe's commitment I was able to run my display.

01-03-2014, 04:43 PM
I know I wet a little overboard. Thanks to Joe's commitment I was able to run my display.
I would like to see a video of your display - possible?

01-03-2014, 05:02 PM
Sure, here is the link
There is already a thread (http://doityourselfchristmas.com/forums/showthread.php?30519-My-first-year-of-sequencing) to it.

01-03-2014, 08:28 PM
Eureka! The show started on the first try! (No problems at all)
Thank you for the fix Joe.

01-05-2014, 10:54 AM
Original post - Removed (wrong thread)
Sorry about that.

01-05-2014, 11:01 AM
Removed reply.