Quantcast
Channel: X1 Discussion - All Topics
Viewing all 8513 articles
Browse latest View live

X1 Search 8.6 Release - Build 6003ch

$
0
0
At the suggestion of X1 tech support, I did a clean uninstall of X1 and reinstalled it. That solved the problem for me. Here are the instructions I was given, but you should confirm that this will work for you by contacting tech support. You will need your license ID and password to do the new installation. As always, be sure to set a restore point before doing anything that involves your computer's registry.

PREREQUISITE:

If you can launch the X1 interface go to Menu > License and Deactivate your current license activation.

- UNINSTALL

1. Access Control Panel > Programs & Features.

2. Uninstall X1 Search. When prompted, opt NOT to save your X1 settings.

3. Check the following locations for remaining X1 Search files, and delete them:

- C:\Users\<username>\AppData\Local\X1 Search - this is the default location of the X1 Search data directory.
- C:\Program Files\X1 Search - this is the install location of the X1 program files.
- C:\Program Files (x86)\X1 Search - this is the install location of the X1 program files on a 64-bit operating system, running a 32-bit version of Outlook.

NOTE: You may find an X1 Search directory under C:\ProgramData\. You do NOT need to delete this directory.

4. Click Start > Run > Regedit or click your Windows Logo Key + R to launch regedit.exe and delete the X1 Search registry keys found in any of the following locations:

- HKEY_CURRENT_USER\Software\X1 Search
- HKEY_CURRENT_USER\Software\Wow6432Node\X1 Search
- HKEY_LOCAL_MACHINE\Software\X1 Search
- HKEY_LOCAL_MACHINE\Software\Wow6432Node\X1 Search

- FRESH INSTALL

1. Perform a fresh install of X1 Search 8 by launching the X1Searchsetup.exe found here: http://download.x1.com/downloads/pro/X1SearchSetup.exe

X1 Search 8.6 Release - Build 6003ch

$
0
0
SoCalScott wrote:
Quote:cscott wrote:If we can't get you up and running on 8.6, we'll roll you back to the previous version, however the checkbox in the "Options" window to disable all future automatic update checks is specific to 8.6, so you'll be prompted to upgrade from time to time.


Can you tell us how to do this so we can get up and running again while X1 figures out what's wrong with the update?

Thanks!

Do you have a Windows restore point that predates the X1 "upgrade"?

File names within ZIP mangled

$
0
0
X1 Search 8.5.2 6001si (64-bit) on Windows 10

When my search matches files inside a .ZIP file, the names of the matching files usually have additional characters appended. These always seem to be 8 alphanumerics followed by dot "." and 3 more alphanumerics.

Example files and the filename shown in the "Name" column:
    OposSOInfo.rc => OposSOInfo.rcvujxbjdh.ala
    OposSOInfo.cpp => OposSOInfo.cpp2qxh2kxb.a53
    resource.h => resource.htxupxos1.plm
