X1 Search 8.5.1 Release - Build 6001se

[cscott]

Hello all,

We’re tremendously excited to announce the GA release of X1 Search 8.5.1!

This 8.5.1 release should resolve many of the issues that were identified with help from your feedback after the release of Search 8.5. During this development cycle we were able to: optimize the speed of the incremental “quick” scans in the Outlook connector, fix issues related to Low Disk Space safeguards, and add the ability to customize the X1 Search shortcut keys.

Please see the release notes below for the full list of new features and bug fixes.

You can upgrade via Menu>Info>Check for Updates Button, or you can download with the below links. There are a few links available below depending on what you prefer to install. The new .MSI will help users only download the code from X1 one time if they are going to install it on more than one computer. It will also enable Enterprise IT administrators to use their standard MSI deployment tools.

Bootstrapper: http://download.x1.com/downloads/search/X1SearchSetup.exe
64-bit MSI: http://download.x1.com/downloads/search/6001se/X1Search.msi
32-bit MSI:x86: http://download.x1.com/downloads/search/6001se/X1Search32.msi

Search 8.5.1 Release Notes:

New Features:
• Dramatically improved the speed of incremental "quick" scans in Outlook
• Added support for X1 Rapid Discovery Connector post-search actions on Microsoft Exchange items
• Added the ability to customize or remove X1 Search shortcut keys
• A notification message now displays when index optimization is in progress
• Outlook scanners now give more useful status information

Bug Fixes:
• Fixed a bug that caused the date for some emails to be incorrectly displayed as 1/1/4501
• Addressed an issue that could cause scanners to pause due to an incorrectly reported Low Disk space condition
• Fixed an issue that caused the Outlook index to be lost when returning a system suspend or resume event
• Fixed a crash that could happen OneDrive for Business authentication prompt was displayed
• Files within a compressed container now properly respect content indexing filesize limits
• All Outlook saved searches can now be properly shared
• Selecting "Clear Filter" now clears only the user-inputted filtering criteria, not the preset terms for a saved search
• Uninstalling now correctly removes the "Plugins" folder from the install directory
• Installer slideshow displays high definition slides to those machines which support it
• Many other key bug fixes and improvements

Thank you for all your continued support, and keep the feedback coming.

Best,
Chris

[Kenward]

• Added the ability to customize or remove X1 Search shortcut keys

Where do we find this?

I can find the Edit shortcut option for saved searches. (Right Click on the search you want to edit.) Is that it?

How about changing other shortcuts? Toggle the Navigation Tree, for example. Is that possible?

[Jogy]

• Added the ability to customize or remove X1 Search shortcut keys

Where do we find this?

I can find the Edit shortcut option for saved searches. (Right Click on the search you want to edit.) Is that it?

How about changing other shortcuts? Toggle the Navigation Tree, for example. Is that possible?

Open the Options page, and at the top there should be a new tab named "Shortcuts" where you can change a bunch of UI shortcuts.

Jogy

[PeterRHawkes]

I have installed on Windows 10 Creator machine with 32 bit Outlook 2016. X1 was working perfectly before but not now!!

It is cycling through startup diplaying 'Connecting to Search Service' and then 'Ready' and then back to 'Connecting to Search Service etc etc. At times it pops up a message that the .nst file cannot be configured.

I tried sending support request with diagnostics but that crashed twice so unsure whether that has been received as I have not had the normal email receipt.

An ideas would be greatly appreciated as at the moment I have no X1!!??

Peter R Hawkes

[Kenward]

I have installed on Windows 10 Creator machine with 32 bit Outlook 2016. X1 was working perfectly before but not now!!

