Recovery Agent could not create the JobQueue COM object

Article:TECH26331  |  Created: 2007-02-13  |  Updated: 2007-03-08  |  Article URL http://www.symantec.com/docs/TECH26331
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.
Article Type
Technical Solution

Issue



The scheduled snapshots fail with the following events logged in the application event log:

Altiris Recovery Solution Error Client UI  43 N/A SNAPSHOT "Error accessing the Recovery Solution Server. Cannot create interface to object.
Local Event Code: 0xc00c002b
System Event Code: 0xc0130052

Altiris Recovery Solution Error Client Files I/O Engine  36 N/A SNAPSHOT "Failed to update the progress dialog.
Local Event Code: 0xc0030024
System Event Code: 0x00000000

Altiris Recovery Solution Error Recovery Agent  55 N/A SNAPSHOT "Recovery Agent could not create the JobQueue COM object.
Local Event Code: 0xc0020037
System Event Code: 0xc0130052


Environment



Recovery Solution 6.2.2332

Cause



Snapshot fails because the snapshot dialog could not be launched due to timeout with the Recovery Solution server

Solution



Hotfix 12 is in the form of AeXRSAgt.exe, AeXRSAView.exe, and AgentRes.dll. These should be applied to the client computer the following way:

  1. Stop the Recovery Agent service on the client computer.
  2. Browse to %Program Files%\Altiris\eXpress\Client Recovery Agent.
  3. Replace the old AeXRSAgt.exe, AeXRSAView.exe and AgentRes.dll with the new AeXRSAgt.exe, AeXRSAView.exe and AgentRes.dll
  4. Restart the Recovery Agent service on the client computer.

The hotfix can also be updated to the Recovery Solution Agent Packages which are located on three locations: one location on the Notification Server and two locations on the Recovery Solution Server.

AeXRSAgt.exe, AeXRSAView.exe and AgentRes.dll should be updated to the Data1.cab (which are present in the Recovery Solution Agent package) which can be modified using the ASPack.exe utility. Whenever a client-side fix is replaced on the client computer, the fix can be updated on the Recovery Solution Agent package so that the next time the Recovery Solution Agent is installed on a new client computer so that the fix is automatically present on the client computer.

The Data1.cab, should be modified on the following locations:

  1. Folder Program Files\Altiris\Notification Server\NSCap\Bin\Win32\X86\Recovery Agent Package located on the Notification Server.
  2. Folder Program Files\Altiris\Recovery Solution\Server\Agent\Install located on the Recovery Solution Server.
  3. Folder Program Files\Altiris\Recovery Solution\Server\Agent\Package located on the Recovery Solution Server.

The fix can be replaced in the Data1.cab the following way:

  1. Use ASPack.exe to modify Recovery Solution Agent package.
  2. Locate ASPack.exe in folder C:\Program Files\Altiris\Recovery Solution\Console\Tools.
  3. Launch ASPack.exe from C:\Program Files\Altiris\Recovery Solution\Console\Tools.
  4. For the Source Package, browse to Program Files\Altiris\Notification Server\NSCap\Bin\Win32\X86\Recovery Agent Package\Data1.cab in ASPack.exe.
  5. Select Action as Modify Package files from the drop-down list and click Start.
  6. After clicking Start, the list of files contained in Data1.cab or AgentSetup.exe will be shown.
  7. Click the Add button and add the new fix.
  8. After the new fix has been added click next and a message will be displayed, “The package has been modified. Press the Finish button to save changes.” Click Finish.
  9. After the package has been saved, continue modifying the Data1.cab or AgentSetup.exe on the other two remaining locations, i.e. Program Files\Altiris\Recovery Solution\Server\Agent\Install and Program Files\Altiris\Recovery Solution\Server\Agent\Package by repeating steps 1 to 8 again.


Legacy ID



32734


Article URL http://www.symantec.com/docs/TECH26331


Terms of use for this information are found in Legal Notices