|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 9/1/2010
Posts: 136
|
In my Windows program that is generating an index on a set of files by calling AddDocument with a New Documents.PreloadedDocument, I'm getting the following error with some of the files:
Lexicon order ("""".compareTo("""") <= 0)
I'm not sure what this is referring to or whether it is something to be concerned about or should I just ignore it. Can you give any ideas for what I should look at in the files where it's occurring? Thanks!
|
|
|
|
Rank: Advanced Member
Groups: Administrators, Registered
Joined: 8/13/2004
Posts: 2,669
Location: Canada
|
I would be looking for anything unusual in the character set. So perhaps unusual unicode characters. Non English chars should be fine, but perhaps control characters or collapsible characters. If you can narrow it down to a document that always does it, I would be happy to look at it for you. -your feedback is helpful to other users, thank you!
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 9/1/2010
Posts: 136
|
Thanks, Jim! I think that's probably the problem. I'm indexing XML files, and in one that gives the error, when I edit the file in a text editor, it shows a code of "" which I assume is a control character of some sort. In the original I think it was some kind of a footnote indicator. Do I need to scrub these characters out somehow before sending the text to AddDocument, or is there another way to handle this?
|
|
|
|
Rank: Advanced Member
Groups: Administrators, Registered
Joined: 8/13/2004
Posts: 2,669
Location: Canada
|
I tested with a PreloadedDocument containing the character with code '02' which is the 'start of text' control char, and it worked OK - so I'm not sure it is or isn't the problem. If it's straightforward for you to scrub control chars out, then please do that. If you are indexing programmatically, such as using PreloadedDocument and can isolate the problem down somewhat, I would be happy to get the code the produces the problem, and fix it properly in SearchUnit. Thanks -your feedback is helpful to other users, thank you!
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 9/1/2010
Posts: 136
|
I can send you several of the documents that are producing the error. Should I send them by email?
|
|
|
|
Rank: Advanced Member
Groups: Administrators, Registered
Joined: 8/13/2004
Posts: 2,669
Location: Canada
|
Yes please. -your feedback is helpful to other users, thank you!
|
|
|
|
Rank: Advanced Member
Groups: Administrators, Registered
Joined: 8/13/2004
Posts: 2,669
Location: Canada
|
Thanks for the files, I indexed all of them (using the standard indexing, not PreloadedDocument) with the current build and they seemed fine. Can you show me the exact version number of your Keyoti4.SearchEngine.Core.DLL that you're referencing please? I'm wondering if we've fixed it since the version you have. -your feedback is helpful to other users, thank you!
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 9/1/2010
Posts: 136
|
From the file properties of the DLL, it says the file version is 2017.7.18.501.
|
|
|
|
Rank: Advanced Member
Groups: Administrators, Registered
Joined: 8/13/2004
Posts: 2,669
Location: Canada
|
I think this MSI will solve it https://www.dropbox.com/...p-v7-Languages.msi?dl=0
-your feedback is helpful to other users, thank you!
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 9/1/2010
Posts: 136
|
Thanks, Jim! That did the trick. The index generated without any error messages.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 9/1/2010
Posts: 136
|
Jim, I'm posting on this thread because the problem we're having seems to have started since I updated Keyoti on our web server. Every morning, around 3:00 a.m., our primary domain freezes and gives a "service unavailable" (I think HTTP error 503) message. Restarting the server clears up the problem for the rest of the day. Only the one domain freezes; we have several other domains on the same server running the same version of site code, and they never seem to be affected.
In browsing the event log, I came across the following message (which occurs throughout the day, even a few minutes ago):
Event code: 3012
Event message: An error occurred processing a web or script resource request. The requested resource 'fKeyoti4.SearchEngine.Web,2017.7.18.501,,58d9fd2e9ec4dc0e|Keyoti.SearchEngine.Web.ClientFiles.AutoComplete.js' does not exist or there was a problem loading it.
Event time: 6/7/2019 10:10:56 AM
Event time (UTC): 6/7/2019 3:10:56 PM
Event ID: 1ffb7513b0d34d1ab3b7c1fc7448692f
Event sequence: 16208
Event occurrence: 9
Event detail code: 0
I recognize the reference to version 2017.7.18.501 as the previous version; the current version is 2017.7.18.904. I have searched everywhere I can think of on our web server for any residual DLLs for the 501 version but can't find any. All of the Keyoti references in our web.config are to the 904 version.
Do you have any suggestions for how I can find what is generating these messages in the application log?
|
|
|
|
Rank: Advanced Member
Groups: Administrators, Registered
Joined: 8/13/2004
Posts: 2,669
Location: Canada
|
I can't think how SearchUnit would freeze the server, but I can help you figure out the erroneous request, Dan. That request is coming from a WebResource.axd URL. The SearchUnit Web Controls use Javascript that is embedded in the DLL and ASP.NET has a mechanism to get those files out of the DLL. To do it, it generates a URL like /WebResource.axd?....... with a long string of GET params. There is GET parameter that references a specific DLL, in your case it is the older version. So, this could be because: 1. You have hard coded a link to webresource.axd in one of your pages. If you have any links in the source of your site that has webresource.axd, that isn't going to work anymore because it's assembly version specific. Definitely avoid doing that. 2. Something is wrong in the webresource.axd links generated by ASP.NET. You can see if that's true by loading the page with F12 open, and looking at the Network tab. If the webresource.axd URLs are erroring and that is creating errors in the event log like the one above, at that exact time, then the problem is in the URL generation. Let me know please -your feedback is helpful to other users, thank you!
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 9/1/2010
Posts: 136
|
Thanks, Jim! I searched all my code and don't see any hard-coded references to webresource.axd.
I loaded several pages on our site with F12 and the Network tab, but there were no errors displayed. The last time an event of this type was written to the event log was about an hour ago. I also noticed that the messages are warnings, not errors, so this particular problem is probably not causing our one domain to freeze.
|
|
|
|
Rank: Advanced Member
Groups: Administrators, Registered
Joined: 8/13/2004
Posts: 2,669
Location: Canada
|
This might help with the hang, if you find it is anything to do with SearchUnit let me know https://www.leansentry.com/Guide/IIS-AspNet-Hangs-your feedback is helpful to other users, thank you!
|
|
|
