Hotfix 35: Recovery Agents cannot see the Recovery Server because ''AeXRSVault'' ISAPI of IIS is under heavy load
|Article:TECH39363|||||Created: 2008-02-19|||||Updated: 2008-02-21|||||Article URL http://www.symantec.com/docs/TECH39363|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
Recovery Solution Agents installed on the client computers are unable to connect to the Recovery Solution Server inspite of the Recovery Solution Server Service is running. The client computers can see the Recovery Server via ping and telnet to port 443.
Rebooting the Recovery Server or restarting IIS are the ways to restore the connection once this occurs.
Recovery Solution 6.2.2332 (6.2 SP1)
Recovery Solution Agents communicate via HTTP(S)
Heavy load on "AeXRSVault" ISAPI of IIS, totally unexpected re-entrance of a HTTP method, has been observed. As a result of re-entrance, there was incorrect reset of "in use" flag of an interface entry item. So the next run of the periodic "DoCleanUp" task tries to release the item, which is actually in use. As a result, a C++ exception (and probably memory corruption) may occur. The C++ exception leads to unfunctional clean up and then to a resource leakage. All of these cause the IIS application pool to hang after awhile.
This issue is resolved by introducing correct interlocked reference counting, so an interface entry item will be released only if there is no references to it. In this scenario, it will work correctly regardless of any assumption of re-entrance and multithreading.
This hotfix can be applied the following way:
- Stop the Recovery Solution Server Service on the Recovery Server.
- Stop Internet Information Services (IIS) Manager.
- Browse to %Program Files%\Altiris\Recovery Solution\Server\HTTPVault directory on the Recovery Solution Server.
- Replace the old RsHttpVault.dll with a new one from attachments*.
- Start Internet Information Services (IIS) Manager.
- Restart the Recovery Solution Server Service.
Note: You may need to grant the local Administrators group full control permissions to the \HTTPVault directory prior to replacing the updated dll.
|Description||Logged in tlndev (Altiris - Talinn) database|
Article URL http://www.symantec.com/docs/TECH39363