An unhandled exception occurred in your 3DxWare

[dragonvn]

Hi all,

I just bought a IBM Spaceball 4000 FLX S/N:000829. Although I downloaded a right driver 3DxSoftware_v2-8-2 and installed correctly as instructions, it still doesn't work. In the first time, it works perfectly after installation. However, if either I restart or turn off computer, it doesn't work anymore. And I got this stupid message that made me crazy:

"An unhandled exception occurred in your 3DxWare driver session, would you like to save a diagnostic file?". Either I press Yes or No button, it still doesn't work. If I pressed Yes, I cannot open 3DxWare Control Panel. It doesn't show anything when I select it. And if I click Yes button, another window shows up

Saved dump file to 'C:\Docume~1\TonyTr~1\LocalS~1\Temp\3DxWare.dmp'

I am using Window XP Service Pack 2.

Please help me out because without it I cannot work in Catia.

Thanks,

Tony Tran

[agoenczi]

Hi dragonvn

I suppose that in this case something went wrong during the installation. Please completely remove 3DxSoftware as described here. Afterwards install again 3DxSoftware v2-8-2 making a custom installation and selecting the right version of Catia (R14 and later, or R13 and earlyer) and selecting only 3DxWare (and the plug-ins which you really need).

Please let me know if whether after such a re-installation works.

[dragonvn]

Sorry. I still got the same error after I uninstalled and re-installed as your instructions. Maybe Catia causes this problem. When I open Catia, trees and branches do not show up. Axis System is the main screen instead of being on the left top of screen. Anybody here what wrong with it.

Thanks,

Tony Tran

[jwick]

Try deleting all your saved configurations (under %APPDATA%...).

[dragonvn]

And now I got another problem with VGA Compatible. There is a yellow mark next to Device Manager. How can I know which a right VGA driver to install and where I can download?

Thanks

Tony Tran

[jwick]

?? !!

Just what did you delete under %APPDATA% ? I was suggesting you delete your saved 3DxWare configurations ( %APPDATA%\3Dconnexion\3DxWare\profiles: files named userXX.scg )

If you deleted anything more than that, I suggest you restore your system to the last known working level.

Jim
3Dx Software Development

[dragonvn]

Code: Select all

Try deleting all your saved configurations (under %APPDATA%...)

Could you please tell me where I can find %APPDATA%?

Thanks

[agoenczi]

Hi dragonvn

Just start Explorer (Windows Explorer and not Internet Explorer) and type in in the address field %appdata% - Windows will convert this in a real, not any more symbolic path (which will be something similar with:

"C:\Documents and Settings\<your>\Application Data\").

[cassio]

Hi There!
I'm new to this board and hope this wasn't discussed more
in detail here.

I just received the SpaceNavigator yesterday and installed
the latest drivers from the Web site.

Host is Windows XP, SP2, all updates installed.

I just hit the default installation of the SpaceNavigator Software and
enabled all 3d enabled application plugins out of curiosity how the
plugin works (because I want to get Mentor PCB Design tools supported).
After installation, everything seems to work fine. Demos and
supported software started and worked fine with the exception of
Adobe Reader 8.1 - no navigation there.)

The fun starts after I restarted the Computer the next day.
The CPU was completely hogged up right after login. The
Desktop Icons didn't appear. After about 15minutes I was
able to start the Task Manager and saw that 3dxsrv.exe
sucked up 99% CPU load. After some other 5 minutes I got the
app killed and the system started to respond normally.

So... fine thing! What do you recommend?
Reinstallation is a good idea. But wouldn't it be interesting in the
first place, why 3dxsrv crashed? Any debugging hints (for professionals)?
How to remove single 3dx supported applications to see which
plugin fails? Please document the registry footprint of the 3dx software.

When I restart the driver, I get the attached logfile. Well, it just hangs again. Unfortunately, I don't have a debugger installed on this machine.

Regards,

Cassio

