Here is what we have...
.NET server (release candidate) running Index Server...
We have recently installed the microsoft updates... friday
and on saturday (am) we were no longer able to query the index... When I came in on monday I was getting this error:
CreateRecordset error 'c0041800'
The content index is corrupt.
I was informed that the catalog was indeed corupt and I needed to rebuild it.
Question #1. In the future... can I just cpoy over the catalog.wci folder/contents to another machine, then copy it back over if there is a similar problem in the future instead of having to rebuild the catalog?
Researching this error on MicroSoft, they way it could be a possible Hardware failure, or an abrupt shutdown may have occured (or power failure).
In the process of running Index Server, we were doing some Perl commands, and Installs (Active State) on friday... Would this cause the problem? I know it shouldn't, but we are infact running a .NET release candidate.
Also, Windows updates have been run around that time.... Myself personaly I wouldn't do the updates unless it was crucial... Am I correct on this?
Thanks so much
.NET server (release candidate) running Index Server...
We have recently installed the microsoft updates... friday
and on saturday (am) we were no longer able to query the index... When I came in on monday I was getting this error:
CreateRecordset error 'c0041800'
The content index is corrupt.
I was informed that the catalog was indeed corupt and I needed to rebuild it.
Question #1. In the future... can I just cpoy over the catalog.wci folder/contents to another machine, then copy it back over if there is a similar problem in the future instead of having to rebuild the catalog?
Researching this error on MicroSoft, they way it could be a possible Hardware failure, or an abrupt shutdown may have occured (or power failure).
In the process of running Index Server, we were doing some Perl commands, and Installs (Active State) on friday... Would this cause the problem? I know it shouldn't, but we are infact running a .NET release candidate.
Also, Windows updates have been run around that time.... Myself personaly I wouldn't do the updates unless it was crucial... Am I correct on this?
Thanks so much