<?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 Re: Attempting to populate VCRM in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289770#M34905</link>
    <description>I would not trust VCRM working on a virtual machine. So much of how VCRM work relies on the system management homepage SMHP and the insight agents IMA .&lt;BR /&gt;&lt;BR /&gt;Stick it on a 300,400,500,600,700 series proliant. Its only a fileshare so shouldn't really affect anything. But it does like SMHP and IMA around.</description>
    <pubDate>Mon, 20 Oct 2008 12:32:18 GMT</pubDate>
    <dc:creator>Adrian Clint</dc:creator>
    <dc:date>2008-10-20T12:32:18Z</dc:date>
    <item>
      <title>Attempting to populate VCRM</title>
      <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289766#M34901</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I have had a problem updating the VCRM on my Insight server, when I go to Tools, and select Version Control Repository Manager, and I select my VCRM server, (which is trusted, and has it listed as trust by certificate), I get the following error for Contents of Version Control Repository:&lt;BR /&gt;&lt;BR /&gt;Error retrieving repository. Ensure the Version Control Repository Manager (VCRM) is installed and running. Be sure a trust relationship is established with the repository device. Finally, the VCRM may not respond if it is in the process of updating its catalog. In this case simply try again later. &lt;BR /&gt;&lt;BR /&gt;-&lt;BR /&gt;&lt;BR /&gt;I have seen a thread on here where a person has had to go and move their repository, and it worked, but I found after rebooting, you have to move it, this has gotten very frustrating for me. &lt;BR /&gt;&lt;BR /&gt;I've reinstalled VCRM several times and as well, the latest HP SIM is loaded on the server, (HP SIM 5.0 SP2)&lt;BR /&gt;&lt;BR /&gt;The VCRM is on a Vmware server, the virtual is using windows 2003 R2 32 bit OS&lt;BR /&gt;&lt;BR /&gt;Thank you</description>
      <pubDate>Sun, 19 Oct 2008 01:46:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289766#M34901</guid>
      <dc:creator>InsightBlues</dc:creator>
      <dc:date>2008-10-19T01:46:58Z</dc:date>
    </item>
    <item>
      <title>Re: Attempting to populate VCRM</title>
      <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289767#M34902</link>
      <description>Latest SIM is 5.2 SP2</description>
      <pubDate>Mon, 20 Oct 2008 07:51:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289767#M34902</guid>
      <dc:creator>Maxim Revutskiy</dc:creator>
      <dc:date>2008-10-20T07:51:16Z</dc:date>
    </item>
    <item>
      <title>Re: Attempting to populate VCRM</title>
      <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289768#M34903</link>
      <description>I meant 5.2 SP2</description>
      <pubDate>Mon, 20 Oct 2008 11:57:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289768#M34903</guid>
      <dc:creator>InsightBlues</dc:creator>
      <dc:date>2008-10-20T11:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: Attempting to populate VCRM</title>
      <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289769#M34904</link>
      <description>Also, this is a the thread I am referring to, and this is not an acceptable solution because it will break again:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1224507755648+28353475&amp;amp;threadId=1205765" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1224507755648+28353475&amp;amp;threadId=1205765&lt;/A&gt;</description>
      <pubDate>Mon, 20 Oct 2008 12:04:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289769#M34904</guid>
      <dc:creator>InsightBlues</dc:creator>
      <dc:date>2008-10-20T12:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: Attempting to populate VCRM</title>
      <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289770#M34905</link>
      <description>I would not trust VCRM working on a virtual machine. So much of how VCRM work relies on the system management homepage SMHP and the insight agents IMA .&lt;BR /&gt;&lt;BR /&gt;Stick it on a 300,400,500,600,700 series proliant. Its only a fileshare so shouldn't really affect anything. But it does like SMHP and IMA around.</description>
      <pubDate>Mon, 20 Oct 2008 12:32:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289770#M34905</guid>
      <dc:creator>Adrian Clint</dc:creator>
      <dc:date>2008-10-20T12:32:18Z</dc:date>
    </item>
    <item>
      <title>Re: Attempting to populate VCRM</title>
      <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289771#M34906</link>
      <description>I just did that, placing the repository on another machine, it does work, but I don't know for how long..</description>
      <pubDate>Mon, 20 Oct 2008 16:20:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289771#M34906</guid>
      <dc:creator>InsightBlues</dc:creator>
      <dc:date>2008-10-20T16:20:40Z</dc:date>
    </item>
    <item>
      <title>Re: Attempting to populate VCRM</title>
      <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289772#M34907</link>
      <description>I've got HPSIM and the VCRM on the same virtual server and they work fine. That does have an SMH as installed by HPSIM.&lt;BR /&gt;&lt;BR /&gt;For VCA Access to the VCRM I've always set up a local account on the VCRM Server and used that for access.&lt;BR /&gt;&lt;BR /&gt;There also needs to be a Trust Relationship established for things to work.&lt;BR /&gt;Any reason why you want the VCRM on a server separate from the HPSIM Server?</description>
      <pubDate>Tue, 21 Oct 2008 05:45:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289772#M34907</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2008-10-21T05:45:01Z</dc:date>
    </item>
    <item>
      <title>Re: Attempting to populate VCRM</title>
      <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289773#M34908</link>
      <description>It's ok it run the VCRM in a VM - It's supported.&lt;BR /&gt;&lt;BR /&gt;Using more than one VCRM is a good idea if you have a slow WAN - this was you can point the VCA to a local VCRM.&lt;BR /&gt;&lt;BR /&gt;I suspect that ig you go to the SMH and select VCRM it works fine however when you try to go to it from SIM you die.&lt;BR /&gt;&lt;BR /&gt;If you have a lot of items in your repositoy it SIM will give up on it and assume it can't talk to it...tell SIM to wait a bit longer so....&lt;BR /&gt;&lt;BR /&gt;You have a very large repository and / or a slow VCRM. &lt;BR /&gt;&lt;BR /&gt;By default SIM only waits 15 seconds to retrieve all the VCRM data which is very commonly not enough time&lt;BR /&gt;&lt;BR /&gt;The fix is to edit globalsettings.props&lt;BR /&gt;http_request_timeout=15   change to 60&lt;BR /&gt;&lt;BR /&gt;Run mxconfigrefresh and your problem should be resolved.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Oct 2008 18:08:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/4289773#M34908</guid>
      <dc:creator>Gordon Leonard</dc:creator>
      <dc:date>2008-10-21T18:08:05Z</dc:date>
    </item>
    <item>
      <title>Re: Attempting to populate VCRM</title>
      <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/5784705#M54497</link>
      <description>&lt;P&gt;I am running SIM &amp;amp; VCRM on same VM and changing this setting resolved issue for me.&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/793655"&gt;@Gordon Leonard&lt;/a&gt; wrote:&lt;BR /&gt;&lt;BR /&gt;The fix is to edit globalsettings.props&lt;BR /&gt;http_request_timeout=15 change to 60&lt;BR /&gt;&lt;BR /&gt;Run mxconfigrefresh and your problem should be resolved.&lt;BR /&gt;&lt;BR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Aug 2012 21:45:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/5784705#M54497</guid>
      <dc:creator>Martin2000</dc:creator>
      <dc:date>2012-08-29T21:45:53Z</dc:date>
    </item>
    <item>
      <title>Re: Attempting to populate VCRM</title>
      <link>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/6258597#M57623</link>
      <description>&lt;P&gt;I tried several different values, up to 270, and it still didn't work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a last resort I put in '600'.&amp;nbsp; But I did it for both "http_request_timeout" and ALSO for "VCRM_timeout".&amp;nbsp; Anyway, that worked.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Nov 2013 19:31:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/attempting-to-populate-vcrm/m-p/6258597#M57623</guid>
      <dc:creator>TrevorT</dc:creator>
      <dc:date>2013-11-04T19:31:08Z</dc:date>
    </item>
  </channel>
</rss>

