Parser Error compat.browser - Please help Intranet Site Down.
I just started getting this. Didn't do anything I know of. I have verified this file is there and works. Looked in side of it.
Wss 3.0 has been running great until 11:00am today, didn't change anything.Line 1, position 1 looks like this in the document
<browsers>
<browser id="Safari2" parentID="Safari1Plus">
<controlAdapters>
<adapter controlType="System.Web.UI.WebControls.Menu"
adapterType="" />What am I missing here? Please Help
Server Error in '/' Application.
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 id="Safari2" parentID="Safari1Plus"> Line 3: <controlAdapters>
Source File: /App_Browsers/compat.browser Line: 1
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210
[HttpParseException]: Data at the root level is invalid. Line 1, position 1.
at System.Web.Configuration.BrowserCapabilitiesCodeGenerator.ProcessBrowserFiles(Boolean useVirtualPath, String virtualDir)
at System.Web.Compilation.ApplicationBrowserCapabilitiesCodeGenerator.GenerateCode(AssemblyBuilder assemblyBuilder)
at System.Web.Compilation.ApplicationBrowserCapabilitiesBuildProvider.GenerateCode(AssemblyBuilder assemblyBuilder)
at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider)
[HttpParseException]: Data at the root level is invalid. Line 1, position 1.
at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider)
at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders()
at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
at System.Web.Compilation.BrowserCapabilitiesCompiler.GetBrowserCapabilitiesType()
at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
[HttpException]: Data at the root level is invalid. Line 1, position 1.
at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()
at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)
[HttpException]: Data at the root level is invalid. Line 1, position 1.
at System.Web.HttpRuntime.FirstRequestInit(HttpContext context)
at System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context)
at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)Also getting this
Event Type: Failure Audit
Event Source: Security
Event Category: Object Access
Event ID: 560
Date: 3/29/2007
Time: 1:00:03 PM
User: *****\wss3pooldemo
Computer: *****Description:
Object Open:
Object Server: SC Manager
Object Type: SERVICE OBJECT
Object Name: WinHttpAutoProxySvc
Handle ID: -
Operation ID: {0,19961704}
Process ID: 840
Image File Name: C:\WINDOWS\system32\services.exe
Primary User Name: BLYSERVER$
Primary Domain: *****
Primary Logon ID: (0x0,0x3E7)
Client User Name: wss3pooldemo
Client Domain: *****
Client Logon ID: (0x0,0x12E8C23)
Accesses: Query status of service
Start the service
Query information from service
Privileges: -
Restricted Sid Count: 0
Access Mask: 0x94
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.and this one
Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1310
Date: 3/29/2007
Time: 1:06:42 PM
User: N/A
Computer: *****
Description:
Event code: 3006
Event message: A parser error has occurred.
Event time: 3/29/2007 1:06:42 PM
Event time (UTC): 3/29/2007 7:06:42 PM
Event ID: 45e791819dd04c249a7e269ddc530641
Event sequence: 1
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1032202749/Root-7-128196688021727606
Trust level: WSS_Minimal
Application Virtual Path: /
Application Path: C:\Inetpub\wwwroot\wss\VirtualDirectories\80\
Machine name: *****
Process information:
Process ID: 3804
Process name: w3wp.exe
Account name: *****\dealer
Exception information:
Exception type: HttpException
Exception message: Data at the root level is invalid. Line 1, position 1.
Request information:
Request URL: http://*****/it/_vti_bin/lists.asmx
Request path: /it/_vti_bin/lists.asmx
User host address: 172.16.1.98
User:
Is authenticated: False
Authentication Type:
Thread account name: *****\dealer
Thread information:
Thread ID: 1
Thread account name: *****\dealer
Is impersonating: False
Stack trace: at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()
at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters)
Custom event details:For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 3/29/2007
Time: 1:00:02 PM
User: *****\wss3pooldemo
Computer: *****Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
to the user BLYTHEDESIGN\wss3pooldemo SID (S-1-5-21-4239727938-222710763-1804924817-1486). This security permission can be modified using the Component Services administrative tool.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
- CambiadoJohn SaundersMVPjueves, 07 de mayo de 2009 17:42It's a WSS question, not a general .ASMX question (From:ASMX Web Services and XML Serialization)
Respuestas
I would like to meet the person that made this part of the system work as it does. I fixed this error I would think many people might have this over time.
Idea of what could be the issues was only found here.
http://forums.asp.net/thread/1270047.aspx
In doing some editting on the intranet site which is WSS v3 I openned a file called web.config from the c:\inetpub\wwwroot\wss\virutaldirectories\80
ok so no big deal didn't edit the file or change anything. I openned the file with SharePoint Designer after I did this I remembered I needed to work in these files in Virtual web designer and not sharepoint designer ok my bad didn't save anything seems stupid but I didn't give it a thought.
Just openning the file seems to be enough to have the system create a sub folder called _vti_pvt or something like that. In trouble shoot this error I openned a few files and it created this folder and made a copy of each file I openned and put it in a sub folder with the same name I found 6 of these folders all new. I guess this file is not a true xml file and made the whole site crash for 2 hours.
I deleted these directories and everything worked right away.
The person that set this up should be shot. No really
Todas las respuestas
I would like to meet the person that made this part of the system work as it does. I fixed this error I would think many people might have this over time.
Idea of what could be the issues was only found here.
http://forums.asp.net/thread/1270047.aspx
In doing some editting on the intranet site which is WSS v3 I openned a file called web.config from the c:\inetpub\wwwroot\wss\virutaldirectories\80
ok so no big deal didn't edit the file or change anything. I openned the file with SharePoint Designer after I did this I remembered I needed to work in these files in Virtual web designer and not sharepoint designer ok my bad didn't save anything seems stupid but I didn't give it a thought.
Just openning the file seems to be enough to have the system create a sub folder called _vti_pvt or something like that. In trouble shoot this error I openned a few files and it created this folder and made a copy of each file I openned and put it in a sub folder with the same name I found 6 of these folders all new. I guess this file is not a true xml file and made the whole site crash for 2 hours.
I deleted these directories and everything worked right away.
The person that set this up should be shot. No really
- Strange behavior,
i just deleted the folder
_vti_cnf of /App_Browsers/ and everything backs
Thank You so much !!!!!
I think it's not a good idea to solve configuration problems like this by deleting files. Getting rid of *.browser files in any additional folders is a loss of ASP.NET sites multi-browser compatibility features. The right way - to analyse cause and to correct a mistake! The source of such a server error is the mismatch of application-level browser definition files (with .broswer file name extension) and ASP.NET predefined browser definitions. The ASP.NET predefined browser definition files are stored in %SystemRoot%\Microsoft.NET\Framework\<ASP.NET version>\CONFIG\Browsers (in case of Jbenisek - %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\CONFIG\Browsers\ ). Application-level definitions like SharePoint are placed in the application's App_Browsers directory. They use parentID attribute in a new browser definition to inherit settings, or use the refID attribute to add capabilities to an existing browser definition. When the inherition chain is broken - the *.browser parse error appears. To solve "Parser error" for .browser file we need to check the right structure %SystemRoot%\Microsoft.NET\Framework\<ASP.NET version>\CONFIG\Browsers\ predefined and maintained by the .NET Framework *.browser files. By default there are only *.browser files. Any additional files - the potential cause of problem. For example, there could be found some additional *.dll like ASP.BrowserCapsFactory.dll or additional scripts that malfunction and cause the error. Getting rid of such a files could solve problem without damaging of existing application-level configurations!
I agree however I verified this configuration with 5 other SharePoint v3 servers all setup the same way. I have many companies with the same configuration. These folders were not default and were not present in anyother install. After some testing I found that because I openned the file with SharePoint Designer and not Expressions it created the files which crashed sharepoint to a debut screen.
I backed up these folders then deleted just these added new folders and everything else came back.
Its funny but by deleting the folders (_vti_bin or something ) it worked for me. I can remember such things happening with Frontpage too. Anyways thanks for the info.- Thank you!!
Deleting this file in the \App_Browsers\ folder fixed our site as well!
I too tried opening our site with Sharepoint Designer (2007) and did NOT save changes, etc... I was pulling my hair out until I found this thread. I had that same \_vti_cnf folder duplicated in this directory, and deleting it brought us right back up.
Hey Microsoft, Sharepoint Designer shouldn't bring down our Sharepoint sites so easily! Thank You Guys!!
Deleting *.browser files from App_Browsers folder solves the problem.- Deleting the App_Browsers folder in my Sharepoint site fixed my problem as well. Although this folder resides in all 3 of my other Sharepoint sites and they are all running fine.
