locked
CRM 2011 w3wp.exe SocketException The requested name is valid but no data of the requested type was found at Microsoft.Crm.Web.Workplace.UIXmlDescriptionGenerato RRS feed

  • Question

  • Hi everybody,

    since a week we got several ASP.Net 4.0 Warning on the AppServer and we're not able to configure any new outlook client, which is just a visible consequence of this exception.

    Do you have any idea what could happened and how to solve it?

    We're currently on UR11 and didn't have any problems in the past!

    Thank you in advance!

    Event code: 3005 
    Event message: An unhandled exception has occurred. 
    Event time: 1/14/2014 9:51:05 AM 
    Event time (UTC): 1/14/2014 8:51:05 AM 
    Event ID: 629e91fca18746f69b5d2eb0d9c0e1a5 
    Event sequence: 1059601 
    Event occurrence: 389 
    Event detail code: 0 
     
    Application information: 
        Application domain: /LM/W3SVC/2/ROOT-1-130341185733305174 
        Trust level: Full 
        Application Virtual Path: / 
        Application Path: C:\Program Files\Microsoft Dynamics CRM\CRMWeb\ 
        Machine name: X-S-CRM15 
     
    Process information: 
        Process ID: 4568 
        Process name: w3wp.exe 
        Account name: ARTHREX\gmbh_crmappadmin 
     
    Exception information: 
        Exception type: SocketException 
        Exception message: The requested name is valid, but no data of the requested type was found
       at Microsoft.Crm.Web.Workplace.UIXmlDescriptionGenerator.ConfigureMenus()
       at Microsoft.Crm.Application.Controls.AppUIPage.OnPreRender(EventArgs e)
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

     
     
    Request information: 
        Request URL: http://x-c-crm02:5555/ArthrexFR/_root/getUIXml.aspx?client=OutlookWorkstationClient&online=1&savedCredentials=0&signOutSupported=0&hash=5E-49-C3-88-4E-EF-53-4A-B0-99-60-C2-62-1C-EB-C3 
        Request path: /ArthrexFR/_root/getUIXml.aspx 
        User host address: 192.168.x.x 
        User: ARTHREX\xgueddimi 
        Is authenticated: True 
        Authentication Type: Negotiate 
        Thread account name: ARTHREX\gmbh_crmappadmin 
     
    Thread information: 
        Thread ID: 20 
        Thread account name: ARTHREX\gmbh_crmappadmin 
        Is impersonating: False 
        Stack trace:    at Microsoft.Crm.Web.Workplace.UIXmlDescriptionGenerator.ConfigureMenus()
       at Microsoft.Crm.Application.Controls.AppUIPage.OnPreRender(EventArgs e)
       at System.Web.UI.Control.PreRenderRecursiveInternal()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Tuesday, January 14, 2014 9:28 AM

All replies

  • Hello Tim,

    i have the same exception. Did you find the problem?

    Best regards Michael


    Gruß Michael

    Tuesday, February 4, 2014 9:05 PM
  • Did this start happening after installing rollup 11?  If so, is removing the rollup an option to see if this helps?

    Look in the deployment manager for CRM and make sure that all the orgs are at the same rollup level if you have more than 1 org.

    If you have more than 1 org that is a different rollup level or you attempt to connect the Outlook client to 2 different CRM environments such as DEV and TEST environments where the rollup levels are different, I have seen this not let the Outlook client complete configuration.  You don't want to run mismatched rollup version anywhere with CRM because it could cause unforeseen issues.

    You may want to run a fiddler trace to watch the packets, and run both a CRM server trace and Outlook client trace while trying to configure to see what CRM is having a problem with.


    Jason Peterson

    Wednesday, February 5, 2014 11:12 AM
  • It's fixed in the meantime.
    There was a wrong entry in the HelpServerURL from the ConfigSettings table of the MSCRM_Config DB.
    It pointed to an already deleted server. After updating this to our currently used app server everything works fine:-)
    Wednesday, February 12, 2014 12:27 PM