none
Problems with Custom Code Validation Tool -- Silverlight InitializeError code 2103

    Question

  • I am having some trouble running the custom code validation tool. At this point I have a new org with no custom code or data in it (I was thinking the problem was related to our rather large solution so I created a new org which has nothing in it). Anyway, I import the custom code validation tool into the org and try to run it. Unfortunately, I am simply greeted with a blank white window (due to an exception thrown by Silverlight).

    I have uninstalled/reinstalled Silverlight (both the version 4.0.xxx linked from the page if Silverlight is not installed as well as the most recent version) and no luck. I have also tried using multiple browsers, multiple computers, and reducing all internet security settings to low. Is anybody else having this problem and/or is there anything else I should try?

    This is the exception when I open the error console for the page:

    SCRIPT5022: Unhandled Error in Silverlight Application
    Code: 2103    
    Category: InitializeError       
    Message: 2103 An error has occurred.     
     
    CustomCodeValidationTool.html, line 41 character 13
    Thursday, March 14, 2013 6:56 PM

All replies

  • I'm just stabbing in the dark here:  Are you using SSL to protect the site?

    Dave Berry - MVP Dynamics CRM - http:\\crmentropy.blogspot.com Please follow the forum guidelines when inquiring of the dedicated CRM community for assistance.

    Thursday, March 14, 2013 9:31 PM
    Moderator
  • Thanks for the response! Unfortunately, I do not believe SSL is a factor here. The server is running on a local machine and I am connecting via an http:// connection.

    Something odd to note is that I did actually download the .html file and the linked .xap file directly from browser and tried to run the Silverlight app via the browser as just a local file and ended up with the exact same error message I mentioned above.

    The fact that this occurs on pretty much all computers I've tested this on leads me to believe this is an actual problem with the Silverlight app itself (it was just published a few days ago!). Of course, it could also be a common setting across all computers in my work environment, but at this point I have no idea what to even check.


    • Edited by CaspianB Thursday, March 14, 2013 10:32 PM Fix typos
    Thursday, March 14, 2013 9:47 PM
  • I reproduced it myself, in a virgin, post-UR12 org.  I've picked apart the XAP, and can't see anything particularly wrong with the AssemblyManifest.  The cause generally points to an invalid "Startup Object" for the Silverlight App, generally because of a namespace change.  Either way, seems like something to escalate to Microsoft.

    Dave Berry - MVP Dynamics CRM - http:\\crmentropy.blogspot.com Please follow the forum guidelines when inquiring of the dedicated CRM community for assistance.

    Friday, March 15, 2013 3:40 AM
    Moderator
  • Same trouble running code validation tool.

    In IE and Chrome i get

    Uncaught Error: Unhandled Error in Silverlight Application 
    Code: 2103    
    Category: InitializeError       
    Message: 2103 An error has occurred.
    CustomCodeValidationTool.html:41

    Does anyone have any ideas?

    Friday, March 15, 2013 8:35 AM
  • We burned a support issue with MS on this.  Turns out the tool is unsupported.  But they did give me a link to an older version that seems to work (for now):

    http://pinpoint.microsoft.com/en-us/applications/microsoft-dynamics-crm-2011-custom-code-validation-tool-12884943369

    -JayB

    Friday, March 15, 2013 5:37 PM
  • JBlaeske, thank you. This version works.
    Monday, March 18, 2013 5:10 AM
  • There's a new version 1.0.0.3 of the Custom Code Validation Tool released and available on Microsoft Download: http://www.microsoft.com/en-us/download/details.aspx?id=30151

    Upon my initial tests this one didn't seem to suffer from the same problems as the previous 1.0.0.2 version did.


    Jukka Niiranen - My blog: Surviving CRM - Follow @jukkan on Twitter

    Tuesday, May 14, 2013 7:33 AM