Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
3.x, 4.x | |
Platform |
||
Operating system |
W2K Server |
|
|
|
||
Error |
SAV Event ID 1005: could not scan file due to low kernel stack Dblhook Event ID: 8196: The maximum amount of memory for replication queuing has been reached. Replication is stopped and memory is being freed. |
|
|
|
||
Symptoms |
The Tertiary (source) freezes from time to time, when DT and Symantec are active at the same time. |
|
|
|
||
Cause |
There are SAV versions that consume a lot of kernel memory. Since there is only a fixed amount of kernel memory in a system, a misbehaving kernel driver may use up the kernel memory and cause the server to be sluggish or freeze up. | |
|
|
||
Solution |
1. Install Symantec Antivirus Corporate Edition v10.1.5 or higher. Symantec Antivirus Corporate edition version 10.1.5 or higher resolves the Event ID 1005. As of this writing, the version posted in symantec site is 10.1.6.6000. The customer's copy of SAV may be elligible for s/w updates. Go to http://fileconnect.symantec.com. Enter the SAV serial number. If it is authenticated, the available upgrades will be listed. For more info on Event 1005, refer to http://entkb.symantec.com/security/output/n2002071208532048.html. You may need to apply the workaround in that article if the latest version of SAV did not fix the Event 1005. 2. Move the DoubleTake Disk queue to a physical disk that is not a source. In a tertiary server, the Disk queue can be moved to a drive other than the RAID. 3. Exclude Doubletake.exe and the disk queue folder from real time antivirus scan. 4. Increase the memory queue used by DoubleTake, but make sure that system available memory is at least 512MB. Set or add the following registry values: HKLM\System\CurrentControlSet\Services\Dblhook\Parameters\DisableGateway(DWORD) = 1 5. Check if SystemPages is set too high as per http://www.microsoft.com/technet/prodtechnol/exchange/Analyzer/644410c7-3620-452d-b4b7-37ba368c30de.mspx?mfr=true . If it is, set the following registry value: For W2K Server: HKLM\System\CurrentControlSet\Session Manager\Memory Management\SystemPages = 31000 (decimal) For W2K3 Server: HKLM\System\CurrentControlSet\Session Manager\Memory Management\SystemPages = 0 6. Check the event log if the server is experiencing the problem discussed in http://support.microsoft.com/kb/312362/en-us. If it is, set the PoolUsageMaximum to 40 (decimal) 7. Reboot the server. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
EPM, Windows 2000, administrator |
|
|
|
||
Technical contact(s) |
Philip Samaniego |
|
Submitted by |
Philip Samaniego |
|
Date submitted |
30 May 2007 |
|