Problem with Update...
 
Notifications
Clear all

Problem with Update from latest WSP

3 Posts
2 Users
0 Reactions
2,337 Views
Posts: 6
Topic starter
(@qmex-mp)
Active Member
Joined: 9 years ago

Hi,

first of all: amazing work you have done.

I tried the Update today. I can open Enterprise Server site, and Server Site without Problems. But if i open the now updated Portal Site:

 

[WebException: The request failed with HTTP status 400: Bad Request.]
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) +690496
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) +327
SolidCP.EnterpriseServer.esAuthentication.GetSystemSetupMode() +50
SolidCP.Portal.Login.Page_Load(Object sender, EventArgs e) +92
System.Web.UI.Control.LoadRecursive() +71
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Control.LoadRecursive() +190
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3178

 

Some Ideas? The only Error I got with the Update was from sql Script:

Msg 2627, Level 14, State 1, Line 4
Violation of PRIMARY KEY constraint 'PK_ServiceTypes'. Cannot insert duplicate key in object 'dbo.Providers'. The duplicate key value is (303).

2 Replies
Posts: 6
Topic starter
(@qmex-mp)
Active Member
Joined: 9 years ago

Update:

Fixed it.

PortalApp_Data/SiteSettings

Remeber: Probably for one Linux Admins its the same, for windows not . . .

http://localhost:9002 != http://127.0.0.1:9002

Now its working.

Reply
Posts: 1967
Admin
(@m-tiggelaar)
Noble Member
Joined: 9 years ago

Hello,

Violation of PRIMARY KEY constraint ‘PK_ServiceTypes’. Cannot insert duplicate key in object ‘dbo.Providers’. The duplicate key value is (303).

Seems to be the mysql provider (if you run the script again it shouldn't give further issues, will be addressed permanently shortly)

 

The http://localhost:9002 is indeed an issue it was fixed in one of my commits but some how returned, i will address this shortly aswell.

I did note down this issue in my migration manual tho, as it's always something to look out for (not everyone has enterprise under http://127.0.0.1:9002 but it is the default)

 

Regards,

Marco

Reply
Share: