Skip to main content
D
DavidBigelow17-Peridot
17-Peridot
July 11, 2022
Solved

pfcAsyncConnection.AsyncConnection_Connect() throws XToolkitNotFound error for ONE user

  • July 11, 2022
  • 1 reply
  • 1483 views
I am using Creo Parametric Release 6.0 and Datecode6.0.5.1

pfcAsyncConnection.AsyncConnection_Connect() throws XToolkitNotFound error

Here are the errors that I faced
We have a standalone J-Link application. When it tries to connect pfcAsyncConnection.AsyncConnection_Connect() throws a XToolkitNotFound error. This error has been duplicated with a separate test program that does nothing but connect.

This is only happening for one or two users at this one customer. Other customers, and other users at the same customer run this application without issue.

We've verified that their PATH is set up correctly, and that pro_comm_msg.exe is running. Their IT has verified that there isn't a security issue.

Any ideas?
    Best answer by MartinHanak

    Hi,

    Compare the hostname and the computername by running the Command prompt commands:
    hostname
    echo %computername%

     

    If they indeed don't match, as resolution, either compile the runtime to the latest datecode or change the registery key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName

     

    1 reply

    M
    MartinHanak24-Ruby IIIAnswer
    24-Ruby III
    July 12, 2022

    Hi,

    Compare the hostname and the computername by running the Command prompt commands:
    hostname
    echo %computername%

     

    If they indeed don't match, as resolution, either compile the runtime to the latest datecode or change the registery key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName

     

      D
      DavidBigelow17-PeridotAuthor
      17-Peridot
      August 9, 2022

      That fixed it.. Their computername was one letter shorter than their hostname, I assume due to computername allowing fewer characters than hostname.  User is working now!

        Terms & ConditionsAccessibility statement