locked
ATA stuck at startup: The request is not supported RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    After installing the ATA Leight Gateway on a Windows 2012 R2 server with AD, DNS, DHCP and Hyper-V, 24GB RAM, 340GB free on drive C: it stops on startup:

    The Microsoft Advanced Threat Analytics Gateway service terminated unexpectedly.  It has done this x time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

    2017-03-10 17:16:11.5299 8796 5   00000000-0000-0000-0000-000000000000 Error [ServiceChannel] System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: The request is not supported (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

    System.ComponentModel.Win32Exception: The request is not supported
       at System.ServiceModel.Dispatcher.TaskMethodInvoker.InvokeEnd(Object instance, Object[]& outputs, IAsyncResult result)
       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeEnd(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage7(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).

    And this one in the ExceptionStatisticsLog:

    Count: 390

    System.ComponentModel.Win32Exception (0x80004005): The request is not supported
       at System.ServiceModel.Dispatcher.TaskMethodInvoker.InvokeEnd(Object instance, Object[]& outputs, IAsyncResult result)
       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeEnd(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage7(MessageRpc& rpc)
       at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

    Any help is appreciated

    Pieter

    Wednesday, March 15, 2017 9:31 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote
    Hello Pieter,

    You'd better separate the deployment for ATA Lightweight Gateway and Hyper-V. You can deploy domain controller and ATA Lightweight Gateway on a dedicated server, such as a physical machine or a VM.

    Hyper-V is a virtualization technology, which deploys a hypervisor between the underlying hardware, and the operating system. This may cause unexpected behavior, especially if the application, such as ATA Lightweight Gateway needs to call the underlying hardware, such as CPU, Memory and Ethernet. The most common issue is race condition.


    Best regards,
    Andy Liu

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 16, 2017 2:10 AM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote
    Hello Pieter,

    You'd better separate the deployment for ATA Lightweight Gateway and Hyper-V. You can deploy domain controller and ATA Lightweight Gateway on a dedicated server, such as a physical machine or a VM.

    Hyper-V is a virtualization technology, which deploys a hypervisor between the underlying hardware, and the operating system. This may cause unexpected behavior, especially if the application, such as ATA Lightweight Gateway needs to call the underlying hardware, such as CPU, Memory and Ethernet. The most common issue is race condition.


    Best regards,
    Andy Liu

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 16, 2017 2:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Andy,

    We have one physical server. I can move the AD and gateway to a new VM, and leave the physical server to only handle the Hyper-V environment. Would that work?

    It will be an interesting challenge, but should be doable.

    Best regards,

    Pieter

    Thursday, March 16, 2017 9:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Pieter,

    Of course, it works.

    This is what I recommended, you can deploy Hyper-V on the physical server, and install domain controller and ATA lightweight gateway on a VM.

    Best regards,

    Andy Liu

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, March 16, 2017 9:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Andy,

    I moved the AD to a VM, and now it works.

    Best Regards

    Pieter

    Friday, March 17, 2017 7:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello Pieter,

    You are welcome.

    Glad to hear it works now.



    Best regards,
    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, March 21, 2017 9:36 AM