# Strange IIS Action Behaviour
**URL:** https://www.finalbuilder.com/forums/t/strange-iis-action-behaviour/2676
**Category:** Bugs
**Created:** [September 21, 2006, 6:43am UTC](https://www.finalbuilder.com/forums/t/strange-iis-action-behaviour/2676 "2006-09-21T06:43:52Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [September 21, 2006, 6:43am UTC](https://www.finalbuilder.com/forums/t/strange-iis-action-behaviour/2676/1 "2006-09-21T06:43:52Z")
I’m using FB 4.2.0.276, and having no end of trouble with IIS actions that _used to work_. I have verified that all my services are running as expected, that I can create and delete virtual directories using cscript, and yet I can’t get the FinalBuilder actions to run.
Even doing an IISRestart merely cacks with generic “Could not conect to server…” style information. Does anyone have any ideas?
---
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [September 21, 2006, 6:45am UTC](https://www.finalbuilder.com/forums/t/strange-iis-action-behaviour/2676/2 "2006-09-21T06:45:53Z")
I ought mention the exact text is:
Connectig to server ‘localhost’ …
An error occured in accessing the WMI Provider:
Could not open IIS 6 service provider on localhost :
---
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [September 21, 2006, 8:00am UTC](https://www.finalbuilder.com/forums/t/strange-iis-action-behaviour/2676/3 "2006-09-21T08:00:49Z")
Forcing FinalBuilder into debug indicates:
try
{
objService = objLocator.ConnectServer(ServerName, Service, User, Pass);
}
catch(E)
{
throw "Could not open IIS 6 service provider on " + ServerName + " : " + ExceptionMessage(E);
}
from FinalBuilder-OnExecute in FinalBuilder.exe. This is only on delete virtual directory though.
---
### Author:  [@angus](https://www.finalbuilder.com/forums/u/angus)
#### Post date: [September 22, 2006, 1:44am UTC](https://www.finalbuilder.com/forums/t/strange-iis-action-behaviour/2676/4 "2006-09-22T01:44:47Z")
Hi Chayim,
All of the IIS actions use the same code to obtain access to the WMI service provider, so they’re probably all failing for the same reason (namely the SwbemLocator.ConnectServer() call which is shown above in the debug output.)
I’ve emailed you some suggestions via our support system, so please let us know how you go (via just one of these two locations, if possible.)
Regards,
Angus