<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Unable to delete Rack in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/unable-to-delete-rack/m-p/3220343#M1738</link>
    <description>Our SIM suffered the "missing menu items" after discovering a rack and an enclosure that had a blank in their name. When attempting to delete the Rack via the GUI, I get a message that this is a container that contains other systems that are not deleted. This makes sense except that I have now deleted everything except this rack and the CMS server itself. The CMS is a DL380 - so should not stop the rack from being deleted from SIM.&lt;BR /&gt;&lt;BR /&gt;MXNODE returns the CMS and an Internal Error.&lt;BR /&gt; &lt;BR /&gt;The rack and enclosure names have been updated to remove the blanks.&lt;BR /&gt;&lt;BR /&gt;Has anyone experienced something similar?&lt;BR /&gt;</description>
    <pubDate>Tue, 16 Mar 2004 12:21:52 GMT</pubDate>
    <dc:creator>Stephen Daley</dc:creator>
    <dc:date>2004-03-16T12:21:52Z</dc:date>
    <item>
      <title>Unable to delete Rack</title>
      <link>https://community.hpe.com/t5/server-management-systems/unable-to-delete-rack/m-p/3220343#M1738</link>
      <description>Our SIM suffered the "missing menu items" after discovering a rack and an enclosure that had a blank in their name. When attempting to delete the Rack via the GUI, I get a message that this is a container that contains other systems that are not deleted. This makes sense except that I have now deleted everything except this rack and the CMS server itself. The CMS is a DL380 - so should not stop the rack from being deleted from SIM.&lt;BR /&gt;&lt;BR /&gt;MXNODE returns the CMS and an Internal Error.&lt;BR /&gt; &lt;BR /&gt;The rack and enclosure names have been updated to remove the blanks.&lt;BR /&gt;&lt;BR /&gt;Has anyone experienced something similar?&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Mar 2004 12:21:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/unable-to-delete-rack/m-p/3220343#M1738</guid>
      <dc:creator>Stephen Daley</dc:creator>
      <dc:date>2004-03-16T12:21:52Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to delete Rack</title>
      <link>https://community.hpe.com/t5/server-management-systems/unable-to-delete-rack/m-p/3220344#M1739</link>
      <description>Are there any remaining events associated with those deleted systems?</description>
      <pubDate>Tue, 16 Mar 2004 14:04:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/unable-to-delete-rack/m-p/3220344#M1739</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2004-03-16T14:04:42Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to delete Rack</title>
      <link>https://community.hpe.com/t5/server-management-systems/unable-to-delete-rack/m-p/3220345#M1740</link>
      <description>The only events were the initial discovery of the Rack and the CMS.&lt;BR /&gt;&lt;BR /&gt;I have solved the problem by deleting some rogue entries that had been left in the Database. SIM had not deleted all table entries associated with the Enclosure but had removed the device. This explains why the Rack could not be deleted. As soon as I had deleted all references to the Enclosure in the tables, I was able to delete the Rack via the GUI.&lt;BR /&gt;&lt;BR /&gt;All menus are back, devices rediscovered and the system appears to be working again.</description>
      <pubDate>Wed, 17 Mar 2004 12:05:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/unable-to-delete-rack/m-p/3220345#M1740</guid>
      <dc:creator>Stephen Daley</dc:creator>
      <dc:date>2004-03-17T12:05:24Z</dc:date>
    </item>
  </channel>
</rss>

