Project

General

Profile

Actions

Bug #92728

closed

TYPO3 Exception: #1203699034 after new Installation of v10

Added by Hans-Georg Althoff over 3 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2020-10-28
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.4
Tags:
Windows 2019 V10
Complexity:
Is Regression:
Sprint Focus:

Description

I am using MS Server 2019 and IIS.
I created a new sub folder in my wwwroot directory, to install a test system for V10.
After I have copied all files from the 10.4.9 zip file and tried to start typo3 I recieve a Oops, an error occurred!.
I have enabled the IUSR user with all write privileges.
In the log file I have the following entries:
Wed, 28 Oct 2020 11:10:13 +0100 [CRITICAL] request="6ff344f26f339" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1203699034: A cache with identifier "cache_core" does not exist. | TYPO3\CMS\Core\Cache\Exception\NoSuchCacheException thrown in file C:\inetpub\wwwroot\typo3\sysext\core\Classes\Cache\CacheManager.php in line 138. Requested URL: https://test.althoff-fam.de/ - {"TYPO3_MODE":"FE","exception":"TYPO3\\CMS\\Core\\Cache\\Exception\\NoSuchCacheException: A cache with identifier \"cache_core\" does not exist. in C:\\inetpub\\wwwroot\\typo3\\sysext\\core\\Classes\\Cache\\CacheManager.php:138\nStack trace:\n#0 C:\\inetpub\\wwwroot\\typo3\\sysext\\core\\Classes\\Core\\Bootstrap.php(109): TYPO3\\CMS\\Core\\Cache\\CacheManager->getCache('cache_core')\n#1 C:\\inetpub\\wwwroot\\index.php(24): TYPO3\\CMS\\Core\\Core\\Bootstrap::init(Object(Composer\\Autoload\\ClassLoader))\n#2 C:\\inetpub\\wwwroot\\index.php(25): {closure}()\n#3 {main}"}
Wed, 28 Oct 2020 11:22:56 +0100 [CRITICAL] request="1e758f667ffed" component="TYPO3.CMS.Core.Error.ProductionExceptionHandler": Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1203699034: A cache with identifier "cache_core" does not exist. | TYPO3\CMS\Core\Cache\Exception\NoSuchCacheException thrown in file C:\inetpub\wwwroot\typo3\sysext\core\Classes\Cache\CacheManager.php in line 138. Requested URL: https://test.althoff-fam.de/typo3/index.php?route=%2Fajax%2Flogin%2Ftimedout&skipSessionUpdate=1 - {"TYPO3_MODE":"BE","exception":"TYPO3\\CMS\\Core\\Cache\\Exception\\NoSuchCacheException: A cache with identifier \"cache_core\" does not exist. in C:\\inetpub\\wwwroot\\typo3\\sysext\\core\\Classes\\Cache\\CacheManager.php:138\nStack trace:\n#0 C:\\inetpub\\wwwroot\\typo3\\sysext\\core\\Classes\\Core\\Bootstrap.php(109): TYPO3\\CMS\\Core\\Cache\\CacheManager->getCache('cache_core')\n#1 C:\\inetpub\\wwwroot\\typo3\\index.php(24): TYPO3\\CMS\\Core\\Core\\Bootstrap::init(Object(Composer\\Autoload\\ClassLoader))\n#2 C:\\inetpub\\wwwroot\\typo3\\index.php(25): {closure}()\n#3 {main}"}

If I do the same with 9.5.22 everything works fine.

Actions #1

Updated by Benni Mack about 3 years ago

  • Status changed from New to Needs Feedback

Hey,

this issue seems related to either

a) an extension using "cache_core" as cache (it has been renamed to "core")
b) a OpCache in PHP using old code

from my first impression. Is that possible?

Actions #2

Updated by Hans-Georg Althoff about 3 years ago

I don't have any extension cache_core or core. I could only find php_wincache.dll.
I am using FASTCGI, and as ong as know there is nothing to reset.
I tried also to install over V9 and got the same problem.
A cache with identifier "cache_core" does not exist.
The problem is created by Bootstrap::init.
It is areal clean installation. Only standard extensions installed!

Actions #3

Updated by Christian Kuhn about 2 years ago

  • Status changed from Needs Feedback to Closed

Hey Hans-Georg. I'm unsure on what exactly is wrong in these instances, but this is most likely not a core bug: We would know about such a hard issue and would have fixed it already.

I don't know how to proceed here on core side and I currently see no other solution than to close the issue for now. In case you're still experiencing this, you may need to debug around on your own a bit more, to see where exactly this broken cache config stems from.

Feel free to come up with a fresh issue in case you can debug around on this and it still turns out to be a core issue.

Actions

Also available in: Atom PDF