Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Configuration - Server Application Error

Status
Not open for further replies.

Fletch12

IS-IT--Management
Aug 13, 2002
140
US
I am no longer able to build asp web applications from my PC. When I do so I receive a Server Error in '/' Application. However, a colleague of mine is able to build pages fine, and we run off the same web server. I am pretty sure I checked all pieces of the local web.config file, but are there other local files that I can check. Thanks,

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS
 
Hi,

Have you recently migrated your application and forgotten to recreate your virtual directory as an application in IIS? Take a look at your application logs in Event Viewer and see if it has logged any error messages there. And have you applied a IE security patch lately? Our dev machines started displaying this message after we applied a security patch for IE.

HTH,
Keith
 
Are you referring to my local machine event logs or the web server. I check both and did not see anything that I thought would be connected to this problem.
 
I have applied IE security fixes recently to my PC. Do you know which fixes these were by chance?
 
If there were any error messages, they would reside in your application log on the server. As I did not apply the fixes myself, I do not know the exact name of the fix. I will have to ask the system admin. I'll paste the batch file that solved our problems. Let me know if it works for you. Take the code and copy it into a file (fixasp.cmd) and double click the file to run it. Disregard the comments saying that this fix is not required for ASP.net v1.1. We had the error on our 2K Servers with version 1.1 of the .NET framework.

Code:
REM This batch file addresses issues that exist with MS03-32 with
REM V1.0 of ASP.NET on Windows XP only
REM If you have any other configuration, you should not need to run this
@echo off 

REM if exist %SystemRoot%\microsoft.net\framework\v1.1.4322\mscorlib.dll goto v11_installed

REM "Changing to the Framework install directory"
cd /d %SystemRoot%\microsoft.net\framework\v1.1.4322 

echo "Stopping IIS"
iisreset /stop 
echo "----------------------"

echo "Stopping the ASP.NET state service if it is running"
net stop aspnet_state
echo "----------------------"

echo "Deleting the ASPNET account"
net user ASPNET /delete 
echo "----------------------"

echo "Creating a new ASPNET account with a temporary password"
net user ASPNET 1pass@word /add 
echo "----------------------"

echo "Launching runas to create a profile"
echo "You will see a command window being created"
echo "type 1pass@word when prompted for the temporary password" 
runas /profile /user:ASPNET cmd.exe 
echo "----------------------"

echo "Re-registering ASP.NET and the ASPNET account"
aspnet_regiis -i 
echo "A new random password has been autocreated for the ASPNET account"
echo "----------------------"

echo "Restarting IIS"
iisreset /start 
echo "----------------------"

echo "The workaround has been applied"
echo "Please try accessing an ASP.NET page"
echo "If you have any custom access controls settings for the ASPNET account,"
echo "you will need to recreate them"
echo "If you were running the ASP.NET state service, you'll need to restart it"
goto done

:v11_installed
echo "Version 1.1 appears to be installed, you should not need to run this file"

:done


Let me know if this fixes your problems or not.

HTH,
Keith
 
We are running v1.0.3705 of .NET Framework on our Web Server, not v1.1.
 
Doesn't it seem odd though that I can no longer build asp apps but another developer at our site can. To me, that means it is something to do with my PC?
 
If I were, I'd upgrade to v1.1. It might fix the problem after you reinstall. v1.1 also fixes a lot of bugs that v1.0 had. Are you compiling on your machine or another server?

Keith
 
I am compiling on my machine. I think I will upgrade to version 1.1 on both my machine and the web server now.
 
I hate to state the obvious here, but did you check to make sure that the virtual directory is configured as an application as the error message stated?

That's the only thing I've ever personally seen that will throw this particular exception...

The fact that your colleague is running apps on the same box proves it's not a Framework issue.

That button is on the general tab of the properties dialogue on the virtual directory. Button towards the bottom that says "Create" next to the "application name" text box.

-p

penny.gif
penny.gif

The answer to getting answered -- faq855-2992
 
Yes, I have checked this and what's strange is that before when I was able to create asp web apps I would have to go into IIS on the web server and create these, but now once I build a new asp app, these are already created. But they do not work. However, when my colleague creates a asp app her sites are not created, yet they seem to work.
 
I think I got it. I have had IIS installed on my local machine for a while and always just had it disabled. I guess through updates to Windows and IE however, it affected this somehow. So I removed IIS, and now I can once again compile asp pages from my machine. Thanks for the help.


[afro2]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top