Article ID: 282178
Article Last Modified on 10/18/2002
APPLIES TO
- Microsoft Commerce Server 2000 Standard Edition
This article was previously published under Q282178
SYMPTOMS
When you request ads multiple times on a single page, house advertisements are not displayed as expected .
CAUSE
When you use filtering (page group, size, custom filters) to target ads on the site, the AdvertisingNeedOfDelivery component does not set the NeedOfDelivery (NOD) for every ad.
WORKAROUND
Reconfigure the advertising pipeline or pipelines on the site, so that the AdvertisingNeedOfDelivery component is executed before any other filtering or scoring components. Specifically, move the AdvertisingNeedOfDelivery component into the Filter stage before the FilterContent component.
NOTE: After you modify the pipeline, you must restart the application to get the new pipeline out of the IIS cache, and reloaded it from the pipeline file. This is due to IIS caching of the pipeline files.
RESOLUTION
To resolve this problem, obtain the latest service pack for Commerce Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
297216 INFO: How to Obtain the Latest Commerce Server 2000 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Microsoft Commerce Server 2000. This problem was first corrected in Commerce Server 2000 Service Pack 1.
MORE INFORMATION
Every ten seconds, this component sets a flag to "recalculate NOD for all ads on schedule now." The problem is, however, that this component is seeing a filtered view of the ads, so that not all ads get their NOD initialized. If you use a different filter on a subsequent request, then the cached NOD is used.
Keywords: kbbug kbpending KB282178
