Hi, 1. It is more of some character issue in the document. Unless you fix that character, The indexing fails again and again.
2. Sometimes because of heavy load on liveserver, the documents are not sent properly to verity search engine. So indexing fails for many documents. I have 2 LiveServers installed. One on Win Server : here Indexing fails for almost 10-20% of the documents. This happens when i try to upload like 50-100 and more files in one go. What i do is i parse the syslog.info file and upload them again. That way i get less indexing errors and then reeat it again.This is only for our internal testing/Learning purposes. If i upload like 5-10 files in one go, Very less indexing errors occurs. The other is RedHat Linux : Here i never faced indexing issues and even though we face it is very rare. Here if indexing fails for the first time then it fails everytime. SInce our production environment is this, We face less issues with indexing, But if we get one its difficult to spot which character and where etc stuff. I don't think OS is the issue. But it definitely depends on the hardware config. I suggest uploading failed docs again. If the indexing fails then too, You must modify the file to remove such characters. Only OpenText and Verity must be able to Pinpoint to the exact error. Please do reply me if you get any such resolution/Fix from them. Just to add, We didn't create any OT Ticket. We will be going live with about 300,000 documents in a week or so. I will then look into how to fix this issue just in case if we have any.Currently we uploaded 1000 files in one go to LiveServer for indexing and there were no indexing errors. We are just hoping it happens for all the remaining files also. Regards, Rakesh. On Fri, Oct 23, 2009 at 4:16 PM, Andy Rubio <[email protected]> wrote: > > Hi Rakesh, > > We're getting exactly this problem too! It seems to have Open Text's > engineers stumped. > > Have you opened a ticket with them? > Has the problem been resolved? > > We're getting pretty desperate for a solution here. > > Regards, > Andy > > On Oct 4, 3:06 pm, Eric Koleda <[email protected]> wrote: > > Hi Rakesh, > > > > Were you looking at the XML content as seen from the LS interface? If > > so, try loading the XML from the same URL that was reported in the > > error (this is howVerityloads it). It may be returning slightly > > different content. > > > > Best, > > - Eric > > > > On Sep 14, 2:31 pm, rakesh kumar jalla <[email protected]> wrote: > > > > > Hi, > > > > > We are using RedDot LiveServer which usesveritysearch engine Version > 6.1.1 > > > to index files. > > > Lately we see some errors in syslog.info file and cant figure out what > it > > > means. > > > > > This is the entry in log file : > > > > > Mon Sep 14 01:05:01 2009 > > > msg(1): Error E0-1514 (Drvr): TstrIOFilter:flt_xml: XML parser > callback() > > > - not well-formed at line 57, pos 3042 > > > Mon Sep 14 01:05:01 2009 > > > msg(1): Warn E2-0527 (Document Index): Document 79 ( > http://127.0.0.1:8080/cps/rde/xsearchengine?prjID=cnw&cntID=News%2f20... > > > Stream error (-2) - SKIPPING > > > > > Even though the line 57 of the document has only 23 characters,here it > shows > > > not well formed at line 57, pos 3042. > > > > > Checked for the xml validation on w3c.org and it showed no errors. > > > > > Would be grateful if anyone can throw some light into why this is > happening. > > > > > Thanks, > > > Regards, > > > Rakesh. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en -~----------~----~----~----~------~----~------~--~---
