IIS 7.0 - PowerShell

Re: New-WebSite error

spencer205 — Tue, 11 Nov 2008 19:53:50 GMT

I'm getting this error too. Has this been fixed yet?

Re: New-WebSite error

ShayL — Mon, 07 Jul 2008 20:28:30 GMT

Sergei,

I run the following 5 commands in a row, notice that the second command has no output while the fifth shows that the site exists and running. Thanks for the update on the WAS issue.

PS > New-WebSite test1

Name             ID   State      Physical Path                  Bindings
----             --   -----      -------------                  --------
test1            2                                              http *:80:test1
New-WebSite : The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)
At line:1 char:12
+ New-WebSite <<<< test1

PS > Get-WebItemState iis:\sites

PS > Get-WebItemState test1
Get-WebItemState : Cannot find path 'C:\test1' because it does not exist.
At line:1 char:17
+ Get-WebItemState <<<< test1

PS > Get-WebSiteState test1
Get-WebItemState : The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)
At line:1 char:17
+ get-webitemstate <<<< "IIS:\sites\test1"

PS > dir iis:\sites

Name             ID   State      Physical Path                  Bindings
----             --   -----      -------------                  --------
Default Web Site 1    Started    %SystemDrive%\inetpub\wwwroot http *:80:
test1            2                                              http *:80:test1

Re: New-WebSite error

sergeia — Mon, 07 Jul 2008 18:56:06 GMT

This is the timing issue I mentioned in my earlier post. WAS needs more time to pick new site or pool and start it, therefore (depending on your system) you could see this error, it is produced by output routine. Both site and pool are succesfully created, but State field of their PS representation needs runtime object that wasn't created by WAS yet.

I will fix this by next update of the provider.

Thanks,

Sergei

Re: New-WebSite error

rsiddaw — Mon, 07 Jul 2008 18:38:30 GMT

I also get the same error using new-appPool

PS> New-AppPool -Name 'pool1'

Name State Applications
---- ----- ------------
pool1
New-AppPool : The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)
At line:1 char:12
+ New-AppPool <<<< -Name 'pool1'

Re: New-WebSite error

rsiddaw — Mon, 07 Jul 2008 18:14:46 GMT

I see the same error and I have the Activation Service running

Re: New-WebSite error

sergeia — Mon, 07 Jul 2008 03:20:28 GMT

Shay, could you check status of your site using command "get-webitemstate path_to_site"? I think that Windows Activation Service (WAS) doesn't work on you machine. On output Powershell tries to get status of this object to fill column State, and seems that this fails. Or, you may try run command "dir iis:\sites". If you see no error and all sites show non-empty status field, it may be some problem with change notification, when site is created, it takes some time while WAS picks up status of this site.

Please give me more details on this failure.

--Sergei

New-WebSite error

ShayL — Fri, 04 Jul 2008 12:02:44 GMT

Congratulations for the second CTP release!

I get an error when trying to create a new site on Vista SP1:

PS 8> New-WebSite -name test6

Name ID State Physical Path Bindings
---- -- ----- ------------- --------
test6 6 http *:80:test6
New-WebSite : The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)
At line:1 char:12
+ New-WebSite <<<< -name test6

Here's the full error information:

Exception             : System.Runtime.InteropServices.COMException (0x800710D8): The object identifier does not repres
                        ent a valid object. (Exception from HRESULT: 0x800710D8)
                           at Microsoft.IIs.PowerShell.Framework.Interop.IAppHostProperty.get_Value()
                           at Microsoft.IIs.PowerShell.Framework.ConfigurationElement.GetPropertyValue(IAppHostProperty
                         property)
                           at Microsoft.IIs.PowerShell.Framework.ConfigurationAttribute.get_Value()
                           at Microsoft.IIs.PowerShell.Provider.RuntimeCommandBase.GetRuntimeProperty(String propName)
                           at Microsoft.IIs.PowerShell.Provider.GetItemStateCommand.ProcessRecord()
                           at System.Management.Automation.Cmdlet.DoProcessRecord()
                           at System.Management.Automation.CommandProcessor.ProcessRecord()
TargetObject          :
CategoryInfo          : NotSpecified: (:) [New-WebSite], COMException
FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.IIs.PowerShell.Provider.NewWebSiteCommand
ErrorDetails          :
InvocationInfo        : System.Management.Automation.InvocationInfo
PipelineIterationInfo : {0, 1, 1}

I found that if you assign the command to a variable then the error is gone

$newSite = New-WebSite -name test6