The object invoked has disconnected from its client

The object invoked has disconnected from its client

3D4Play
Collaborator Collaborator
1,632 Views
11 Replies
Message 1 of 12

The object invoked has disconnected from its client

3D4Play
Collaborator
Collaborator

What the title says. This is a new error message, for sure. It happened after successfully creating an iPart. Non-fatal. Inventor just threw it, then went on as usual after the OK click-out. What's it mean?

 

 

0 Likes
1,633 Views
11 Replies
Replies (11)
Message 2 of 12

mcgyvr
Consultant
Consultant

Seems to typically mean a program assigned to open or do something is not available. (Whatever program they are using for ipart table creation or something now maybe.. I know there are some changes related to not needing excel/LibXL)

I wouldn't worry if I could still edit the ipart table/add rows,etc...



-------------------------------------------------------------------------------------------
Inventor 2023 - Dell Precision 5570

Did you find this reply helpful ? If so please use the Accept Solution button below.
Maybe buy me a beer through Venmo @mcgyvr1269
0 Likes
Message 3 of 12

johnsonshiue
Community Manager
Community Manager

Hi! It seems to be related to certain VB.Net or VBA related operations. Here is a related discussion.

 

https://forums.autodesk.com/t5/inventor-customization/macro-issue-the-object-invoked-has-disconnecte...

 

Is here any VB script or iLogic rule inside the iPart factory? Personally, I think iPart factory should be totally driven by its author table. No iLogic rule or VB script should be used within the factory. It is because iPart was designed to create library parts. Any attempt to alter an iPart outside of the table may lead to confusing behaviors.

There are only a few exception I can think of when iLogic rule can be used within an iPart. For example, use iProperty to drive text parameter for an emboss feature.

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 4 of 12

3D4Play
Collaborator
Collaborator

Johnson,

 

No VB or iLogic involved. In further investigation, I see that it's actually not creating the iPart, and there is an (as yet, unknown) issue with Excel. Creating an iPart is now crashing Inventor. Excel won't start on its own, although it starts and runs an instance in the background (according to task manager) each time it's been called from Inventor or with start program. I've done the latest Windows updates, and I'm digging a little deeper.

0 Likes
Message 5 of 12

johnsonshiue
Community Manager
Community Manager

Hi! Try a few things. Close Inventor and go to CMD. Type in the following command (replace ? with the release number).

 

"C:\Program Files\Autodesk\Inventor 202?\Bin\Inventor.exe" / install

 

This will help Windows register Inventor properly. Restart Inventor. Create an iPart. If it is still crashing, you may want to uninstall Microsoft Office and reinstall it. Excel might not have been registered properly somehow.

Many thanks!

 



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 6 of 12

3D4Play
Collaborator
Collaborator

Thanks, I will try the first step, and do the rain dance.  I've already tried the Excel repair and reinstall. It did not work, but there were still errors, and I'm still researching.

0 Likes
Message 7 of 12

3D4Play
Collaborator
Collaborator

Well. Nope. This is after the Inventor re-registration you suggested. Now back to Excel.

 

3D4Play_0-1610663745536.png

 

 

0 Likes
Message 8 of 12

johnsonshiue
Community Manager
Community Manager

Hi! Did Inventor crash right after start? Or try to create an iPart factory?



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 9 of 12

3D4Play
Collaborator
Collaborator

Opened fine, just crashed when I tried to create the iPart

0 Likes
Message 10 of 12

johnsonshiue
Community Manager
Community Manager

Hi! Have you installed the latest MS Office Update? The crash seems to indicate Inventor.exe is blocked from starting up Excel.exe. Try a few other things.

1) Run Inventor.exe as admin.

2) Go to Control Panel -> System -> Advanded System Settings -> Environment Variables -> create "UseLibXL" and set its value to "False", not '0'

Many thanks!

 



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes
Message 11 of 12

3D4Play
Collaborator
Collaborator

Johnson,

 

That did not work. I had in the past used the UseLibXL environment variable but cleared it when I upgraded to 2020. I've had no issues until this started a few days ago.

 

I am not running Office, only Excel, and it's an old version - frankly, the only reason I even have it installed is for Inventor. Here's a shameless plug and plea for OpenOffice (LibreOffice) support. If you had that support I'd dump Excel in a flash. OK, off my soapbox...

 

0 Likes
Message 12 of 12

johnsonshiue
Community Manager
Community Manager

Hi! For 2020, "UseLibXL" needs to be set to '0.' For 2021, it needs to be set to "False."

Many thanks!



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes