Index server - Sharepoint - migration
Pete McDonald
server 2003/sharepoint?
Do I have to migrate to sharepoint?
I thought sharepoint was backwards compatible
Bottom line I have got some trivial but very important applications
currently running on server 2000 / index server that need to run on server
2003. Can I just tweak a setting, etc? Or do I have to install index server?
(Can I?) Or can I just edit the ASP code to reference some other object that
will provide the same functions as IXSSO?
Please help.
ANY info appreciated.
I have been looking on MS and other sites for info, but short of reading all
the sharepoint dox, I can't see any easy way to glean the answer to my core
question. I don't mind learning sharepoint, but right now, I am most
concerned with insuring I am working in the correct direction as I have no
time to waste.
TIA.
Hilary Cotter
such can be run simultaneously on the same machine. Sharepoint team services
is a different product which only allows you to search within the web
sites - you are really searching the docs stored in the database.
So pick which one you want to use and search with it. You can instantiate
the ixsso components within a web part and search the indexing services
catalogs. Or you can use sharepoint.
Not sure if this answers your question.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pete McDonald" <pmcd...@mcdonaldconsult.com> wrote in message
news:pdTGd.1651$ry.806@fed1read05...
Pete McDonald
"Hilary Cotter" <hilary...@gmail.com> wrote in message
news:emJzlTM$EHA....@TK2MSFTNGP09.phx.gbl...
> sharepoint portal server and indexing services are different products and
> as
> such can be run simultaneously on the same machine.
Its getting close to my question.
The issue is, which I apparently didn't describe well is that I have a
client with some old code running under "index service" not the sharepoint
index server, but the old pre-"site sever" version. This is a document
search application.
Ideally, I would like to use the existing code unchanged on the new system.
I finally found an obscure article microsoft wrote on converting from
siteserver to sharepoint. Based on that article, I can see that I have three
choices.
Re implement using sharepoint. - Far too much work for this client's budget.
Retain a system running 2000/index server, as just an indexing/search
provider. - not too bad, but a dedicated machine sucks.
Or ideally install the old indexing server product under server 2003. - If
this can be done without complicating anything on the new server, it would
be nice.
Any input/pointers appreciated.
Thanks.
Pete
George Cheng [MSFT]
changed much since NTOP.
There is no way to install the old version on 2003.
Thank You
George Cheng
Microsoft Application Center & Index Server Support
Note: This article has no warranties implicit or explicit.
All the content is given on the "as is" basis and the user
takes full responsibility for its use and assumption.
Microsoft Corporation Copyright 2004
All Rights Reserved
--------------------
| From: "Pete McDonald" <pmcd...@mcdonaldconsult.com>
| Newsgroups: microsoft.public.inetserver.indexserver
| References: <pdTGd.1651$ry.806@fed1read05>
<emJzlTM$EHA....@TK2MSFTNGP09.phx.gbl>
| Subject: Re: Index server - Sharepoint - migration
| Lines: 90
| Organization: McDonald Technology Consulting
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <26UGd.1660$ry.410@fed1read05>
| Date: Mon, 17 Jan 2005 11:11:25 -0800
| NNTP-Posting-Host: 68.7.178.230
| X-Complaints-To: ab...@cox.net
| X-Trace: fed1read05 1105989118 68.7.178.230 (Mon, 17 Jan 2005 14:11:58
EST)
| NNTP-Posting-Date: Mon, 17 Jan 2005 14:11:58 EST
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!newsfeed-0.progon.net!progon.net!cox.net!news-xfe
r.cox.net!p01!fed1read05.POSTED!53ab2750!not-for-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.inetserver.indexserver:30760
| X-Tomcat-NG: microsoft.public.inetserver.indexserver
Pete McDonald
""George Cheng [MSFT]"" <GCh...@online.microsoft.com> wrote in message
news:7PGOMEN$EHA....@cpmsftngxa10.phx.gbl...
> Why would you need the old indexing product? Index Server really hasn't
> changed much since NTOP.
Please don't misunderstand my tone in this reply. I am quite frustrated at
the moment, and your answer only served to make it worse. If I misunderstood
you I apologize.
I thought the explanation of why I would want to run the old indexing
product is completely obvious. Code written for it does not work under 2003.
What your point was regarding its rate of change I am not sure...
Is your comment to suggest that there is some way that I can use the older
style code on 2003?
You know, I am a bit rushed, so perhaps I did a poor job of explaining.
Lets try one more time.
I have a CLIENT.
They have a computer system
This client depends on a system based on the old document search
architecture.
They are upgrading to sbs 2003
sbs has many cool new features related to document management, none of which
are relevant since they would have to be customized, and or many employees
trained.
The client would like to continue using the system they had. They only
upgraded the server because they needed to have a more reliable platform,
better support etc. They did not intend to rewrite their document seasrch
software as well.
Coming full circle is there any way to run the older style index server code
with little or no modification on sbs 2003. If not, then I believe you have
answered your own question as well as mine. If it will run, then your
original comment makes sense and my only suggestion would be that it would
have been nice if had offered that information to begin with..
Here is a code fragment that should illustrate the code being used so that
there is no ambiguity.
set session("query") = nothing
set session("recordset") = nothing
nextrecordnumber = 1
set q = server.createobject("ixsso.query")
. . .
set rs = q.createrecordset("nonsequential")
. . .
etc.
It fails and indicates the service is not running.
Thank you.
Hilary Cotter
post the code?
Index Server code should work on newer machines with minor adjustments.
"Pete McDonald" <pmcd...@mcdonaldconsult.com> wrote in message
news:26UGd.1660$ry.410@fed1read05...
George Cheng [MSFT]
Index Server 3.1 Windows 2003.
The only main thing that changed was the default dialect, but that would
not produce the error you are seeing.
Does the mmc search page work?
Thank You
George Cheng
Microsoft Application Center & Index Server Support
Note: This article has no warranties implicit or explicit.
All the content is given on the "as is" basis and the user
takes full responsibility for its use and assumption.
Microsoft Corporation Copyright 2004
All Rights Reserved
--------------------
| From: "Pete McDonald" <pmcd...@mcdonaldconsult.com>
| Newsgroups: microsoft.public.inetserver.indexserver
| References: <pdTGd.1651$ry.806@fed1read05>
<emJzlTM$EHA....@TK2MSFTNGP09.phx.gbl> <26UGd.1660$ry.410@fed1read05>
<7PGOMEN$EHA....@cpmsftngxa10.phx.gbl>
| Subject: Re: Index server - Sharepoint - migration
| Lines: 221
| Organization: McDonald Technology Consulting
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <OzVGd.1674$ry.1099@fed1read05>
| Date: Mon, 17 Jan 2005 12:51:26 -0800
| NNTP-Posting-Host: 68.7.178.230
| X-Complaints-To: ab...@cox.net
| X-Trace: fed1read05 1105995118 68.7.178.230 (Mon, 17 Jan 2005 15:51:58
EST)
| NNTP-Posting-Date: Mon, 17 Jan 2005 15:51:58 EST
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!border1.nntp.dca.gi
ganews.com!nntp.giganews.com!peer01.cox.net!cox.net!news-xfer.cox.net!p01!fe
d1read05.POSTED!53ab2750!not-for-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.inetserver.indexserver:30763
| X-Tomcat-NG: microsoft.public.inetserver.indexserver
Pete McDonald
> If your search code worked with Index Server 2.0 NT4, it should work with
> Index Server 3.1 Windows 2003.
First let me reiterate my apology. You obviously are trying to be helpful.
It just didn't seem that way in my (at the time) warped mind.
Second let me say that is good news, and what I thought until I started
trying to use it.
> The only main thing that changed was the default dialect, but that would
> not produce the error you are seeing.
Hmmm...
> Does the mmc search page work?
Yes. (at least if by mmc search page you mean the help and or other related
fuctions that may be accessed while one is in MMC.
>
> Thank You
No... Rather, thank you...
George Cheng [MSFT]
in the Index Server mmc?
Thank You
George Cheng
Microsoft Application Center & Index Server Support
Note: This article has no warranties implicit or explicit.
All the content is given on the "as is" basis and the user
takes full responsibility for its use and assumption.
Microsoft Corporation Copyright 2004
All Rights Reserved
--------------------
| From: "Pete McDonald" <pmcd...@mcdonaldconsult.com>
| Newsgroups: microsoft.public.inetserver.indexserver
| References: <pdTGd.1651$ry.806@fed1read05>
<emJzlTM$EHA....@TK2MSFTNGP09.phx.gbl> <26UGd.1660$ry.410@fed1read05>
<7PGOMEN$EHA....@cpmsftngxa10.phx.gbl> <OzVGd.1674$ry.1099@fed1read05>
<Ovr7wlN$EHA....@cpmsftngxa10.phx.gbl>
| Subject: Re: Index server - Sharepoint - migration
| Lines: 326
| Organization: McDonald Technology Consulting
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <mgXGd.1684$ry.160@fed1read05>
| Date: Mon, 17 Jan 2005 14:47:14 -0800
| NNTP-Posting-Host: 68.7.178.230
| X-Complaints-To: ab...@cox.net
| X-Trace: fed1read05 1106002066 68.7.178.230 (Mon, 17 Jan 2005 17:47:46
EST)
| NNTP-Posting-Date: Mon, 17 Jan 2005 17:47:46 EST
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!border1.nntp.dca.gi
ganews.com!nntp.giganews.com!peer01.cox.net!cox.net!p01!fed1read05.POSTED!53
ab2750!not-for-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.inetserver.indexserver:30766
Pete McDonald
> So you are able to return results when you run the "query the catalog"
> page
> in the Index Server mmc?
Duh...
I stupidly assumed that the indexing service in sharepoint had subsumed the
functionality of index server 2.0. This compounded itself when I saw the
"service not running message", and could not find a console for index
server. I therefore assumed the error was an indication that I had to refer
to a different service (i.e., sharepoint related) under 2003.
Your question, once I understood the underlying meaning that there was
indeed still a thing called index server allowed me to identify the problem.
I added index server to an mmc console, and found that it was there, but not
running. It was not running because it was disabled. I don't know whether it
was an install option that the guy who built it was unaware of or what, but
once enabled it appears to have started working. I still have to install the
rest of the junk that makes it all work, but the core functionality is now
working and I expect it to all work.
On one hand, I apologize for wasting your time with something I should have
been able to identify myself. OTOH, I am very grateful for the help.
Thank you again.
Best regards.
Pete McDonald
George Cheng [MSFT]
computer management. If Index Server is not checked in Windows Components
the startup status for the service will be disabled, but it will still be
installed.
Thank You
George Cheng
Microsoft Application Center & Index Server Support
Note: This article has no warranties implicit or explicit.
All the content is given on the "as is" basis and the user
takes full responsibility for its use and assumption.
Microsoft Corporation Copyright 2004
All Rights Reserved
--------------------
| From: "Pete McDonald" <pmcd...@mcdonaldconsult.com>
| Newsgroups: microsoft.public.inetserver.indexserver
| References: <pdTGd.1651$ry.806@fed1read05>
<emJzlTM$EHA....@TK2MSFTNGP09.phx.gbl> <26UGd.1660$ry.410@fed1read05>
<7PGOMEN$EHA....@cpmsftngxa10.phx.gbl> <OzVGd.1674$ry.1099@fed1read05>
<Ovr7wlN$EHA....@cpmsftngxa10.phx.gbl> <mgXGd.1684$ry.160@fed1read05>
<gGNsQmO$EHA....@cpmsftngxa10.phx.gbl>
| Subject: Re: Index server - Sharepoint - migration
| Lines: 442
| Organization: McDonald Technology Consulting
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| Message-ID: <4kYGd.1691$ry.580@fed1read05>
| Date: Mon, 17 Jan 2005 15:59:27 -0800
| NNTP-Posting-Host: 68.7.178.230
| X-Complaints-To: ab...@cox.net
| X-Trace: fed1read05 1106006400 68.7.178.230 (Mon, 17 Jan 2005 19:00:00
EST)
| NNTP-Posting-Date: Mon, 17 Jan 2005 19:00:00 EST
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!feed.news.tiscali.de!e
asynet-quince!easynet.net!peer01.cox.net!cox.net!p01!fed1read05.POSTED!53ab2
750!not-for-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.inetserver.indexserver:30768