Announcement

Collapse
No announcement yet.

Dataflame upgrade to PHP 5.3x problems

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Dataflame upgrade to PHP 5.3x problems

    Dataflame have upgraded the server I'm using from PHP 5.2x to 5.3x and now when I try to retrieve orders I get error messages as below. The upgrade was this morning and I'm at a loss as what to do. I am using Actinic Business 9.0.4 JFJA. Any help out there please.

    Regards Martin

    Actinic received a server error from the web server. The CGI scripts are not executing properly on the server. The error could be caused by several things. Check:
    - the 'Path to the Perl shell'
    - the 'CGI script extension'
    - the 'Path to CGI-BIN'
    - the 'CGI-BIN URL.
    - the amount of web space left on your server
    - if your server is configured to accept POSTs to CGI scripts
    - the permissions on the server:

    On Linux/Unix based servers the permissions should be:
    cgi-bin (755) – drwxr-xr-x
    Online Store Folder (777) – drwxrwxrwx
    On Windows based servers (need to be checked with the hosting company):
    IIS
    cgi-bin = read/execute
    Online Store Folder = read/write/execute
    NTFS
    cgi-bin = Catalog's FTP account needs 'Change' permissions on the directory
    Online Store Folder = Catalog's FTP account needs 'Change' permissions on the directory AND the IUSR_<servername> account needs to have 'Change' permissions on the directory

    Run Web | Configure Web Site Details... to review your web site configuration.

    #2
    They may have reset the permissions as per the error message.

    Presuming you have linux hosting and not windows hosting...
    Use an FTP client like CuteFTP or similar and connect to your server space using the same login details as in your network settings. Then you can click on the acatalog directory and check that is has permissions of 777, similarly click on the cgi-bin directory and check that ot has permissions of 755.

    Comment


      #3
      Thanks very much for the info, I will look at it tomorrow.

      Comment


        #4
        Thank you Duncan, it just needed to be reset after the change of server.
        Regards
        Martin

        Comment

        Working...
        X