Video Screencast Help

If anybody has a document on "Manual configuration of the Application Pools" for CMS 7.0 (IIS 6),please share

Created: 26 Apr 2013 | 4 comments

If anybody has a document on "Manual configuration of the Application Pools" for CMS 7.0 (IIS 6),please share

Operating Systems:

Comments 4 CommentsJump to latest comment

andykn101's picture

The original discussion appears to have been deleted, I think there's too many issues around reverting it for upgrades.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

HighTower's picture

This is part of a comment that was posted in the original thread.  Shortly after both the KB and Connect articles were taken down:

There are risks with separating app pools.  Some of these have only been encountered as customers have split app pools and have encountered issues that later were diagnosed to be related to the App Pool separation. 

Risk 1:

I mentioned earlier, ITMS maintains several caches in this memory space.  Some of these caches have made assumptions that there is only once.  By spinning some apps into their own AppPools, some of these caches have been duplicated.  This has resulted in issues keeping the caches in Sync or issues from not being in sync.  Some of the symptoms of this have been degradation of throughput over time until IIS is restarted or recycled.

Risk 2:

User web applications of ITMS leverage ASP.Net Application and Session state.  Some pages embed controls, pages, content, etc from “registered” solutions.  When the web applications are moved, it can impact the dynamic loading and references to such state information.  This may not always be readily apparent because of asynchronous requests or impact to isolated areas of functionality (such as report customizations, data class customizations, customized views, etc).  It may depend on what solutions you have installed and what pages, controls, or ITMS items those solutions have created, used, or extended.  Often, this may be visible to the user as random state errors in parts of the UI affected by the split.  It may also be manifest in IIS logs that report an increase in HTTP request errors.

Risk 3:

Since ITMS and all solutions (including 3rd parties) expect one web application; direct calls, configurations or other interactions may fail during a given solution install or even in the Symantec Management Platform itself.  This can prevent required changes from being applied.  This is why, even in this forum discussion, there is attention given to “reverting the split.”  It is necessary to revert when installing new solutions, upgrading any solution, applying any service pack, or even applying most hot fixes that perform configuration.  As a result, this becomes a management burden that may be mistakenly forgotten…especially if ITMS administration changes hands.  Tight change control needs to be followed.

Due to these risks, separating app pools is often discouraged as a first phase attack at tuning.  Rather, understanding what is causing the need to split and remediating the cause is the preferred solution.

Bottom line is that Symantec does not currently recommend it and does not want their customers to make this change.

arpita bhadra's picture

I was planning to test it in a TEST setp,before applying to production setup.Only if I do not face any issues in the test setup,I shall apply the same to production

.I am facing too many issues when application shows that server is busy.It resumes working only when App pool/iis is restarted .There are times when App pool stops on its own resulting to unavailability of the application completely.That is why I wanted to try out with the application spliiting .

Please suggest if any alternative available.

HighTower's picture

Are you up to date?  Current version of CMS is 7.1 SP2 MP1 Rollup 4.

Have you contacted Support?