Thanks Scot for your follow-up. We reviewed the article you mention
and didn't find anything new in there for us.
I don't believe this is an issue of a newer config file on the server
not downloading and overwriting an older config file on a client. Our
problem is the config file is not being transferred down, period.
Let me restate the problem: we have two servers set up. One is a
Windows 2000 server and the other is a Windows 2003 server. We
configure virtual directories with the same setup on each machine. We
copy an executable along with it's associated config file and
supporting dll's into each virtual directory. We can successfully
launch and run the application from the Windows 2000 server. We can
successfully launch the application from the Windows 2003 server but
it fails to run because the app.config file is not transferred down
from the Windows 2003 server. This is true if we try to launch the
application from a client on which the application has never been
launched, and on a machine on which we've cleared the download cache
with gacutil /cdl.
When we examine the web log on the Windows 2003 server we can see that
all attempts to retrieve the app.config file failed with 401
responses. We've enabled anonymous access on the virtual directory and
have enabled transfer of config files from the virtual directory by
removing the .config extension from the list of handled extensions
and/or altering the httpHandler in web.config to allow transfer of
.config files.
There seems to be an additional block for .config files on the Windows
2003 server and I'm wondering where that is. If there are any further
tests we can run to eliminate or find other possibilities, please let
me know.
Thanks,
Mike
I have scoured the internal databases here for any information that might explain this but have come up dry. No bug reports, prevous cases, etc. At this point my suggestion is that
you use one of your MSDN Incidents and open a support call so you can work directly with a specialist in that area.If it turns out to be a bug in the product you would most likely not
be decremented on your incident count. If you have an actual Reproducable scenario to give to the Support Professional when you call that would probably help to speed things
along.
Scot Rose, MCSD
Microsoft Visual Basic Developer Support
Email : scotr@online.microsoft.com <Remove word online. from address>
This posting is provided ?AS IS?, with no warranties, and confers no rights.
Get Secure!
http://www.microsoft.com/security
http://www.microsoft.com/protect
--------------------
>From: Mike Livenspargar <botatus@hotmail.com>
>Subject: Re: Windows Server 3003 and No-Touch Deployment
>Date: Thu, 23 Oct 2003 09:50:18 -0700
>Message-ID: <tivfpv07m18dd8vneeub0ecin3t9b815ue@4ax.com>
>References: <#vdcAwvgDHA.2084@TK2MSFTNGP10.phx.gbl> <EMFBhERiDHA.1752@cpmsftngxa06.phx.gbl> <#9zGMhDjDHA.360@TK2MSFTNGP10.phx.gbl>
<TpjW1kxlDHA.576@cpmsftngxa06.phx.gbl>
>X-Newsreader: Forte Free Agent 1.93/32.576 English (American)
>MIME-Version: 1.0
[quoted text clipped - 170 lines]
>>>
>>>Mike
Junfeng Zhang[MSFT] - 30 Oct 2003 01:07 GMT
Did you read Alan's Blog?
http://blogs.gotdotnet.com/alanshi/commentview.aspx/fafd34ae-e72d-44ca-bb2d-7614
ecfa2070
> I have scoured the internal databases here for any information that might explain this but have come up dry. No bug reports, prevous cases, etc. At
this point my suggestion is that
> you use one of your MSDN Incidents and open a support call so you can work directly with a specialist in that area.If it turns out to be a bug in the
product you would most likely not
> be decremented on your incident count. If you have an actual Reproducable scenario to give to the Support Professional when you call that would
probably help to speed things
> along.
>
[quoted text clipped - 3 lines]
>
> This posting is provided "AS IS", with no warranties, and confers no
rights.
> Get Secure!
> http://www.microsoft.com/security
[quoted text clipped - 6 lines]
> >Message-ID: <tivfpv07m18dd8vneeub0ecin3t9b815ue@4ax.com>
> >References: <#vdcAwvgDHA.2084@TK2MSFTNGP10.phx.gbl> <EMFBhERiDHA.1752@cpmsftngxa06.phx.gbl>
<#9zGMhDjDHA.360@TK2MSFTNGP10.phx.gbl>
> <TpjW1kxlDHA.576@cpmsftngxa06.phx.gbl>
> >X-Newsreader: Forte Free Agent 1.93/32.576 English (American)
[quoted text clipped - 5 lines]
> >Lines: 1
> >Path: cpmsftngxa06.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP10.phx.gbl
> >Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework:56938
> >X-Tomcat-NG: microsoft.public.dotnet.framework
[quoted text clipped - 53 lines]
> >>
> >>This posting is provided "AS IS", with no warranties, and confers no
rights.
> >>Get Secure!
> >>http://www.microsoft.com/security
[quoted text clipped - 104 lines]
> >>>
> >>>Mike
Scot Rose [MSFT] - 30 Oct 2003 16:17 GMT
Actaully, My search didn't turn up THAT page... Looks like the answer though doesn't it... Thanks for chiming in here...
Scot Rose, MCSD
Microsoft Visual Basic Developer Support
Email : scotr@online.microsoft.com <Remove word online. from address>
This posting is provided ?AS IS?, with no warranties, and confers no rights.
Get Secure!
http://www.microsoft.com/security
http://www.microsoft.com/protect
--------------------
>From: "Junfeng Zhang[MSFT]" <juzhang@online.microsoft.com>
>References: <#vdcAwvgDHA.2084@TK2MSFTNGP10.phx.gbl> <EMFBhERiDHA.1752@cpmsftngxa06.phx.gbl> <#9zGMhDjDHA.360@TK2MSFTNGP10.phx.gbl>
<TpjW1kxlDHA.576@cpmsftngxa06.phx.gbl> <tivfpv07m18dd8vneeub0ecin3t9b815ue@4ax.com> <NK8kXIjnDHA.1548@cpmsftngxa06.phx.gbl>
>Subject: Re: Windows Server 3003 and No-Touch Deployment
>Date: Wed, 29 Oct 2003 16:07:58 -0800
[quoted text clipped - 236 lines]
>> >>>
>> >>>Mike
nospam_donbarber@hotmail.com - 24 Dec 2003 23:19 GMT
All,
Just checking to see if there is any more info on the issue that Mike has
raised here.
We are having the exact (to the letter) problem outlined below where we can
not get the app.config file to download from a Windows 2003 Server (or
Windows XP), but the same app will work on Windows 2000.
I have tried all of the workarounds mentioned by Chris Sells, Alan Shi, and
Ingo and others to no avail.
Any help would be very much appreciated.
> I have scoured the internal databases here for any information that might explain this but have come up dry. No bug reports, prevous cases, etc. At
this point my suggestion is that
> you use one of your MSDN Incidents and open a support call so you can work directly with a specialist in that area.If it turns out to be a bug in the
product you would most likely not
> be decremented on your incident count. If you have an actual Reproducable scenario to give to the Support Professional when you call that would
probably help to speed things
> along.
>
[quoted text clipped - 3 lines]
>
> This posting is provided "AS IS", with no warranties, and confers no
rights.
> Get Secure!
> http://www.microsoft.com/security
[quoted text clipped - 6 lines]
> >Message-ID: <tivfpv07m18dd8vneeub0ecin3t9b815ue@4ax.com>
> >References: <#vdcAwvgDHA.2084@TK2MSFTNGP10.phx.gbl> <EMFBhERiDHA.1752@cpmsftngxa06.phx.gbl>
<#9zGMhDjDHA.360@TK2MSFTNGP10.phx.gbl>
> <TpjW1kxlDHA.576@cpmsftngxa06.phx.gbl>
> >X-Newsreader: Forte Free Agent 1.93/32.576 English (American)
[quoted text clipped - 5 lines]
> >Lines: 1
> >Path: cpmsftngxa06.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP10.phx.gbl
> >Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework:56938
> >X-Tomcat-NG: microsoft.public.dotnet.framework
[quoted text clipped - 53 lines]
> >>
> >>This posting is provided "AS IS", with no warranties, and confers no
rights.
> >>Get Secure!
> >>http://www.microsoft.com/security
[quoted text clipped - 104 lines]
> >>>
> >>>Mike