ThinkingRock Forum

Hi,

I can export neither text or XML from Epsilon on a Mac Tiger. TR produces an empty file.

Although I could initially produce PDFs in Epsilon, it quit after about a month. Acrobat says that the file is corrupt.

Any chance that fixes are afoot? If so, when might we see them? Together, these two bugs mean that I cannot print. I need to.

Thanks!

Could you look at this topic http://thinkingrock.com.au/forum/viewtopic.php?t=1159 and see if it helps. If not, let us know any specific error messages.

_________________
Claire
ThinkingRock Analyst and Tester

Claire,

Thank you for the link. It proved to be helpful in a suggestive way. Yes, I had been specifying fields for the export. No, I did not have "0x1" in my data.

Nevertheless, there was something amiss, as OmniOutliner could not open the file, and Mozilla kicked back the error that is copied below. I could not figure out what part of that code was wrong.

These items were all done, so I purged them. Now everything is back to normal. I can burn reports to PDF. I can also export fields at will. Very happy camper.

May I suggest that TR make purging a bit easier? I ended up manually deleting each item, as I could not find any way to globally delete all of the done items.

Thanks! Much.


XML Parsing Error: reference to invalid character number Location: file:///Users/Arturo/Desktop/thinking-rock.xml Line Number 64, Column 2805:</notes><done>true</done><doneDate>2007-11-03 21:47:21.121 PDT</doneDate><success>Changed 3 unit to 2 with Mic 10/15. Times will be Mondfays 9-11 AM</success><modified>2007-11-03 21:47:21.133 PDT</modified></action><action><id>373</id><created>2007-10-06 22:45:12.996 PDT</created><parent><description>Return sales video to Ramon Martiniez at UCB</description><topic><context><state><created>2007-10-06 22:45:12.996 PDT</created></state><notes></notes><done>false</done><modified>2007-10-18 10:00:06.81 PDT</modified></action><action><id>386</id><created>2007-10-09 11:27:50.497 PDT</created><parent><description>Call Bud Travers</description><topic><context><state><created>2007-10-09 11:27:50.498 PDT</created></state><notes>Saw Bud and met son at Kirala on Thursday 10/4</notes><done>false</done><success>Set up a lunch</success><modified>2007-10-09 17:33:11.297 PDT</modified></action><action><id>416</id><created>2007-10-18 08:50:50.343 PDT</created><parent><description>Contact IABC student about Faye&apos;s PCs</description><topic><context><state><created>2007-11-19 11:00:34.333 PST</created></state><notes></notes><done>false</done><modified>2007-11-19 11:00:34.333 PST</modified></action><action><id>448</id><created>2007-10-19 16:39:11.828 PDT</created><parent><description>Prepare for Berkeley Group session in the evening</description><topic><name>None</name><description>No topic.</description><color><red>0</red><green>0</green><blue>0</blue><alpha>255</alpha></color><background><red>255</red><green>255</green><blue>255</blue><alpha>255</alpha></background></topic><context><name>None</name><description>No context.</description></context><state><date>2007-10-24 00:00:00.0 PDT</date><durationHours>0</durationHours><durationMinutes>0</durationMinutes><created>2007-10-19 16:41:18.771 PDT</created></state><notes>Most members will not have had BA100. I will explain the demeanor of a consultant; i.e. Problem solver and trusted advisor. I will give tips on how to speak at the final presentation. They will get tips on how to do their executive summary in 10-15 slides. I will also discuss how to write their final reports. &#x0;

Claire,

The copied code seems to have two problems.

1. The initial note tag is a closing tag: "</notes>"

2. However, the corruption is probably the last set of characters: "&#x0;"

Note the similarity to the offending code in the post to which you sent me. I did not find any element of "0x1," but here we have "#x0."

The provenance is similar as well. The last item was copied and pasted out of an Entourage calendar entry.

Perhaps, the paste function introduced unparseable characters into the TR file.

Hi

Yes, that (2) would be the problem. To fix it you need to open the file in a editor that will show up such characters (I use 0xEd) and delete them - make a backup first though.
Or send us the file and we will do it for you.

_________________
ThinkingRock Developer