HI,

I have a problem with e-mail archiving.
When I use the setting track e-mail with an e-mail token on the server and
when sending a email with the webclient the following error accures.

Server was unable to process request.

Details van uitzondering: System.Web.Services.Protocols.SoapException:
Server was unable to process request.


Stacktracering:

[SoapException: Server was unable to process request.]

System.Web.Services.Protocols.SoapHttpClientProtoc ol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall) +1496
System.Web.Services.Protocols.SoapHttpClientProtoc ol.Invoke(String
methodName, Object[] parameters) +218
Microsoft.Crm.Platform.Proxy.EmailWebService.Send( Guid emailId, Boolean
issueSend, String trackingToken) +132
Microsoft.Crm.Application.SMWrappers.Email.Send(St ring id, Boolean
issueSend, String trackingToken) +93
Microsoft.Crm.Application.Platform.Email.Send() +83
Microsoft.Crm.Web.Activities.EmailDetailPage.Send( Object sender,
DataEventArgs e) +83
Microsoft.Crm.Application.Forms.DataEventProcessor .Raise(FormEventId
eventId, FormState state, User user, String objectId, Entity entity) +176
Microsoft.Crm.Application.Forms.AppForm.RaiseDataE vent(FormEventId
eventId) +89
Microsoft.Crm.Application.Forms.EndUserForm.Initia lize(Entity entity) +56
Microsoft.Crm.Application.Forms.CustomizableForm.E xecute(Entity entity,
String formId, String formType) +83
Microsoft.Crm.Application.Forms.CustomizableForm.E xecute(Entity entity) +13
Microsoft.Crm.Web.Activities.EmailDetailPage.Confi gureForm() +261
Microsoft.Crm.Application.Controls.AppPage.OnPreRe nder(EventArgs e) +30
System.Web.UI.Control.PreRenderRecursiveInternal() +62
System.Web.UI.Page.ProcessRequestMain() +1499


Does someone have a solution?

Regards

Jan

JN wrote:
I had the same problem andI ended up going to Microsoft to get the
problem fixed. My problem was when I went into Systems Settings, Email
tracking tab and made the
tracking token prefix null. There is a bug in the system that can't
handle that. You have to go to the actual SQL table and null out the
value (table: OrganizationBase, Field: TrackingPrefix). You can then go

back to the email tracking tab and make the token prefix something
valid. There is a hot patch to fix the bug (KB article 910242). This
all started because I was trying to get rid of the darn tracking token
that shows up at the end of the email subject. It doesn't look good at

all. Has anyone found a way around this? I realize that there is no
other place to put this token but has someone found an acceptable
solution that their customers can live with? Like some other prefix
that would look better?