"Nguyen Tran" <wintran@gmail.com> wrote in message
news:ccb54238.0409141210.73b906de@posting.google.com...
> John,
>
> I looked into the logs. I think I found the problem. There seems to
> be a space after the file type column. The document table has a
> FileType of varchar(4) and the staging table had a FileType of
> char(4). That's where the extra space come from. I have trimmed the
> space and the search works now.
>
> Thanks for all your help.
>
> -Nguyen Tran
>
> "John Kane" <jt-kane@comcast.net> wrote in message
news:<erYXJIfmEHA.536@TK2MSFTNGP11.phx.gbl>...
> > Nguyen Tran,
> > Yes. How exactly are you "... post[ing] the data from the staging table
into
> > [your] permanent document table"? As do you have "Change Tracking" with
> > "Update Index in Background" enabled for your permanent document table,
and
> > depending upon how (BCP, BULK INSERT, etc.) you are posting or
transferring
> > the documents, the binary bits may not be copied exactly as they should.
> >
> > Could you also review your server's Application event log for any
"Microsoft
> > Search" or MssCi source event errors, warnings or informational
messages?
> > Basically, if the internal structure of the document is not maintained
> > exactly, then the MSSearch daemon will not correctly recognize the data
in
> > the IMAGE column as a true MS Word, Adobe PDF file etc. Also, if
possible,
> > could you forward to me a copy (dummy one) that you posted or
transferred
> > via the above means that is has been extracted from the image column.
This
> > file can then be examined to determine if &/or what may be the problem.
> >
> > Thanks,
> > John
> >