VBT.EXE crashes during the Knowledge Script check in process. (NETIQKB47325)

  • 7747325
  • 02-Feb-2007
  • 10-Dec-2010

Environment

NetIQ AppManager 6.x
NetIQ AppManager 7.0.x

Situation

VBT.EXE crashes during the Knowledge Script check in process.
AppManager QDB repository installation reports application events.
Error: 'The exception Privileged instruction. (0xc0000096) occured in the application at location 0x0012fc20.'

Resolution

This error is usually caused by a security corruptiong or a memory configuration conflict. You can adjust the DCOM security setting or you can specify a fixed amount of memory for SQL Server. Plan these changes for a time when you can reboot your SQL Server machine.

To adjust the DCOM security settings:

  1. On the repository server, click Start > Run.
  2. Enter DCOMCNFG.
  3. Expand from the tree in the left pane until you see your server.
  4. Click on your server to display My Computer.
  5. Right-click My Computer and click Properties.
  6. Select the Security tab.
  7. Ensure the Default Access and Launch permissions are set for the Local Administrators group and the Service Account you are using to install AppManager.
  8. Verify that any future NetIQ AppManager Services account as well as the two groups System and Interactive have the same DCOM permissions.
  9. Reboot the machine.

To specify a static or fixed amount of memory for SQL Server:

  1. In SQL Enterprise Manager, expand down to the SQL Server hosting your AppManager repository.
  2. Right-click on the machine name and select Properties.
  3. Select the Memory tab.
  4. Select Use a fixed amount of memory and set the option to approximately half of your available system memory.
  5. Reboot the machine.

Cause

This problem can occur when:

  • An AppManager product had been installed previously.
  • DCOM permissions are corrupted or not specified.
  • Memory related problems are occuring on the machine

Additional Information

Formerly known as NETIQKB47325

Feedback service temporarily unavailable. For content questions or problems, please contact Support.