locked
Cannot Qualify or Disqualify a lead after UR 12 RRS feed

  • Question

  • After installing UR 12 we haven't been able to qualify or disqualify any leads. Initially we had a problem involving the dialog and not being able to click the OK or cancel buttons. We tracked this to an issue where function window.onload( ) would not work until we changed it to window.onload = function( ). This fixed our issue of not being able to click the ok or cancel buttons. Now whenever we select qualify or disqualify and select OK we get this:

    >System.FormatException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #4E09D892: System.FormatException: Input string was not in a correct format.
    >   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
    >   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
    >   at Microsoft.Crm.Application.Components.PageHandlers.LeadRecordPageHandler.Qualify(Object sender, DataEventArgs e)
    >   at Microsoft.Crm.Application.Forms.DataEventProcessor.Raise(FormEventId eventId, FormState state, String objectId, Entity entity)
    >   at Microsoft.Crm.Application.Forms.AppForm.RaiseDataEvent(FormEventId eventId)
    [2013-02-08 11:00:16.831] Process: w3wp |Organization:00000000-0000-0000-0000-000000000000 |Thread:   47 |Category: Platform |User: 00000000-0000-0000-0000-000000000000 |Level: Info |ReqId: b9369686-903b-47d0-b401-0a2f66ff8891 | ExceptionConverter.ConvertMessageAndErrorCode  ilOffset = 0x28B
                    at ExceptionConverter.ConvertMessageAndErrorCode(Exception exception, Int32& errorCode)  ilOffset = 0x28B
                    at ExceptionConverter.ToSingleFaultOther(Exception exception)  ilOffset = 0x2B
                    at ExceptionConverter.ToSingleFaultUnTyped(Exception exception)  ilOffset = 0x3A
                    at ExceptionConverter.ConvertToFault(Exception exception)  ilOffset = 0x57
                    at ExceptionConverter.TryConvertToFaultExceptionInternal(Exception exception, Boolean createNewFaultException, FaultException`1& faultException)  ilOffset = 0x6D
                    at FaultHelper.ConvertToFault(Exception exception)  ilOffset = 0x0
                    at ErrorInformation..ctor(Exception exception, Uri requestUrl, Boolean logError, IOrganizationContext context)  ilOffset = 0x24B
                    at ErrorInformation..ctor(Exception exception, Uri requestUrl, IOrganizationContext context)  ilOffset = 0x0
                    at AppForm.HandleSaveEntityException(Exception exception, FormEventId eventType, String url)  ilOffset = 0x22
                    at AppForm.RaiseDataEvent(FormEventId eventId)  ilOffset = 0x5E
                    at EndUserForm.Initialize(Entity entity)  ilOffset = 0x1F
                    at CustomizableForm.Execute(Entity entity, FormDescriptor fd)  ilOffset = 0x62
                    at LeadRecordPageHandler.ConfigureFormHandler()  ilOffset = 0x66
                    at RecordPageHandler.ConfigureFormWrapper()  ilOffset = 0xC
                    at GenericEventProcessor.RaiseEvent(String eventName)  ilOffset = 0x2D
                    at PageManager.OnPreRender(EventArgs e)  ilOffset = 0x53
                    at Control.PreRenderRecursiveInternal()  ilOffset = 0x54
                    at Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)  ilOffset = 0x69E
                    at Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)  ilOffset = 0x3C
                    at Page.ProcessRequest()  ilOffset = 0x14
                    at Page.ProcessRequest(HttpContext context)  ilOffset = 0x31
                    at CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()  ilOffset = 0x11D
                    at HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)  ilOffset = 0x15
                    at ApplicationStepManager.ResumeSteps(Exception error)  ilOffset = 0x10E
                    at HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)  ilOffset = 0x5C
                    at HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)  ilOffset = 0xFC
                    at ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)  ilOffset = 0x45
    >exit: ConvertMessageAndErrorCode: errorCode: 0x80040216; message: System.FormatException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #4E09D892

    I'm not sure what string it is trying to convert to numeric and I'm not sure where to look next. Any help would be appreciated.

    Friday, February 8, 2013 4:52 PM

Answers

  • I've found that the Currency field needs to be on the lead form (although it can be hidden), and this was causing a similar error (although not sure it was exactly the same).

    Neil Benson, CRM Addict and MVP at Slalom Consulting. Find me on Twitter. Join over 20,000 other CRM professionals on the Microsoft Dynamics CRM group on LinkedIn.

    Friday, February 8, 2013 5:49 PM
    Moderator
  • Rollup 13 should fix the problem.

    Strange thing is that file conv_lead.aspx was not replaced by an upgraded version of rollup 13.

    We had to manualy copy this file from a clean install + rollup 13/

    Friday, May 24, 2013 11:44 AM

All replies

  • I've found that the Currency field needs to be on the lead form (although it can be hidden), and this was causing a similar error (although not sure it was exactly the same).

    Neil Benson, CRM Addict and MVP at Slalom Consulting. Find me on Twitter. Join over 20,000 other CRM professionals on the Microsoft Dynamics CRM group on LinkedIn.

    Friday, February 8, 2013 5:49 PM
    Moderator
  • That was actually one of the first things I checked after browsing the forums and  researching the issue on the internet. The currency field is on both the lead form and the convert lead dialog as well, so this unfortunately is not the cause of our issue. Thank you for the quick reply.
    Friday, February 8, 2013 6:02 PM
  • Anyone else have any ideas?
    Sunday, February 10, 2013 9:53 PM
  • Hi, did you find a solutions for this?

    Same problem here.

    Kind regards,

    Geert

    Thursday, May 23, 2013 11:24 AM
  • Please try to put currency field on lead form and then try to qualify. you will not have issue.

    hope this helps.


    Friday, May 24, 2013 11:41 AM
  • Rollup 13 should fix the problem.

    Strange thing is that file conv_lead.aspx was not replaced by an upgraded version of rollup 13.

    We had to manualy copy this file from a clean install + rollup 13/

    Friday, May 24, 2013 11:44 AM