Invalid character in a base-64 string. Unexpected end of file wh

This sounds like a bad report link or DataDefinition issue. It is generating a huge amount of data and the .xml file terminates without proper ending so the report cannot generate.
I have seen similar problems when the report is expecting data in a field that was improperly linked in the table.
Another cause could be that someone has Cut/Pasted data from Word or Outlook and invalid characters are in the Comment fields.
Try stripping all comments and print again.

That is all I can think of for now.
Good Luck,
George Hicks


--- In vantage@yahoogroups.com, "jim_chance" <jim_chance@...> wrote:
>
> While running a report for the date range of Nov. we've encountered the following error message after clicking the print preview and before any parms/Crystal report is displayed.
>
> Data problem?
> The XML file is larger than normal.
>
> Report works if ran for Dec.
>
> ???
>
> Any input is greatly appreciated.
>
> Invalid character in a base-64 string. Unexpected end of file while parsing name has occurred.
>
While running a report for the date range of Nov. we've encountered the following error message after clicking the print preview and before any parms/Crystal report is displayed.

Data problem?
The XML file is larger than normal.

Report works if ran for Dec.

???

Any input is greatly appreciated.

Invalid character in a base-64 string. Unexpected end of file while parsing name has occurred.