---3DxWare.log ----
23:35:55.937: 3DxWare driver startup: 8/17/2007 23:35:55
23:35:55.937: 3DxWare Driver Version 6.4.4 : July 10, 2007
23:35:55.937: -quiet -- disabled
23:35:55.937: -shutdown -- disabled
23:35:55.937: -protocol -- none given. All protocols enabled.
23:35:55.937: -com -- Disabled, using spcware.ini file settings.
23:35:55.937: -dev -- Disabled, using spcware.ini settings.
23:35:55.937: -eps disabled sending each event.
23:35:55.937: -log enabled
23:35:55.937: -logLevel ffffffff
23:35:55.937: -logFile C:\Dokumente und Einstellungen\xxx\Anwendungsdaten\3Dconnexion\3DxWare\3DxWare.log
23:35:55.937: -searchWarnDlg enabled
23:35:55.937: -showGUI not enabled
23:35:55.937: -hideGUI not enabled
23:35:55.937: UdCtl: Attempting to find (ID=1031) 'German' locale in DE_DE
23:35:55.937: UdCtl: Found resource DLL in C:\Programme\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare\DE_DE\3dxsrv.dll
23:35:55.937: UdCtl: initialization successful.
23:35:55.937: UdCtl: Attempting to open Beliebiges Gerät (-1) on USB.
23:35:55.953: UdCtl: Attempting to load device DLL: C:\Programme\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare\UdDev\HIDDev.dll
23:35:55.968: UdDev: Attempting to open 3Dx-supported HID device on USB
23:36:2.296: UdDev: Beeping the device
23:36:2.296: UdDev: SpaceNavigator opened
23:36:2.296: UdCtl: Using device layer Any Supported 3Dconnexion USB Device supporting 0x22208050
23:36:2.296: UdCtl: Device 0 (Beliebiges Gerät(-1) on USB) -- enabled.
23:36:2.296: Device Type: 6
Num Buttons: 2
Num DOF: 6
CanBeep: 1
Device Name: SpaceNavigator
Port Name: USB
Firmware: HID Firmware Version 3.18
Version 3.18
Orientation 0
23:36:2.312: UdCtl: Attempting to load UI DLL: C:\Programme\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare\UdUi\udui.dll
23:36:2.859: UdUi->InitDLL: UI DLL Initializing
23:36:24.390: UdUi:TlReadConfigFile: Reading file: C:\Programme\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare\DE_DE\profiles\default\any.scg
23:36:24.421: UdUi:TlReadConfigFile: Reading file: C:\Programme\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare\DE_DE\profiles\default\any.scg
23:36:24.437: UdUi->SetOrientation: About to create windows.
23:36:24.484: SetOrientation: B4 ResetAppNameBox call
23:36:24.484: 23:36:24.484: SetOrientation: After ResetAppNameBox call
23:36:28.500: UdUi->SetOrientation: Windows Created.
23:36:28.500: UdCtl: UI (3DxWare UI v3.0) initialized.
23:36:28.500: UdCtl: Attempting to load transport DLL C:\Programme\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare\UdTrans\kbdtrans.dll.
23:36:28.562: kbdtrans: Keyboard transport layer initialization
23:36:28.562: kbdtrans: Function table load successful
23:36:28.593: kbdtrans: Sendkey.dll successfully loaded.
23:36:28.687: UdCtl: Transport DLL: kbdtrans.dll -- enabled
23:36:28.687: Name: Window Keypress 1.0
23:36:28.687: Protocol ID: 50
23:36:28.687: Event Mask: 0x100
23:36:28.687: UdCtl: Attempting to load transport DLL C:\Programme\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare\UdTrans\mwmtrans.dll.
23:36:28.781: mwmtranslog - Messages were registered
23:36:28.781: mwmtranslog - Opened hidden window
23:36:28.781: Mwmtrans: Username: xxx
23:36:28.812: mwmtrans.dll:UdTransInit: NOT Terminal Services Environment
23:36:28.812: UdCtl: Transport DLL: mwmtrans.dll -- enabled
23:36:28.812: Name: Windows Messaging
23:36:28.812: Protocol ID: 10
23:36:28.812: Event Mask: 0x76
23:36:28.812: UdCtl: Attempting to load transport DLL C:\Programme\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare\UdTrans\pxytrans.dll.
23:36:29.046: Loading Proxy DLLs
23:36:29.046: UdCtl: Transport DLL: pxytrans.dll -- enabled
23:36:29.046: Name: Proxy
23:36:29.046: Protocol ID: 5
23:36:29.046: Event Mask: 0x76
23:36:29.046: UdCtl: Attempting to load transport DLL C:\Programme\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare\UdTrans\s80trans.dll.
23:36:29.046: mwmtrans: MagellanRPCServerInterface: endpoint is Magellan3DController
23:36:29.109: s80trans: SpaceWare 8.0 transport layer initialization
23:36:29.109: s80trans: Function table load successful
23:36:29.109: s80trans: Memory map loaded successfully
23:36:29.109: UdCtl: Transport DLL: s80trans.dll -- enabled
23:36:29.109: Name: SpaceWare 8.0
23:36:29.109: Protocol ID: 30
23:36:29.109: Event Mask: 0x76
23:36:29.109: UdCtl: numWaitHdls: 2 numTransHdls: 1 numDevHdls: 1
23:36:29.171: UdCtl: udfenNT.dll loaded sucessfully
----------------------------------------------------

[cassio]

Okay, I tried to uninstall the crappy 3dxWare, resulting in:

Error 1905.Module C:\Programme\3Dconnection\3Dconnexion 3DxSoftware\3DxQuickTime\3DxQuick.dll failed to unregister. HRESULT -2147220472. Contact your support personnel.

Well... who is my support personnel?

What a pity. The product seems to be really cool, but the software
is really a shame.

Regards,

cassio.

[jwick]

Hello cassio,

I don't think you have a crash. You have an infinite loop of some sort. We occasionally, but rarely see this. It is often traced down to antivirus software preventing the USB port from being opened cleanly. Please temporarily disable any antivirus software from looking at USB ports and report back to us.

3DxSrv.exe is the driver, not one of the plugins. Removing plugins is not necessary.

I don't think any Mentor PDB tools support the SpaceNavigator. Enough people haven't contacted them to ask for it. I may be wrong. Sometimes we are not told when an ISV adds support.

Jim
3Dx Software Development

[cassio]

Hello cassio,
I don't think you have a crash. You have an infinite loop of some sort.

I don't see a difference here. The problem renders the machine
unusable and not easily fixable by average users which is
definitely a showstopper!
Did you ever thought about putting some timeouts into critical
functions into your driver or publishing debug versions to
get user feedback?

The RBC9 SpaceDriver works just fine without any hazzles on
the same environment. So it's not really some antivirus software
which caused the troubles here. Bad antivirus scanners seems
to be the default excuse for every weak piece of software.

Regards,

Cassio

[jwick]

Believe me cassio, if this problem was in any way reproducible on any one of our dozens of test machines, it would have been fixed a long time ago.

Falling on my sword now...