The type initializer for 'TDx.SmartUi.App' threw an exception

Questions and answers about 3Dconnexion devices on Windows.

Moderator: Moderators

Post Reply
RichardWest
Posts: 6
Joined: Fri Feb 18, 2022 12:49 pm

The type initializer for 'TDx.SmartUi.App' threw an exception

Post by RichardWest »

Greetings.

I have a customer that is getting the following error when launching the 3DConnexion app. "The type initializer for 'TDx.SmartUi.App' threw an exception" So far I have done the following.
Rollback windows updates that were recently installed
Uninstalled the 3DConnexion software
installed 3DxWare64_v10-8-5_r3424 from a fresh download
uninstalled .NET 4.8
installed .NET4.8
installed all Windows updates
temporarily disabled Anti-Virus software
tried logging as a Domain Admin user

None of this has resolved the issue. Along with the exception for SmartUI I also get 2 other exceptions. One for piemenus and one for LCD . All suggestions (other than wiping the drive and starting again) are welcome.
ngomes
Moderator
Moderator
Posts: 3458
Joined: Mon Nov 27, 2006 7:22 am
Contact:

Re: The type initializer for 'TDx.SmartUi.App' threw an exception

Post by ngomes »

RichardWest wrote: Fri Feb 18, 2022 1:05 pm installed .NET4.8
Why version 4.8 of .NET Framework? The driver components (3DxSmartUi.exe, 3DxVirtualLCD.exe, etc) have a dependency on v. 4.7.2, not 4.8.

What operating system is your customer using? If it is a recent version of Windows 10 (or 11), then there is no need to install the .NET Framework since the required version is already included in Windows.
Nuno Gomes
RichardWest
Posts: 6
Joined: Fri Feb 18, 2022 12:49 pm

Re: The type initializer for 'TDx.SmartUi.App' threw an exception

Post by RichardWest »

ngomes wrote: Fri Feb 18, 2022 1:22 pm
RichardWest wrote: Fri Feb 18, 2022 1:05 pm installed .NET4.8
Why version 4.8 of .NET Framework? The driver components (3DxSmartUi.exe, 3DxVirtualLCD.exe, etc) have a dependency on v. 4.7.2, not 4.8.

What operating system is your customer using? If it is a recent version of Windows 10 (or 11), then there is no need to install the .NET Framework since the required version is already included in Windows.
.NET 4.8 as they have other software that requires the current version of .NET which is 4.8. They are running Windows 10 Pro. This was working last week until the 17 Feb. Windows updates were applied that morning and the mouse stopped working. You would think that rolling back the update would correct it, but it didn't.
ngomes
Moderator
Moderator
Posts: 3458
Joined: Mon Nov 27, 2006 7:22 am
Contact:

Re: The type initializer for 'TDx.SmartUi.App' threw an exception

Post by ngomes »

Check if you can find a "3DxSmartUi.log" file in %LOCALAPPDATA%\3Dconnexion\3DxWare and then share the file's content here.
RichardWest
Posts: 6
Joined: Fri Feb 18, 2022 12:49 pm

Re: The type initializer for 'TDx.SmartUi.App' threw an exception

Post by RichardWest »

ngomes wrote: Mon Feb 21, 2022 9:22 am Check if you can find a "3DxSmartUi.log" file in %LOCALAPPDATA%\3Dconnexion\3DxWare and then share the file's content here.
2/18/2022 12:40:18 PM, , Line 0: createdNewMutex: True
2/18/2022 12:40:18 PM: Startup
2/18/2022 12:40:18 PM: Not found resource string for key 'AppNotSupported'. English value is used
2/18/2022 12:40:18 PM, , Line 0: Exception: The type initializer for 'TDx.SmartUi.App' threw an exception. Terminating
2/18/2022 12:40:20 PM: 3DxServiceState.xml contents:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><DriverState xmlns="" FormatVersion="1.3"><_3DxWareInfo><Dir>3Dconnexion 3DxWare 10 InstallLocation missing from reg</Dir><Version>10.8.5.3424</Version></_3DxWareInfo><_3DxWinCoreInfo><Dir>C:\Program Files\3Dconnexion\3DxWare\3DxWinCore\</Dir><Version>17.8.5.19118</Version></_3DxWinCoreInfo><SoftwareUpdateInfo><Status>Status_Unknown</Status><CheckForUpdatesMessage>CheckForUpdates</CheckForUpdatesMessage></SoftwareUpdateInfo><Global><Settings><Culture>en-US</Culture></Settings></Global><LastInput><DeviceID>ID_ProductID_C626</DeviceID></LastInput><DeviceTypeList><Device><Name>SpaceNavigator</Name><ID>ID_ProductID_C626</ID><Discontinued /><Connections><Connection><DevConnection>SI_CONNECTION_USB</DevConnection><ActiveState>SI_ACTIVESTATE_USBCONNECTED</ActiveState></Connection></Connections><CfgProperties><ID>ID_STR_EXPLORER_BACKGROUND</ID><Name>STR_EXPLORER_BACKGROUND</Name><FileName>C:\Program Files\3Dconnexion\3DxWare\3DxWinCore\Cfg\Explorer_Background.xml</FileName><InheritsFromID>ID_Default_Cfg</InheritsFromID></CfgProperties><AppInfo><Name>STR_EXPLORER_BACKGROUND</Name><ExecutableName>explorer.exe</ExecutableName><ProcessID>9948</ProcessID><HashCode>1411</HashCode><SyncID>0</SyncID><ApplicationName>Desktop</ApplicationName><CurrentButtonBank>Default</CurrentButtonBank><CurrentButtonBankInfo><ID>Default</ID></CurrentButtonBankInfo><CurrentAxisBank>Default</CurrentAxisBank><CreateCfgInfo Type="User"><Filename>C:\Users\dbunting\AppData\Roaming\3Dconnexion\3DxWare\Cfg\Explorer_Background.xml</Filename><AppInfo><Signature><Name>STR_EXPLORER_BACKGROUND</Name></Signature><Options></Options></AppInfo><CfgProperties><ID>ID_STR_EXPLORER_BACKGROUND</ID><Name>STR_EXPLORER_BACKGROUND</Name><InheritsFromID>ID_STR_EXPLORER_BACKGROUND</InheritsFromID></CfgProperties></CreateCfgInfo></AppInfo></Device></DeviceTypeList><DeviceInfoList><Device><Name>SpaceNavigator</Name><ID>ID_ProductID_C626</ID><VendorID>46d</VendorID><ProductID>c626</ProductID><FirmwareVersion>4.04</FirmwareVersion><Discontinued /><DevType>SI_SPACENAVIGATOR</DevType><DevClass>SI_CLASS_3DMOUSE</DevClass><DevConnection>SI_CONNECTION_USB</DevConnection><Location><USB>\\?\HID#VID_046D&amp;PID_C626#6&amp;247F9DB&amp;0&amp;0000#{4D1E55B2-F16F-11CF-88CB-001111000030}</USB></Location><PairingCode>ffffffffffffff000000</PairingCode><LastSeen>2022:2:5:18:17:32:24:796</LastSeen><ActiveState>SI_ACTIVESTATE_USBCONNECTED</ActiveState><ShowInGUI>true</ShowInGUI></Device></DeviceInfoList></DriverState>
RichardWest
Posts: 6
Joined: Fri Feb 18, 2022 12:49 pm

