upgrade to 1.4.4 us...
 
Notifications
Clear all

upgrade to 1.4.4 using script

4 Posts
2 Users
0 Reactions
700 Views
Posts: 7
 Matt
Topic starter
(@matt)
Active Member
Joined: 8 years ago

I used the 1.6 script to upgrade from 1.4.2 to 1.4.4. Seemed to go okay. When I try to save/update the MS SQL 2019 as a service property, I receive this error (below). However, when I go out and click on the 2017 server and update it, I don't receive any error and I'm taken to a screen that says the server version is 1.4.2 (the sidebar text:

  • SolidCP Server Version:
    1.4.2
  • SolidCP Server Filepath:
    C:SolidCPServer)

But the bottom of the webpage says:

Control Panel Powered by SolidCP. Copyright © 2019 all rights reserved.
Version 1.4.4

The script updated the server right? Or only the website and not the server?

Page URL:
http://myservername.com:9001/Default.aspx?pid=Servers&mid=255&ctl=edit_service&ServiceID=7&ServerID=1

Logged User:
serveradmin

Work on Behalf:
serveradmin

Hosting Space:
0

Stack Trace:
System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Can not create 'Microsoft SQL Server 2019' provider instance with 'SolidCP.Providers.Database.MsSqlServer2019, SolidCP.Providers.Database.SqlServer' type ---> System.ArgumentNullException: Value cannot be null.
Parameter name: type
at System.Activator.CreateInstance(Type type, Boolean nonPublic)
at System.Activator.CreateInstance(Type type)
at SolidCP.Providers.HostingServiceProviderWebService.get_Provider()
--- End of inner exception stack trace ---
at SolidCP.Providers.HostingServiceProviderWebService.get_Provider()
at SolidCP.Server.ServiceProvider.Install()
--- End of inner exception stack trace ---
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at SolidCP.Providers.ServiceProvider.Install()
at SolidCP.EnterpriseServer.esServers.InstallService(Int32 serviceId)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at SolidCP.EnterpriseServer.esServers.InstallService(Int32 serviceId)
at SolidCP.Portal.ServersEditService.btnUpdate_Click(Object sender, EventArgs e)

3 Replies
Posts: 1457
Admin
(@trobinson)
Noble Member
Joined: 9 years ago

Hello,

If the sidebar shows the incorrect version there was most likely a issue with accessing the UNC path on that server to update the files.

You can follow the procedure at https://solidcp.com/kb/update/manual-update/ for SolidCP Server to update the individual server.

Kind Regards,

Trevor

Reply
Posts: 7
 Matt
Topic starter
(@matt)
Active Member
Joined: 8 years ago

Okay, thanks. Do I need to redo everything? Or, at least, will the database be okay if I run the script against it and it was already updated? Or will that mess it up? Or can I assume the database is okay and just update the website files?

One thing I realized is: I don't have sql 2019 installed yet. So that could be the reason for the other error.

Reply
Posts: 1457
Admin
(@trobinson)
Noble Member
Joined: 9 years ago

Hello,

The database would normally be fine but you can rerun it without any harm. I would normally just do the server files but if your unsure i would redo it also.

The SQL 2019 shouldn't be an issue.

Kind Regards,

Trevor

Reply
Share: