[Solved] Invalid object name 'dbo.cp_Settings'.
Hi, new installation, remote SQL server.. following installation it creates a whole bunch of tables but will not load CloudPanel throwing error:
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Invalid object name ‘dbo.cp_Settings’.
this table does not appear to exist in the database when looking at the tables in SQL management studio
Did you do a new installing to an existing database? You can’t do that because the installation creates the initial tables on new installs and then CloudPanel updates it to the latest version. The log file (CloudPanel.log) will show you a list of migration that are pending when it starts because it will try to update them. Please take a look at the log file.
Hi Jacob,
Thank you for your quick response.
The database is clean. We have created a new SQL instance with a new database called CloudPanel. Could this have anything to do with collation or anything like that?
My colleague Chris has pointed out that the table simply doesn’t exist amongst all the other tables.
I have attached the CloudPanel log to this response. I am unable to locate anything within this that tells me anything different to what I already know.
Kind Regards,
Anthony.
Edit: Unable to attach CloudPanel.log – “File type not allowed”
This is the stand-out error:
[2018-03-19 08:57:46,778] | ERROR | CloudPanel.Bootstrapper| Error: System.Data.Entity.Core.EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details. —> System.Data.SqlClient.SqlException: Invalid object name ‘dbo.cp_Settings’.
We released 3.2.0256.0 which should resolve this issue you were having. The problem was during the first start up it was trying to read from that table before it could create it. Can you download this latest version?
Hallelujah! It works.
Thanks for getting that bug fix out quick since 3.2.255.0.
Kind Regards,
Anthony.
- 5 Forums
- 716 Topics
- 3,649 Posts
- 0 Online
- 258 Members