Solved

Keeping App_Browsers/_vti_cnf deleted

Posted on 2009-05-14
5
767 Views
Last Modified: 2012-05-07
We have all probably seen the ruthless message below:
-------------------------------------------------
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Data at the root level is invalid. Line 1, position 1.

Source Error:


Line 1:  <browsers>
Line 2:    <browser refID="safari1plus">
Line 3:  
-------------------------------------------------

Which simply means that the frontpage server extensions has once again added the _vti_cnf folder in the App_Browsers folder of your application on the server.  Deletng this folder clears out the error.  My qestion is, short of running a script ever 60 seconds, is there a clean way of keeping this folder gone or perhaps fixing .net so that it doesn't complain that the folder exists?

Thanks!
0
Comment
Question by:jglazer63
  • 2
  • 2
5 Comments
 
LVL 9

Expert Comment

by:sevensnake77
ID: 24384907

You just need to deploy your ASPX Pages, the BIN directory, web.config and other static files like XML, JPG etc.,
So, you can avoid them getting into the deployment server.

Also you need to remove the front page extension using IIS, This way it will not happen again.
0
 

Author Comment

by:jglazer63
ID: 24385660
Remove FP extensions?  I thought that was the best way to work with IIS an Visual Studio (ie, open Remote web server).  Am I wrong?
0
 
LVL 9

Expert Comment

by:sevensnake77
ID: 24387709
No you are correct, This is the best way to use a remote server.  but if you keep having that problem you should remove the extension on the production server
0
 

Accepted Solution

by:
jglazer63 earned 0 total points
ID: 24396812
Well if it comes to removing fp extensions and loosing that ease of use over writing a stupid script that just deletes that folder, i'll write the script.  I just hate that this has been an issue for so long and nobody has come up with a solution.
0
 

Expert Comment

by:JGarlandX
ID: 28921480
I ran across this today and it took me a while to figure out a solution. I want to keep FP extensions on my sites so here is what I did.

1. Create a blank text file named "_vti_cnf"

2. Delete the _vti_cnf folder

3. Upload the "_vti_cnf" text file.

FrontPage will not be able to create a new _vti_cnf folder because a file of that same name will already exist

0

Featured Post

U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Just a quick little trick I learned recently.  Now that I'm using jQuery with abandon in my asp.net applications, I have grown tired of the following syntax:      (CODE) I suppose it just offends my sense of decency to put inline VBScript on a…
This article discusses the ASP.NET AJAX ModalPopupExtender control. In this article we will show how to use the ModalPopupExtender control, how to display/show/call the ASP.NET AJAX ModalPopupExtender control from javascript, how to show/display/cal…
This Micro Tutorial demonstrates using Microsoft Excel pivot tables, how to reverse engineer competitors' marketing strategies through backlinks.
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question