November Happy Hour will be moved to Thursday December 5th.
AI OnAI Off
The term 'New-EPiCMSWizard' is not recognized as a cmdlet
Which powershell snap-ins do you have installed and what version are they? E.g. (from a powershell command prompt):
PS C:\Users\Administrator> Get-PSSnapin -r
Name : EPiServer.Install.CMS.5.2.375.236
PSVersion : 1.0
Description : PowerShell snap-in for installing/unistalling EPiServer components
Name : EPiServer.Install.CMS.6.0.501.0
PSVersion : 1.0
Description : PowerShell snap-in for installing/unistalling EPiServer components
Name : EPiServer.Install.Common.1
PSVersion : 1.0
Description : PowerShell snap-in for installing/unistalling EPiServer components
Name : EPiServer.Install.SnapIn.5.2.375.7
PSVersion : 1.0
Description : PowerShell snap-in for installing/unistalling EPiServer components
Name : EPiServer.Upgrade.CMS5.6.0.501.0
PSVersion : 1.0
Description : PowerShell snap-in for upgrading EPiServer components
Feb 15, 2010 14:32
It would see the client only has the following.
PS F:\> Get-PSSnapin -r
Name : SqlServerCmdletSnapin100
PSVersion : 1.0
Description : This is a PowerShell snap-in that includes various SQL Server cmd
lets.
Name : SqlServerProviderSnapin100
PSVersion : 1.0
Description : SQL Server Provider
So I assume the powershell install failed.
Feb 15, 2010 14:52
Perhaps. The snap-ins are only installed in x86 powershell. Did you run this using x64 version of powershell by any chance?
Feb 15, 2010 14:57
I have just asked the client to check whether they ran the x86 or x64 version. I will update you shortly.
Cheers
Feb 15, 2010 15:01
The client has now tried running the x86 version of the powershell and this is also reporting no EPiServer snapins installed.
Feb 15, 2010 15:50
3-way debuggin is a bit tricky. You could ask if they remember anything odd or different compared to the installation instructions and to send the log files that are generated during install.
Feb 15, 2010 16:06
Yup 3 way debugging is very tricky :)
I have asked them to reinstall but choose Application mode on the install as I am aware they have been using the Express method.
Feb 15, 2010 16:21
The client tried an uninstall and reinstall, but used the Application mode rather than Express and this has now solved the issue. It would be great to know why the Express install was failing but at least it is now working for them.
Feb 16, 2010 9:32
Have you installed only the EPiServerCMS.msi? If so, you also have to install EPiServerShared.msi to update the deployment center. That in turn needs EPiServer.Framework.msi and you should be good.
Apr 23, 2014 15:28
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
Hi,
We are in need of some pointers here please, I have a client who is in the process of comparing CMS software and whilst trying to install a demo of EPiServer 6 they have run into the following issue:
The term 'New-EPiCMSWizard' is not recognized as a cmdlet, function, operable p
rogram, or script file. Verify the term and try again.
When executing
At C:\Program Files (x86)\EPiServer\CMS\6.0.452.2\Install\System Scripts\Delete
Site.ps1:46 char:27
+ $wizard = New-EPiCMSWizard <<<< "DeleteSiteWizard"
=
Get-EPiIsBulkInstalling
Error - System.Management.Automation.CommandNotFoundException: The term 'New-EPiCMSWizard' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again.
at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName)
at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin)
at System.Management.Automation.CommandFactory._CreateCommand(String commandName, CommandOrigin commandOrigin)
at System.Management.Automation.CommandFactory.CreateCommand(String commandName, CommandOrigin commandOrigin)
at System.Management.Automation.Parser.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList)
at System.Management.Automation.Parser.PipelineNode.Execute(Array input, Pipe outputPipe)
at System.Management.Automation.Parser.AssignmentStatementNode.Execute(Array input, Pipe outputPipe)
at System.Management.Automation.Parser.StatementListNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList)
Can't stress how important this is for us as the client is a Major UK bank and we need to make sure there experience of this demo is seamless.
Thanks
Greg