Automation error - object disconnected from its clients

I have a spreadsheet driven by VBA.

Running on my computer with Excel 2019 it works. I have now transferred it to two other computers running Excel 2016.
On one it works perfectly, the other gives an error message:

Run-time error '-2147417848(80010108)'
Automation error
The object invoked has disconnected from its clients

The code identified as the cause is

Please Login or Register  to view this content.

Can anyone help to resolve this error?

I don't think the problem is with the cited code snippet. It appears much earlier. Without being able to analyze all the code, however, there's not much you can say.

Artik

The complete code is below.

it is driven by a button click to create 4 pdf files from 4 sheets.

Please Login or Register  to view this content.

Try not to activate the sheets before publishing to PDF. By the way, a slightly shortened code:

Please Login or Register  to view this content.

Artik

Thank you for showing the use of Split!

However, the problem is still there.

Can you explain what the meaning of the error message? The help on the Microsoft site is not very useful.

1. Does the problem also occur with other sheets? For the test, remove from Split AD, and in subsequent tests, remove the next sheet names.
2. Where is CommandButton1 embedded? In the sheet or in the Userform?

Artik

It exists on sheet1

The main issue is that I have run the process many times on my computer, as has another user on hers. It's just one other that has the problems.

I have checked the libraries that each system accesses and they are all the same.

So my major concern is I don't understand what the error message is saying. If I did I might be able to solve the issue!

The problem is that the message does not match the presented macro. Sometimes it happens that Excel displays strange messages.
1. One of the reasons might be that the code in the module is too long (over 64KB), but you probably don't have that much code.
2. Another reason may be the accumulation of garbage in the working layer of the file (invisible to the user). In that case, I recommend VBADecompiler from Francisco Orlando Magalhães Filho.
3. You can also check if something changes if you set TakeFocusOnClick to False in the CommandButton properties (Developer/Design mode/Properties -> select CommandButton -> change property TakeFocusOnClick).

This is where my ideas stop, because it is an unusual error, the cause of which is difficult to trace.

Artik