Iis Error 13
Contents |
Powered by Microsoft® Translator Wikis - Page Details First published by arnavsharma (MVP, Microsoft Community Contributor, Microsoft Partner) When: 9 Jan 2014 1:52 AM Last revision by arnavsharma error 13 the data is invalid vpn (MVP, Microsoft Community Contributor, Microsoft Partner) When: 9 Jan 2014 1:55
Windows Process Activation Service Error 13 The Data Is Invalid
AM Revisions: 2 Comments: 1 Options Subscribe to Article (RSS) Share this Engage! Wiki Ninjas Blog (Announcements) error 13 the data is invalid windows event log Wiki Ninjas on Twitter TechNet Wiki Discussion Forum Can You Improve This Article? Positively! Click Sign In to add the tip, solution, correction or comment that will help other error 13 the data is invalid windows defender users.Report inappropriate content using these instructions. Wiki > TechNet Articles > Service Won’t start: Error 13: The data is invalid. Service Won’t start: Error 13: The data is invalid. Article History Service Won’t start: Error 13: The data is invalid. On Windows 7 machines, sometimes a window service behaves unexpectedly and does not starts giving an error:
Error Code 13 The Data Is Invalid Group Policy
“Error 13: The data is invalid” Firstly use the process monitoring tool to see any Access denied errors, on files folders and registry keys. Most of the cases arise due to some file/keys/folder restrictions that can be captured using the tool. Here is the resolution for few services : For IIS: Error in the event logs : The Windows Process Activation Service encountered an error trying to read configuration data from file ‘\\?\C:\Windows\system32\inetsrv\config\applicationHost.config’, line number ’0′. The error message is: ‘Configuration file is not well-formed XML’. The data field contains the error number. When any changes are made on web applications in IIS it creates a backup of the applicationHost.config file in c:\inetpub\history. Just copy the file from the history and put it into c:\windows\system32\inetsrv\config. Event Log service: On using process monitoring tool, you will see Access denied error on registry keys. Giving full permission and cleaning this folder %SystemRoot%\System32\Winevt\Logs will solve the issue. WMI service: Rebuilding the WMI repository will solve the issue http://blogs.technet.com/b/askperf/archive/2009
contained within it may be out of date, not reflect my current views and/or contain broken links. If you feel this article is still valid and requires updating, you can use the contact form to let me know. However, I make no guarantee that it will get updated.
This morning I ran into a problem when running a repair on my broken SharePoint installation. Everything seemed to be going well until the setup needed to restart the World Wide Web Publishing service (IIS). The error message was rather cryptic, say that it might be due to my login account not having service start http://social.technet.microsoft.com/wiki/contents/articles/22358.service-wont-start-error-13-the-data-is-invalid.aspx permissions – but I know I have. Debugging step 1: Look in the windows services list and see if I can manually start the service. This was a little more helpful as it told me it couldn’t start due to a dependency not starting. Debugging step 2: Check the service dependencies. It appears that the Windows Process Activation service (WAS) wouldn’t start, although it only returned the message “Error 13: The http://www.gringod.com/2008/08/15/when-iis-wont-start-error-13/ data is invalid?. Debugging Step 3: Check the system event log. Here I found the most helpful message so far: The Windows Process Activation Service encountered an error trying to read configuration data from file ‘\\?\C:\Windows\system32\inetsrv\config\applicationHost.config', line number '0′. The error message is: ‘Configuration file is not well-formed XML'. The data field contains the error number. It seems that at some point the applicationHost.config got trashed. Luckily, when you make changes to web applications in IIS it creates a backup of the applicationHost.config file in c:\inetpub\history. All you need to do is copy a good copy from the history and put it into c:\windows\system32\inetsrv\config. And Roberts your mothers brother, WAS starts, IIS starts and the repair of SharePoint can continue! ps. I’m running IIS7 on Windows 2008 Server. Related PostsHTTP Proxy Per Git RepositoryThe Quick Way To Trash SharePointBeating CRM2011 Anti-XSS with a Web Resource ShimVisendoSMTPExtender Management Web ServiceSharePoint Link List – Part 2SharePoint Link List – Part 1 Related Tags: applicationHost.config, Error 13, history, IIS, sharepoint, WAS, windows 38 responses so far Logging In... Leave a Reply Cancel reply 38 Replies 34 Comments 0 Tweets 0 Facebook 4 Pingbacks Last reply was 6 months ago Jessica View 8 September 2008 Thanks for the post, I had exactly thechecked out if there is something reported to Event Viewer and I found the following error message – Error 12: The data is invalid. It turned out that during shutdown http://weblogs.asp.net/gunnarpeipman/iis-won-t-start-error-13-the-data-is-invalid of my virtual machine IIS config file was ruined. Solution to my problem was very simple. IIS configuration is in file c:\windows\system32\inetsrv\applicationHost.config. In my case this file was same by size as before but it was filled with null bytes. When changes are made to this file then previous version is backed up to c:\inetpub\history\ directory. I copied last working configuration file from history directory to inetsrv directory error 13 and started www service. Luckily, everything works again. If you need more specific description about this error then GrinGod blog has very good posting to read: When IIS Wont Start – Error 13. 2 Comments The beset way is to re-install your IIS. Shannon. - Wednesday, November 4, 2009 2:55:48 AM i got this from an online soucreYes, Pure ASP Upload supports uploading large files on the Windows 13 the data 2003 server. However:IIS6.0 prevent the upload of files more than +200Kb. So you need to make some changes in the default IIS settings first.BackgroundFor IIS6.0 users, the AspMaxRequestEntityAllowed property specifies the maximum number of bytes allowed in the entity body of an ASP request. If a Content-Length header is present and specifies an amount of data greater than the value of AspMaxRequestEntityAllowed, IIS returns a 403 error response.This property is related in function to MaxRequestEntityAllowed, but is specific to ASP request. Whereas you might set the MaxRequestEntityAllowed property to 1 MB at the general World Wide Web Publishing Service (WWW Service) level, you may choose to set AspMaxRequestEntityAllowed to a lower value, if you know that your specific ASP applications handle a smaller amount of data.SolutionOpen your metabase.XML which is located in c:\Windows\System32\Inetsrv find the line AspMaxRequestEntityAllowed and change it to 1073741824 . This is 1GB of course you can enter another value to suite your needs.NOTE: Before you edit the file, be sure to stop the IIS service first or else you won't be able to save the file. Karl - Saturday, May 12, 2012 2:40:22 AM Comments have been disabled for this content. Terms Of Use - Powered by Orchard