Dave
Thu May 18 16:01:08 CDT 2006
In addition to the somewhat dire possible causes on that KB, I had one
client who had this error as a result of CR/LF characters in the
lastname and jobtitle of the contact records... Ours were inserted
as a result of a Scribe import job from data entered by users via a web
page. You might want to open up an MS support case for this, because
the instructions were to do a direct update of CRM, something I don't
like to do without their blessing. But, Henning Peterson gave us this
fix, and it appears to be pretty benign, and worked for this client:
update contactbase set lastname = replace(lastname,char(13),'')
update contactbase set lastname = replace(lastname,char(10),'')
update contactbase set Jobtitle = replace(jobtitle,char(13),'')
update contactbase set Jobtitle = replace(jobtitle,char(10),'')
(Henning first changed the filter on the user's download, and enabled
tracing to find that one specfic contact record had the bad data...
You can also directly update the contact through the GUI to remove the
bad characters, which, if there are only a couple, is probably a better
approach...)
HTH,
Dave
-------------------------------------------------
David L. Carr, President
Visionary Software Consulting, Inc.
http://www.vscrm.com
971-327-6944
**New** See a 23-minute recorded webinar detailing all VAST CRM
auditing features.
http://www.vscrm.com/webinar.htm