Re: The type initializer for 'TDx.SmartUi.App' threw an exception

Post by RichardWest »

@ngomes
have you had time to review the 3DxSmartUi.log that I shared?
ngomes
Moderator
Moderator
Posts: 3458
Joined: Mon Nov 27, 2006 7:22 am
Contact:

Re: The type initializer for 'TDx.SmartUi.App' threw an exception

Post by ngomes »

RichardWest wrote: Tue Mar 01, 2022 11:30 am have you had time to review the 3DxSmartUi.log that I shared?
Sorry for keeping you waiting but we only managed to complete the analysis yesterday.

The log didn't tell us anything. At this point, you may want to reach to our Technical Support team and have this looked at.
RichardWest
Posts: 6
Joined: Fri Feb 18, 2022 12:49 pm

Re: The type initializer for 'TDx.SmartUi.App' threw an exception

Post by RichardWest »

ngomes wrote: Thu Mar 03, 2022 7:54 am
RichardWest wrote: Tue Mar 01, 2022 11:30 am have you had time to review the 3DxSmartUi.log that I shared?
Sorry for keeping you waiting but we only managed to complete the analysis yesterday.

The log didn't tell us anything. At this point, you may want to reach to our Technical Support team and have this looked at.

There was one line in the logs that caught my eye. <Device><Name>SpaceNavigator</Name><ID>ID_ProductID_C626</ID><Discontinued />
It was the discontinued part that was what I was spotting. Compared to other workstations using the exact same mouse and working, the driver version was different. The working systems had driver 10.6.4 whereas the one not working was using driver version 10.8.6. When we uninstalled the driver and installed 10.6.4, everything works.

Conclusion: The current driver does not support legacy devices. Seems like either you use old outdated drivers or make sure you have a current product. it's a shame that 3Dconnexion doesn't support older products in newer releases.
ngomes
Moderator
Moderator
Posts: 3458
Joined: Mon Nov 27, 2006 7:22 am
Contact:

Re: The type initializer for 'TDx.SmartUi.App' threw an exception

Post by ngomes »

RichardWest wrote: Thu Mar 10, 2022 11:19 am Conclusion: The current driver does not support legacy devices.
Version 10.8.6 is the very latest release and has support for the SpaceNavigator as stated here.

It would appear that you're affected by something else that changed in the driver since version 10.6.4 (released at the end of 2019).

At this point, I suggest getting in touch with our Technical Support team.
luping
Posts: 1113
Joined: Wed Mar 20, 2019 5:54 pm

Re: The type initializer for 'TDx.SmartUi.App' threw an exception

Post by luping »

RichardWest wrote: Thu Mar 10, 2022 11:19 am
ngomes wrote: Thu Mar 03, 2022 7:54 am
RichardWest wrote: Tue Mar 01, 2022 11:30 am have you had time to review the 3DxSmartUi.log that I shared?
Sorry for keeping you waiting but we only managed to complete the analysis yesterday.

The log didn't tell us anything. At this point, you may want to reach to our Technical Support team and have this looked at.

There was one line in the logs that caught my eye. <Device><Name>SpaceNavigator</Name><ID>ID_ProductID_C626</ID><Discontinued />
It was the discontinued part that was what I was spotting. Compared to other workstations using the exact same mouse and working, the driver version was different. The working systems had driver 10.6.4 whereas the one not working was using driver version 10.8.6. When we uninstalled the driver and installed 10.6.4, everything works.

Conclusion: The current driver does not support legacy devices. Seems like either you use old outdated drivers or make sure you have a current product. it's a shame that 3Dconnexion doesn't support older products in newer releases.
If there's SpaceNavigator hardware, only update the 3DxWare driver version to v10.8.3, no newer version should be installed if there's only SpaceNavigator, that's all.
Post Reply