CRM 4.0 published customizations not showing for hours RRS feed

  • Question

  • When creating customizatons they are taking hours to show. I found a similar thread here that provides a solution to restart IIS, which of course works as a temporary fix but what is the actual issue?


    I found another similar error where the suggestion was to automate resetting the applicatoin pool? Once again, this isn't a solid fix?


    Anyone have any suggestions?

    Event code: 3005 
    Event message: An unhandled exception has occurred. 
    Event time: 5/6/2011 11:26:40 AM 
    Event time (UTC): 5/6/2011 3:26:40 PM 
    Event ID: b00e393196a7427f872bac6dbf0bfb4c 
    Event sequence: 62956 
    Event occurrence: 15 
    Event detail code: 0 
    Application information: 
      Application domain: /LM/W3SVC/2/ROOT-2-129490970702463116 
      Trust level: Full 
      Application Virtual Path: / 
      Application Path: C:\Program Files\Microsoft Dynamics CRM\CRMWeb\ 
      Machine name: CRMSERVER1 
    Process information: 
      Process ID: 5616 
      Process name: w3wp.exe 
    Exception information: 
      Exception type: NullReferenceException 
      Exception message: Object reference not set to an instance of an object. 
    Request information: 
      Request URL: http://crm.TEST.COM/CRM+Test/tools/vieweditor/viewManager.aspx?id={6BD0B8E0-6F46-4DD6-81DD-6D2157DB659C}&entityId={D7910E7E-F377-E011-B033-0019B9EE141F}&default=1 
      Request path: /CRMTest/tools/vieweditor/viewManager.aspx 
      User host address: 
      User: org\end.user 
      Is authenticated: True 
      Authentication Type: Negotiate 
      Thread account name: NT AUTHORITY\NETWORK SERVICE 
    Thread information: 
      Thread ID: 3 
      Thread account name: NT AUTHORITY\NETWORK SERVICE 
      Is impersonating: False 
      Stack trace:  at Microsoft.Crm.Web.Tools.Views.ViewManagerPage.ConfigureForm()
      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)
    Custom event details: 



    Friday, May 6, 2011 7:04 PM

All replies

  • Anyone have any ideas?
    Monday, May 9, 2011 12:12 PM
  • Sounds like a caching issue.  You could try clearing your cache and then accessing the application after the changes are published.

    Regards, Donna

    Monday, May 16, 2011 1:30 AM