search cancel

Data Classification Services - The remote endpoint is not currently in service at this location - 0x803d000e


Article ID: 162484


Updated On:


Symantec Products


Under specific circumstances, Data Classification from Enterprise Vault to the Symantec Data Classify Server (on a Windows Operating System) will cease.  This can cause a backlog of items within targeted user or journal mailboxes where archiving needs to take place.

On the Enterprise Vault server (within the Enterprise Vault Event Logs), the following error is seen:

Event ID 45342

The Data Classification Client could not connect to a classification server and will now wait for a server to become available.

Status: The remote endpoint is not currently in service at this location.  (0x803d000e)



To resolve this issue, work through the following steps on the Data Classification server until the error is no longer reproduced:

NOTE:  Some steps may not be relevant for a given Data Classification server.  If that is the case, then simply move on to the next step.

  1. In the Services Microsoft Management Console (MMC) snap-in, restart the Net.Tcp Listener Adapter.
  2. In the Services MMC snap-in, restart the Net.Tcp Port Sharing Service.
  3. Repair the WCF and WF components.

    On Windows Server 2008, use the ServiceModel Registration Tool ( ServiceModelReg.exe ) as follows:

    1. Open a Command Prompt window.

    2. Change to the folder %SystemRoot%\Microsoft.Net\Framework\v3.0\Windows Communication Foundation .

    3. Type the following command:

      ServiceModelReg.exe -r
      For more information on the ServiceModel Registration Tool, see the following Microsoft Knowledge Base article:

    On Windows Server 2012 , remove and add .NET Framework features as follows: (Note: it has been found that the steps below also work on a Windows 2008 server and have resolved the issue)

    1. Start the Remove Roles and Features wizard.
    2. On the Features page, under .NET Framework 3.5 Features, clear the check boxes for HTTP Activation and Non-HTTP Activation.
    3. Click Next to the end of the wizard, and then click Remove. The features are removed.
    4. Reinstall these features using the Add Roles and Features wizard.
    Alternatively, on Windows Server 2012, you can use the Deployment Image Servicing and Management (DISM) command line tool to disable and enable the .NET Framework 3.5 features.
  4. Follow the instructions in this Microsoft Knowledge Base article to repair the protocol handlers:

  5. Restart the Symantec Data Classification server.