MacBook Pro Console shows CoreData NSXPCConnection errors

Question

Level 1

4 points

MacBook Pro Console shows CoreData NSXPCConnection errors

Hello, I have an issue with console on my Macbook Pro, macOS Sequoia 15.7.2. The console logo appeared with the following fault messages : (Imagent ) CoreData: Unable to create token NSXPCConnection. NSXPCStoreServerEndpointFactory 0x666cb7370 -newEndpoint returned nil

and also

(searchpartyuseragent)

CoreData: Unable to create token NSXPCConnection. NSXPCStoreServerEndpointFactory 0xabc858d40 -newEndpoint returned nil
Error communicating with persistent store service proxy: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.contactsd.persistence was invalidated: failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.contactsd.persistence was invalidated: failed at lookup with error 159 - Sandbox restriction.}

Is this a threat and how to correct?

Thanks in advance for your input and help.

MacBook Pro 14″, macOS 15.7

Posted on Nov 16, 2025 4:11 AM

Reply

Answer 1

Nov 17, 2025 6:22 PM in response to 18SDZ02

that is just the panic report header. there is much more information in the rest of the text.

Kernel Panic Reports are stored in the Folder at:

/Library/Logs/DiagnosticReports

If you copy and paste that string into:

Finder > Go menu > Go to Folder

it will take you to the Folder where those reports are stored.

Kernel panic reports are named with Date&Time and start or end in ‘panic’

If you find one, please post as much as you can here, by using the “additional text” Icon in the reply footer (looks like a paper with writing). (Once the report devolves into incessant software-names or incessant Base-64 dumps with lots of AAAAAA lines, you are done.)

Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.

Reply

Answer 2

Nov 16, 2025 10:17 AM in response to 18SDZ02

Venturing into Console logs without a specific search in mind is the path to madness.

Console logs have messages that can lead you to believe any conjecture AND its complete opposite. They can never be read in isolation.

¿What are your GROSS symptoms?

Reply

Answer 3

18SDZ02 Author

Level 1

4 points

Nov 18, 2025 12:35 AM in response to Grant Bennet-Alder

Thanks for the guidance. I couldn't find any Kernel panic reports in the mentioned folder. Believe those below are of no harm.

ExcUserFault_lsd-2025-11-12-233313.ips

locationd-2025-11-16-144254.ips

secd-2025-11-16-144241.ips

ANECompilerService_2025-11-16-142315_mstsc-2.cpu_resource.diag

secd-2025-11-16-140723.ips

ANECompilerService_2025-11-16-140208_mstsc-2.cpu_resource.diag

siriactionsd-2025-11-16-135947.ips

mds_stores_2025-11-16-133231_mstsc-2.cpu_resource.diag

Microsoft Word_2025-11-16-114401_mstsc-2.cpu_resource.diag

Microsoft Word_2025-11-14-161701_mstsc-2.cpu_resource.diag

Microsoft Word_2025-11-13-181529_mstsc-2.cpu_resource.diag

ANECompilerService_2025-11-12-234116_mstsc-2.cpu_resource.diag

Reply

Answer 4

18SDZ02 Author

Level 1

4 points

Nov 17, 2025 4:14 PM in response to Grant Bennet-Alder

Console never appeared before, so lost with looking for gross symptoms.

Here is a snapshot of the crash report. Maybe this might help.

Reply