This makes it impossible for me to refine the search based on "Type" column, which I did quite often with my previous X1 6.7.4 (which didn't have this issue - plus was faster Image ).

(I think that this is similar to part of the bug report "Not previewing content of ZIP files" by diesis. Dec 26, 2017 12:03 pm)

File names within ZIP mangled

$
0
0
I installed X1 Search 8.6 6003ch (64-bit) on 3/14, and am pleased to report that this issue is resolved! (In my limited testing thus far.)

In addition, the display of name vs. path is much cleaner. Repeating the example from my 2/28 post in this thread:

If "C:\Dir1\Dir2\Zfile1.zip" contains "Dir3\Dir4\Zfile2.zip" which contains "Dir5\Dir6\Filename.txt", then the line for Filename.txt showed this with 8.5.2 (where mangledx.ext was a seemingly random 8.3 string):
- Path column: C:\Dir1\Dir2\Zfile1.zip\Dir3\Dir4\Zfile2.zip
- Name column: Dir3/Dir4/Zfile2.zipmangledx.ext\Dir5\Dir6\Filename.txt

But with 8.6, it shows this much better result:
- Path column: C:\Dir1\Dir2\Zfile1.zip\Dir3\Dir4\Zfile2.zip\Dir5\Dir6
- Name column: Filename.txt

Thank you!

File names within ZIP mangled

$
0
0
Thanks for your interest in this.
I have emailed you 2 sample ZIP files plus screenshots of how they appear on my system.
- Curtiss

File names within ZIP mangled

$
0
0
Hi,

If a file is not too large, can you try to send it to jogy at x1dev dot com?

Jogy

File names within ZIP mangled

$
0
0
Cơ hội đầu tư BĐS hiệu quả với nhiều chính sách ưu đãi:
[size=4][size=4]6th element[/size][/size]
Giá bán chỉ từ 34 triệu/m2 (VAT + full nội thất cao cấp)
CĂN HỘ ĐẲNG CẤP – SỞ HỮU VỊ TRÍ VÀNG – KÝ HĐMB TRỰC TIẾP CĐT
Golden Park
THỦ TỤC LINH HOẠT – DỄ DÀNG – NHANH CHÓNG

File names within ZIP mangled

$
0
0
As my initial file indexing continued, I realized a second and very important (to me) effect of the mangling of file extensions with a ZIP file:
>> The file contents are not indexed, because the extension doesn't match an indexed extension.
Since I have many old projects in ZIP files (and only in ZIP files), I no longer can find those that referenced search terms within them.

File names within ZIP mangled

$
0
0
It happens on all ZIP files with a .zip or .zipx extension. (Most of the .zip files were created by the old command line zip.exe 2.2 by Mark Adler et al, while the .zipx are by WinZip 19.5.) My index shows 4725 .zip files, of which 69 are .zipx.

The only exceptions that I have found are:

(1) .zip files without a .zip extension: I sometimes rename a file to save old copies, so I found a couple cases of files such as "xxx.zip.000" where the filenames that it contains are shown correctly, without the seemingly random 8.3 characters added.

(2) .zip files within a .zip file: For these cases, the name of the second .zip file is mangled but its file name is not. Example to show to pattern that I see:
If "C:\Dir1\Dir2\Zfile1.zip" contains "Dir3\Dir4\Zfile2.zip" which contains "Dir5\Dir6\Filename.txt", then the line for Filename.txt will show this (where mangledx.ext is a seemingly random 8.3 string):
- Path column: C:\Dir1\Dir2\Zfile1.zip\Dir3\Dir4\Zfile2.zip
- Name column: Dir3/Dir4/Zfile2.zipmangledx.ext\Dir5\Dir6\Filename.txt

Please let me know if I should upload a couple sample files (e.g. to Dropbox) or if there are any diagnostic files that would be helpful. And whether to post them here or to a private location.

Note: After posting my response "the file contents are not indexed", I changed the indexing options for many of my directories to "Everything (all files)" from "File names and sizes, plus content for specified extensions)". This caused X1 to index into my source and other files, although probably causes X1 to look at the contents of more files than I need.

File names within ZIP mangled

$
0
0
Hi,

does this happen with all .zip files or only with some specific ones?

Since we cannot reproduce the issue, can you please provide an example .zip file that would show this problem?

Jogy

File names within ZIP mangled

$
0
0
That is great news. I look forward to updating to the new software.
Since other features are working well in my tests, I plan to purchase your software within the next few days.

File names within ZIP mangled

$
0
0
Hi,

I tested with the files you provided and there was indeed a bug in 8.5.2, which is already fixed in the upcoming version 8.6.

The new version will be released pretty soon, perhaps next week if all goes well.

Jogy

X1 Search 8.6 Release - Build 6003ch

$
0
0
X1 now appears to be indexing a lot slower than normal, causing excessive CPU usage for me. During those times X1 is very slow to respond. Is another release coming out soon.....?

X1 Search 8.6 Release - Build 6003ch

$
0
0
I find it interesting that many people are reporting similar problems. And what do we hear from X1...crickets. Nothing. Nada. Zip.

I've already started exploring other options, and if this situation doesn't get fixed quickly, I will probably go to another program.

X1 Search 8.6 Release - Build 6003ch

$
0
0
Was able to get this version installed, but I want to go back in time an beat my two day previous self for even considering the upgrade. Stupid... stupid... stupid.

I don't get it. Why do search results now take 15-20 seconds to show up? Why, once they show up, do preview windows take 10-20 seconds to show up? I moved from a perfectly functioning installation to one that, if I use it, will actually slow down my work-flow by a considerable amount.

If I uninstall and move back to the previous version (how do I even do that?), what are the odds that this installation has corrupted the previous? You should include an option on the upgrade message: "Never show this again" for those of us too stupid to leave well enough alone.

edit: Why is the "open" option in email greyed out? Why can I only open email using ctrl-o? Also, why, after waiting 10-20 seconds for the preview to show up, does the preview many times not actually show up?

X1 Search 8.6 Release - Build 6003ch

$
0
0
hektic wrote:Hello,

Upon installing the new version I have lost all of my results.

There are 628,000 items indexed in my X1, but the morning after installing the latest 8.6 update I can no longer view any results.

The left hand navigation tree is visible, but when you click on it nothing becomes highlighted. The software is not frozen. I can click across the top navigation menu (All, email, email and attachments, etc). However, no matter what I click on, it states "no results" even though on the bottom left hand corner it says 628,872 items indexed.

I'm running windows 10 with latest updates. I have tried uninstalling and re-installing and it makes no difference. Do you have any suggestions as to what the issue could be?

Thank you.


Exactly my situation as well.

X1 Search 8.6 Release - Build 6003ch

$
0
0
Cgy-Jim wrote:My install just crashes with no explanation. Says see the log. What log?

Cgy-jim,

Many users who have issues installing via the bootstrapper often have success when using the direct .MSI installers which are linked above.

That being said, if you'd like to help us troubleshoot this issue here's what the error message refers to:

SETUP/INSTALL LOGS:
X1SearchSetup.log
X1Setup.log
x1search_install##########.log (looks like x1search_install635833909506379069.log)
MSI@@@@@.LOG (where @= a string of numbers and letters)

Here is how to locate those:
1. Click the "Start" button
2. In the Run box, enter the following: %TEMP%
3. Press Enter
4. In the resulting directory, sort by the 'Name" column and view the most current 'x1setup.log', 'x1search_install##########.log' and 'MSI@@@@@.LOG' files

I'm happy to pass along feedback and logs to the development team, but for best results I'd try the going through the X1 Support system.

It makes it easier for us to track trending issues and resolve them if possible.

X1 Search 8.6 Release - Build 6003ch

$
0
0
My installation attempt also failed twice - one after a complete reboot. Same problem as Cgi-joe above.
W10, 64-bit
Looking forward to a fix.

X1 Search 8.6 Release - Build 6003ch

$
0
0
Add me to the list of those who did the update and now have a non-functioning X1.

This seems to happen every time there is an update to X1. Maybe I should just ignore future updates.

Very frustrating.

X1 Search 8.6 Release - Build 6003ch

$
0
0
cscott wrote:
Quote:SoCalScott wrote:I find it interesting that many people are reporting similar problems. And what do we hear from X1...crickets. Nothing. Nada. Zip.

I've already started exploring other options, and if this situation doesn't get fixed quickly, I will probably go to another program.


Sorry to hear you're having a bad experience. We're here and listening, however these forums are generally not the best method of finding support.

Would you mind submitting a support ticket here: https://www.x1.com/support/x1_search_submit_case.html so we can take a crack at resolving this issue for you?


Already done...and have submitted diagnostics zip file as well. I'm now on Day 2 without my desktop search. I rely on X1 heavily, and almost missed a deadline because I had to manually open dozens of documents and do individual searches in each document.

I appreciate that you're listening, but based on what I'm reading in the forums, lots of people are having problems with the latest release, and the complaints sound very similar. It sure seems like X1 pushed out a bad update, and the best things you can do at this point are (a) fix it, and (b) keep your customers informed on what you're doing to fix it, and give us a timeline.
Viewing all 8513 articles
Browse latest View live