Is that after this latest update? (That's the subject of this discussion.)

If so, you could try reinstalling it, just in case the original install failed in some way.

The first message tells you how to get the latest version.

[JBreault]

Installed 8.51. The attachment preview image is too far to the right side so I can't see the whole attachment. I've tried all size options, zoom options and font options to center the image or make it left justified. I did not have this problem with 8.5.

Help!

John
Macbook 2016 using Parallels, Windows 10

[PeterRHawkes]

This is indeed 8.5.1 I installed when prompted by the software this morning.

I have downloaded from the link but wont install as it says I have the current version?

PRH

[Kenward]

Installed 8.51. The attachment preview image is too far to the right side ...

What search is this?

I'm having trouble understanding which view you are using.

A screen shot could help.

[Kenward]

I have downloaded from the link but wont install as it says I have the current version?

Which link? There are three.

Try the msi file. Then you should get a "repair" option.

[PeterRHawkes]

Used 64Bit Link and clicked on Repair .... same problem remains?

PRH

[tmcgove]

I am excited to try your update. Could you pass this suggestion on to your PM ... when the update notice appeared it was not clear that you need check box to proceed. see screenshot here: https://screenshot.net/geyjmf7

Thanks

Tmcgove

[Jogy]

I have installed on Windows 10 Creator machine with 32 bit Outlook 2016. X1 was working perfectly before but not now!!

It is cycling through startup diplaying 'Connecting to Search Service' and then 'Ready' and then back to 'Connecting to Search Service etc etc. At times it pops up a message that the .nst file cannot be configured.

I tried sending support request with diagnostics but that crashed twice so unsure whether that has been received as I have not had the normal email receipt.

An ideas would be greatly appreciated as at the moment I have no X1!!??

Peter R Hawkes

Hi,

can you check in the data folder (by default in C:\Users\USERNAME\AppData\Local\X1 Search\), in the subfolder "logs", if there are any *.crash.xml files, and if they are, what is their content? This may help in diagnosing what is the issue.

Jogy

[PeterRHawkes]

Does this help!?

<?xml version="1.0" encoding="utf-8"?>
<CrashLog>
<User LogID="0" InstallID="b51cdafd-0d02-41ce-bc5a-44c92d3bea9d" Email="" CountryCode="44" Company="" ChannelName="X1">
<UserDescription />
</User>
<CrashDetails CrashDate="2017-05-17 14:37:29" CrashDateInfo="Utc (Utc offset +01:00)" BuildNumber="6001se" AppName="X1Pro" AppComponent="X1ServiceHost.exe" MiniDumpFileName="4481ac41-fd71-40ee-a834-adb2d4cf534f">
<Data />
<ErrorMessage>UnmanagedCodeException: Crash in X1IndexCore.dll (address 0x85583)</ErrorMessage>
<HelpLink />
<StackTrace />
<TypedValues>(Int32)HResult=-2146233088
</TypedValues>
<InnerException />
<CurrentManagedStack>LogCrash at offset 963 in file:line:column &lt;filename unknown&gt;:0:0
LogCrash at offset 45 in file:line:column &lt;filename unknown&gt;:0:0
a at offset 346 in file:line:column &lt;filename unknown&gt;:0:0
</CurrentManagedStack>
</CrashDetails>
<ComputerDetails>
<OS CodeSet="1252" OSLanguage="2057" PAEEnabled="" IsPrimaryOS="True" OperatingSystemSKU="48" OSProductSuite="256" ProductType="1" OtherTypeDescription="" MaxProcessMemorySize="137438953344">
<DetailedOSDescription>6.2.9200.0, , Win32NT</DetailedOSDescription>
<BootDevice>\Device\HarddiskVolume2</BootDevice>
<SystemDevice>\Device\HarddiskVolume4</SystemDevice>
<SystemDirectory>C:\WINDOWS\system32</SystemDirectory>
<WindowsDirectory>C:\WINDOWS</WindowsDirectory>
</OS>
<LastBootUpTime>0.12</LastBootUpTime>
<CPU>Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz - Intel64 Family 6 Model 69 Stepping 1</CPU>
<VirtualMem>Free: 13320112kb of 18777160kb</VirtualMem>
<PhysicalMem>Free: 3587008kb of 8291400kb</PhysicalMem>
<PageFileMem>Free: 10485760kb of 10485760kb</PageFileMem>
<HDDs>
<LogicalHardDrive Name="C:" Free="194742902784" Size="505253195776" />
</HDDs>
<OutlookVersion />
<MapiVersion />
<FirefoxVersion />
<DotNetVersions>
<DotNetVersion>2.0.50727.4927</DotNetVersion>
<DotNetVersion>3.0.30729.4926</DotNetVersion>
<DotNetVersion>3.5.30729.4926</DotNetVersion>
<DotNetVersion>4.7.02046</DotNetVersion>
<DotNetVersion>4.0.0.0</DotNetVersion>
</DotNetVersions>
</ComputerDetails>
</CrashLog>

[rezato]

I was prompted to update to 8.5.1 (from 8.5 6001qm (64-bit)). It went thru Preparing setup, Download, "Closing application", then "Preparing uninstallation", where it failed with the message "Unable to complete setup due to an unexpected error. Please see logs for details."

The original 8.5 installation is still there, and functions as before if I refuse the upgrade when I start up the application

I see a crash file in my X1 Search\logs folder, but it's from May 8th. Any other log files that can shed light on what went wrong?

Thanks,
Reza

[Jogy]

Hi,

yes, this shows that there is a problem with the index, and it prevents the app from starting. What exactly is the problem is hard to determine, it may be caused by some data that was indexed ...

What you can try now is to go to the data folder and delete all *.dat files, then start X1 again. This will keep your settings, but start indexing again from scratch.

Jogy

Does this help!?

<?xml version="1.0" encoding="utf-8"?>
<CrashLog>
<User LogID="0" InstallID="b51cdafd-0d02-41ce-bc5a-44c92d3bea9d" Email="" CountryCode="44" Company="" ChannelName="X1">
<UserDescription />
</User>
<CrashDetails CrashDate="2017-05-17 14:37:29" CrashDateInfo="Utc (Utc offset +01:00)" BuildNumber="6001se" AppName="X1Pro" AppComponent="X1ServiceHost.exe" MiniDumpFileName="4481ac41-fd71-40ee-a834-adb2d4cf534f">
<Data />
<ErrorMessage>UnmanagedCodeException: Crash in X1IndexCore.dll (address 0x85583)</ErrorMessage>
<HelpLink />
<StackTrace />
<TypedValues>(Int32)HResult=-2146233088
</TypedValues>
...</CrashLog>

[PeterRHawkes]

That's done it; deleted all .dat files and now x1 is rebuilding index!! A shame but hopefully the upgrade will be worth the 500k items re-indexing!!

Thanks Jogy

PRH

[cscott]

I am excited to try your update. Could you pass this suggestion on to your PM ... when the update notice appeared it was not clear that you need check box to proceed. see screenshot here: https://screenshot.net/geyjmf7

Thanks

Tmcgove

Thanks for the feedback, tmcgove. We'll keep that in mind for future releases.

[tjh]

I had to delete all the *.dat files in Appdata\Local\X1 Search after the upgrade.
Othewise X1 kept saying "Unable to connect to the Indexing Service" or similar (I didn't write down the message, sorry)

Deleting all the dat files has fixed it though, working again now.

[spirus60]

The dialogue box to update to 8.5.1 has popped up on occasion but the software won't install successfully. I tried the "remove the dat file" step from an earlier post - just for fun - but the install still fails. I've rebooted and all that but still no joy.

The error message comes in an X1 Search dialogue box saying "unable to complete setup due to an unexpected error. please see logs for details"

So it would be nice if X1 told me where the logs were - I did find them - but it's not clear which log file I should be looking at as there are many of them.

What are the recommended diagnostic steps?

Thanks

P.S. I determined that it was faster to just uninstall my current 8.5 version and then reinstall directly to 8.5.1. So far, so good.

[poy]

Dear X1 developers.

As much as I like new features - can you please do something to fix stability issues with your index?

It took 2 weeks to build a full index of 7Mio objects.
And then I could use it for a couple of weeks.

Today X1 reports 2Mio indexed items.

As many times before there was no error message, no system crash or other signs of unusual system behaviour.

Instead of adding new stuff, please cure these alzheimer's disease symptoms.

Even if an index file became corrupt due to bad things like power outage, shouldn't it be possible to check the index for integrity and repair it?

Weeks of re-indexing are more than annoying!

PLEASE:

Can't you make it reliable?

When it works, X1 is the greatest thing.
But far too often it doesn't.

[Armchaircritic]

I am having the same issue on my Win 7 machine. Worked great until this update. I've sent in the reports but it's so bad I cant even use it.
Hope you deal with it soon.

I have installed on Windows 10 Creator machine with 32 bit Outlook 2016. X1 was working perfectly before but not now!!

It is cycling through startup diplaying 'Connecting to Search Service' and then 'Ready' and then back to 'Connecting to Search Service etc etc. At times it pops up a message that the .nst file cannot be configured.

I tried sending support request with diagnostics but that crashed twice so unsure whether that has been received as I have not had the normal email receipt.

An ideas would be greatly appreciated as at the moment I have no X1!!??

Peter R Hawkes

[jhason]

Hello,

I'm still having this issue with my Win 7 64-bit Enterprise laptop running with 20 GB of RAM and plenty of fast SSD hard drive space. Deleting the .dat file didn't work. This is quite annoying being a long time user and customer. Any suggestions would be greatly appreciated.

I had this problem with my Surface Pro 4 running Win 10 64-bit but it looks like the issue went away after deleting all of the .dat files and rerunning the indexing process.

Jhason

[PeterRHawkes]

Simply clearing the dat files was ok until indexing got stuck. In the end I uninstalled X1 altogether with all settings and licence and started from scratch! Good job X1 is worth the effort as it was a lot of time wasted in a simple upgrade!

Peter H

[poy]

Hello,

I'm still having this issue with my Win 7 64-bit Enterprise laptop
...
Jhason

Hi Jhason,

When I bought it a couple of years ago, it was great. Hands down it was my favorite tool on my machine.

But X1 has become unreliable.

After having saved plenty of time when it worked, I have now wasted significantly more time re-indexing re-installing and checking this forum for useful answers which typically never come.

X1 product- and service-quality can only improve.

Kind regards,
p

[poy]

Beep beep beep beep!!!
Alzheimer stroke again.
X1 index reached 7,2 Mio items and when I started my notebook today, it's back to 1,1 Mio.

Hey X1 folks,
Obviously you can't make the index reliable. Whatever the reason might be. Perhaps you had to sacrifice speed - who knows.
But why don't you offer some sort of automatic index backup?
I started to backup the index files which X1 screws up every now and then. But having to do this manually really BEEPs.
As this index crashing is a well known X1 feature, why doesn't X1 backup the stuff it needs on its own?

These constant crashes really BEEP big time.
Don't you agree?

[Kenward]

As this index crashing is a well known X1 feature ...

Really?

Can you point to messages with the same disease so that the X1 folks can look for common factors?

I don't recall seeing enough messages with same symptoms to justify the "well known X1 feature" tag, but I may not be paying enough attention.

You talk of a notebook, could there be a hibernation issue involved here?

Backup would be nice. As it is, I resort to the usual system image and daily data backups to keep me in business. But that is too blunderbuss.

[cscott]

Beep beep beep beep!!!
Alzheimer stroke again.
X1 index reached 7,2 Mio items and when I started my notebook today, it's back to 1,1 Mio.

Hey X1 folks,
Obviously you can't make the index reliable. Whatever the reason might be. Perhaps you had to sacrifice speed - who knows.
But why don't you offer some sort of automatic index backup?
I started to backup the index files which X1 screws up every now and then. But having to do this manually really BEEPs.
As this index crashing is a well known X1 feature, why doesn't X1 backup the stuff it needs on its own?

These constant crashes really BEEP big time.
Don't you agree?

Hello Poy,

Nice to hear from you again.

I'd love to see what's causing the issue, but as we've discussed before you're uncomfortable with providing us with the information we'd need to assist you.

Our goal is to build the fastest and most stable indexing software possible. However, we can't test for every environment and dataset.

I certainly understand your frustration, but given that we're at a bit of an impasse with supporting your particular index loss issues, I am not sure how far I can go to support you.

I will take your feature request for an index backup feature to heart - it's a great idea for an improvement and I hope to have it implemented in the future.

Best,
Chris