Ask the Community
Groups
Object reference not set to the instance of an object - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>This error occurs when using the Replication Catalog</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <p><strong>.NET Framework dependency of our PHD console (management client application)</strong></p> <p>If you encounter the following error when using the Replication Catalog:</p> <p>Object reference not set to the instance of an object</p> <p>And you also find an XML parsing error in the PHD Console log, the machine on which the PHD Console is running may need to have its installation of the .NET Framework updated to .NET Framework 2.0 <strong>SP2</strong>.</p> <p>An example log entry:</p> <p> <em>ERROR 2012-04-02 10:48:51 — <PHDVBAppliance xmlns=''> was not expected.</em>)</p> <p>To check the current .NET Framework service pack version, you can browse the Windows Registry and check the following key: </p> <p>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727\SP</p> <p>Note the absence of a . (dot) in NET Framework Setup above. The above key's value should be:</p> <p> 0x00000002 (2)</p> <p>If it is NOT 2, then install the appropriate update from this link:</p> <p><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fen%2Fdetails.aspx%3Fdisplaylang%3Den%26id%3D1639">http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=1639</a></p> <h4 data-id="caution-from-microsoft-using-the-windows-registry-editor-incorrectly-can-cause-serious-system-wide-problems-that-may-require-you-to-re-install-windows-to-correct-them-microsoft-cannot-guarantee-that-any-problems-resulting-from-the-use-of-the-registry-editor-can-be-solved-use-this-tool-at-your-own-risk">Caution (from Microsoft): Using the Windows Registry Editor incorrectly can cause serious, system-wide problems that may require you to re-install Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of the Registry Editor can be solved. Use this tool at your own risk.</h4> </article> </main>