3CXWin8Phone.exe crashing on Win10 (1903)

[Pat3]

I installed 3CX Win8 Phone (Link from the WebApp) and the Program immediately crashes at start:

Name der fehlerhaften Anwendung: 3CXWin8Phone.exe, Version: 16.0.1.81, Zeitstempel: 0x5c6e6393
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.18362.267, Zeitstempel: 0x91664cab
Ausnahmecode: 0xe06d7363
Fehleroffset: 0x00113442
ID des fehlerhaften Prozesses: 0x8938
Startzeit der fehlerhaften Anwendung: 0x01d55f25183e3297
Pfad der fehlerhaften Anwendung: C:\ProgramData\3CXPhone for Windows\PhoneApp\3CXWin8Phone.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll
Berichtskennung: f0cddc79-7a7b-400d-a996-b05bf60d7f65
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

und der 2. Eintrag:
Anwendung: 3CXWin8Phone.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: Ausnahmecode e06d7363, Ausnahmeadresse 76CA3442

Windows 10 64bit
Version 1903
Build: 18362.295

 

[JohnS_3CX]

Hi Pat3

Its not really possible to know what causes this.

My suggestion is to at least make sure you have the VCP redistributables. These are installed when the client is installed but if you deny the installation then the client cannot run.

1. Go to https://www.microsoft.com/en-us/download/details.aspx?id=26999
2. Get vcredist_x86.exe version 10.0
3. Install it, then relaunch the client

 

[Pat3]

I finally found the issue, it was a conflict of a DShow library initialization.

desktop_dev.cp Desktop video src initialized with 2 device(s):
desktop_dev.cp 0: Screen 1
desktop_dev.cp 1: Screen 2
dshow_dev.c Failed initializing DShow: COM library already initialized with incompatible concurrency model

I'm just wondering why the application directly crashes without any notification if a screen grabber functionality is not working on a CTI telephone client...

 

[JohnS_3CX]

Do you mean you are using a screen capture software?

 

[Pat3]

No it conflicted with a 3th party USB camera driver

 

[JohnS_3CX]

Oh I see. These things can happen from time time, I don't know if it can be avoided in all cases.

The client probably won't change much in the future as we are more focused on bringing our webclient in the forefront of development. The only thing I can recommend is if you can look for a newer camera driver if this is an option.

Some cameras might work without their 3rd party software (like apps that remove the background, or change you picture to look like an avatar etc) and can just work with installing only their driver. Hope this helps.

 

[Pat3]

Unfortunatley to install the 3CX client is the only possibility to register 3CX in Win10 for the URL:tel protocol

 

[JohnS_3CX]

Do you just need to click on numbers from websites or your CRM and call them?

You can use click to call with our Web Client and this does not require you to install the Windows client, you just need to have google chrome.

https://www.3cx.com/phone-system/click-to-call/

 

[Pat3]

No it's not just from Websites. We have local applications which require to handle URL:tel from Windows natively

 

[JohnS_3CX]

Ok then just install click to call, and log the user in to the webclient via Chrome.

You should be able to click numbers on websites and have the webclient dial for you either as a soft client or CSTA on your deskphone




Note: CSTA replaced the old CTI mode, so much older phones wont work in this mode