﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Virtual Hold Users Forum / Virtual Hold / Technical Questions  / Evening Virtual Hold restarts / Latest Posts</title><generator>InstantForum.NET v4.1.4</generator><description>Virtual Hold Users Forum</description><link>http://www.virtualholdforum.com/</link><webMaster>afrazer@virtualhold.com</webMaster><lastBuildDate>Thu, 09 Sep 2010 14:49:48 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Evening Virtual Hold restarts</title><link>http://www.virtualholdforum.com/Topic164-5-1.aspx</link><description>I see that this post was viewed dozens of times, so I'll post the solution: we upgraded physical memory. &lt;/P&gt;&lt;P&gt;We are running version 6.6, and the recommended memory size is 4G. The machine had only 2G RAM, and it was all allocated to SQLServer. It was obvious the evening we went in to upgrade the machine that the problem was memory -- we were there at the usual time the problem happened, and when running Task Manager &amp;gt; Processes and sorting by memory usage it was apparent that the machine didn't have any memory left. It was probably trying to do some sort of scheduled cleanup or backup. The result was transfers, hangups, etc., when we called the server on our test phone number.&lt;/P&gt;&lt;P&gt;Adding 2G solved the problem. There have been no evening restarts for 10 days now.</description><pubDate>Mon, 30 Nov 2009 11:25:09 GMT</pubDate><dc:creator>MarcRobinson</dc:creator></item><item><title>Evening Virtual Hold restarts</title><link>http://www.virtualholdforum.com/Topic164-5-1.aspx</link><description>We're having a problem with VH restarting itself several times a week. We're running version 6.6. I've checked the system logs and looked at the VH logs, but not found much help there. &lt;/P&gt;&lt;P&gt;VH support mentions that the heartbeat gets lost in some cases. &lt;/P&gt;&lt;P&gt;I've noticed that we sometimes see a socket failure between VHTOperationModeService and VHT_QueueManager immediately before the failure.&lt;/P&gt;&lt;P&gt;I've also noticed that less often we see "faulting application VHT_QueuManager.exe" before the failures, with the cause being module ntdll.dll .&lt;/P&gt;&lt;P&gt;The server has only 2G of memory in it, and SQLServer has all that memory reserved for its own use (ouch! -- we plan to fix soon by adding another 2G!), but I don't think this is the root cause. If it were memory, I'd expect the problem to occur at times when VH is actually handling customer calls -- morning. It tends to be idle in the evening.&lt;/P&gt;&lt;P&gt;Curiously, the failures occur the large majority of the time between 20:30 and 22:00 in the evening.&lt;/P&gt;&lt;P&gt;We've excluded everything from virus scans that might be used by VH, and we are not doing backups at that time of evening.&lt;/P&gt;&lt;P&gt;I'm pretty much out of ideas at the moment and will appreciate any suggestions from more experienced hands. I'm new to VH.</description><pubDate>Tue, 10 Nov 2009 11:56:54 GMT</pubDate><dc:creator>MarcRobinson</dc:creator></item></channel></rss>