Thanks for all your help!
Meanwhile I've learned from
http://groups.google.de/groups?hl=de...eadm=01d301c35
86e%24d75f9c00%24a601280a%40phx.gbl&rnum=2&prev=/groups%3Fq%3DWindows%2B2000
%2BSP4%2BASP.NET%2Bfailure%26hl%3Dde%26lr%3D%26ie% 3DUTF-8%26oe%3DUTF-8%26sel
m%3D01d301c3586e%2524d75f9c00%2524a601280a%2540phx .gbl%26rnum%3D2 and from
my own experiences that the error comes with SP4.
According to my investigations there is a bug in SP4 blocking the Frontpage
Server Extensions/WebDAV on certain server installations. Hope they'll fix
it soon. Meanwhile I guess I have to re-install my whole server over the
weekend and give it SP3... :(((
Best wishes,
Axel Dahmen
-------------------------
"Rabii" <ne****@yahoo.fr> wrote in message
news:uJ**************@TK2MSFTNGP10.phx.gbl...
Axel Dahmen wrote:
1) check with dcomcnfg that .net debugers let debug users (that your
user part of this group) to activate them.
I've examined my DCOM configuration. It seems well configured.
2) is the debugging problem applay to all projects, even new one ?
Yes. I've created a new project and can't debug that either.
Interesting: VS let's me attach to a running IE process. However, it
doesn't halt on any breakpoint...
try aspnet_regiis.exe -i ( you find this file in
C:\WINNT\Microsoft.NET\Framework\v1.0.3705 if you have framework version
1 )