04-03-2009 08:45 PM
Ran into this problem A LOT while trying to design a report.. turned off my email (OutLook) and it did not happen again. Has anyone else had this problem? How did you solve it? I think since my email synch with Act that that was my problem (my email synchs every minute). It is very frustrating, hoping that there is a definite fix to this.
04-04-2009 12:14 PM
What version of ACT!?
What does your email sync with?
04-06-2009 07:13 AM
04-09-2009 12:33 PM
04-09-2009 01:07 PM
I've heard of other possibilities:
1. Opportunity based reports that include more than the company and contact fields from the contact table.
2. An extra data source line at the start of a subreport
3. Open the file in notepad and look for anything that looks like a GUID. You shouldn't have one in a report. Take out the offending line and try again
Most often happens with reports converted from ACT! 6.0, but can get corruption in other ways
Post back if any of these help
04-09-2009 02:23 PM
09-22-2011 01:18 PM
Got this error in ACT Pro 2011 while customizing a report. Can't get around it. None of the suggestions resolved it. Not using or synching with Outlook. Opened the report in Notepad and removed strings of numbers - basically at random, I'm a business person not a programmer. It made no difference.
09-22-2011 01:56 PM
That error indocates that corruption has been introduced into the template XML code. I've typically encountered this when manipulating subreports. Most often a data source line has been added by the editor to the subreport code. The problem is easily fixed provided you understand the XML structure of the template and know what to look for. Unfortunately that knowledge only comes with experience. Bottom line is that the error can only be corrected at the template XML code level. If you are going to work at the code level I suggest that you download the XML Notepad from Microsoft, it's free.
There is a third party book with comprehensive training information on the ACT! reports, here is the link.
02-24-2013 06:10 PM
03-26-2013 06:26 PM
I found this solution in another message but it worked for me...