Search Engine: Elastic

Article ID: 112458, created on Oct 6, 2011, last review on Sep 26, 2016

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Operations Automation 5.4
  • Operations Automation 5.0


The Operations Automation (OA) background task Turn off FTP access for Hosted Service User fails with an error as below:

Task name       Turn off FTP access for Hosted Service User 1038998 on host '' (host_id=38).
Last execution output   Exception during execution of MPF request: 'The filename, directory name, or volume label syntax is incorrect. [<response><errorContext description="The filename, directory name, or volume label syntax is incorrect." code="0x8007007b" executeSeqNo="3"><errorSource namespace="NTFSManager" procedure="changeFileOwner"/></errorContext></response>]'.

Other POA tasks may fail with the same diagnostics, for example tasks Delete webspace, Configure security settings for site application. Failure can also be different, for example:

Destination host 'WINWEB01.provider.tld' (#xxx), IP '' : Provisioning request failed. The system cannot find the path specified. [<response><errorContext description="The system cannot find the path specified." code="0x80070003" executeSeqNo="9"><errorSource namespace="NTFSManager" procedure="setFileOwner"/></errorContext></response>]


  1. The full path of one or more files or directories within the customer's webspace is longer than 255 characters or contains illegal characters.

    The limitations of the underlying technology (MPF - Microsoft Provisioning Framework) used by OA does not allow OA to handle objects on filesystems when the full path is longer than 255 characters, or objects whose names are legal in NTFS but not legal in the Windows API (common for Frontpage sites).

  2. Folder with webspace has a name like


    and is not able to be opened.


Case 1:

Use the following workaround:

  1. List all files down the webspace file hierarchy

    C:\> dir E:\CustomerData\webspaces\<webspace_id>\ /b /s > c:\files.txt
  2. Use a tool such as Excel or the Linux shell to calculate the length of strings in c:\files.txt. For example, using the Linux command line, you could use:

    awk '{ if (length($0) > 254 ) print }' files.txt > long_paths.txt

    or locally (if Powershell is present)

    PS> $data = Get-Content "c:\files.txt"
    PS> foreach ($line in $data) {
        if ($line.length -gt 254){write-host $line}
  3. Temporarily move all files with path longer than 254 characters out of the webspace
  4. Process the task
  5. Move files back to their original locations

You can also use the solutions in this Microsoft KB article:

A permanent solution is being considered by OA maintenance team in the scope of an alternate provisioning technology to provide Windows Shared Hosting services.

Case 2

Rename the folder back to original name via command line:

rename "D:\CustomerData\webspaces\webspace_00123456.{37565F78-3C79-4DD8-9D3C-CF76DF6B41E3}" "webspace_00123456"

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 c27596ac4fff6cb4c8ec8891dae57001 2554725ed606193dd9bbce21365bed4e ac82ce33439a9c1feec4ff4f2f638899 e12cea1d47a3125d335d68e6d4e15e07 5b048d9bddf8048a00aba7e0bdadef37 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF