By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,130 Members | 2,228 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,130 IT Pros & Developers. It's quick & easy.

Why IISAdmin service requires restart to pick up web.config change

P: n/a
Hi there...i don't know if this is more an IIS thing or a .net thing, but i'm
trying to figure out why it is sometimes required for the IISAdmin service to
be restarted in order for changes to the web.config file to be picked up? For
example, changes to database connection strings...At first i thought this has
something to do with the way the application is developed - perhaps certain
applications cache this information rather then reading from the web.config
file on each access....but then i noticed that the same application installed
on different servers behaved differently. On one server the db connection
change was automatic & did not require any restart of services. On another
server - it did require a restart. And i don't think its a case of just
giving IIS 'enough time' to pick up the changes, because i gave it a whole 24
hours and the app was still pointing to the old database.

I would appreciate any insight into this - as well as any pointers to some
MS documentation that explains how this all works...

May 2 '07 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.