Zum Inhalt springen

Erweiterungsmanager Internal Server Error

Erstellt am 28. Oktober 2019 · 1 Antwort · letzte Antwort am 29. Oktober 2019

Tags: TYPO3 9, Frage

hannesw11 ·

Hallo Zusammen,

bei der Neuinstallation einer T3 9.5.10 Version bekomme ich beim Laden der TER immer einen Internal Server Error der wie folgt beginnt:

Aktualisieren der Erweiterungsliste

error(Internal Server Error): <!DOCTYPE html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="robots" content="noindex, follow">
<title>Oops, an error occurred!</title>
<link rel="stylesheet" href="/2020/typo3/sysext/core/Resources/Public/Css/errorpage.css">
</head>
<body class="t3-message-page t3-errorpage-message">
<div class="t3-error-wrap">
<div class="t3-message-page-container">
<div class="t3-message-page-logo">
<img src="/2020/typo3/sysext/backend/Resources/Public/Images/typo3_orange.svg" class="typo3-error-image" alt="TYPO3 logo">
</div>
<div class="callout callout-danger">
<div class="media">
<div class="media-left">
<span class="fa-stack fa-lg callout-icon">
<i class="fa fa-circle fa-stack-2x"></i>
<i class="fa fa-exclamation-triangle fa-stack-1x"></i>
</span>
</div>
<div class="media-body">
<h4 class="alert-title">Oops, an error occurred!</h4>
<div class="callout-body">
An exception occurred while executing &#039;SELECT `a`.`uid` AS `uid` FROM `tx_extensionmanager_domain_model_extension` `a` LEFT JOIN `tx_extensionmanager_domain_model_extension` `b` ON (`a`.`repository` = `b`.`repository`) AND (`a`.`extension_key` = `b`.`extension_key`) AND (`a`.`integer_version` &lt; `b`.`integer_version`) WHERE (`a`.`repository` = ?) AND (`b`.`extension_key` IS NULL) ORDER BY `a`.`uid` ASC&#039; with params [1]:

The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay

</div>
</div>
</div>
</div>
<div id="t3-footer">
<div id="t3-copyright-notice">
TYPO3 is an open source content management system. To maintain the quality of the system and to improve it, please help us by
donating.
Copyright &copy; 1998-2019 Kasper Skårhøj. Extensions are copyright of their respective owners. Go to
<a href="https://typo3.org/">https://typo3.org/</a> for details.

Danke für Antworten!

Hannes

Norman2k ·

Steht doch ganz eindeutig da, wo das Problem ist:
The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET MAX_JOIN_SIZE=# if the SELECT is okay

D.h. du musst SQL_BIG_SELECTS auf 1 setzen, nicht in TYPO3 sondern MySQL oder was auch immer du als Datenbank verwendest.