SolidCP Auto Upgrad...
 
Notifications
Clear all

SolidCP Auto Upgrade Script - PowerShell

47 Posts
13 Users
0 Reactions
15.3 K Views
Posts: 100
 Ben
(@maoxiong)
Estimable Member
Joined: 7 years ago

I got that same error and I'm using 2012.

I just commented out all the backup lines.

Reply
Posts: 5
(@lazito)
Active Member
Joined: 8 years ago

Hello,
When auto-upgrade, we received this error in Enterpriseserver phase:
New-SMBShare : The name has already been shared.
On D:DownloadswordpressSolidCP-Auto-Upgrade.ps1:403 caractere:6
+ New-SMBShare -Name "SCPUpgrade$" -Path "$SCP_UpdateDirEnterprise Server - ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (MSFT_SMBShare:ROOT/Microsoft/Windows/SMB/MSFT_SMBShare) [New-SmbShare], C
imException
+ FullyQualifiedErrorId : Windows System Error 2118,New-SmbShare
Exception when calling "GetHostEntry" com "1" argumento(s): "This host is not known"
On D:DownloadswordpressSolidCP-Auto-Upgrade.ps1:408 caractere:45
+ if (([System.Net.Dns]::gethostentry("$($SCP_Database_Servr.Split("")[0])") ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : SocketException
how should we proceed in this case?

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

Hello,

It sounds like your machine may still have the share SCPUpgrade$. Can you check its network shares to see if this is present? If it is you should be able to manually remove it and run the script.

Kind Regards,

Trevor Robinson

Reply
Posts: 1
(@fbritop)
New Member
Joined: 6 years ago

Hello,

I have just try to update to version 1.4.2 with your script with the following error on IIS

Module
IIS Web Core

Notification
Unknown

Handler
Not yet determined

Error Code
0x8007000d

Config Error
Only one <configSections> element allowed. It must be the first child element of the root <configuration> element

Config File
\?C:WebsitePanelPortalweb.config

I have checked both sites on ports 9002 and 9003 and they all run OK with:

Server

Status:
Running

Version:
1.4.2

URL:
http://node01.vm1.inoba.com:9003

ASP.NET Mode:
32-bit

Is there any manual solution to the web.config files?

Thanks
FBP

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

Since it's having an issue with SolidCP Portal web.config i assume some settings / changes have been set via IIS that the upgrade script can't work with.

most easy is just to replace it with a fresh copy (SolidCP Portal web.config does not contain any settings) from:  http://installer.solidcp.com/Files/stable/SolidCP-Portal.zip

Reply
Page 7 / 7
Share: