V14 3CXPhone Crashing once provisioned

Discussion in 'Windows' started by scottdAMS, Sep 22, 2015.

Thread Status:
Not open for further replies.
  1. scottdAMS

    Joined:
    Sep 22, 2015
    Messages:
    2
    Likes Received:
    0
    Upgraded recently to v14 and proceeded to upgrade the 3cxphone software and as soon as a user provisions it from the new welcome email it crashes. Now this works fine on my machine and I cannot see any differences.
    Things I've tried...

    1. fresh install
    2. Different phones - Cisco 502g and Htek UC842
    3. provision working end user to machines having the issue - still crashes

    At the end of the log file is the below error

    [22.09.2015 18:50:02.043][2] System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it.
    at System.Windows.Threading.Dispatcher.VerifyAccess()
    at System.Windows.DependencyObject.SetValue(DependencyProperty dp, Object value)
    at _3CXWin8Phone.Views.DialPadView.ClearBurstStatus()
    at _3CXWin8Phone.Views.DialPadView.Instance_SipShutdown(Object sender, EventArgs e)
    at _3CXWin8Phone.Biz.OnSipShutdown()
    at _3CXWin8Phone.Biz.FreeSIPResources()

    [22.09.2015 18:50:02.048][2] Exception occurred during application exit
    [22.09.2015 18:50:02.048][2] System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it.
    at System.Windows.Threading.Dispatcher.VerifyAccess()
    at _3CXWin8Phone.App._ReleaseAndShutDown(Boolean exitApplication)


    anyone seen anything similar??
     
  2. MichaelB

    MichaelB Member
    3CX Support

    Joined:
    Aug 25, 2009
    Messages:
    401
    Likes Received:
    3
    Update your .net framework from 4.0 to 4.5
    Its a bug in .net framework 4.0
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. scottdAMS

    Joined:
    Sep 22, 2015
    Messages:
    2
    Likes Received:
    0
    Thanks Michael that resolved the issue
     
Thread Status:
Not open for further replies.