This topic contains 5 replies, has 3 voices, and was last updated by 
Paul Hester 2 hours, 8 minutes ago.
-
Posts
-
I am hoping someone can help me. I am not sure what is wrong with my system. I was running 1.0 fine for years, but then started having lots of problems. So I decided to replace it with 2.0. It is still using the same database.
When I browse to ports 9003 (Server) and 9002 (Enterprise Server), things appear to be ok.
However, when I browse to port 9001 (Portal), I just get the Startup page. This page refreshes every 4 seconds, but never goes away. I have left it for hours to see if it finally gets to a login page. I have also rebooted server and reset IIS, but still no good.
Any ideas of what to look for?
Hi Paul,
I believe you are suffering of the same problem of mine.
I tried to update to 2.0 because my 1.0 version started to show up with some issues, for example, websites creation errors, long time loading, hosting plan errors…
During the update my error log point to:
IF NOT EXISTS (SELECT * FROM [dbo].[ServiceItemTypes] WHERE [ItemTypeID] = 380)
INSERT [dbo].[ServiceItemTypes] ([ItemTypeID], [GroupID], [DisplayName], [TypeName], [TypeOrder], [CalculateDiskSpace], [CalculateBandwidth], [Suspendable], [Disposable], [Searchable], [Importable], [Backupable]) VALUES (380, 55, N’MsSQL2019Database’, N’MSPControl.Providers.Database.SqlDatabase, MSPControl.Providers.Base’, 1, 1, 0, 0, 1, 1, 1, 1)The error was The INSERT statement conflicted with the FOREIGN KEY constraint “FK_ServiceItemTypes_ResourceGroups”. The conflict occurred in database “MSPControl”, table “dbo.ResourceGroups”, column ‘GroupID’.
Then I believe if you run this script bellow, BEFORE to update the MSPControl, the update will run ok:
IF NOT EXISTS (SELECT * FROM [dbo].[ResourceGroups] WHERE [GroupID] = ’55’)
BEGIN
INSERT [dbo].[ResourceGroups] ([GroupID], [GroupName], [GroupOrder], [GroupController], [ShowGroup]) VALUES (55, N’Sharepoint Enterprise Server’, 15, N’MSPControl.EnterpriseServer.HostedSharePointServerEntController’, 1)
END
GOI didn’t try it yet, because I must have to wait until the weekend to try again!
Hi Paul,
This weekend I tried again to update to MSPControl 2.0, to get the update process successfully finished, I runned these scripts before to start the update process:
INSERT [dbo].[ResourceGroups] ([GroupID], [GroupName], [GroupOrder], [GroupController], [ShowGroup]) VALUES (55, N’MsSQL2019′, 10, N’MSPControl.EnterpriseServer.DatabaseServerController’, 1)
INSERT [dbo].[Providers] ([ProviderID], [GroupID], [ProviderName], [DisplayName], [ProviderType], [EditorControl], [DisableAutoDiscovery]) VALUES (1207, 55, N’MsSQL’, N’Microsoft SQL Server 2019′, N’MSPControl.Providers.Database.MsSqlServer2019, MSPControl.Providers.Database.SqlServer’, N’MSSQL’, NULL)
INSERT [dbo].[ServiceItemTypes] ([ItemTypeID], [GroupID], [DisplayName], [TypeName], [TypeOrder], [CalculateDiskSpace], [CalculateBandwidth], [Suspendable], [Disposable], [Searchable], [Importable], [Backupable]) VALUES (380, 55, N’MsSQL2019Database’, N’MSPControl.Providers.Database.SqlDatabase, MSPControl.Providers.Base’, 1, 1, 0, 0, 1, 1, 1, 1)
INSERT [dbo].[ServiceItemTypes] ([ItemTypeID], [GroupID], [DisplayName], [TypeName], [TypeOrder], [CalculateDiskSpace], [CalculateBandwidth], [Suspendable], [Disposable], [Searchable], [Importable], [Backupable]) VALUES (381, 55, N’MsSQL2019User’, N’MSPControl.Providers.Database.SqlUser, MSPControl.Providers.Base’, 1, 0, 0, 0, 1, 1, 1, 1)
INSERT [dbo].[Quotas] ([QuotaID], [GroupID], [QuotaOrder], [QuotaName], [QuotaDescription], [QuotaTypeID], [ServiceQuota], [ItemTypeID], [HideQuota]) VALUES (790, 55, 1, N’MsSQL2019.Databases’, N’Databases’, 2, 0, 380, NULL)
INSERT [dbo].[Quotas] ([QuotaID], [GroupID], [QuotaOrder], [QuotaName], [QuotaDescription], [QuotaTypeID], [ServiceQuota], [ItemTypeID], [HideQuota]) VALUES (791, 55, 2, N’MsSQL2019.Users’, N’Users’, 2, 0, 381, NULL)
INSERT [dbo].[Quotas] ([QuotaID], [GroupID], [QuotaOrder], [QuotaName], [QuotaDescription], [QuotaTypeID], [ServiceQuota], [ItemTypeID], [HideQuota]) VALUES (792, 55, 3, N’MsSQL2019.MaxDatabaseSize’, N’Max Database Size’, 3, 0, NULL, NULL)
INSERT [dbo].[Quotas] ([QuotaID], [GroupID], [QuotaOrder], [QuotaName], [QuotaDescription], [QuotaTypeID], [ServiceQuota], [ItemTypeID], [HideQuota]) VALUES (793, 55, 5, N’MsSQL2019.Backup’, N’Database Backups’, 1, 0, NULL, NULL)
INSERT [dbo].[Quotas] ([QuotaID], [GroupID], [QuotaOrder], [QuotaName], [QuotaDescription], [QuotaTypeID], [ServiceQuota], [ItemTypeID], [HideQuota]) VALUES (794, 55, 6, N’MsSQL2019.Restore’, N’Database Restores’, 1, 0, NULL, NULL)
INSERT [dbo].[Quotas] ([QuotaID], [GroupID], [QuotaOrder], [QuotaName], [QuotaDescription], [QuotaTypeID], [ServiceQuota], [ItemTypeID], [HideQuota]) VALUES (795, 55, 7, N’MsSQL2019.Truncate’, N’Database Truncate’, 1, 0, NULL, NULL)
INSERT [dbo].[Quotas] ([QuotaID], [GroupID], [QuotaOrder], [QuotaName], [QuotaDescription], [QuotaTypeID], [ServiceQuota], [ItemTypeID], [HideQuota]) VALUES (796, 55, 4, N’MsSQL2019.MaxLogSize’, N’Max Log Size’, 3, 0, NULL, NULL)
After the update I finally got the Login page to be showed, but when I tried to login using the serveradmin credentials, the page blink and no access is done. I looked for errors in Audit Log table, Windows Event Viewer and in Browser Developer Tools (F12) no errors was found! I ended up reverting the update.
Thanks for your help and guidance Marcelo. I’ve tried the same things as you, as far as updating the database manually, and also am getting no where. This really sucks. I have thousands of current customers that can’t login, and I can’t add new ones. Even though I provide free services, I still want them to work.
I’ve even gone to another machine to try installing from scratch, hoping to then be able to find any differences to fix in my production environment. But the installer never completes successfully there. I am totally confused and frustrated.
I’ve alerted developer. Do you have any additional logs?
Looks like SQL Server 2016 is now required as a minimum, because I see the use of JSON_VALUE function in some procedures. I guess I will upgrade my SQL Server and then try again.
You must be logged in to reply to this topic.