We have updated our customers to 12.7.0.8525 however now Quickbooks Pro 2021 is not allowing the launch of the company files over the network. If we disable auto containment it works fine. There are no log’s stating its being stopped otherwise we could whitelist it.
Hi @monster-it Suggest you revert to an earlier release of CCS to start, we never push out new versions until we have tested in house and then on a small number of machines.
We started getting calls Thursday from endpoints using QuickBooks Desktop Pro 2019 and 2021. Process of elimination led us to find the same - auto-containment seems to be the cause. This Applications log event has been common for all affected endpoints:
Log Name: Application
Source: QuickBooks
Date: 3/19/2021 11:33:39 AM
Event ID: 4
Task Category: Error
Level: Error
Keywords: Classic
User: N/A
Computer: XXXXXXXXXX3
Description:
An unexpected error has occured in “QuickBooks Desktop Pro 2019”:
DMError Information:-6123Additional Info:The server we are attempting to attach to can’t be found
Event Xml:
<Event xmlns=“http://schemas.microsoft.com/win/2004/08/events/event”>
<System>
<Provider Name=“QuickBooks” />
<EventID Qualifiers=“0”>4</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=“2021-03-19T18:33:39.6867581Z” />
<EventRecordID>20895</EventRecordID>
<Correlation />
<Execution ProcessID=“0” ThreadID=“0” />
<Channel>Application</Channel>
<Computer>XXXXXXXXXX3</Computer>
<Security />
</System>
<EventData>
<Data>QuickBooks Desktop Pro 2019</Data>
<Data>DMError Information:-6123Additional Info:The server we are attempting to attach to can’t be found</Data>
</EventData>
</Event>
Rather than trying to roll-back affected endpoints, we’re leaving auto-containment disabled until this gets resolved.