Changing physical path on IIS through appcmd isn't activatedusing appcmd to add new web site issueSetting up IIS 7.5 Shared Configuration (with encrypted values) on Windows Server 2008 R2 CoreIIS 7.x Application Pool Best PracticesDirectly editing IIS 7 applicationHost.config configuration fileIIS 7 What does Physical path credentials logon type mean?Unable to access newly created web site in IIS 7.5IIS applications appear in appcmd but not in IIS manager tree viewIIS7.5 Virtual Directory Wrong Physical PathWhy does scripting with appcmd behave differently than using IIS GUI?How to get “Physical Path Credentials Logon Type” for site and application?
How to set the font color of quantity objects (Version 11.3 vs version 12)?
Subtleties of choosing the sequence of tenses in Russian
In gnome-terminal only 2 out of 3 zoom keys work
Sci-fi novel series with instant travel between planets through gates. A river runs through the gates
When and why did journal article titles become descriptive, rather than creatively allusive?
Does a creature that is immune to a condition still make a saving throw?
Why is current rating for multicore cable lower than single core with the same cross section?
Binary Numbers Magic Trick
Is GOCE a satellite or aircraft?
Confusion about capacitors
How to creep the reader out with what seems like a normal person?
Minimum value of 4 digit number divided by sum of its digits
Do I have to worry about players making “bad” choices on level up?
Please, smoke with good manners
Confused by notation of atomic number Z and mass number A on periodic table of elements
Transfer over $10k
Modify locally tikzset
Help, my Death Star suffers from Kessler syndrome!
How to determine the actual or "true" resolution of a digital photograph?
Why does nature favour the Laplacian?
How to replace the "space symbol" (squat-u) in listings?
gnu parallel how to use with ffmpeg
Asahi Dry Black beer can
What's the polite way to say "I need to urinate"?
Changing physical path on IIS through appcmd isn't activated
using appcmd to add new web site issueSetting up IIS 7.5 Shared Configuration (with encrypted values) on Windows Server 2008 R2 CoreIIS 7.x Application Pool Best PracticesDirectly editing IIS 7 applicationHost.config configuration fileIIS 7 What does Physical path credentials logon type mean?Unable to access newly created web site in IIS 7.5IIS applications appear in appcmd but not in IIS manager tree viewIIS7.5 Virtual Directory Wrong Physical PathWhy does scripting with appcmd behave differently than using IIS GUI?How to get “Physical Path Credentials Logon Type” for site and application?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
We have come across an issue on IIS 7.5 where we have a simple deploy system which consists of the following:
Create a zip-file of new webroot, consisting of three folders:
Api
Site
Manager
This is unzipped into a new folder (let's say we call it "SITE_REV1"), and contains a script which invokes the following (one for each webroot):
C:Windowssystem32inetsrvappcmd set vdir "www.site.com/" -physicalPath:"SITE_REV1Site"
This usually work, in 9/10 times. In some cases, the webroot seems to be updated correctly (if I inspect basic settings in IIS Manager, the path looks correct), but the running site in question is actually pointed to the old location. The only way we have managed to "fix it", is by running an IIS-reset. It isn't enough to recycle the application pool in question.
Sometimes it seems to even necessary be to make a reboot, but I'm not 100% sure that is accurate (it hasn't always been myself that was fixing the problem).
I rewrote the script using Powershell and the Web-Administration module, hoping that there was a glitch in appcmd, but the same issue occurs.
Set-ItemProperty "IIS:Siteswww.site.com" -Name physicalPath -Value "SITE_REV1Site"
Has anyone experienced something like this? Do anyone have a clue on what's going on, and what I can try and do to prevent this issue? Doing an IIS reset is not really a good option for us, because that would affect all sites on the server every time we try and deploy changes on a single site.
EDIT: We have identified that a start/stop of the site (NOT the application pool) in IIS Manager resolves the errorneous physical path, but if I stop the site using appcmd, change physical path, and then start it, I still suffer from the same issues. I'm at a blank...
scripting powershell iis-7.5 deployment appcmd
asked Apr 4 '13 at 12:55
jishijishi
5441922
|
show 4 more comments
We have come across an issue on IIS 7.5 where we have a simple deploy system which consists of the following:
Create a zip-file of new webroot, consisting of three folders:
Api
Site
Manager
This is unzipped into a new folder (let's say we call it "SITE_REV1"), and contains a script which invokes the following (one for each webroot):
C:Windowssystem32inetsrvappcmd set vdir "www.site.com/" -physicalPath:"SITE_REV1Site"
This usually work, in 9/10 times. In some cases, the webroot seems to be updated correctly (if I inspect basic settings in IIS Manager, the path looks correct), but the running site in question is actually pointed to the old location. The only way we have managed to "fix it", is by running an IIS-reset. It isn't enough to recycle the application pool in question.
Sometimes it seems to even necessary be to make a reboot, but I'm not 100% sure that is accurate (it hasn't always been myself that was fixing the problem).
I rewrote the script using Powershell and the Web-Administration module, hoping that there was a glitch in appcmd, but the same issue occurs.
Set-ItemProperty "IIS:Siteswww.site.com" -Name physicalPath -Value "SITE_REV1Site"
Has anyone experienced something like this? Do anyone have a clue on what's going on, and what I can try and do to prevent this issue? Doing an IIS reset is not really a good option for us, because that would affect all sites on the server every time we try and deploy changes on a single site.
EDIT: We have identified that a start/stop of the site (NOT the application pool) in IIS Manager resolves the errorneous physical path, but if I stop the site using appcmd, change physical path, and then start it, I still suffer from the same issues. I'm at a blank...
scripting powershell iis-7.5 deployment appcmd
asked Apr 4 '13 at 12:55
jishijishi
5441922
1
For those times when it doesn't work, is it possible that the requests were existing ones being served by the old app pool via overlapping rotation? Not sure of the uptime requirements of your site, but you could try disabling overlapping rotation and including an app pool recycle command in your deployment script.
– explunit
Apr 4 '13 at 13:47
No, all subsequent requests is served from the old webroot, even an application recycle will reload the application from the old root. An IIS reset is the only way we have managed to restore it. It's like the applicationHost.config is updated (since IIS manager shows the correct path), but the IIS server itself works from the previous configuration...
– jishi
Apr 4 '13 at 13:49
I can not find a mention of it in applicationHost.config, so I assume it's the default "false"?
– jishi
Apr 4 '13 at 13:59
OK, was thinking if disallowOverlappingRotation = true, then old app pool might not be shutting down due to a long-running thread or something. Which is why IIS Reset would be required to fully clear it. Interesting question -- will be curious to see what answers show up.
– explunit
Apr 4 '13 at 14:01
Bear in mind an app pool recycle isn't the same as stop/start. Have you tried this method? Bear in mind, this will kill all current connections and make the site unavailable (error 500) until the app pool is restarted.
– John Homer
Apr 11 '13 at 14:35
|
show 4 more comments
We have come across an issue on IIS 7.5 where we have a simple deploy system which consists of the following:
Create a zip-file of new webroot, consisting of three folders:
Api
Site
Manager
This is unzipped into a new folder (let's say we call it "SITE_REV1"), and contains a script which invokes the following (one for each webroot):
C:Windowssystem32inetsrvappcmd set vdir "www.site.com/" -physicalPath:"SITE_REV1Site"
This usually work, in 9/10 times. In some cases, the webroot seems to be updated correctly (if I inspect basic settings in IIS Manager, the path looks correct), but the running site in question is actually pointed to the old location. The only way we have managed to "fix it", is by running an IIS-reset. It isn't enough to recycle the application pool in question.
Sometimes it seems to even necessary be to make a reboot, but I'm not 100% sure that is accurate (it hasn't always been myself that was fixing the problem).
I rewrote the script using Powershell and the Web-Administration module, hoping that there was a glitch in appcmd, but the same issue occurs.
Set-ItemProperty "IIS:Siteswww.site.com" -Name physicalPath -Value "SITE_REV1Site"
Has anyone experienced something like this? Do anyone have a clue on what's going on, and what I can try and do to prevent this issue? Doing an IIS reset is not really a good option for us, because that would affect all sites on the server every time we try and deploy changes on a single site.
EDIT: We have identified that a start/stop of the site (NOT the application pool) in IIS Manager resolves the errorneous physical path, but if I stop the site using appcmd, change physical path, and then start it, I still suffer from the same issues. I'm at a blank...
scripting powershell iis-7.5 deployment appcmd
asked Apr 4 '13 at 12:55
jishijishi
5441922
We have come across an issue on IIS 7.5 where we have a simple deploy system which consists of the following:
Create a zip-file of new webroot, consisting of three folders:
Api
Site
Manager
This is unzipped into a new folder (let's say we call it "SITE_REV1"), and contains a script which invokes the following (one for each webroot):
C:Windowssystem32inetsrvappcmd set vdir "www.site.com/" -physicalPath:"SITE_REV1Site"
This usually work, in 9/10 times. In some cases, the webroot seems to be updated correctly (if I inspect basic settings in IIS Manager, the path looks correct), but the running site in question is actually pointed to the old location. The only way we have managed to "fix it", is by running an IIS-reset. It isn't enough to recycle the application pool in question.
Sometimes it seems to even necessary be to make a reboot, but I'm not 100% sure that is accurate (it hasn't always been myself that was fixing the problem).
I rewrote the script using Powershell and the Web-Administration module, hoping that there was a glitch in appcmd, but the same issue occurs.
Set-ItemProperty "IIS:Siteswww.site.com" -Name physicalPath -Value "SITE_REV1Site"
Has anyone experienced something like this? Do anyone have a clue on what's going on, and what I can try and do to prevent this issue? Doing an IIS reset is not really a good option for us, because that would affect all sites on the server every time we try and deploy changes on a single site.
EDIT: We have identified that a start/stop of the site (NOT the application pool) in IIS Manager resolves the errorneous physical path, but if I stop the site using appcmd, change physical path, and then start it, I still suffer from the same issues. I'm at a blank...
scripting powershell iis-7.5 deployment appcmd
scripting powershell iis-7.5 deployment appcmd
asked Apr 4 '13 at 12:55
jishijishi
5441922
asked Apr 4 '13 at 12:55
jishijishi
5441922
edited Feb 19 '17 at 10:55
jishi
asked Apr 4 '13 at 12:55
jishijishi
5441922
asked Apr 4 '13 at 12:55
jishijishi
5441922
asked Apr 4 '13 at 12:55
jishijishi
5441922
5441922
1
For those times when it doesn't work, is it possible that the requests were existing ones being served by the old app pool via overlapping rotation? Not sure of the uptime requirements of your site, but you could try disabling overlapping rotation and including an app pool recycle command in your deployment script.
– explunit
Apr 4 '13 at 13:47
No, all subsequent requests is served from the old webroot, even an application recycle will reload the application from the old root. An IIS reset is the only way we have managed to restore it. It's like the applicationHost.config is updated (since IIS manager shows the correct path), but the IIS server itself works from the previous configuration...
– jishi
Apr 4 '13 at 13:49
I can not find a mention of it in applicationHost.config, so I assume it's the default "false"?
– jishi
Apr 4 '13 at 13:59
OK, was thinking if disallowOverlappingRotation = true, then old app pool might not be shutting down due to a long-running thread or something. Which is why IIS Reset would be required to fully clear it. Interesting question -- will be curious to see what answers show up.
– explunit
Apr 4 '13 at 14:01
Bear in mind an app pool recycle isn't the same as stop/start. Have you tried this method? Bear in mind, this will kill all current connections and make the site unavailable (error 500) until the app pool is restarted.
– John Homer
Apr 11 '13 at 14:35
|
show 4 more comments
1
For those times when it doesn't work, is it possible that the requests were existing ones being served by the old app pool via overlapping rotation? Not sure of the uptime requirements of your site, but you could try disabling overlapping rotation and including an app pool recycle command in your deployment script.
– explunit
Apr 4 '13 at 13:47
No, all subsequent requests is served from the old webroot, even an application recycle will reload the application from the old root. An IIS reset is the only way we have managed to restore it. It's like the applicationHost.config is updated (since IIS manager shows the correct path), but the IIS server itself works from the previous configuration...
– jishi
Apr 4 '13 at 13:49
I can not find a mention of it in applicationHost.config, so I assume it's the default "false"?
– jishi
Apr 4 '13 at 13:59
OK, was thinking if disallowOverlappingRotation = true, then old app pool might not be shutting down due to a long-running thread or something. Which is why IIS Reset would be required to fully clear it. Interesting question -- will be curious to see what answers show up.
– explunit
Apr 4 '13 at 14:01
Bear in mind an app pool recycle isn't the same as stop/start. Have you tried this method? Bear in mind, this will kill all current connections and make the site unavailable (error 500) until the app pool is restarted.
– John Homer
Apr 11 '13 at 14:35
1
1
For those times when it doesn't work, is it possible that the requests were existing ones being served by the old app pool via overlapping rotation? Not sure of the uptime requirements of your site, but you could try disabling overlapping rotation and including an app pool recycle command in your deployment script.
– explunit
Apr 4 '13 at 13:47
For those times when it doesn't work, is it possible that the requests were existing ones being served by the old app pool via overlapping rotation? Not sure of the uptime requirements of your site, but you could try disabling overlapping rotation and including an app pool recycle command in your deployment script.
– explunit
Apr 4 '13 at 13:47
No, all subsequent requests is served from the old webroot, even an application recycle will reload the application from the old root. An IIS reset is the only way we have managed to restore it. It's like the applicationHost.config is updated (since IIS manager shows the correct path), but the IIS server itself works from the previous configuration...
– jishi
Apr 4 '13 at 13:49
No, all subsequent requests is served from the old webroot, even an application recycle will reload the application from the old root. An IIS reset is the only way we have managed to restore it. It's like the applicationHost.config is updated (since IIS manager shows the correct path), but the IIS server itself works from the previous configuration...
– jishi
Apr 4 '13 at 13:49
I can not find a mention of it in applicationHost.config, so I assume it's the default "false"?
– jishi
Apr 4 '13 at 13:59
I can not find a mention of it in applicationHost.config, so I assume it's the default "false"?
– jishi
Apr 4 '13 at 13:59
OK, was thinking if disallowOverlappingRotation = true, then old app pool might not be shutting down due to a long-running thread or something. Which is why IIS Reset would be required to fully clear it. Interesting question -- will be curious to see what answers show up.
– explunit
Apr 4 '13 at 14:01
OK, was thinking if disallowOverlappingRotation = true, then old app pool might not be shutting down due to a long-running thread or something. Which is why IIS Reset would be required to fully clear it. Interesting question -- will be curious to see what answers show up.
– explunit
Apr 4 '13 at 14:01
Bear in mind an app pool recycle isn't the same as stop/start. Have you tried this method? Bear in mind, this will kill all current connections and make the site unavailable (error 500) until the app pool is restarted.
– John Homer
Apr 11 '13 at 14:35
Bear in mind an app pool recycle isn't the same as stop/start. Have you tried this method? Bear in mind, this will kill all current connections and make the site unavailable (error 500) until the app pool is restarted.
– John Homer
Apr 11 '13 at 14:35
|
show 4 more comments
2 Answers
2
active
oldest
votes
Does changing the physical path from IIS Manager work correctly and immediately?
You might want to try the following command. Differently syntax, should have the same result but maybe it works slightly different internally causing IIS to pick up the changes (better):
C:WindowsSystem32inetsrvappcmd.exe set app "www.site.com/" -[path='/'].physicalPath:"SITE_REV1Site"
answered Apr 12 '13 at 21:01
Marco MiltenburgMarco Miltenburg
1,03189
AFAIK we have never had any problem when we change it manually in IIS manager, only programatically.
– jishi
Apr 14 '13 at 10:31
add a comment |
An app pool recycle should be sufficient per site basis. These are independent processes. Too often articles and processes promote using iisreset. Is stopping / starting the app pool for the one site an option? Is this a single server solution and are you trying to minimze downtime for the site? There is an option to Disable recycling on configuration changes. Then you can manually recycle. When the problem happens, what is listed in the applicationHost.config?
answered Apr 14 '13 at 10:00
Steve SchofieldSteve Schofield
40924
I'm not 100% sure, but since IIS Manager list the new path, I assume that applicationHost.config is up to date. However, when the process recycles, it doesn't seem to use the newly configured values. Since this only happens occasionally it's hard to troubleshoot it in a timely manner.
– jishi
Apr 14 '13 at 10:30
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f496092%2fchanging-physical-path-on-iis-through-appcmd-isnt-activated%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Does changing the physical path from IIS Manager work correctly and immediately?
You might want to try the following command. Differently syntax, should have the same result but maybe it works slightly different internally causing IIS to pick up the changes (better):
C:WindowsSystem32inetsrvappcmd.exe set app "www.site.com/" -[path='/'].physicalPath:"SITE_REV1Site"
answered Apr 12 '13 at 21:01
Marco MiltenburgMarco Miltenburg
1,03189
AFAIK we have never had any problem when we change it manually in IIS manager, only programatically.
– jishi
Apr 14 '13 at 10:31
add a comment |
Does changing the physical path from IIS Manager work correctly and immediately?
You might want to try the following command. Differently syntax, should have the same result but maybe it works slightly different internally causing IIS to pick up the changes (better):
C:WindowsSystem32inetsrvappcmd.exe set app "www.site.com/" -[path='/'].physicalPath:"SITE_REV1Site"
answered Apr 12 '13 at 21:01
Marco MiltenburgMarco Miltenburg
1,03189
AFAIK we have never had any problem when we change it manually in IIS manager, only programatically.
– jishi
Apr 14 '13 at 10:31
add a comment |
Does changing the physical path from IIS Manager work correctly and immediately?
You might want to try the following command. Differently syntax, should have the same result but maybe it works slightly different internally causing IIS to pick up the changes (better):
C:WindowsSystem32inetsrvappcmd.exe set app "www.site.com/" -[path='/'].physicalPath:"SITE_REV1Site"
answered Apr 12 '13 at 21:01
Marco MiltenburgMarco Miltenburg
1,03189
Does changing the physical path from IIS Manager work correctly and immediately?
You might want to try the following command. Differently syntax, should have the same result but maybe it works slightly different internally causing IIS to pick up the changes (better):
C:WindowsSystem32inetsrvappcmd.exe set app "www.site.com/" -[path='/'].physicalPath:"SITE_REV1Site"
answered Apr 12 '13 at 21:01
Marco MiltenburgMarco Miltenburg
1,03189
answered Apr 12 '13 at 21:01
Marco MiltenburgMarco Miltenburg
1,03189
answered Apr 12 '13 at 21:01
Marco MiltenburgMarco Miltenburg
1,03189
answered Apr 12 '13 at 21:01
Marco MiltenburgMarco Miltenburg
1,03189
1,03189
AFAIK we have never had any problem when we change it manually in IIS manager, only programatically.
– jishi
Apr 14 '13 at 10:31
add a comment |
AFAIK we have never had any problem when we change it manually in IIS manager, only programatically.
– jishi
Apr 14 '13 at 10:31
AFAIK we have never had any problem when we change it manually in IIS manager, only programatically.
– jishi
Apr 14 '13 at 10:31
AFAIK we have never had any problem when we change it manually in IIS manager, only programatically.
– jishi
Apr 14 '13 at 10:31
add a comment |
An app pool recycle should be sufficient per site basis. These are independent processes. Too often articles and processes promote using iisreset. Is stopping / starting the app pool for the one site an option? Is this a single server solution and are you trying to minimze downtime for the site? There is an option to Disable recycling on configuration changes. Then you can manually recycle. When the problem happens, what is listed in the applicationHost.config?
answered Apr 14 '13 at 10:00
Steve SchofieldSteve Schofield
40924
I'm not 100% sure, but since IIS Manager list the new path, I assume that applicationHost.config is up to date. However, when the process recycles, it doesn't seem to use the newly configured values. Since this only happens occasionally it's hard to troubleshoot it in a timely manner.
– jishi
Apr 14 '13 at 10:30
add a comment |
An app pool recycle should be sufficient per site basis. These are independent processes. Too often articles and processes promote using iisreset. Is stopping / starting the app pool for the one site an option? Is this a single server solution and are you trying to minimze downtime for the site? There is an option to Disable recycling on configuration changes. Then you can manually recycle. When the problem happens, what is listed in the applicationHost.config?
answered Apr 14 '13 at 10:00
Steve SchofieldSteve Schofield
40924
I'm not 100% sure, but since IIS Manager list the new path, I assume that applicationHost.config is up to date. However, when the process recycles, it doesn't seem to use the newly configured values. Since this only happens occasionally it's hard to troubleshoot it in a timely manner.
– jishi
Apr 14 '13 at 10:30
add a comment |
An app pool recycle should be sufficient per site basis. These are independent processes. Too often articles and processes promote using iisreset. Is stopping / starting the app pool for the one site an option? Is this a single server solution and are you trying to minimze downtime for the site? There is an option to Disable recycling on configuration changes. Then you can manually recycle. When the problem happens, what is listed in the applicationHost.config?
answered Apr 14 '13 at 10:00
Steve SchofieldSteve Schofield
40924
An app pool recycle should be sufficient per site basis. These are independent processes. Too often articles and processes promote using iisreset. Is stopping / starting the app pool for the one site an option? Is this a single server solution and are you trying to minimze downtime for the site? There is an option to Disable recycling on configuration changes. Then you can manually recycle. When the problem happens, what is listed in the applicationHost.config?
answered Apr 14 '13 at 10:00
Steve SchofieldSteve Schofield
40924
answered Apr 14 '13 at 10:00
Steve SchofieldSteve Schofield
40924
answered Apr 14 '13 at 10:00
Steve SchofieldSteve Schofield
40924
answered Apr 14 '13 at 10:00
Steve SchofieldSteve Schofield
40924
40924
I'm not 100% sure, but since IIS Manager list the new path, I assume that applicationHost.config is up to date. However, when the process recycles, it doesn't seem to use the newly configured values. Since this only happens occasionally it's hard to troubleshoot it in a timely manner.
– jishi
Apr 14 '13 at 10:30
add a comment |
I'm not 100% sure, but since IIS Manager list the new path, I assume that applicationHost.config is up to date. However, when the process recycles, it doesn't seem to use the newly configured values. Since this only happens occasionally it's hard to troubleshoot it in a timely manner.
– jishi
Apr 14 '13 at 10:30
I'm not 100% sure, but since IIS Manager list the new path, I assume that applicationHost.config is up to date. However, when the process recycles, it doesn't seem to use the newly configured values. Since this only happens occasionally it's hard to troubleshoot it in a timely manner.
– jishi
Apr 14 '13 at 10:30
I'm not 100% sure, but since IIS Manager list the new path, I assume that applicationHost.config is up to date. However, when the process recycles, it doesn't seem to use the newly configured values. Since this only happens occasionally it's hard to troubleshoot it in a timely manner.
– jishi
Apr 14 '13 at 10:30
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f496092%2fchanging-physical-path-on-iis-through-appcmd-isnt-activated%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
For those times when it doesn't work, is it possible that the requests were existing ones being served by the old app pool via overlapping rotation? Not sure of the uptime requirements of your site, but you could try disabling overlapping rotation and including an app pool recycle command in your deployment script.
– explunit
Apr 4 '13 at 13:47
No, all subsequent requests is served from the old webroot, even an application recycle will reload the application from the old root. An IIS reset is the only way we have managed to restore it. It's like the applicationHost.config is updated (since IIS manager shows the correct path), but the IIS server itself works from the previous configuration...
– jishi
Apr 4 '13 at 13:49
I can not find a mention of it in applicationHost.config, so I assume it's the default "false"?
– jishi
Apr 4 '13 at 13:59
OK, was thinking if disallowOverlappingRotation = true, then old app pool might not be shutting down due to a long-running thread or something. Which is why IIS Reset would be required to fully clear it. Interesting question -- will be curious to see what answers show up.
– explunit
Apr 4 '13 at 14:01
Bear in mind an app pool recycle isn't the same as stop/start. Have you tried this method? Bear in mind, this will kill all current connections and make the site unavailable (error 500) until the app pool is restarted.
– John Homer
Apr 11 '13 at 14:35