Using Barcode results in poor Console performance or hangs the Console

Article:TECH200552  |  Created: 2012-12-05  |  Updated: 2014-02-06  |  Article URL http://www.symantec.com/docs/TECH200552
Article Type
Technical Solution


Issue



When using Barcode (Home > Service and Asset Management > Barcode), such as trying to access a synchronization profile, the page takes a very long time to load, times out or even causes the Symantec Management Server to hang.


Cause



Various.


Solution



It is difficult to state exactly what may be causing this, other than to suggest that this is caused most likely by environmental issues. For example, if the Symantec Management Platform (SMP) server is under a heavy strain, already performs poorly, or has many jobs that are being processed, SQL deadlocks and timeouts can occur. This can impact other areas of the Console, such as Barcode. Further troubleshooting, such as reviewing the Altiris server logs, should next be performed.

A workaround to helping Barcode perform better is to add its own temporary IIS application pool. The original issue(s), most likely environmental, should still be resolved, however. As these may take awhile by other teams to fix, in the meantime, use Barcode with its own app pool. If this greatly improves performance and stability, then environmental (i.e., non-Barcode-caused issues) are again, the likely culprit.

Instructions for IIS V7.x (Windows Server 2008)
 

  1. On the Symantec Management Platform Server, go into IIS in Windows (Start > Administrative Tools > Internet Information Services (IIS) Manager).
  2. Click to expand the server name.
  3. Right click Application Pools > Add Application Pool.
  4. In the Name field, enter a name for the new app pool, such as "Barcode".
  5. Ensure that the .NET Framework version is "v2.0.50727", which it should be the default.
  6. Change the Managed pipeline mode from Integrated (default) to Classic.
  7. Click on the OK button.
  8. With the new application pool highlighted in the Application Pools window, click on the Advanced Settings action.
  9. Ensure that the .NET Framework Version is set to V2.0 (default).
  10. Ensure that the Managed Pipeline Mode is set to Classic from Integrated (default).
  11. Click on the OK button.
  12. Click on Sites to expand it > Default Web Site > Altiris > Barcode.
  13. Click on Advanced Settings.
  14. Change the Application Pool from the default Classic .NET AppPool (w3wp) to the new one created on step 4.
  15. Click on the OK button.
  16. Click on the next OK button. This completes the changes. If any unforeseen issues occur due to this, these steps can be reverted by simply changing Barcode's app pool back to Classic .NET AppPool; the other instructions will not cause any issues.
  17. Restart IIS. Then, test the issue that Barcode was experiencing. If this is resolved or much better at the least, continue working on resolving the environmental issues with their respective support teams, such as Notification Server technical support.


Instructions for IIS V6 (Windows Server 2003)
 

  1. On the Symantec Management Platform Server, go into IIS in Windows (Start > Administrative Tools > Internet Information Services (IIS) Manager).
  2. Click to expand the server name.
  3. Right click on the Application Pools folder > New > Application Pool.
  4. In the "Application pool ID" field, enter a Name for the new app pool, such as "Barcode".
  5. Click on the OK button.
  6. Click on the Web Sites folder to expand it > Default Web Site > Altiris > Barcode.
  7. Right click on Barcode > Properties.
  8. On the Virtual Directory tab, change the "Application pool" to the new one created on step 4.
  9. Click on the ASP.NET tab.
  10. Ensure that the ASP.NET version is "v2.0.50727", which it should be the default.
  11. Click on the OK button. This completes the changes. If any unforeseen issues occur due to this, these steps can be reverted by simply changing Barcode's app pool back to DefaultAppPool.
  12. Restart IIS. Then, test the issue that Barcode was experiencing. If this is resolved or much better at the least, continue working on resolving the environmental issues with their respective support teams, such as Notification Server technical support.


Related Articles

Barcode sync fails to add new assets
http://www.symantec.com/business/support/index?page=content&id=TECH203704

Trying to sync Barcode assets results in a timeout
http://www.symantec.com/business/support/index?page=content&id=TECH214798




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


Terms of use for this information are found in Legal Notices