It’s Update time, and I’m stuck at the start. 2023.0.4 to 2026

[Fuquar7]

Fatal error: Uncaught PDOException: SQLSTATE[42S01]: Base table or view already exists: 1050 Table ‘si_sql_patchmanager’ already exists in /homepages/mysite.com/master/Inc/Claz/PdoDb.php:1287
Stack trace:
#0 /homepages/mysite.com/master/Inc/Claz/PdoDb.php(1287): PDOStatement->execute()
#1 /homepages/mysite.com/master/Inc/Claz/SqlPatchManager.php(145): Inc\Claz\PdoDb->query()
#2 /homepages/mysite.com/master/Inc/Claz/SqlPatchManager.php(215): Inc\Claz\SqlPatchManager::runSqlPatch()
#3 /homepages/mysite.com/master/index.php(247): Inc\Claz\SqlPatchManager::runPatches()
#4 {main}
thrown in /homepages/mysite.com/master/Inc/Claz/PdoDb.php on line 1287

[fearless359]

Is there more information in the tmp/log/php.log file? In particular the actual command that is trying to be executed?

[Fuquar7]

[19-Feb-2026 15:01:01 America/Indiana/Indianapolis] PHP Fatal error:  Uncaught PDOException: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'si_sql_patchmanager' already exists in /homepages/MySite.com/master/Inc/Claz/PdoDb.php:1287
Stack trace:
#0 /homepages/MySite.com/master/Inc/Claz/PdoDb.php(1287): PDOStatement->execute()
#1 /homepages/MySite.com/master/Inc/Claz/SqlPatchManager.php(145): Inc\Claz\PdoDb->query()
#2 /homepages/MySite.com/master/Inc/Claz/SqlPatchManager.php(215): Inc\Claz\SqlPatchManager::runSqlPatch()
#3 /homepages/MySite.com/master/index.php(247): Inc\Claz\SqlPatchManager::runPatches()
#4 {main}
  thrown in /homepages/MySite.com/master/Inc/Claz/PdoDb.php on line 1287
[19-Feb-2026 15:01:01 America/Indiana/Indianapolis] PdoDb destruct - incomplete transaction - rollback performed.

[fearless359]

That’s not giving me enough information to determine the issue. Please enable logging to output debug info. Do this by changing the loggerLevel setting in the custom.config.ini to the DEBUG setting. Then delete the si.log file in the tmp/log directory. Then run SI. This should create a new si.log file. Please zip this and attach the zip file to a response to this topic. Hopefully that will help guide me to where the error is.

Oh, before uploading the log file, you should read through it a blank out personal info such as the SI login password as once uploaded, anyone can view the file.

• This reply was modified 2 weeks, 3 days ago by fearless359.

[Fuquar7]

See attached.

I appreciate your help.

Attachments:

1. si.zip

[Fuquar7]

I did not change anything in the log file

This part did not look right to me

`2026-02-22, 12:39 pm > DEBUG > init.php – $_SESSION: Array
(
[timeout] => 1771841925
[id] => 1
[domain_id] => 1
[username] => demo
[email] => demo@simpleinvoices.group
[fakeAuth] => 1
[user_id] => 0
)

[fearless359]

The section you are looking at is a default login, typically when a new installation is being implemented. This is not an issue. What is an issue is that the program is acting as though you have an empty database, or at least an empty si_sql_patchmanager table. You say you are doing an upgrade. Is your custom.config.ini pointing to the correct database?

[Fuquar7]

My custom.config.ini is the same as I had from my last working version.

[fearless359]

I think the issue is with the content of your si_sql_patchmanager table. Please export it, zip it and attach it here?

[Fuquar7]

attached

Attachments:

1. si_sql_patchmanager.zip

[fearless359]

The issue is that the patch process couldn’t handle the case where not all applied patch history records are present in the si_sql_patchmanager table. Yours starts at patch 319 and ends at patch 335. I have corrected this error so your situation is not an issue. Download the latest SI version and run it. This should fix your issue.

[Author]

Posts