Hi,
after every quick-repair the following error occurs and is written to the suitecrm.log-file:
ERROR: rmdir_recursive(): argument cache/themes/SuiteP/modules is not a file or a dir.
The written text is correct…the file/folder really not exists but also never existed. So why this errors occurs?
Permission is set to full-access to the owner (IIS AppPool\SUITECRM_TEST) for the complete website-folder.
I installed a new test-system with suiteCRM 7.10.0.
The only changes are
[the current language-pack (German)
Curreny to € /Euro
Changed SMTP-Server our Exchange-Server
I cleared the firefox-cache…and after each “quick repair” the Error “[FATAL] ERROR: rmdir_recursive(): argument cache/themes/SuiteP/modules is not a file or a dir.” is written to the log…
I cant reproduce the Server Error 500, but if it happens, then the suitecrm.log contains the ^^ error.
I tried with IIS AppPool\SUITECRM_TEST as the owner and also IUSR as owner of all the files/folder with full access…no difference
If we cant solve this problem, we must abort the suitecrm-project :S
I ran into this problem as well, both on Apache and Azure WebApps(IIS). Sometimes a clean install fixed it. I think I fixed it once by creating the directory so it could remove it. Also, make sure the permissions are set correctly. Try an install without a sub directory and see if you get the same results. IIRC I had some sort of issue with a subdir install on IIS.
Sorry - I missed the part about “Windows”. I don’t think those options have any effect at all on Windows, they’re just ignored.
(www-data is the Apache web server user name on Ubuntu)
Ok, so maybe you can turn your attention to permissions inheritance in the parent folder, cache/themes/SuiteP
This is what controls the permissions that a new directory created there will receive.
If you install SysInternals Suite from Microsoft’s site, you won’t regret it. They are simply excellent, especially Process Explorer, Autoruns and Process Monitor.
With this last one, you can set it up to watch exactly which directories your web server process is creating, reading, deleting, etc., and exactly which error it is getting.