[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1267
  • Last Modified:

Microsoft CRM 3.0, Object refernce not set to an instance of an object

Steps done to create error message :

Logged into CRM as admin. Clicked on Settings, Customization, Customize Entities, (x2 click) Opportunity
New Window pops up.
Click on Attributes, (x2 click) actualclosedate (or any attribute listed) and receive this error:

Microsoft CRM Unhandled Error Details:
Server Error in '/' Application.

Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
   Microsoft.Crm.Web.Tools.SystemCustomization.Attributes.ManageAttributePage.ConfigureSchemaSection(AttributeInfo attributeInfo) +593
   Microsoft.Crm.Web.Tools.SystemCustomization.Attributes.ManageAttributePage.ConfigureControls() +76
   Microsoft.Crm.Web.Tools.SystemCustomization.Attributes.ManageAttributePage.ConfigurePage() +884
   Microsoft.Crm.Application.Controls.AppPage.OnPreRender(EventArgs e) +20
   System.Web.UI.Control.PreRenderRecursiveInternal() +62
   System.Web.UI.Page.ProcessRequestMain() +1499

I found this Microsoft article http://support.microsoft.com/kb/934690  and followed the instructions. We did not however have this file (Microsoft.crm.MetadataService) as they said we would.  Reset IIS and error still  appears.

System is SBS 2003 Premium

Thanks in advance.
1 Solution
glennwarnerAuthor Commented:
After contacting Microsoft, they suggest we verify that Rollup 2 Update was indeed installed. After re-installing the update on the , we had to reinstall the updates on the clients and clear the cache. Error went away and all works as expected.

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now