• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

revert back to 7.5.6

jonium

Basic Pleskian
I used the version 7.5.6 and all went well.
I upgrade to 7.6.0 and patch to 7.6.1 and get a lot of errors.
Some sites using php get error:
____________
CGI Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers.
____________

I think it's because of the upgrade of php to ver. 4.4.2 (first it was 4.3.1.1)

another site using asp.net get this error:
____________
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: BC31019: Unable to write to output file 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\88406ce2\4a0cbbf1\App_Web_dati.aspx.cdcab7d2.yj5cm_yl.dll': The directory name is invalid
____________

Maybe that during upgrade plesk set wrong the permissions ?
Is there a way to revert back to 7.5.6 ?
 
here is another error I haven't before of upgrading:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Microsoft Access Driver]General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0xef8 Thread 0x980 DBC 0x180f57c Jet'.

/ArchivioFotografico.asp, line 67

I tried to change permissions of c:/temp and c:/windows/temp but nothing

Need urgently help.
Thanks
 
I thýnk your problem plesk maýn user permýssons because plesk all folder securýty check and this 3 maýn user configure deny you give this user confýgure read execute
 
after updating to 7.6.1 i have the same problems as mentioned in the first post.

Does anyone know how to solve this as CGI and ASP on my server generate the same errors ?

Note: Some PHP scripts work on one website bud don't on an other, it seems like a permissions problem ?
 
cgi error is usaully iis fault. you can turn to php isapi instead.

a question, how did you upgrade from 7.5.6 to 7.6.0 ?
 
Same CGI Problems

We are having the same problems with cgi's on a website after just recently switching to Plesk 7.6.1 from a IIS 5.0 (custom solution)

We added a new page to the site/cgi:

http://www.catoctinsoftware.com/cgitest.htm

This page will allow you to test execute a cgi program that does nothing but return a page indicating that it worked. This program was tested on 3 different IIS5 servers before being uploaded to my site. On the new NetStorm server it currently returns a 'misbehaved error message'.

I don't think that I have the proper rights to run a windows cgi
executable. I am also getting errors ('operation failed') when trying to list the rights on any files under the cgi-bin directory using Plesk's file manager. I also cannot see or set the rights on the cgi-bin directory itself.

My other suspesions is that it is related to a virtual directory / working directory problem. This page talks about it some: http://www.sixapart.com/movabletype/kb/known/cgi_error_on_ii.html


Please let me know what you find out.
 
for php execution issues, there are lots of different problems related predominantly to security permissions, version of php, etc.

We ran into most of them (well, our clients did) unfortunately and what we've had to do to get most of them working was;

a) upgrade the version of php running on the server to one that does not contain the bug. simplest way to do this was to just download the version of php from the main php server and *overwrite* the existing php installation directory with the downloaded files. back up your existing php directory if you're worried about it. just note that I'm not talking about running an 'installation', just extract the files into the existing relative directories. you can get the full 4.4.4 zip version at this location

b) check permissions on your php directory, php.ini in the windows directory, your php script files/directories, etc. I haven't mapped all of these out specifically but in general you need to check the specific IUSR_xxdomainxx account on the script files, and psaxxx (adm, cln, srv) on the system php directories/files. I'd love to know *exactly* what these permissions settings are supposed to be at the system level but I don't. Hopefully SWsoft will be forthcoming given all of the issues with 6.1 permissions.

c) If the domain in question is using php via ISAPI then try it without it (running as straight cgi)...if not then vice versa (run it as ISAPI). We've rarely run into instances where running as ISAPI would resolve anything, but we do have two sites where the php application had to be run as a cgi and would *not* run as ISAPI.

These areas resolved the majority of our clients php issues.

Hope any of this helps,

-matt
 
Back
Top