Hello,

I'm getting the "Failed to connect to Excel" message as well but in somewhat different circumstances.

Windows 10 Pro, 21H1 (64 Bit)
Adagio Ledger 9.3B (210331). AP is having the issue as well, I didn't check any others.
Office 2016 Pro Plus (64 Bit)

I checked the GL 9.3B SP 210527 notes and didn't see any mention that seemed issue relevant
A repair of Excel did not work for me.
I checked the LocalServer and LocalServer32 Default Registry Entries and the path to launch Excel is correct


Here's a scenario that I hope means something to the developer brains among us ...

> Check Windows Task Manager (WTM) - no instances of Excel running
> Open GL Sample Data and try Excel Directing the GL Batches Grid
> Nothing "seems" to happen, as in Excel does not appear to launch and does not show on the status bar and I will get the "Failed to connect to Excel" message
> Check the WTM and an Excel instance shows and shows that it launched from the expected location
> Close the Failed ... message (no other messages appear) and go and try to Excel Direct the GL Departments Grid
> Nothing happens and no Failed message appears
> Check the WTM and still only one instance of Excel
> Launch Excel directly from desktop (launches from same location that the WTM instance started by the GL shows) to a blank worksheet (interestingly Book2) and just leave open and minimised
> Check the WTM and now two instances of Excel running but I still can't see anything of the app from the first instance that was, I assume, started by Adagio GL
> Go back to GL and now try to Excel Direct the Edit Accounts Grid - action now, Excel opens showing my Excel Direct in Book 3
> Check WTM and there are still only 2 instances of Excel showing. However, I can point to the Excel icon on the Task Bar and see three workbooks pop up, Book 2 (on left) the Empty Sheet, Book 1 (middle) see next note and Book 3 (right) the last attempt that worked, the Edit Accounts grid.
> VERY INTERESTINGLY, Book 1 shows the Department grid. Remember, that was my second attempt that showed no result but it was after the failed first attempt that had caused an Excel instance to open in the WTM even though nothing actually showed up on the user's desktop not task bar
> Leaving all of the other Excel Sheets open, the next thing I tried is an Excel Direct Print of the Trial Balance report - up came the "Failed to connect to Excel" message again [Ok] then gave "Error code 1000 on ToXLSaveWorkbook" [Ok] then gave "ExcelDirect failed" [Ok] then returned to the report options dialog window
> Check the WTM and now a third Excel instance added there
> Immediately try same TB Excel Direct Print again and same result (messages and another 4th Instance of Excel in WTM)
> I Closed the three Workbooks (1, 2 and 3) and the 2 Excel instances in WTM that they were associated with closed
> The 2 Excel instances left in WTM I believe are to do with the 3 failed Excel Direct Print attempts of the TB at the end. Though they are in WTM, no Excel shows as running on the Status Bar
> I used the WTM to End the 2 "orphaned" instances of Excel

NB: As the above seemed to show that Excel Direct (not Excel Direct Print) worked better if Excel was already open, I then opened a blank Excel workbook (Book1) and left minimised while trying to export the Departments Grid - worked great (Book2). Closed it (leaving Book1 open and minimised) and tried the Edit Batches Grid - Worked fine

Sooooo ...
<> Excel Direct just won't work properly unless Excel is already opened
<> Excel Direct Print won't work properly at all

Any suggestions before I tell their IT to
1. Remove Office 64 Bit completely (using the Microsoft Office Uninstall Tool) and re-install
If no joy then ...
2. Remove Office 64 Bit completely (using the Microsoft Office Uninstall Tool) and re-install Office 32 Bit

Thanks, Pete