Search Engine: Elastic

Article ID: 3934, created on Feb 8, 2008, last review on May 10, 2014

  • Applies to:
  • Helm 4



When trying to change the Scripting Support settings for a domain such as changing the ASP.NET version, it fails with the error:

Could not fully update scripting support settings


Failed to Get Site Settings for domain {$domainname}

In the error log, you see the following error:

<entry date='633203715708025608' utc_offset='-4' assembly='IISBase' source='ScriptingBase' method='SetScriptingSupport'>An exception (TargetInvocationException) occured setting the scripting support information for the domain name System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x800710D8): The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)

   --- End of inner exception stack trace ---

   at System.DirectoryServices.DirectoryEntry.Invoke(String methodName, Object[] args)

   at WHA.Helm.Providers.IISBase.MetabaseNode.aBQ=(String aRQ=, Object[] ahQ=)

   at WHA.Helm.Providers.IISBase.ApplicationPool.Recycle()

   at WHA.Helm.Providers.IISBase.VirtualDirectory.VRQ=(Int32 VhQ=)

   at WHA.Helm.Providers.IISBase.VirtualDirectory.set_AspNetVersion(Int32 value)

   at WHA.Helm.Providers.IISBase.Site.set_AspNetVersion(Int32 value)

   at WHA.Helm.Providers.AspNetExtension.SetAspNet(String State, Site Site, ProviderData CommandData)

   at DxQ=.whQ=.lhQ=(Site xxQ=, ProviderData yBQ=)

   at WHA.Helm.Providers.IISBase.ScriptingBase..SetScriptingSupport(ProviderData CommandData)</entry>


This is most likely because the domain in question is in its own application pool, and that application pool is stopped.

1.) Go into IIS, go to Application Pools and locate the Application Pool with the same name as the domain.

2.) Right-click on it, and choose Start.

3.) Go back to Helm and try to alte rthe Scripting Support settings again.

It should now work - if not, please contact your support provider.

0331e0e4efc12686c3f22fc2cdda9f03 152090ff5e9a05ea7e1cf0c248449638 3ef1f5f998c0dc182718a7fe4376f875

Email subscription for changes to this article
Save as PDF