hexagon logo
Register Sign in
  • Replies 38 replies
  • Subscribers 223 subscribers
  • Views 379 views
  • Users 0 members are here
Options
Related

PC-DMIS Software to Server connection unbearable. Please help.

Alvin_A2
Hello. I have a 7.10.7 SF electric machine running PC-DMIS 2020 R2. We all know the unfortunate notoriousness of software crashes. But, I am having too many issues and need help.

From my understanding, I have a virtual dongle and with that, every line of code or action I do with PC-DMIS communicates online to its server base. I have had my software crash several times just from saving as one example. There are also times when I try to re-open the software and when I open a project it says that the server is busy and I have to restart my computer to fix it. (I've checked my task manager and could not find anything to stop in order to avoid restarting the computer).

Should I try to receive a physical dongle like the older machines to avoid these issues? I never had this stuff happen until I started using the virtual dongle. I don't even know if I can do that to be honest.

Also, I haven't done my research thoroughly enough but I'm at the point where I feel I can't trust Exact Measurements versus Legacy anymore. Sometimes the differences in results can be over .001 (inches) and even greater. I know I've set up my datums properly for both ways to spit out the results. I also find it silly how in R1 you could get away with apparently a not properly constrained datum to give results that may be inaccurate and now 2020 R2 won't allow you to even create the feature if it's not constrained right with the datum scheme.

Thanks for taking the time to read my post! I appreciate it.
Parents
  • After KTM and Don's suggestion, I just saved and I am still stuck on a frozen never ending spinning wheel.

    You'd think the prices Hexagon charges for everything that after decades they could figure out how to make their software not crash.

    Thanks for all the input and help from everyone, but this is insane that it won't stop.
  • in reply to Alvin_A2
    I know this post is really old but I came here to say that I am having similar issues as Alvin_A2. We are using the Hexagon supplied windows PCs and PC-DMIS (2021.1) crashes so hard that we can't open the task manager or windows start button and the machine has to be forcibly restarted. The windows event viewer shows this error. It seems like it's something related to the .NET runtime. If anyone is still paying attention to this thread and you solved this issue I would love some help.

    Exception Info: System.ComponentModel.Win32Exception
    at MS.Win32.UnsafeNativeMethods.RegisterClassEx(WNDCLASSEX_D)
    at MS.Win32.HwndWrapper..ctor(Int32, Int32, Int32, Int32, Int32, Int32, Int32, System.String, IntPtr, MS.Win32.HwndWrapperHook[])
    at System.Windows.Threading.Dispatcher..ctor()
    at System.Windows.Threading.Dispatcher.get_CurrentDispatcher()
    at System.Windows.Application..ctor()
    at PcDmisShared.PcDmisApplication..ctor()
    at PcDmisShared.PcDmisApplication.Initialize()
    at <Module>.PcDmisViewFactory.initializeViewFactoryResources()
    at <Module>.n()

    The problem appears to be a System.ComponentModel.Win32Exception, which usually implies a Windows API call went south.

    RegisterClassEx: Indicates a problem with registering a window class, which is pretty low-level. This might be because the class is already registered, or some parameters are incorrect.

    Dispatcher: Involved in managing the UI thread. If this is failing, it's a sign that the WPF application is having fundamental issues initializing.
Reply
  • in reply to Alvin_A2
    I know this post is really old but I came here to say that I am having similar issues as Alvin_A2. We are using the Hexagon supplied windows PCs and PC-DMIS (2021.1) crashes so hard that we can't open the task manager or windows start button and the machine has to be forcibly restarted. The windows event viewer shows this error. It seems like it's something related to the .NET runtime. If anyone is still paying attention to this thread and you solved this issue I would love some help.

    Exception Info: System.ComponentModel.Win32Exception
    at MS.Win32.UnsafeNativeMethods.RegisterClassEx(WNDCLASSEX_D)
    at MS.Win32.HwndWrapper..ctor(Int32, Int32, Int32, Int32, Int32, Int32, Int32, System.String, IntPtr, MS.Win32.HwndWrapperHook[])
    at System.Windows.Threading.Dispatcher..ctor()
    at System.Windows.Threading.Dispatcher.get_CurrentDispatcher()
    at System.Windows.Application..ctor()
    at PcDmisShared.PcDmisApplication..ctor()
    at PcDmisShared.PcDmisApplication.Initialize()
    at <Module>.PcDmisViewFactory.initializeViewFactoryResources()
    at <Module>.n()

    The problem appears to be a System.ComponentModel.Win32Exception, which usually implies a Windows API call went south.

    RegisterClassEx: Indicates a problem with registering a window class, which is pretty low-level. This might be because the class is already registered, or some parameters are incorrect.

    Dispatcher: Involved in managing the UI thread. If this is failing, it's a sign that the WPF application is having fundamental issues initializing.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement