As you have premium support, I'd file an official support request.
↧
X1 becomes unresposive a few mins after starting
↧
X1 becomes unresposive a few mins after starting
Ever since I purchased the X1 Search Client with Premium Support, it becomes unresponsive after a few minutes of starting.
Thereafter, it will not start again till I do a Windows restart, and then it becomes unresponsive again.
The Windows error details are appended below.
Would appreciate any information to resolve this problem.
Thanks,
Anil Pande
----------------------------------------------------------------------------------------------------------------------------------------------------
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name:AppHangB1
Application Name:X1.exe
Application Version:8.3.1.5028
Application Timestamp:5480afcf
Hang Signature:659f
Hang Type:0
OS Version:6.1.7601.2.1.0.256.48
Locale ID:1033
Additional Hang Signature 1:659fbb6a30ec18bac92901335755dda3
Additional Hang Signature 2:96c9
Additional Hang Signature 3:96c9dd39f46bf397f48986f775696b98
Additional Hang Signature 4:659f
Additional Hang Signature 5:659fbb6a30ec18bac92901335755dda3
Additional Hang Signature 6:96c9
Additional Hang Signature 7:96c9dd39f46bf397f48986f775696b98
Thereafter, it will not start again till I do a Windows restart, and then it becomes unresponsive again.
The Windows error details are appended below.
Would appreciate any information to resolve this problem.
Thanks,
Anil Pande
----------------------------------------------------------------------------------------------------------------------------------------------------
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name:AppHangB1
Application Name:X1.exe
Application Version:8.3.1.5028
Application Timestamp:5480afcf
Hang Signature:659f
Hang Type:0
OS Version:6.1.7601.2.1.0.256.48
Locale ID:1033
Additional Hang Signature 1:659fbb6a30ec18bac92901335755dda3
Additional Hang Signature 2:96c9
Additional Hang Signature 3:96c9dd39f46bf397f48986f775696b98
Additional Hang Signature 4:659f
Additional Hang Signature 5:659fbb6a30ec18bac92901335755dda3
Additional Hang Signature 6:96c9
Additional Hang Signature 7:96c9dd39f46bf397f48986f775696b98
↧
↧
8.3.1.1 5003az x64 "All files up to date" on screen message
Hmm. Ever since I last posted here, I have not seen this phenomenon.
I tried playing around with minimising and maximising, but still I can't provoke message and its ghostly aftermath.
Then again, there is a large hole in my X1 index, where it has forgotten a key folder and shows little sign of indexing it again. Sadly, I have come to expect episodes like that from time to time.
I tried playing around with minimising and maximising, but still I can't provoke message and its ghostly aftermath.
Then again, there is a large hole in my X1 index, where it has forgotten a key folder and shows little sign of indexing it again. Sadly, I have come to expect episodes like that from time to time.
↧
8.3.1.1 5003az x64 "All files up to date" on screen message
I agree. A fairly recent "innovation".
↧
8.3.1.1 5003az x64 "All files up to date" on screen message
Ditto here. Seems to have come in with the last update or two.
↧
↧
8.3.1.1 5003az x64 "All files up to date" on screen message
Ah! I've just made a discovery! If you Quit X1 completely, and then restart it, it starts maximised, and the problem doesn't reoccur.
It seems to only happen on the initial load, after start-up of the PC, if you have opted to "Start X1 Minimised". So I think I have solved it by unticking the "Start X1 Minimised" box in Options.
It seems to only happen on the initial load, after start-up of the PC, if you have opted to "Start X1 Minimised". So I think I have solved it by unticking the "Start X1 Minimised" box in Options.
↧
8.3.1.1 5003az x64 "All files up to date" on screen message
Same for me ![Image]()
When X1 starts, it starts minimised to the tray - and the offending message doesn't show at this point.
But as soon as I "full screen" X1 to use it, the message appears in the top left of my main monitor ("X1 Search: Index is up-to-date"), and won't go away.
It persists even if I close X1 back to the tray, and won't go away until I completely quit X1.
I have Windows 8.1 Enterprise - fully patched.
When X1 starts, it starts minimised to the tray - and the offending message doesn't show at this point.
But as soon as I "full screen" X1 to use it, the message appears in the top left of my main monitor ("X1 Search: Index is up-to-date"), and won't go away.
It persists even if I close X1 back to the tray, and won't go away until I completely quit X1.
I have Windows 8.1 Enterprise - fully patched.
↧
8.3.1.1 Connection with the x1 service has been lost
X1 had been stable for months. Today, it won't run: gives error "Connection with the x1 service has been lost, try a restart." Restart does nothing. Outlook PST corruption issue noted for the earlier versions and recommended PST repair does nothing. So, a new issue. What is the fix?
↧
8.3.1.1 Connection with the x1 service has been lost
Uninstalled X1. Deleted all folders "X1 search". Reinstalled. Problem with Service Not Started fixed.
Now, if X1 folks would fix the bug that gives the ghostly "All Files Indexed" message, I would be happy.
Murray
Now, if X1 folks would fix the bug that gives the ghostly "All Files Indexed" message, I would be happy.
Murray
↧
↧
Problems with X1 Search 8
Here's what I am finding does not work properly in Search 8.3.3.1 Build 5003az: When Search is indexing, it interferes considerably with other running programs. I have a Windows computer with an I7 core CPU and 32 GB of RAM. To now, I have been able to run multiple CPU and memory intensive programs without a hitch: Photoshop, Lightroom, Bridge, InDesign and others all running at the same time with Norton Internet Security running in the background with no problem. Sometimes I have run these programs with Norton antivirus doing a scan or even Norton Ghost doing a backup with no hitch. Yet, whenever Search indexes, I can't run even one of these programs without hiccups: hesitation in opening, saving, temporary freezing, etc. Even Search itself stops running smoothly when it is indexing: it will freeze for a time (several seconds) before it runs again. In addition, I find that, when other programs are showing the above symptoms, and this prompts me to look at Search, I find that Search is alternating frequently between indexing and being up to date. This continues for a while, but if I close down Search and re-open it, it will stop this behavior and remain with the up-to-date message for quite a while until this behavior starts again. If X1 is not indexing, it does not interfere with other programs. I remember, many years ago, that X1 Client had this problem but it was finally solved after several updates. Any suggestions until that happens?
↧
Large files (above 100MB) not being indexed!
X1 Search 8 will index up to 2MB of total text of any given document.
The maximum file size setting determines the total size of files that X1 will attempt to index. This is meant to capture documents that may have other elements such as formatting and images that can drive up the total size of a file. Word documents are a perfect example of file sizes being larger than immediately makes sense for the amount of text they contain.
2MB of text is a lot of text, and we've found this maximum to be more than sufficient for a typical business user's needs.
Yes, you may have documents that have more than 2MB of text, but these generally fall out of the standard business productivity use-case.
You could try splitting up your documents so they can be indexed, but this may be an onerous task depending on the size, formatting, and nature of the document.
I hope this helps explain what you are experiencing.
Thanks!
The maximum file size setting determines the total size of files that X1 will attempt to index. This is meant to capture documents that may have other elements such as formatting and images that can drive up the total size of a file. Word documents are a perfect example of file sizes being larger than immediately makes sense for the amount of text they contain.
2MB of text is a lot of text, and we've found this maximum to be more than sufficient for a typical business user's needs.
Yes, you may have documents that have more than 2MB of text, but these generally fall out of the standard business productivity use-case.
You could try splitting up your documents so they can be indexed, but this may be an onerous task depending on the size, formatting, and nature of the document.
I hope this helps explain what you are experiencing.
Thanks!
↧
Large files (above 100MB) not being indexed!
Yes, confirm this.
In the past I used to scan a lot of old documents and saved them into single PDF's (depending on the subject)
Files often got as big as 300, 400MB. The biggest ones were 500/600MB.
Regretfully they are not bein indexed by X1, even when setting the size to 999MB (under options)
Maybe because it would take too long, or too much CPU resources, I don't know.
However, if that were the case, I guess, maybe users should decide then: they may decide to let X1 run overnight for example.
dtSearch ($199) may be a bit expensive for individuals I guess.
=
In the past I used to scan a lot of old documents and saved them into single PDF's (depending on the subject)
Files often got as big as 300, 400MB. The biggest ones were 500/600MB.
Regretfully they are not bein indexed by X1, even when setting the size to 999MB (under options)
Maybe because it would take too long, or too much CPU resources, I don't know.
However, if that were the case, I guess, maybe users should decide then: they may decide to let X1 run overnight for example.
dtSearch ($199) may be a bit expensive for individuals I guess.
=
↧
Large files (above 100MB) not being indexed!
@kenward
[Off-topic]
Oneliner only: ref yr reply 6 days ago (other forum) : note that Chris confirmed that 7.5 isn't dead but he is he is working on CM8. For obvious reasons I can't write it there.
("No guarantees though" he said, as he is the only one working on it)
-
[Off-topic]
Oneliner only: ref yr reply 6 days ago (other forum) : note that Chris confirmed that 7.5 isn't dead but he is he is working on CM8. For obvious reasons I can't write it there.
("No guarantees though" he said, as he is the only one working on it)
-
↧
↧
Large files (above 100MB) not being indexed!
I have set my max file size for content indexing to "99999 MB". I have selected a folder of TMX files (many of them up to a GB or so in size), and set X1 to index "Everything" in the folder.
I tried using "File names and sizes" and adding ".TMX" and "TMX" to the Specify File Types list, but this didn't work.
Indexing completes way too quickly and most of my TMXs are not indexed.
I also just noticed that other files, large .txt files are not being indexed.
It would appear that X1 isn't indexing anything above 100MB or so. At least that's the largest files I can spot in the results.
What am I doing wrong?
I tried using "File names and sizes" and adding ".TMX" and "TMX" to the Specify File Types list, but this didn't work.
Indexing completes way too quickly and most of my TMXs are not indexed.
I also just noticed that other files, large .txt files are not being indexed.
It would appear that X1 isn't indexing anything above 100MB or so. At least that's the largest files I can spot in the results.
What am I doing wrong?
↧
Large files (above 100MB) not being indexed!
Ha ha, I'm a translator and terminologist and have zillions of huge text files on my computer: TMX, TBX, TXT, CSV, TSV, DIC, AFF, XNL, etc. A 500 MB TMX or a 1GB text file are nothing special in my line of business.
E.g., my translation memory search tool (TMLookup) has an index (actually a SQLite db) containing 45,000,000 "translation units", and the folder on my computer where I store all my glossaries and termbases is 30 GB in size and contains 306,311 files and 152,792 folders. Lots of stuff to index!
So far, the only desktop search tool that can handle all this properly is dtSearch. However, I hate the UI and its expensive, which is why I am testing X1.
E.g., my translation memory search tool (TMLookup) has an index (actually a SQLite db) containing 45,000,000 "translation units", and the folder on my computer where I store all my glossaries and termbases is 30 GB in size and contains 306,311 files and 152,792 folders. Lots of stuff to index!
So far, the only desktop search tool that can handle all this properly is dtSearch. However, I hate the UI and its expensive, which is why I am testing X1.
↧
Large files (above 100MB) not being indexed!
Maybe you need to give X1 a few weeks, months even, to index huge files.
I suspect that the default value is much lower than 99999 MB for a good reason.
What file can possibly be that big?
↧
8.3.1.1 5003az x64 "All files up to date" on screen message
The same with 8.3.2.
↧
↧
Large files (above 100MB) not being indexed!
One strategy for checking this would be to create a saved search for Unindexed files.
You'd need to add the Indexing status column. Then you can use -OK as a filter to weed files that are just fine.
The interesting thing is that files that are too big have no status flag at all. Broken files have a helpful status flag.
In the example cited above, files >100MB would be blank, while something just on the edge would be OK.
Thanks for making me revisit this one. I have now started the task of sorting out dud PDF files.
↧
Large files (above 100MB) not being indexed!
Thanks.
What would be impact when this number would be increased to -say- 6, 8 or 10MB?
Rather than users having to split such big documents into sizes that X1 can handle.
Quite a job trying to split -say- a 400MB document into 5x 80MB as
a. one doesn't know when the (in this example) 80 MB has been reached - one might end up with a document that is slightly above the 100mb
b. a lot of harddisk activities
etc.
What would be impact when this number would be increased to -say- 6, 8 or 10MB?
Rather than users having to split such big documents into sizes that X1 can handle.
Quite a job trying to split -say- a 400MB document into 5x 80MB as
a. one doesn't know when the (in this example) 80 MB has been reached - one might end up with a document that is slightly above the 100mb
b. a lot of harddisk activities
etc.
↧
Large files (above 100MB) not being indexed!
Good news. But he does himself no favours by shutting down the forum and saying nothing to the naysayers.
↧