Powershell New-WebApplication

iis-7powershell

[Void][Reflection.Assembly]::LoadWithPartialName("Microsoft.Web.Administration")

New-WebApplication -Name 'testApp' -Site 'Default Web Site' -PhysicalPath c:\test -ApplicationPool DefaultAppPool

That is the contents of test.ps1.
When I run .\test.ps1 I get the following error.

New-WebApplication : Cannot retrieve the dynamic parameters for the
cmdlet. Retrieving the COM class factory for compon ent with CLSID
{688EEEE5-6A7E-422F-B2E1-6AF00DC944A6} failed due to the following
error: 80040154. At C:\code\work\users\mchevett\test.ps1:6 char:19
+ New-WebApplication <<<< -Name 'testApp' -Site 'Default Web Site'
-PhysicalPath c:\test -ApplicationPool DefaultAppPo ol
+ CategoryInfo : InvalidArgument: (:)
[New-WebApplication], ParameterBindingException
+ FullyQualifiedErrorId :
GetDynamicParametersException,Microsoft.IIs.PowerShell.Provider.NewWebApplicationCommand

This error message is not helping me at all. Any ideas how to get a better error message? Thanks for reading!

Best Answer

I had the exact same problem because I was calling the wrong version of PowerShell from my program. I'm not sure about this but I think when you have a x86 program it calls the x86 version of PowerShell, which fails.

To specifically use the 32-bit version, call this one from your program:

C:\Windows\SysWoW64\WindowsPowerShell\v1.0\powershell.exe

To use the 64-bit version (on a 64-bit OS), call this one from your program:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Using C:\Windows\SysNative\WindowsPowerShell\v1.0\powershell.exe from within a 32bit process will give you the 64bit powershell. Using it from within a 64bit process will give you a file-not-found error.

Related Solutions

Powershell – Determine installed PowerShell version

Use $PSVersionTable.PSVersion to determine the engine version. If the variable does not exist, it is safe to assume the engine is version 1.0.

Note that $Host.Version and (Get-Host).Version are not reliable - they reflect the version of the host only, not the engine. PowerGUI, PowerShellPLUS, etc. are all hosting applications, and they will set the host's version to reflect their product version — which is entirely correct, but not what you're looking for.

PS C:\> $PSVersionTable.PSVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
4      0      -1     -1

PowerShell says “execution of scripts is disabled on this system.”

If you're using Windows Server 2008 R2 then there is an x64 and x86 version of PowerShell both of which have to have their execution policies set. Did you set the execution policy on both hosts?

As an Administrator, you can set the execution policy by typing this into your PowerShell window:

Set-ExecutionPolicy RemoteSigned

For more information, see Using the Set-ExecutionPolicy Cmdlet.

When you are done, you can set the policy back to its default value with:

Set-ExecutionPolicy Restricted

You may see an error:

Access to the registry key
'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell' is denied. 
To change the execution policy for the default (LocalMachine) scope, 
  start Windows PowerShell with the "Run as administrator" option. 
To change the execution policy for the current user, 
  run "Set-ExecutionPolicy -Scope CurrentUser".

So you may need to run the command like this (as seen in comments):

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser

Best Answer

Related Solutions

Powershell – Determine installed PowerShell version

PowerShell says “execution of scripts is disabled on this system.”

Related Topic