Wrox Home  
Search P2P Archive for: Go

  Return to Index  

aspx_beginners thread: ALL READ - Server Problem Fix


Message #1 by "Charles E. Brown" <chabrown@b...> on Wed, 22 Jan 2003 08:48:15 -0500
Here is something that comes up periodically. I noticed several new
postings with this as a possible problem.

If you had an anti-virus program running at time of installation, the
.NET Framework may not install properly into the registry. This will
cause all sorts of things to breakdown, including debugging and running
aspx applications.

Microsoft has a fix posted at:

http://support.microsoft.com/?id=306005

I used it, as well as others, and it seems to fix the problems quickly.

Hope this helps,
Charles E. Brown
Author - Fireworks MX From Zero to Hero (FriendsofED publications)
	   Beginning Dreamweaver MX (Wrox Publishing)
Contributor - The Macromedia Studio MX Bible (John Wiley & Sons)


Message #2 by "Alex Smotritsky" <alex.smotritsky@v...> on Thu, 23 Jan 2003 05:31:45 -0500
I ran the stuff in that article and unfortunately, when I attempt to
start debugging I still get this error:

Error while trying to run project: Unable to start debugging on the web
server. You do not have permissions to debug the server. Verify that you
are a member of the 'Debugger Users' group on the server. Would you like
to disable future attempts to debug ASP.NET pages for this project?

I've made sure that everyone is a member of the Debugger Users Group and
that doesn't help.

Any body know what the deal is with this specific bug?

Thanks in advance.

Alex

-----Original Message-----
From: Charles E. Brown [mailto:chabrown@b...] 
Sent: Wednesday, January 22, 2003 8:48 AM
To: aspx_beginners
Subject: [aspx_beginners] ALL READ - Server Problem Fix


Here is something that comes up periodically. I noticed several new
postings with this as a possible problem.

If you had an anti-virus program running at time of installation, the
.NET Framework may not install properly into the registry. This will
cause all sorts of things to breakdown, including debugging and running
aspx applications.

Microsoft has a fix posted at:

http://support.microsoft.com/?id=306005

I used it, as well as others, and it seems to fix the problems quickly.

Hope this helps,
Charles E. Brown
Author - Fireworks MX From Zero to Hero (FriendsofED publications)
	   Beginning Dreamweaver MX (Wrox Publishing)
Contributor - The Macromedia Studio MX Bible (John Wiley & Sons)




Message #3 by "Rohit Arora" <rohit_arora@i...> on Thu, 23 Jan 2003 16:29:47 +0530
Either while creating project give ur ip like 111.111.111.111 instead of
localhost or In browser-->tools-->internet options-->Security tab-->select
local intranet option(click custom level) --goto last option LOGON and
select automatic logon on only intranet zone

hope it helps

regards
rohit

-----Original Message-----
From: Alex Smotritsky [mailto:alex.smotritsky@v...]
Sent: Thursday, January 23, 2003 4:02 PM
To: aspx_beginners
Subject: [aspx_beginners] RE: ALL READ - Server Problem Fix


I ran the stuff in that article and unfortunately, when I attempt to
start debugging I still get this error:

Error while trying to run project: Unable to start debugging on the web
server. You do not have permissions to debug the server. Verify that you
are a member of the 'Debugger Users' group on the server. Would you like
to disable future attempts to debug ASP.NET pages for this project?

I've made sure that everyone is a member of the Debugger Users Group and
that doesn't help.

Any body know what the deal is with this specific bug?

Thanks in advance.

Alex

-----Original Message-----
From: Charles E. Brown [mailto:chabrown@b...]
Sent: Wednesday, January 22, 2003 8:48 AM
To: aspx_beginners
Subject: [aspx_beginners] ALL READ - Server Problem Fix


Here is something that comes up periodically. I noticed several new
postings with this as a possible problem.

If you had an anti-virus program running at time of installation, the
.NET Framework may not install properly into the registry. This will
cause all sorts of things to breakdown, including debugging and running
aspx applications.

Microsoft has a fix posted at:

http://support.microsoft.com/?id=306005

I used it, as well as others, and it seems to fix the problems quickly.

Hope this helps,
Charles E. Brown
Author - Fireworks MX From Zero to Hero (FriendsofED publications)
	   Beginning Dreamweaver MX (Wrox Publishing)
Contributor - The Macromedia Studio MX Bible (John Wiley & Sons)







  Return to Index