Hi All

We are using siteserver for indexing webpages (asp, html, pdf,xml etc..)

asp pages internally call sql server tables.

But now we are moving our o/s to Windows server 2003, it seems it doesn't
support Siteserver, what should we do now? Should we move to commerce server
(I heard it is bulky and comes with lot of features which we don't want and
very
expensive)?

All we want to do is indexing asp pages.

Can any body recommend alternative fix to our problem.

Any suggestions are greatly appreciated.

Cheers

Lenin

[ Post a follow-up to this message ]

There is a registry hack that allows you to install site server on W2k3. You
will also need to install the ss3w2k patch.

1) rename the  HKLM\System\CurrentControlSet\Services\W
3SVC\ImagePath string
to ImagePathTemp
2) add a new string to "c:\windows\system32\inetsrv\inetinfo.exe"
3) Install Site Server
4) Delete the ImagePath string you added to the registry and rename the
original ImagePathTemp back to ImagePath

Naturally, this is TOTALLY UNSUPPORTED, use at your own risk. I use it for
replication functionality only, which seems to work OK. I know something
else broke (badly) if you tried to use it, but I don't remember which
function.

"Lenin" <Lenin@discussions.microsoft.com> wrote in message
news:5CFA25A0-3896-4772-9FA4-AA22E16AE950@microsoft.com...
> Hi All
>
> We are using siteserver for indexing webpages (asp, html, pdf,xml etc..)
>
> asp pages internally call sql server tables.
>
> But now we are moving our o/s to Windows server 2003, it seems it doesn't
> support Siteserver, what should we do now? Should we move to commerce
server
> (I heard it is bulky and comes with lot of features which we don't want
and
> very
> expensive)?
>
> All we want to do is indexing asp pages.
>
> Can any body recommend alternative fix to our problem.
>
> Any suggestions are greatly appreciated.
>
> Cheers
>
> Lenin
>

[ Post a follow-up to this message ]