Outlook Contact Scanner-Some PST files added to X1 could not

[mrwul]

I got the below error

X1 Outlook Contact Scanner
Some PST files added to X1 could not be accessed.
These PST files could not be located and may have been moved:
X:\Path\OutlookFileName.pst

=

=

However, there is nothing wrong with the .pst file.
a. it is not moved, it exists and has been there for many years
b. it is also tagged in X1 settings.

This error is with X1 v.8.5.2 6001si x64
Never saw this in the previous version.

I might simply start re-indexing, there will be -no- error.
It simply pops up once or twice, though X1 is working fine as far as I can see.

Weird though..
=

[mrwul]

Likely something to do with

-
Application: X1OutlookService32.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidCastException
at X1.Outlook.Service.OutlookService.HandleException(System.Exception)
at X1.Outlook.Service.OutlookService+<>c__DisplayClass19_1.<ExecuteMAPICode>b__0()
at X1.Outlook.Service.OutlookService.MAPIThreadStart(System.Object)
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart(System.Object)
-

Will send X1 an email - not sure whether or not they are regularly checking the forum...

=

[Kenward]

I have seen that, but it is transient. The PST files connects later.

Sometimes it seems to be related to other things going on on the PC, like a backup program locking the file.

[longview]

I am experiencing exactly the same issue. Only started a few weeks ago. X1 has no problem finding files but has an annoying habit of producing this error message almost at random

[mrwul]

As info: I did submit a 'case' to X1 support.
They asked me to send over the diagnostics report.
This I didn't: so much personal data is transmitted, frankly, I feel a little uncomfortable to do so.
Informed them accordingly and decided to let it rest and accept the error.
Maybe, at one point in time, they will find a fix anyhow.
=

[cscott]

Hi all,

Yes, we do read this forum regularly.

There have been many reports of this message popping up recently (indeed, in the last couple of weeks). We have reason to believe that it may be related to a recent Windows update.

I myself have been affected by this particular issue. It seems to be fairly harmless (as Kenward says, the affected PST reconnects and is searchable) but like all of you I dislike having error messages for "no" reason.

Rest assured, we're looking into it - but as always, any additional info that you'd like to provide certainly can't hurt.

Best,
Chris

[mrwul]

Thanks. As said earlier, maybe it has something to do with EventID 1026
Something with .NET Runtime?

=


=

[cscott]

Thanks. As said earlier, maybe it has something to do with EventID 1026
Something with .NET Runtime?

=


=

Do you by chance have .NET4.7 installed? We've seen reports of strange bugs with Windows 7 and .NET 4.7.

[mrwul]

I am running Windows 10 x64 bld 15063.413 (latest)
as well as the latest .NET Framework version.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
shows Release: 460798
which is: Windows 10 Creators Update: 460798 - .NET Framework 4.7

=

[mrwul]

Note that I encountered the below error:
"Something went wrong and your search couldn't be completed"

I just disabled the X1 Add-in and the error was gone...
Wouldn't know whether the error was caused by the add-in though, but possibly it may be related(?)


=



=



=
EventID 1026
Application: X1OutlookService32.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidCastException
at X1.Outlook.Service.OutlookService.HandleException(System.Exception)
at X1.Outlook.Service.OutlookService+<>c__DisplayClass19_1.<ExecuteMAPICode>b__0()
at X1.Outlook.Service.OutlookService.MAPIThreadStart(System.Object)
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart(System.Object)

=

[cscott]

Note that I encountered the below error:
"Something went wrong and your search couldn't be completed"

I just disabled the X1 Add-in and the error was gone...
Wouldn't know whether the error was caused by the add-in though, but possibly it may be related(?)


=



=



=
EventID 1026
Application: X1OutlookService32.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidCastException
at X1.Outlook.Service.OutlookService.HandleException(System.Exception)
at X1.Outlook.Service.OutlookService+<>c__DisplayClass19_1.<ExecuteMAPICode>b__0()
at X1.Outlook.Service.OutlookService.MAPIThreadStart(System.Object)
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart(System.Object)

=

Interesting. I've passed this info off to our Development team for investigation and filed a bug report. Look for a fix in future versions. So far, the most successful workaround has been to roll back to .NET v4.5.2

[Foo Alié]

Hello,

I get the same error, now : "These PST files could not be located and may have been moved" with Windows 10 64 bits (with all the latest updates) / X1 Search 8.5.2 60015i (64—bit) / BitDefender.
Of course, Outlook works, my PST file is here and didn't move. And currently X1 never reconnects to the lost PST file until I reboot.
I have tried to uninstall completely X1 and reinstall it. Same random punishment.

I also frequently lose the connection with the X1 service.

Any progress in the search of the reason of this boring bug ?
X1 is currently no more reliable.

Thanks

Here is what I find in the event viewer :
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-10-14T14:28:46.079542100Z" />
<EventRecordID>62239</EventRecordID>
<Channel>Application</Channel>
<Computer>SIRIUS</Computer>
<Security />
</System>
- <EventData>
<Data>Application : X1OutlookService64.exe Version du Framework : v4.0.30319 Description : le processus a été arrêté en raison d'une exception non gérée. Informations sur l'exception : System.InvalidCastException à X1.Outlook.Service.OutlookService.HandleException(System.Exception) à X1.Outlook.Service.OutlookService+<>c__DisplayClass19_1.<ExecuteMAPICode>b__0() à X1.Outlook.Service.OutlookService.MAPIThreadStart(System.Object) à System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) à System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) à System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) à System.Threading.ThreadHelper.ThreadStart(System.Object)</Data>
</EventData>
</Event>

[mnoisy]

Identical Issue. Can duplicate on second win 10 machines on 17035 and 17025.

Both clean windows installations.