Be the first to post a text review of Di IIS Web Manager. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Forum thread added

  zerox66 created the Delete function forum thread

  posted by zerox66 840 days ago

• Tracker artifact added

  alexhiggins732 created the Abilty to switch server and supply alternate credentials. artifact

  posted by alexhiggins732 973 days ago

• Tracker artifact added

  alexhiggins732 created the Cannot login to IIsApplicationPoolMain.aspx artifact

  posted by alexhiggins732 973 days ago

• Tracker artifact added

  alexhiggins732 created the Input string was not in a correct format. artifact

  posted by alexhiggins732 973 days ago

• Forum comment added

  alexhiggins732 commented on the RE: Invalid namespace forum thread

  posted by alexhiggins732 973 days ago

• Forum comment added

  alexhiggins732 commented on the RE: Why Access Denied? forum thread

  posted by alexhiggins732 973 days ago

• Forum thread added

  alexhiggins732 created the Invalid namespace forum thread

  posted by alexhiggins732 973 days ago

• Forum comment added

  alexhiggins732 commented on the RE: Input string was not in a correct format? forum thread

  posted by alexhiggins732 973 days ago

• Tracker artifact added

  lucifer79 created the System.Data.OleDb.OleDbException: Unspecified error artifact

  posted by lucifer79 1252 days ago

• Security Fix

  Thanks to Anton for this mail : "I finally tracked it down. Turns out that each namespace in the CIM repository has a security descriptor to control access. I was able to access root\cimv2 just fine from ASP.NET and VBScript, but was getting Access Denied when trying to access the root\MicrosoftIISv2 namespace. Luckily, an error was generated in the EventViewer: "Access to the root\MicrosoftIISv2 namespace was denied. The namespace is marked with RequiresEncryption but the client connection was attempted with an authentication level below Pkt_Privacy. Re try the connection using Pkt_Privacy authentication level." Before Windows Server 2003 SP1, providers could not set namespace security to require encryption before returning data. It looks like with SP1, the RequiresEncryption is configurable and is also the default. You can change this through the WMI control (globally) or programmatically per connection. In VB, it would look like this: set locatorObj = CreateObject("WbemScripting.SWbemLocator") locatorObj.Security_.authenticationLevel = WbemAuthenticationLevelPktPrivacy In C#, it would look like this: ConnectionOptionsObject = new ConnectionOptions(); ConnectionOptionsObject.Username = UserName; ConnectionOptionsObject.Password = Password; ConnectionOptionsObject.Authentication = AuthenticationLevel.PacketPrivacy; I have not tested this on other platforms outside of W2K3, SP1, as it presumably wasn't needed. Not sure if you're planning on publishing a newer version of your libraries any time soon, but just adding the line above to each ConnectionOptions object will fix this if anyone else experiences the issue."

  posted by ibrahimuludag 1486 days ago