Different result sets on live and staging environment

From: Marc Hoeijmans (anonymous_at_discussions.microsoft.com)
Date: 02/27/04


Date: Fri, 27 Feb 2004 01:40:24 -0800

Hello I have an MS Indexserver challenge concerning the
return of a different result set on our staging
environment (Win 2000/IIS5.0/IndexServer3.0) and live
environment (Win NT/IIS4.0/IndexServer2.0). Our staging
environment displays the right result set when I query on
custom META-tags.

I have build a news archive page, where you can quick
search (by selecting: All news articles or by selecting a
specific period, e.g. last week, last month, etc.). You
can also use an advanced search, where you can select a
specific news category (sport, information, communication,
etc.) and a month and year.

Problem: When I use the quick search, I get on staging: 32
articles (published in February 2004) displayed in the
result set and on the live environment just 5 articles
(published in February 2004). When I use on both
environments the advanced search and select just February
as Month. The staging environment displays 34 articles
(this is right because two articles are published in 2003
and the rest in 2004), the live environment displays more
articles (34) than with the quick search. This is strange,
because the quick search should display much more items
than just 5. The result set is descending ordered by
ArticleSortDate, the latest article are displayed on top
(feb 2004) and the oldest article (feb 2003) as latest
item in the result set.

Here is the output of some debug code.

Debug code quick seach
<!-- catalog is kluintra -->
<!-- query dialect is 1 -->
<!-- query locale is 1043 -->
<!-- query is @IsArticle =yes -->
<!-- maxrecords is 100 -->
<!-- columns is IsArticle, ArticleSortDate, ArticleIntro,
ContentTitle, vPath, ArticleCategorie, ArticleMonth,
ArticleYear -->
<!-- sortby is ArticleSortDate [d] -->
<!-- scope is /portaal/actueel/nieuws -->

Debug code advanced search
<!-- catalog is kluintra -->
<!-- query locale is 1043 -->
<!-- query is @IsArticle =yes -->
<!-- maxrecords is 100 -->
<!-- columns is IsArticle, ArticleSortDate, ArticleIntro,
ContentTitle, vPath, ArticleCategorie, ArticleMonth,
ArticleYear -->
<!-- sortby is ArticleSortDate [d] -->
<!-- scope is /portaal/actueel/nieuws -->

And here is an example of the META-tags used in the news
articles.
<META name='description' content='Koninklijke Luchtmacht'>
<META name='IsArticle' content='yes'>
<META name='DocumentType' content='Nieuwsbericht'>
<META name='ContentTitle' content='F-16: 30 jaar in de
lucht en 25 jaar bij de KLu'>
<META name='DisplayInDezeRubriek' content='yes'>
<META name='ArticleIntro' content='Eén van de onderwerpen
die aandacht krijgen bij de Open Dagen op 18 en 19 juni op
de vliegbasis Volkel vormt het 25-jarig jubileum van de F-
16 bij de Koninklijke Luchtmacht. Op 7 juni 1979 landde de
J-259 op de vliegbasis Leeuwarden. Wat maar weinig mensen
weten is dat de 'officiële' eerste vlucht van de F-16 in
februari 1974 - dus dertig jaar geleden - plaatsvond en
dat er inmiddels 4.129 F-16's vliegen in liefst 24 landen.
Daarmee is de Fighting Falcon het meest succesvolle
vliegtuig van de laatste decennia.'>
<META name='ArticleSortDate' content='2004/02/23'>
<META name='ArticleMonth' content='2'>
<META name='ArticleYear' content='2004'>
<META name='ArticleCategorie' content='Operationeel'>
<META name='NaamAuteur' content='Sectie
Luchtmachtcommunicatie'>
<META name='EmailAuteur' content='LUCOinfo@mindef.nl'>

Who has any idea of what possible could went wrong. Tips,
tricks and debug directions are more than welcome. Thanks
in advance.

P.s. we are absolutely sure that on both environment use
the some code (copied from staging to live) and have the
same set of documents published (also copied from staging
to live). The only difference is that both environments
have there own catalog and that they use a different
operating-system.



Relevant Pages

  • Re: Use Case Point Estimation
    ... As I understand from other articles this estimate includes: ... actual functional requirement, ... development environment. ... taken risk into account. ...
    (comp.object)
  • RE: Steps to migrate a win2k domain to 2k3
    ... environment is in Mixed mode, move your FSMO roles over and upgrade the other ... years of experience tells me that a test lab is ... > migration, I found there were a lot of little side articles that I'd ...
    (microsoft.public.windows.server.active_directory)
  • Different result sets on live and staging envirionment
    ... 2000/IIS5.0/IndexServer3.0) and live environment (Win ... Our staging environment displays the right ... All news articles or by selecting a specific period, ... live environment just 5 articles. ...
    (microsoft.public.inetserver.indexserver)
  • Re: HP OfficeJet T45 compatability
    ... Do you know anything about the Win 95/98 environment? ... > specific MS articles that may help: ... > Good luck! ... > Taskbar Repair Tool Plus! ...
    (microsoft.public.windowsxp.general)
  • strange behavior of iText across platforms
    ... I do my development on XP using IBM's RAD developer, ... When I move it to our staging server, ... Worked great in my RAD environment; ...
    (comp.text.pdf)