CA Automation Point

CA Automation Point r11.5 Tip: how to resolve the EventID=6 (quenetd.exe) message showing in the Application Log.

  • 1.  CA Automation Point r11.5 Tip: how to resolve the EventID=6 (quenetd.exe) message showing in the Application Log.

    Broadcom Employee
    Posted 06-10-2015 11:20 AM

    If you find the following message in your Windows Server Application Log when you reboot the AP server, use the solution specified below to resolve the problem:




    Application ("C:\Program Files (x86)\CA\CA_APPSW\quenetd.exe") (PID: 0x5A0) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, contact the application vendor. The technical information that needs to be conveyed to the application vendor is this: "An RPC method has been called on a connectionless protocol sequence ncadg_ip_udp. Usage and support of this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process, please, see" User Action Contact the application vendor for updated version of the application."




    Although this message might concern the system administrator, it is not indicative of a real problem. This error message occurs when CCI attempts to the

    use RPC protocol for communication and, when this fails, it defaults to TCP.



    To resolve, add the Windows Server system environment variable QUEPROTOCOLS with value TCP.

    Setting the environment variable forces CCI to use TCP as the default communication protocol instead of attempting to use RPC. Consequently, you will not see the error message above in your Application log.

    Follow these steps (on Windows Server 2012)

    1. Enter the Windows Control Panel -> System and Security -> User Accounts
    2. select User Accounts
    3. select "Change my Environment Variables".
    4. Add to the System Variables the QUEPROTOCOLS variable with the value TCP.
    5. You can also use the SetX command with the /m flag to permanently set the environment variable in a command prompt, e.g. SetX QUEPROTOCOLS TCP /m