SQL Error on upgrad...
 
Notifications
Clear all

SQL Error on upgrade

14 Posts
2 Users
0 Likes
3,304 Views
Posts: 115
Topic starter
(@jimjams)
Estimable Member
Joined: 8 years ago

Hi,

Just upgraded from 1.4.0 to 1.4.2

SQL Error in powershell and then ran upgrade SQL again manually in SSMS and same error:

--

Msg 547, Level 16, State 0, Line 20610
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_Providers_ResourceGroups". The conflict occurred in database "mywbase", table "dbo.ResourceGroups", column 'GroupID'.
The statement has been terminated.
Msg 547, Level 16, State 0, Line 20620
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ServiceDefaultProperties_Providers". The conflict occurred in database "mywbase", table "dbo.Providers", column 'ProviderID'.
The statement has been terminated.
Msg 547, Level 16, State 0, Line 20621
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ServiceDefaultProperties_Providers". The conflict occurred in database "mywbase", table "dbo.Providers", column 'ProviderID'.
The statement has been terminated.
Msg 547, Level 16, State 0, Line 20622
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ServiceDefaultProperties_Providers". The conflict occurred in database "mywbase", table "dbo.Providers", column 'ProviderID'.
The statement has been terminated.
Msg 547, Level 16, State 0, Line 20623
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ServiceDefaultProperties_Providers". The conflict occurred in database "mywbase", table "dbo.Providers", column 'ProviderID'.
The statement has been terminated.
Msg 547, Level 16, State 0, Line 20624
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ServiceDefaultProperties_Providers". The conflict occurred in database "mywbase", table "dbo.Providers", column 'ProviderID'.
The statement has been terminated.
Msg 547, Level 16, State 0, Line 20625
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ServiceDefaultProperties_Providers". The conflict occurred in database "mywbase", table "dbo.Providers", column 'ProviderID'.
The statement has been terminated.

--

CP seems fine and all functions appear to be working.
Can see SpamExperts options, but cannot see MySQL 8 options under servers.
Wandering what has been broken now.

Any ideas?

Thanks.

13 Replies
Posts: 1456
Admin
(@trobinson)
Noble Member
Joined: 8 years ago

Hello,

There appears to be a slight error in the SQL script Line 20602. The change should be the following:

IF EXISTS (SELECT * FROM [dbo].[ResourceGroups] WHERE [GroupName] = N'MySQL8')

to

IF NOT EXISTS (SELECT * FROM [dbo].[ResourceGroups] WHERE [GroupName] = N'MySQL8')

I am working on publishing the fix shortly.

Thanks,

Trevor Robinson

Reply
Posts: 115
Topic starter
(@jimjams)
Estimable Member
Joined: 8 years ago

Thanks so much Trevor,
Would i be best if i wait for the new upgrade SQL and run it again when ready?

Reply
Posts: 1456
Admin
(@trobinson)
Noble Member
Joined: 8 years ago

Hello,

I have published the new files with the fix. Would you be able to run the latest SQL file?

Thanks,

Trevor Robinson

Reply
Posts: 115
Topic starter
(@jimjams)
Estimable Member
Joined: 8 years ago

From here?
http://installer.solidcp.com/Files/stable/SolidCP-EnterpriseServer-Update.zip
Can i assume its safe to run it again over the live DB? (will back it up first ofc)

Reply
Page 1 / 3
Share: