Install Config Wiki

All about installing, configuring and troubleshooting

User Tools

Site Tools

Trace:
solved_iis_internal_server_error_500_accessing_dokuwiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
solved_iis_internal_server_error_500_accessing_dokuwiki [2022/07/15 14:45] – wikiadminsolved_iis_internal_server_error_500_accessing_dokuwiki [2022/07/15 14:46] (current) – wikiadmin
Line 5: Line 5:
 After upgrading an IIS webserver's PHP version, let's say you upgraded from PHP version 7.2.19 to PHP version 8.1.8, you may have found that some or many of your websites or certain web functions (bulletin board forums and/or phpmyadmin) were not compatible with the upgraded PHP version.  So, to troubleshoot, you probably tried to access your php_errors.log with Notepad++ editor to determine the problem.  However, if your php_errors.log contains too many entries and your editor is "not responding" to open the php_errors.log, then you may have decided to delete this bloated and cumbersome php_errors.log file and create a new php_errors.log file with no data.  At that point, you may have noticed that your DokuWiki is no longer accessible from the web.  Instead you are seeing "Error 500 - Internal Server Error." Now, at this point, you may have reinstalled the older working version of PHP 7.2.19 from your complete file backup (because, with best practices, we always first make a complete backup of the working PHP version before upgrading to or installing a newer PHP version).    After upgrading an IIS webserver's PHP version, let's say you upgraded from PHP version 7.2.19 to PHP version 8.1.8, you may have found that some or many of your websites or certain web functions (bulletin board forums and/or phpmyadmin) were not compatible with the upgraded PHP version.  So, to troubleshoot, you probably tried to access your php_errors.log with Notepad++ editor to determine the problem.  However, if your php_errors.log contains too many entries and your editor is "not responding" to open the php_errors.log, then you may have decided to delete this bloated and cumbersome php_errors.log file and create a new php_errors.log file with no data.  At that point, you may have noticed that your DokuWiki is no longer accessible from the web.  Instead you are seeing "Error 500 - Internal Server Error." Now, at this point, you may have reinstalled the older working version of PHP 7.2.19 from your complete file backup (because, with best practices, we always first make a complete backup of the working PHP version before upgrading to or installing a newer PHP version).   
  
-Here is a possible solution to the 500 Error.  When you created the new php_errors.log file, you may have failed to give "Modify" and "Write" permissions to the IUSR account and IIS_IUSR group.+Here is a possible solution to the 500 Error.  When you created the new php_errors.log file, you may have failed to give "Modify" and "Write" permissions to the IUSR user account and IIS_IUSR group account.
  
 Find the file system location of your php_errors.log based on the setting in your php.ini configuration file. On Windows O/S, the php.ini file is usually located at c:\php\php.ini Find the file system location of your php_errors.log based on the setting in your php.ini configuration file. On Windows O/S, the php.ini file is usually located at c:\php\php.ini
solved_iis_internal_server_error_500_accessing_dokuwiki.txt · Last modified: 2022/07/15 14:46 by wikiadmin