• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Unable to start filemng.exe user list dirs pathtosite\httpdocs (267)

Status
Not open for further replies.

Superkikim

Regular Pleskian
Hi,

Since I have updated Plesk 11.0.9 to 11.5.30 in Windows (6.1.7601), I cannot use some programs from the panel, and jmail does not work anymore.

For the control panel, I get the following error when I try to open the file manager:

Internal error: Unable to start ("C:\Program Files (x86)\Parallels\Plesk\admin\bin\filemng.exe" ftp_user list dirs D:\Inetpub\vhosts\domain.ltd\httpdocs): (267) The directory name is invalid.

Message: Unable to start ("C:\Program Files (x86)\Parallels\Plesk\admin\bin\filemng.exe" ftp_user list dirs D:\Inetpub\vhosts\domain.ltd\httpdocs): (267) The directory name is invalid.
File: Util.php
Line: 55
Type: Exception

If I launch the command from the command prompt, it returns the correct directory listing.

I tried to lookup for the Util.php file to check line 55, but there are many of these and I don't know where to look.

I've tried the reconfigurator, the fix of permission, and all I could with provided tools. Any help welcome...

Additionally, dimac jmail was working fine until then and does not work anymore. No idea why :(
 
For instance, I have this issue with many tools:

Unable to start ("C:\Program Files (x86)\Parallels\Plesk\admin\bin\aspnetcfg.exe" --get-params --machine): (267) The directory name is invalid.
 
[Solved] Unable to start filemng.exe user list dirs pathtosite\httpdocs (267)

Well, I solved the problem...

In my configuration, I moved (a long time ago) the PrivateTemp folder to a different drive, and I made a symbolic link to it. It worked perfectly so far.

Since the upgrade to 11.5, some permissions have changed. Obviously they have been applied to the link, but not to the actual directory. Therefore, I had to fix the permissions on that folder. I looked at the permissions of the link and applied the same to the folder... Everything's back to normal.
 
Status
Not open for further replies.
Back
Top