Office Add-ins error: Cannot connect to catalog

[Bob Manjoney]

One of our admin-managed add-ins (Adobe Sign) has gone AWOL from the ribbon of the Word desktop app recently (it still shows up in the web-app version of Word). One of the suggested troubleshooting steps is to check review the Office Add-ins from within the app itself. When doing so, I receive an error:

Insert ribbon-->Add-ins section-->My Add-ins-->See all...-->Admin Managed
"Cannot connect to catalog"

I've tried: signing out, back in, clearing the Office cache, and redeploying the add-in from central management. The deployment always reports that it was successful.

Can anyone else reproduce this "Cannot connect to catalog" issue, or suggest additional troubleshooting steps/workarounds? 

[#2]

Hi @Bob Manjoney - I hope all is well in your world.

I recently encountered this with another "Modern" Office Add-in, one we're in the process of deploying via Trusted Catalogs.  What's particularly frustrating is that this was working fine a few weeks ago.

Here's what I think I know:

1. The 'Block Web Add-ins' policy is not enabled (set to 0)
2. Doesn't seem to matter whether or not the 'Block the Office Store' policy is configured
3. The manifest file is in place & accessible
4. This was for sure was working in August & July; it's only recently that I've noticed that the add-in is no longer accessible/available.
5. Thanks to AGPM I am the gatekeeper for all group policy modifications so I can confirm no rogue changes have been made.

Me and another sharp guy on my team have examined this fully and we're both at a loss.  We're beginning to wonder if an update changed this behavior.

[#3]

Thanks for confirming and the extra information. This was also working for me up until a few days ago.

[#4]

@Bob Manjoney: We sorted this out today.

• When we were initially manually configuring "Block Web Add-ins" (DisableAllCatalogs) and "Block Office Add-ins" (DisableOMEXCatalogs), we were setting it in HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\WEF\TrustedCatalogs.
• When you configure those two settings in policy (User \ Administrative Templates \ Microsoft Office 2016 \ Security Settings \ Trusts Center \ Trusted Catalogs), it gets written to HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\WEF\TrustedCatalogs.
• Because we need to target this particular Office Add-in to a subset of users, we cannot rely on setting the Trusted Catalog Location policy items so we leveraged registry preferences in order to make use of Item Level Targeting.
  When we dropped those keys we matched our initial test configuration which was to write the Office Add-in settings to to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\WEF\TrustedCatalogs.  Turns out that gets ignored or overridden when something is set at the HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\WEF\TrustedCatalogs level.
• Once we realized this behavior we corrected the discrepancy and decided to rely solely on registry preferences, not policies, and the add-in started working again. 

So we shot ourselves in the foot but it took us a while to realize it.

[#5]

@Julius Perkins  Hi I have this problem in excel with an App that I can't use because it can't connect to the catalogue. It's on a stand-alone PC using Office 2019. The app is Log-Hub. I suspect it's the security on the PC but have no idea how to allow the app to connect to the catalogue.

Any ideas 

[#6]

@Bob Manjoney I did have the same problem. My solution was use the same e-mail to login at Microsoft and Mendeley Reference Manager software, your account registered at Mendeley.com should be the same used to log at Word software.

[#7]

@Julius Perkins 

Hi, I came across this thread while searching for a solution to my issue. I am having a similar issue with my Word Add-Ins--Admin Managed Add-Ins "Cannot connect to Catalog"--but my device is an M1 Mac device (Apple silicon), instead of Windows. I wonder if you had a chance to look into MacOS equivalent debugging of this issue? 

I have signed out, uninstalled, deleted all remaining files, rebooted, and reinstalled-- but the issue remains. I followed this thread I found: https://answers.microsoft.com/en-us/msoffice/forum/all/admin-managed-add-ins-not-available-in-word-m... 

I checked other devices that I have and noticed that both a Windows device and an intel-chip Mac device don't have the issue, even with the same Office account. At the moment I can't tell if it's related to the device (maybe Add-In function is running on Rosetta on the M1 Mac?) or if it's something conflicting in my device. 

Any comment or update would be appreciated. 

Thanks in advance, 

[#8]

Hey there @SupplyChainGuru.  Can you click 'See Details' and post a screenshot of what those details are?

[#9]

We had the same problem in our company and I finally found the cause of our problem today. Some of our users were able to connect, others not. All the users and computers received the same policies etc.
We are busy with migrating our mailboxes form our on prem Exchange servers to Exchange Online. We do this in batches, so some mailboxes are still on prem, some in EXO. Today I found out that the Office add-ins do work for the users with a mailbox in EXO and doesn't work for users with a mailbox in Exchange on prem.
Because we are busy migrating we didn't search for any solution for our users with a mailbox on prem, we just migrate them.

Maybe this info can help some others!

[#10]

I am having the same problem on a Mac running Ventura 13.1, and the tech support from Microsoft has been horrible. Can anyone here help?

- everyone in my company but me can access Insert > Get Add-ins > Admin Managed except me
- I get "Cannot connect to catalog"
- My computer is online at all times
- My computer is not running a VPN
- My computer is not managed by a centralized security policy
- I have used the Microsoft license removal tool
- I have deleted all Microsoft-related items from Keychain Access
- I have completely uninstalled and re-installed Office more than once

Tech support at Microsoft dodges the issue and avoids the case at all costs.

Any recommendations?

[#11]

Having the same issue on my MacBook pro M1 also running Ventura 13.1 and office 16.70.
in the Mac console i see this warning when i try to connect to "Admin Managed Add-ons":

finished with error [-999] Error Domain=NSURLErrorDomain Code=-999 UserInfo={NSErrorFailingURLStringKey=<private>, NSErrorFailingURLKey=<private>, _NSURLErrorRelatedURLSessionTaskErrorKey=<private>, _NSURLErrorFailingURLSessionTaskErrorKey=<private>, NSLocalizedDescription=<private>}

full logs:

default	17:13:09.093343+0100	Microsoft Word	0x135222d40 - [PID=0] WebProcessCache::setApplicationIsActive: (isActive=1)
default	17:13:09.109317+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> resuming, timeouts(60.0, 604800.0) QOS(0x19) Voucher <private>
default	17:13:09.109880+0100	Microsoft Word	[Telemetry]: Activity <nw_activity 12:2[CD37325E-23F8-43D6-9C86-8AB83CF8C12C] (reporting strategy default)> on Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> was not selected for reporting
default	17:13:09.110176+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> {strength 0, tls 4, sub 0, sig 1, ciphers 0, bundle 0, builtin 0}
default	17:13:09.110301+0100	Microsoft Word	Connection 0: creating secure tcp or quic connection
default	17:13:09.110605+0100	Microsoft Word	Connection 23: enabling TLS
default	17:13:09.110620+0100	Microsoft Word	Connection 23: starting, TC(0x0)
default	17:13:09.110651+0100	Microsoft Word	[C23 C5EB6920-410D-4ED5-9113-C78A13F51EC4 Hostname#e297cb77:443 quic-connection, url hash: d5ed175f, definite, attribution: developer, context: com.apple.CFNetwork.NSURLSession.{C2441CBA-2107-41D5-8309-741D421672EA}{(null)}{Y}{2} (private), proc: 96F224B3-5702-3730-98B7-96580495B9D6] start
default	17:13:09.110696+0100	Microsoft Word	[C23 Hostname#e297cb77:443 initial parent-flow ((null))] event: path:start @0.000s
default	17:13:09.110975+0100	Microsoft Word	[C23 Hostname#e297cb77:443 waiting parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: path:satisfied @0.000s, uuid: 557C03FE-5817-49F7-91E8-91274959B165
default	17:13:09.111118+0100	Microsoft Word	[C23 Hostname#e297cb77:443 in_progress parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:start_child @0.000s
default	17:13:09.111140+0100	Microsoft Word	nw_connection_report_state_with_handler_on_nw_queue [C23] reporting state preparing
default	17:13:09.111193+0100	Microsoft Word	[C23.1 Hostname#e297cb77:443 initial path ((null))] event: path:start @0.000s
default	17:13:09.111475+0100	Microsoft Word	[C23.1 Hostname#e297cb77:443 waiting path (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: path:satisfied @0.000s, uuid: 557C03FE-5817-49F7-91E8-91274959B165
default	17:13:09.111828+0100	Microsoft Word	[C23.1 Hostname#e297cb77:443 in_progress transform (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: transform:start @0.001s
default	17:13:09.112528+0100	Microsoft Word	[C23.1.1 Hostname#e297cb77:443 initial path ((null))] event: path:start @0.001s
default	17:13:09.113768+0100	mDNSResponder	[R11781] getaddrinfo start -- flags: 0xC000D000, ifindex: 0, protocols: 0, hostname: <mask.hash: 'lT3fK7iPohFUfEM9Z6KW9Q=='>, options: 0x8 {use-failover}, client pid: 16782 (Microsoft Word)
default	17:13:09.113101+0100	Microsoft Word	[C23.1.1 Hostname#e297cb77:443 waiting path (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: path:satisfied @0.002s, uuid: 1EF2C12D-995D-443A-8BD2-530629D78C76
default	17:13:09.113394+0100	Microsoft Word	[C23.1.1 Hostname#e297cb77:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: resolver:start_dns @0.002s
default	17:13:09.113719+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> setting up Connection 23
default	17:13:09.115950+0100	mDNSResponder	[R11781] getaddrinfo stop -- hostname: <mask.hash: 'lT3fK7iPohFUfEM9Z6KW9Q=='>, client pid: 16782 (Microsoft Word)
default	17:13:09.115993+0100	Microsoft Word	nw_endpoint_resolver_update [C23.1.1 Hostname#e297cb77:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Adding endpoint handler for IPv4#7fd23727:443
default	17:13:09.116620+0100	Microsoft Word	[C23.1.1 Hostname#e297cb77:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: resolver:receive_dns @0.005s
default	17:13:09.117506+0100	Microsoft Word	[C23.1.1.1 IPv4#7fd23727:443 initial path ((null))] event: path:start @0.006s
default	17:13:09.117805+0100	Microsoft Word	[C23.1.1.1 IPv4#7fd23727:443 waiting path (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: path:satisfied @0.007s, uuid: F01529B8-3780-4A91-AE58-9B07CFD35670
default	17:13:09.118269+0100	Microsoft Word	[C23.1.1.1 IPv4#7fd23727:443 in_progress channel-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:start_nexus @0.007s
default	17:13:09.119569+0100	Microsoft Word	[C23.1.1.1 IPv4#7fd23727:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:receive_nexus @0.008s
default	17:13:09.121278+0100	Microsoft Word	[C23.1.1.1 IPv4#7fd23727:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:start_connect @0.010s
default	17:13:09.121814+0100	Microsoft Word	tcp_output [C23.1.1.1:3] flags=[S] seq=3255522068, ack=0, win=65535 state=SYN_SENT rcv_nxt=0, snd_una=3255522068
default	17:13:09.130172+0100	dasd	Trigger: <private> is now [com.microsoft.Word]
default	17:13:09.132263+0100	dasd	Trigger: <private> is now [com.microsoft.Word]
default	17:13:09.150919+0100	Microsoft Word	tcp_input [C23.1.1.1:3] flags=[S.] seq=3862467910, ack=3255522069, win=65535 state=SYN_SENT rcv_nxt=0, snd_una=3255522068
default	17:13:09.150986+0100	Microsoft Word	nw_flow_connected [C23.1.1.1 IPv4#7fd23727:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] Transport protocol connected (tcp)
default	17:13:09.151060+0100	Microsoft Word	[C23.1.1.1 IPv4#7fd23727:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.040s
default	17:13:09.151181+0100	Microsoft Word	boringssl_session_apply_protocol_options_for_transport_block_invoke(1822) [C23.1.1.1:2][0x132df5010] TLS configured [min_version(0x0301) max_version(0x0304) name(redacted) tickets(false) false_start(false) enforce_ev(false) enforce_ats(false) ech(false)]
default	17:13:09.151289+0100	Microsoft Word	boringssl_context_info_handler(2052) [C23.1.1.1:2][0x132df5010] Client handshake started
default	17:13:09.151348+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client enter_early_data
default	17:13:09.151382+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client read_server_hello
default	17:13:09.179224+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client read_server_certificate
default	17:13:09.179251+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client read_certificate_status
default	17:13:09.179271+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client verify_server_certificate
default	17:13:09.179421+0100	Microsoft Word	boringssl_context_evaluate_trust_async(1635) [C23.1.1.1:2][0x132df5010] Performing external trust evaluation
default	17:13:09.179470+0100	Microsoft Word	boringssl_context_evaluate_trust_async_external(1620) [C23.1.1.1:2][0x132df5010] Asyncing for external verify block
default	17:13:09.179593+0100	Microsoft Word	Connection 23: asked to evaluate TLS Trust
default	17:13:09.182729+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> auth completion disp=1 cred=0x0
default	17:13:09.182806+0100	Microsoft Word	Connection 23: TLS Trust result 0
default	17:13:09.182827+0100	Microsoft Word	boringssl_context_evaluate_trust_async_external_block_invoke_3(1576) [C23.1.1.1:2][0x132df5010] Returning from external verify block with result: true
default	17:13:09.182852+0100	Microsoft Word	boringssl_context_certificate_verify_callback(1797) [C23.1.1.1:2][0x132df5010] Certificate verification result: OK
default	17:13:09.182862+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client read_server_key_exchange
default	17:13:09.182931+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client read_certificate_request
default	17:13:09.182955+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client read_server_hello_done
default	17:13:09.182965+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client send_client_certificate
default	17:13:09.182972+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client send_client_key_exchange
default	17:13:09.184340+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client send_client_certificate_verify
default	17:13:09.184350+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client send_client_finished
default	17:13:09.184390+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client finish_flight
default	17:13:09.184451+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client read_session_ticket
default	17:13:09.184458+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client process_change_cipher_spec
default	17:13:09.209779+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client read_server_finished
default	17:13:09.209906+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client finish_client_handshake
default	17:13:09.209942+0100	Microsoft Word	boringssl_context_info_handler(2069) [C23.1.1.1:2][0x132df5010] Client handshake state: TLS client done
default	17:13:09.209985+0100	Microsoft Word	boringssl_context_info_handler(2058) [C23.1.1.1:2][0x132df5010] Client handshake done
default	17:13:09.210232+0100	Microsoft Word	nw_protocol_boringssl_signal_connected(738) [C23.1.1.1:2][0x132df5010] TLS connected [version(0x0303) ciphersuite(TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) group(0x0018) signature_alg(0x0401) alpn(h2) resumed(0) offered_ticket(0) false_started(0) ocsp_received(1) sct_received(0) connect_time(59ms) flight_time(53ms) rtt(28ms) write_stalls(0) read_stalls(6)]
default	17:13:09.210289+0100	Microsoft Word	nw_flow_connected [C23.1.1.1 IPv4#7fd23727:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] Output protocol connected (CFNetworkConnection-9642642)
default	17:13:09.210396+0100	Microsoft Word	[C23.1.1.1 IPv4#7fd23727:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:child_finish_connect @0.099s
default	17:13:09.210448+0100	Microsoft Word	[C23 IPv4#7fd23727:443 in_progress parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:start_connect @0.099s
default	17:13:09.210469+0100	Microsoft Word	nw_flow_connected [C23.1.1.1 IPv4#7fd23727:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] Transport protocol connected (tcp)
default	17:13:09.210527+0100	Microsoft Word	[C23.1.1.1 IPv4#7fd23727:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.099s
default	17:13:09.210576+0100	Microsoft Word	[C23.1.1 Hostname#e297cb77:443 ready resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.099s
default	17:13:09.210678+0100	Microsoft Word	[C23.1 Hostname#e297cb77:443 ready transform (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.100s
default	17:13:09.210778+0100	Microsoft Word	nw_flow_connected [C23.1.1.1 IPv4#7fd23727:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] Output protocol connected (CFNetworkConnection-9642642)
default	17:13:09.210854+0100	Microsoft Word	nw_flow_connected [C23 IPv4#7fd23727:443 in_progress parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Output protocol connected (endpoint_flow)
default	17:13:09.210903+0100	Microsoft Word	[C23 IPv4#7fd23727:443 ready parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_connect @0.100s
default	17:13:09.210964+0100	Microsoft Word	nw_connection_report_state_with_handler_on_nw_queue [C23] reporting state ready
default	17:13:09.210994+0100	Microsoft Word	[C23 IPv4#7fd23727:443 ready parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:changed_viability @0.100s
default	17:13:09.211050+0100	Microsoft Word	[C23.1.1 Hostname#e297cb77:443 ready resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.100s
default	17:13:09.211080+0100	Microsoft Word	[C23.1 Hostname#e297cb77:443 ready transform (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.100s
default	17:13:09.211091+0100	Microsoft Word	[C23 IPv4#7fd23727:443 ready parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.100s
default	17:13:09.211153+0100	Microsoft Word	[C23.1.1.1 IPv4#7fd23727:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:changed_viability @0.100s
default	17:13:09.211211+0100	Microsoft Word	[C23.1.1 Hostname#e297cb77:443 ready resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:changed_viability @0.100s
default	17:13:09.211236+0100	Microsoft Word	[C23.1 Hostname#e297cb77:443 ready transform (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:changed_viability @0.100s
default	17:13:09.211247+0100	Microsoft Word	[C23 IPv4#7fd23727:443 ready parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:changed_viability @0.100s
default	17:13:09.211289+0100	Microsoft Word	nw_flow_connected [C23 IPv4#7fd23727:443 ready parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Output protocol connected (endpoint_flow)
default	17:13:09.211378+0100	Microsoft Word	Connection 23: connected successfully
default	17:13:09.211395+0100	Microsoft Word	Connection 23: TLS handshake complete
default	17:13:09.211478+0100	Microsoft Word	Connection 23: ready C(N) E(N)
default	17:13:09.211594+0100	Microsoft Word	[C23] event: client:connection_reused @0.100s
default	17:13:09.211704+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> now using Connection 23
default	17:13:09.211755+0100	Microsoft Word	Connection 23: received viability advisory(Y)
default	17:13:09.211886+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> sent request, body S 12651
default	17:13:09.337892+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> received response, status 200 content K
default	17:13:09.338046+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> done using Connection 23
default	17:13:09.338421+0100	Microsoft Word	[C23] event: client:connection_idle @0.227s
default	17:13:09.338819+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> response ended
default	17:13:09.339298+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> summary for task success {transaction_duration_ms=229, response_status=200, connection=23, protocol="h2", domain_lookup_duration_ms=3, connect_duration_ms=90, secure_connection_duration_ms=59, private_relay=false, request_start_ms=101, request_duration_ms=0, response_start_ms=227, response_duration_ms=1, request_bytes=12864, response_bytes=1136, cache_hit=false}
default	17:13:09.339400+0100	Microsoft Word	Task <0C12C790-EEC9-4F90-BAD3-99C6407C2C40>.<1> finished successfully
default	17:13:09.341157+0100	Microsoft Word	Connection 23: cleaning up
default	17:13:09.341208+0100	Microsoft Word	[C23 C5EB6920-410D-4ED5-9113-C78A13F51EC4 Hostname#e297cb77:443 quic-connection, url hash: d5ed175f, definite, attribution: developer] cancel
default	17:13:09.341417+0100	Microsoft Word	[C23 C5EB6920-410D-4ED5-9113-C78A13F51EC4 Hostname#e297cb77:443 quic-connection, url hash: d5ed175f, definite, attribution: developer] cancelled
	[C23.1.1.1 F01529B8-3780-4A91-AE58-9B07CFD35670 10.0.20.43:55271<->IPv4#7fd23727:443]
	Connected Path: satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns
	Privacy Stance: Not Eligible
	Duration: 0.230s, DNS @0.002s took 0.003s, TCP @0.010s took 0.030s, TLS 1.2 took 0.059s
	bytes in/out: 7900/13739, packets in/out: 13/21, rtt: 0.026s, retransmitted bytes: 0, out-of-order bytes: 0
default	17:13:09.341635+0100	Microsoft Word	nw_protocol_tcp_log_summary [C23.1.1.1:3] 
	[286B317E-6EDC-4C87-9837-6C710A3B906C <private>:55271<-><private>:443]
	Init: 1, Conn_Time: 29.292ms, SYNs: 1, WR_T: 0/0, RD_T: 0/0, TFO: 0/0/0, ECN: 0/0/0, TS: 0, TSO: 0
	rtt_cache: kernel, rtt_upd: 4, rtt: 26.843ms, rtt_var: 2.062ms rtt_nc: 28.593ms, rtt_var_nc: 6.937ms base rtt: 26ms
	ACKs-compressed: 0, ACKs delayed: 0 delayed ACKs sent: 0
default	17:13:09.341685+0100	Microsoft Word	nw_flow_disconnected [C23 IPv4#7fd23727:443 cancelled parent-flow ((null))] Output protocol disconnected
default	17:13:09.342060+0100	Microsoft Word	nw_connection_report_state_with_handler_on_nw_queue [C23] reporting state cancelled
default	17:13:09.342148+0100	Microsoft Word	tcp_output [C23.1.1.1:3] flags=[FP.] seq=3255535808, ack=3862475811, win=4096 state=FIN_WAIT_1 rcv_nxt=3862475811, snd_una=3255535762
default	17:13:09.369658+0100	Microsoft Word	tcp_input [C23.1.1.1:3] flags=[F.] seq=3862475811, ack=3255535840, win=2048 state=FIN_WAIT_2 rcv_nxt=3862475811, snd_una=3255535840
default	17:13:10.043265+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> resuming, timeouts(60.0, 604800.0) QOS(0x19) Voucher <private>
default	17:13:10.043370+0100	Microsoft Word	[Telemetry]: Activity <nw_activity 12:2[A0E34E88-4663-4185-B6A6-A4CD9D988BBD] (reporting strategy default)> on Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> was not selected for reporting
default	17:13:10.043498+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> {strength 0, tls 4, sub 0, sig 1, ciphers 0, bundle 0, builtin 0}
default	17:13:10.043551+0100	Microsoft Word	Connection 0: creating secure tcp or quic connection
default	17:13:10.043669+0100	Microsoft Word	Connection 24: enabling TLS
default	17:13:10.043679+0100	Microsoft Word	Connection 24: starting, TC(0x0)
default	17:13:10.043697+0100	Microsoft Word	[C24 A654744D-6695-48EC-88EA-FE089DACBC2B Hostname#066287c8:443 quic-connection, url hash: 2dac9386, definite, attribution: developer, context: com.apple.CFNetwork.NSURLSession.{94493F50-4C78-4EF1-A459-3BA2EC6253E9}{(null)}{Y}{2} (private), proc: 96F224B3-5702-3730-98B7-96580495B9D6] start
default	17:13:10.043723+0100	Microsoft Word	[C24 Hostname#066287c8:443 initial parent-flow ((null))] event: path:start @0.000s
default	17:13:10.043848+0100	Microsoft Word	[C24 Hostname#066287c8:443 waiting parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: path:satisfied @0.000s, uuid: 5E08271E-A847-4B9B-A71A-ABDFE37CC3E2
default	17:13:10.043914+0100	Microsoft Word	[C24 Hostname#066287c8:443 in_progress parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:start_child @0.000s
default	17:13:10.043924+0100	Microsoft Word	nw_connection_report_state_with_handler_on_nw_queue [C24] reporting state preparing
default	17:13:10.043953+0100	Microsoft Word	[C24.1 Hostname#066287c8:443 initial path ((null))] event: path:start @0.000s
default	17:13:10.044002+0100	Microsoft Word	[C24.1 Hostname#066287c8:443 waiting path (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: path:satisfied @0.000s, uuid: 5E08271E-A847-4B9B-A71A-ABDFE37CC3E2
default	17:13:10.044043+0100	Microsoft Word	[C24.1 Hostname#066287c8:443 in_progress transform (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: transform:start @0.000s
default	17:13:10.044168+0100	Microsoft Word	[C24.1.1 Hostname#066287c8:443 initial path ((null))] event: path:start @0.000s
default	17:13:10.044296+0100	Microsoft Word	[C24.1.1 Hostname#066287c8:443 waiting path (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: path:satisfied @0.000s, uuid: E8788EB3-365A-472A-BEF8-D9A1B6C5030A
default	17:13:10.044353+0100	Microsoft Word	[C24.1.1 Hostname#066287c8:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: resolver:start_dns @0.000s
default	17:13:10.044403+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> setting up Connection 24
default	17:13:10.044420+0100	mDNSResponder	[R11782] getaddrinfo start -- flags: 0xC000D000, ifindex: 0, protocols: 0, hostname: <mask.hash: 'Vo4ECn2tnTcI/KZLMK6deA=='>, options: 0x8 {use-failover}, client pid: 16782 (Microsoft Word)
default	17:13:10.047008+0100	mDNSResponder	[R11782] getaddrinfo stop -- hostname: <mask.hash: 'Vo4ECn2tnTcI/KZLMK6deA=='>, client pid: 16782 (Microsoft Word)
default	17:13:10.047049+0100	Microsoft Word	nw_endpoint_resolver_update [C24.1.1 Hostname#066287c8:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Adding endpoint handler for IPv4#774eea8f:443
default	17:13:10.047079+0100	Microsoft Word	nw_endpoint_resolver_update [C24.1.1 Hostname#066287c8:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Adding endpoint handler for IPv4#d77c1a91:443
default	17:13:10.047102+0100	Microsoft Word	nw_endpoint_resolver_update [C24.1.1 Hostname#066287c8:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Adding endpoint handler for IPv4#28026f10:443
default	17:13:10.047126+0100	Microsoft Word	nw_endpoint_resolver_update [C24.1.1 Hostname#066287c8:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Adding endpoint handler for IPv4#5aceafe2:443
default	17:13:10.047148+0100	Microsoft Word	nw_endpoint_resolver_update [C24.1.1 Hostname#066287c8:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Adding endpoint handler for IPv4#ca24ad10:443
default	17:13:10.047171+0100	Microsoft Word	nw_endpoint_resolver_update [C24.1.1 Hostname#066287c8:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Adding endpoint handler for IPv4#db4e27c1:443
default	17:13:10.047192+0100	Microsoft Word	nw_endpoint_resolver_update [C24.1.1 Hostname#066287c8:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Adding endpoint handler for IPv4#9a4b07f3:443
default	17:13:10.047215+0100	Microsoft Word	nw_endpoint_resolver_update [C24.1.1 Hostname#066287c8:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Adding endpoint handler for IPv4#aa350678:443
default	17:13:10.047274+0100	Microsoft Word	[C24.1.1 Hostname#066287c8:443 in_progress resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: resolver:receive_dns @0.003s
default	17:13:10.047346+0100	Microsoft Word	[C24.1.1.1 IPv4#774eea8f:443 initial path ((null))] event: path:start @0.003s
default	17:13:10.047491+0100	Microsoft Word	[C24.1.1.1 IPv4#774eea8f:443 waiting path (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: path:satisfied @0.003s, uuid: A06CEAA9-9A37-41B7-884A-27BBD34B607A
default	17:13:10.047549+0100	Microsoft Word	[C24.1.1.1 IPv4#774eea8f:443 in_progress channel-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:start_nexus @0.003s
default	17:13:10.047719+0100	Microsoft Word	[C24.1.1.1 IPv4#774eea8f:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:receive_nexus @0.004s
default	17:13:10.047931+0100	Microsoft Word	[C24.1.1.1 IPv4#774eea8f:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:start_connect @0.004s
default	17:13:10.048022+0100	Microsoft Word	tcp_output [C24.1.1.1:3] flags=[S] seq=1499281573, ack=0, win=65535 state=SYN_SENT rcv_nxt=0, snd_una=1499281573
default	17:13:10.064033+0100	Microsoft Word	tcp_input [C24.1.1.1:3] flags=[S.] seq=2752408525, ack=1499281574, win=65535 state=SYN_SENT rcv_nxt=0, snd_una=1499281573
default	17:13:10.064093+0100	Microsoft Word	nw_flow_connected [C24.1.1.1 IPv4#774eea8f:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] Transport protocol connected (tcp)
default	17:13:10.064157+0100	Microsoft Word	[C24.1.1.1 IPv4#774eea8f:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.020s
default	17:13:10.064285+0100	Microsoft Word	boringssl_session_apply_protocol_options_for_transport_block_invoke(1822) [C24.1.1.1:2][0x166187420] TLS configured [min_version(0x0301) max_version(0x0304) name(redacted) tickets(false) false_start(false) enforce_ev(false) enforce_ats(false) ech(false)]
default	17:13:10.064316+0100	Microsoft Word	boringssl_context_info_handler(2052) [C24.1.1.1:2][0x166187420] Client handshake started
default	17:13:10.064369+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client enter_early_data
default	17:13:10.064400+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client read_server_hello
default	17:13:10.076318+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client read_server_certificate
default	17:13:10.076343+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client read_certificate_status
default	17:13:10.076359+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client verify_server_certificate
default	17:13:10.076524+0100	Microsoft Word	boringssl_context_evaluate_trust_async(1635) [C24.1.1.1:2][0x166187420] Performing external trust evaluation
default	17:13:10.076565+0100	Microsoft Word	boringssl_context_evaluate_trust_async_external(1620) [C24.1.1.1:2][0x166187420] Asyncing for external verify block
default	17:13:10.076699+0100	Microsoft Word	Connection 24: asked to evaluate TLS Trust
default	17:13:10.079374+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> auth completion disp=1 cred=0x0
default	17:13:10.079433+0100	Microsoft Word	Connection 24: TLS Trust result 0
default	17:13:10.079447+0100	Microsoft Word	boringssl_context_evaluate_trust_async_external_block_invoke_3(1576) [C24.1.1.1:2][0x166187420] Returning from external verify block with result: true
default	17:13:10.079471+0100	Microsoft Word	boringssl_context_certificate_verify_callback(1797) [C24.1.1.1:2][0x166187420] Certificate verification result: OK
default	17:13:10.079480+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client read_server_key_exchange
default	17:13:10.079543+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client read_certificate_request
default	17:13:10.079559+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client read_server_hello_done
default	17:13:10.079632+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client send_client_certificate
default	17:13:10.079683+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client send_client_key_exchange
default	17:13:10.080977+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client send_client_certificate_verify
default	17:13:10.080991+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client send_client_finished
default	17:13:10.081028+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client finish_flight
default	17:13:10.081115+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client read_session_ticket
default	17:13:10.081121+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client process_change_cipher_spec
default	17:13:10.091397+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client read_server_finished
default	17:13:10.091454+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client finish_client_handshake
default	17:13:10.091502+0100	Microsoft Word	boringssl_context_info_handler(2069) [C24.1.1.1:2][0x166187420] Client handshake state: TLS client done
default	17:13:10.091511+0100	Microsoft Word	boringssl_context_info_handler(2058) [C24.1.1.1:2][0x166187420] Client handshake done
default	17:13:10.091757+0100	Microsoft Word	nw_protocol_boringssl_signal_connected(738) [C24.1.1.1:2][0x166187420] TLS connected [version(0x0303) ciphersuite(TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) group(0x0018) signature_alg(0x0804) alpn(nil) resumed(0) offered_ticket(0) false_started(0) ocsp_received(1) sct_received(0) connect_time(27ms) flight_time(22ms) rtt(12ms) write_stalls(0) read_stalls(6)]
default	17:13:10.091830+0100	Microsoft Word	nw_flow_connected [C24.1.1.1 IPv4#774eea8f:443 in_progress channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] Output protocol connected (CFNetworkConnection-9642642)
default	17:13:10.091933+0100	Microsoft Word	[C24.1.1.1 IPv4#774eea8f:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:child_finish_connect @0.048s
default	17:13:10.091979+0100	Microsoft Word	[C24 IPv4#774eea8f:443 in_progress parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:start_connect @0.048s
default	17:13:10.092000+0100	Microsoft Word	nw_flow_connected [C24.1.1.1 IPv4#774eea8f:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] Transport protocol connected (tcp)
default	17:13:10.092050+0100	Microsoft Word	[C24.1.1.1 IPv4#774eea8f:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.048s
default	17:13:10.092379+0100	Microsoft Word	[C24.1.1 Hostname#066287c8:443 ready resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.048s
default	17:13:10.092411+0100	Microsoft Word	[C24.1 Hostname#066287c8:443 ready transform (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.048s
default	17:13:10.092605+0100	Microsoft Word	nw_flow_connected [C24.1.1.1 IPv4#774eea8f:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] Output protocol connected (CFNetworkConnection-9642642)
default	17:13:10.092650+0100	Microsoft Word	nw_flow_connected [C24 IPv4#774eea8f:443 in_progress parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Output protocol connected (endpoint_flow)
default	17:13:10.092700+0100	Microsoft Word	[C24 IPv4#774eea8f:443 ready parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_connect @0.048s
default	17:13:10.092777+0100	Microsoft Word	nw_connection_report_state_with_handler_on_nw_queue [C24] reporting state ready
default	17:13:10.092792+0100	Microsoft Word	[C24 IPv4#774eea8f:443 ready parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:changed_viability @0.049s
default	17:13:10.092834+0100	Microsoft Word	[C24.1.1 Hostname#066287c8:443 ready resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.049s
default	17:13:10.092859+0100	Microsoft Word	[C24.1 Hostname#066287c8:443 ready transform (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.049s
default	17:13:10.092883+0100	Microsoft Word	[C24 IPv4#774eea8f:443 ready parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:finish_transport @0.049s
default	17:13:10.093117+0100	Microsoft Word	[C24.1.1.1 IPv4#774eea8f:443 ready channel-flow (satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns)] event: flow:changed_viability @0.049s
default	17:13:10.093261+0100	Microsoft Word	[C24.1.1 Hostname#066287c8:443 ready resolver (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:changed_viability @0.049s
default	17:13:10.093362+0100	Microsoft Word	[C24.1 Hostname#066287c8:443 ready transform (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:changed_viability @0.049s
default	17:13:10.093410+0100	Microsoft Word	[C24 IPv4#774eea8f:443 ready parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] event: flow:changed_viability @0.049s
default	17:13:10.093503+0100	Microsoft Word	nw_flow_connected [C24 IPv4#774eea8f:443 ready parent-flow (satisfied (Path is satisfied), interface: en0[802.11], ipv4, dns)] Output protocol connected (endpoint_flow)
default	17:13:10.093686+0100	Microsoft Word	Connection 24: connected successfully
default	17:13:10.093703+0100	Microsoft Word	Connection 24: TLS handshake complete
default	17:13:10.093781+0100	Microsoft Word	Connection 24: ready C(N) E(N)
default	17:13:10.093883+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> now using Connection 24
default	17:13:10.093976+0100	Microsoft Word	Connection 24: received viability advisory(Y)
default	17:13:10.094259+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> sent request, body S 496
default	17:13:10.104008+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> received response, status 401 content K
default	17:13:10.106643+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> done using Connection 24
default	17:13:10.106888+0100	runningboardd	Acquiring assertion targeting [app<application.com.microsoft.Word.1101153.1152550(501)>:16782] from originator [app<application.com.microsoft.Word.1101153.1152550(501)>:16782] with description <RBSAssertionDescriptor| "com.apple.CFNetwork.StorageDB" ID:373-16782-4708 target:16782 attributes:[
	<RBSDomainAttribute| domain:"com.apple.common" name:"FinishTaskUninterruptable" sourceEnvironment:"(null)">,
	<RBSAcquisitionCompletionAttribute| policy:AfterApplication>
	]>
default	17:13:10.106697+0100	Microsoft Word	[C24] event: client:connection_idle @0.062s
default	17:13:10.106992+0100	runningboardd	Assertion 373-16782-4708 (target:[app<application.com.microsoft.Word.1101153.1152550(501)>:16782]) will be created as inactive as start-time-defining assertions exist
default	17:13:10.106934+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> auth completion disp=2 cred=0x0
default	17:13:10.106973+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> summary for task failure {transaction_duration_ms=63, response_status=401, connection=24, protocol="http/1.1", domain_lookup_duration_ms=3, connect_duration_ms=44, secure_connection_duration_ms=27, private_relay=false, request_start_ms=50, request_duration_ms=0, response_start_ms=60, response_duration_ms=2, request_bytes=1030, response_bytes=655, cache_hit=false}
default	17:13:10.107028+0100	Microsoft Word	Task <7ED490F3-B0EA-428E-B8B2-DB727B2F8EA5>.<1> finished with error [-999] Error Domain=NSURLErrorDomain Code=-999 UserInfo={NSErrorFailingURLStringKey=<private>, NSErrorFailingURLKey=<private>, _NSURLErrorRelatedURLSessionTaskErrorKey=<private>, _NSURLErrorFailingURLSessionTaskErrorKey=<private>, NSLocalizedDescription=<private>}
default	17:13:10.107108+0100	Microsoft Word	Task <F2696B3F-E19B-417B-993D-FD6FFF87E161>.<2> resuming, timeouts(60.0, 604800.0) QOS(0x19) Voucher <private>
default	17:13:10.107867+0100	Microsoft Word	[Telemetry]: Activity <nw_activity 12:2[95DC08E0-2445-4519-B7A8-61F8468F12CC] (reporting strategy default)> on Task <F2696B3F-E19B-417B-993D-FD6FFF87E161>.<2> was not selected for reporting
default	17:13:10.108064+0100	Microsoft Word	Task <F2696B3F-E19B-417B-993D-FD6FFF87E161>.<2> {strength 0, tls 4, sub 0, sig 1, ciphers 0, bundle 0, builtin 0}
default	17:13:10.108187+0100	Microsoft Word	Task <F2696B3F-E19B-417B-993D-FD6FFF87E161>.<2> now using Connection 24
default	17:13:10.108491+0100	Microsoft Word	[C24] event: client:connection_reused @0.064s
default	17:13:10.109203+0100	Microsoft Word	Task <F2696B3F-E19B-417B-993D-FD6FFF87E161>.<2> sent request, body S 496
default	17:13:10.109312+0100	Microsoft Word	Garbage collection for alternative services
default	17:13:10.183419+0100	Microsoft Word	Task <F2696B3F-E19B-417B-993D-FD6FFF87E161>.<2> received response, status 401 content K
default	17:13:10.183592+0100	Microsoft Word	Task <F2696B3F-E19B-417B-993D-FD6FFF87E161>.<2> done using Connection 24
default	17:13:10.183690+0100	Microsoft Word	[C24] event: client:connection_idle @0.139s
default	17:13:10.183806+0100	Microsoft Word	Task <F2696B3F-E19B-417B-993D-FD6FFF87E161>.<2> auth completion disp=2 cred=0x0
default	17:13:10.183855+0100	Microsoft Word	Task <F2696B3F-E19B-417B-993D-FD6FFF87E161>.<2> summary for task failure {transaction_duration_ms=75, response_status=401, connection=24, reused=1, request_start_ms=0, request_duration_ms=0, response_start_ms=75, response_duration_ms=0, request_bytes=1030, response_bytes=655, cache_hit=false}
default	17:13:10.183963+0100	Microsoft Word	Task <F2696B3F-E19B-417B-993D-FD6FFF87E161>.<2> finished with error [-999] Error Domain=NSURLErrorDomain Code=-999 UserInfo={NSErrorFailingURLStringKey=<private>, NSErrorFailingURLKey=<private>, _NSURLErrorRelatedURLSessionTaskErrorKey=<private>, _NSURLErrorFailingURLSessionTaskErrorKey=<private>, NSLocalizedDescription=<private>}
default	17:13:10.185020+0100	Microsoft Word	Connection 24: cleaning up
default	17:13:10.185041+0100	Microsoft Word	[C24 A654744D-6695-48EC-88EA-FE089DACBC2B Hostname#066287c8:443 quic-connection, url hash: 2dac9386, definite, attribution: developer] cancel
default	17:13:10.185098+0100	Microsoft Word	[C24 A654744D-6695-48EC-88EA-FE089DACBC2B Hostname#066287c8:443 quic-connection, url hash: 2dac9386, definite, attribution: developer] cancelled
	[C24.1.1.1 A06CEAA9-9A37-41B7-884A-27BBD34B607A 10.0.20.43:55272<->IPv4#774eea8f:443]
	Connected Path: satisfied (Path is satisfied), viable, interface: en0[802.11], ipv4, dns
	Privacy Stance: Not Eligible
	Duration: 0.141s, DNS @0.000s took 0.003s, TCP @0.004s took 0.016s, TLS 1.2 took 0.027s
	bytes in/out: 5849/2851, packets in/out: 6/11, rtt: 0.019s, retransmitted bytes: 0, out-of-order bytes: 0
default	17:13:10.185693+0100	Microsoft Word	nw_protocol_tcp_log_summary [C24.1.1.1:3] 
	[D8F00E65-44D9-4989-BE33-238CF272697A <private>:55272<-><private>:443]
	Init: 1, Conn_Time: 16.103ms, SYNs: 1, WR_T: 0/0, RD_T: 0/0, TFO: 0/0/0, ECN: 0/0/0, TS: 1, TSO: 0
	rtt_cache: none, rtt_upd: 6, rtt: 19.906ms, rtt_var: 12.187ms rtt_nc: 19.906ms, rtt_var_nc: 12.187ms base rtt: 10ms
	ACKs-compressed: 0, ACKs delayed: 0 delayed ACKs sent: 0
default	17:13:10.185867+0100	Microsoft Word	nw_flow_disconnected [C24 IPv4#774eea8f:443 cancelled parent-flow ((null))] Output protocol disconnected
default	17:13:10.187705+0100	Microsoft Word	nw_connection_report_state_with_handler_on_nw_queue [C24] reporting state cancelled
default	17:13:10.187824+0100	Microsoft Word	tcp_output [C24.1.1.1:3] flags=[F.] seq=1499284456, ack=2752414375, win=2048 state=FIN_WAIT_1 rcv_nxt=2752414375, snd_una=1499284425
default	17:13:10.195409+0100	Microsoft Word	tcp_input [C24.1.1.1:3] flags=[F.] seq=2752414375, ack=1499284457, win=16381 state=FIN_WAIT_2 rcv_nxt=2752414375, snd_una=1499284457
default	17:13:11.178193+0100	runningboardd	Invalidating assertion 373-16782-4708 (target:[app<application.com.microsoft.Word.1101153.1152550(501)>:16782]) from originator [app<application.com.microsoft.Word.1101153.1152550(501)>:16782]
default	17:13:11.674563+0100	runningboardd	Invalidating assertion 373-332-4706 (target:[app<application.com.microsoft.Word.1101153.1152550(501)>:16782]) from originator [osservice<com.apple.coreservices.launchservicesd>:332]
default	17:13:11.677164+0100	Microsoft Word	order window front conditionally: 27a related: 0
default	17:13:11.680321+0100	runningboardd	Invalidating assertion 373-360-4705 (target:[app<application.com.microsoft.Word.1101153.1152550(501)>:16782]) from originator [osservice<com.apple.WindowServer(88)>:360]
default	17:13:11.689539+0100	Microsoft Word	0x135222d40 - [PID=0] WebProcessCache::setApplicationIsActive: (isActive=0)

[#12]

Same problem occurs to us!

[#13]

@johannesboyne 

Hi Johannes,

With third-party add-ins, the best place to get help is with the company that produces the Add-In. No one here is likely to be able to suggest much, even with a popular one like Acrobat or Mendeley. This question, and the responses are a couple of years old. If you think that people who know a lot about Word, but not necessarily about your Add-In could help, I would suggest posting a new question (perhaps with a link to this one) to get the best help.

This is a user-to-user support forum.

[#14]

@Charles_Kenyon
We, as IT-administrators, also experience this issue on our Mac-clients - "Cannot connect to catalog".
The issue not only occurs in Word - but apps like Excel as well. And we don't think it is related to a specific add-in, since we have tried with many different ones, with the same result.

We have deployed a few Add-ins via the Microsoft 365 admin center -> Integrated apps.

We can see the Add-ins in the web-browser on both PC and Mac. We can also see the Add-ins on the PC Desktop client of Word. But when we try to open Office Add-ins, and the Admin Managed-pane, via Word (or other Office-apps like Excel) on a Mac we get following error: Cannot connect to catalog

This error is seen for all users in the tenant.

We have tried the following:

Re-installed the MacOS.
Upgraded to latest version macOS Ventura, 13.2.1.
Secured that the Office version number is the latest: 16.71.
We have "Turn on optional connected experiences" enabled on the Mac-clients.
We have allowed full disk access to Word, Outlook etc.

Is Admin Managed Add-ins supported for Mac or not? It seems like a general issue, since @johannesboyne and @TheIronRock95 also recently reported this.

[#15]

Are the other ones in your company using PC, or Mac? My experience is that this issue is related to Mac, and I have not seen any indication that this feature (Admin Managed Add-ins) works on a Mac.

[#16]

I agree with @securebeam  - This seems to be a more general problem. It worked before for us, and we are an add-in vendor ourselves and have a variety of add-ins deployed internally and managed via admin managed add-ins. It did only happen to one of many macOS devices. 

It definitely works on Macs usually. See the following screenshot here: https://gist.github.com/johannesboyne/46f2ea6b4f9157fe15aa0e07a2a7b520

[#17]

@securebeam 

I solved the problem on my Mac.

1. Removed the entire office install of version 16.71/70, including the license tool and update tool. (https://support.microsoft.com/en-us/office/how-to-remove-office-license-files-on-a-mac-b032c0f6-a431...)
2. Then restarted my laptop.
3. Installed an older office 16.69.23010700. (https://learn.microsoft.com/en-us/officeupdates/update-history-office-for-mac#release-history-for-of...)
4. After this I am able to install Admin Managed Add-ins again.

[#18]

@TheIronRock95 check this out from the official repo: https://github.com/OfficeDev/office-js/issues/3221 

it looks like it's an issue with v16.70 and MacOs Ventura and has been reported and acknowledged by the office team.

[#19]

Open a terminal window and try the following commands which may be helpful:

defaults write com.microsoft.office OfficeWebAddinDisableAllCatalog -bool FALSE
defaults write com.microsoft.office OfficeWebAddinDisableOMEXCatalog -bool FALSE

[#20]

I have the same issue for these products of my Office Pro 2021 for Mac Standalone:

• Word version 16.71 (23031200)

• Excel version 16.71 (23031200)

• PowerPoint version 16.71 (23031200)

Outlook and OneNote have their own errors regarding 2016 versions, even though I thought I purchased a Microsoft Office Pro 2021 for Mac Lifetime License (Standalone).

I have an Intel i7 MacBook Pro. The O/S is Monterey 12.6.3. I typically run stand alone.

Who is "ADMIN" that is managing my "installation" (standalone, connect periodically to Internet) other than me?