Home / user-84549

Nick Jones's questions

Martin Hope
Nick Jones
Asked: 2014-04-08 13:08:16 +0800 CST
  • 1

On a Windows Server 2012 box, I'm using PS to create a new IIS User (for automated deployments using MSDeploy). The command itself appears to work fine -- the user is created -- but as soon as I exit my PowerShell session (typing exit or just closing the command window), a dialog is displayed stating "powershell has stopped working", with the following details:

Problem signature:
  Problem Event Name:   PowerShell
  NameOfExe:    powershell.exe
  FileVersionOfSystemManagementAutomation:  6.2.9200.16628
  InnermostExceptionType:   Runtime.InteropServices.InvalidComObject
  OutermostExceptionType:   Runtime.InteropServices.InvalidComObject
  DeepestPowerShellFrame:   unknown
  DeepestFrame: System.StubHelpers.StubHelpers.GetCOMIPFromRCW
  ThreadName:   unknown
  OS Version:   6.2.9200.2.0.0.400.8
  Locale ID:    1033

The PS commands in question are:

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Web.Management")
[Microsoft.Web.Management.Server.ManagementAuthentication]::CreateUser("Foo", "Bar")

Why is this happening and how can I avoid it?

EDIT: I've also confirmed this be a problem with PowerShell 4.0, so I've added that tag. I've also submitted it on Connect.

UPDATE: It appears that Windows Server 2012 R2 does not have this same bug.

powershell
Martin Hope
Nick Jones
Asked: 2012-01-06 13:01:47 +0800 CST
  • 19

Microsoft's Web Platform Installer lists "Web Deployment Tool 2.1" with a release date of 4/11/2011, and "Web Deployment Tool 2.1 for Hosting Servers" with a release date of 4/8/2011. As far as I can see (by clicking Add, then Install), the contents are the same: the deployment tool itself, SQL Server 2008 R2 Management Objects (Dependency), SQL Server Native Client (Dependency), and SQL Server System CLR Types (Dependency).

Are these actually different, and if so, how? (And if not, why list them both?)

deployment web-platform-installer