Error 13 Data Is Invalid
Contents |
navigationHome Exchange News Tutorials Solutions Videos & Podcasts Books Certificates Office 365 News Tutorials Solutions Videos & Podcasts PowerShell Exchange Office 365 Outlook Tutorials Solutions iis admin error 13 data invalid Videos & Podcasts Windows News Tutorials Solutions Videos & Podcasts More… windows process activation service error 13 the data is invalid Kemp Load Balancers Cisco HP Symantec VMware SuperTekBoy In The News Search SuperTekBoy...Windows Process Activation Service - telnet error 13 the data is invalid Error 13: The data is invalid February 16, 2015 By Gareth Gudger 11 Comments 11 Shares Share Tweet +1 Share RedditI ran into a strange error recently on an error 13 the data is invalid vpn Exchange 2013 server. The WWW Publishing Service was stopped. When I tried to start the service it failed on a dependency. A quick check revealed the Windows Process Activation Service (WAS) was stopped. When I tried to start WAS I received the following error. Windows could not start the Windows Process Activation Service service on Local Computer. Error
Error 13 Invalid Or Unsupported
13: The data is invalid. The Event Viewer was littered with equally cryptic Event IDs, such as WAS 5005 and WAS 5036. Not the first time I've actually encountered an error like this before. I am not sure what causes it. But evidently something in Internet Information Services (IIS) becomes corrupt. Thankfully this blog from GrinGod jogged my memory. It all came flooding back. The applicationHost.config file was messed up. For me the file was completely empty. Not a line of code to be found. Luckily IIS takes backups that can be found in C:\INETPUB\HISTORY. Under here you will see several folders with a prefix of CFGHISTORY. The folder with the highest revision number will be your latest backup. Copy this file and overwrite the existing file at C:\WINDOWS\SYSTEM32\INETSRV\CONFIG. Once the file has been replaced start the WAS service. If WAS starts successfully then you should be able to start the WWW Publishing Service. If that starts successfully, then you can restore all Exchange Web Services. Have you run into this prob
account only takes a few minutes. Join Now New Dell out of the box installed windows updates, and some of our core apps. Went to install another application it failed. I tried to look at the event log and
Error 13 Invalid Or Unsupported Executable Format Windows 7
could not open it. error event log service not running. Tried starting the service got an error 13 invalid or unsupported executable format redhat error cannot start event log service error 13 invalid data. I have tried removing all the event logs in case one is corrupt but error 13 invalid or unsupported executable format centos still cannot start the service. I need this thing done today. I have searched the internet and the only info I can find is remove the corrupt event log. Thanks Reply Subscribe View Best Answer RELATED TOPICS: The things you find https://supertekboy.com/2015/02/16/windows-process-activation-service-will-not-start-error-13-the-data-is-invalid/ in event log... Set Event Log Size using GPO Odd Out of Office and Mailtip problem...ASP.NET 2.0.50727.0 error in event log   4 Replies Datil OP Chad.w Feb 24, 2011 at 10:26 UTC Have you tried deleting the corrupt event log? **Note this is for Windows XP, if you see the same registry entry in your system it is probably the same but beware** 0 Chipotle OP Shep Feb 24, 2011 at 10:32 UTC https://community.spiceworks.com/topic/129708-windows-7-cannot-start-event-log-service-error-13-invalid-data I tried removing all the event logs because I cant start the service to figure out which one is corrupt. Still did not work. 0 Serrano OP Best Answer Gisli_Kerfisstjori Feb 24, 2011 at 11:28 UTC EJS / Skýrr is an IT service provider. Try to remove the previous installed app and reboot the machine, else try safe mode remove all the logs under %SystemRoot%\System32\Winevt\Logs and reboot. 0 Chipotle OP Shep Feb 24, 2011 at 1:14 UTC I removed all apps that had been installed, and rebooted. The event log service is now running. Now to determine which application caused the problem. I suspect that it is USB port security from script logic but we will see. Thanks for the help I will update when I find out what it was. 0 This discussion has been inactive for over a year. You may get a better answer to your question by starting a new discussion. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Join me to this group Reply × Users who spiced this post Read these next... How to setup networking for a home lab HOW-TO: Virtualization Here's a way to separate your VM lab network from
and hosted at their cloud provider. When running a query in Forefront TMG Logs and Reports view, I found the error below: Failed Connection Attempt Log type: Web Proxy (Forward) Status: http://www.fastvue.co/tmgreporter/blog/how-to-solve-13-the-data-is-invalid-error-in-forefront-tmg 13 The data is invalid. Rule: Source: Internal Destination: External Request: GET http:// Filter information: Req ID: 0fdbab91; Compression: client=No, server=Yes, compress rate=0% decompress rate=0% Protocol: http User: anonymous Cause This error occurs when the destination Web Server is using Chunked Encoding but it is not passing the correct TransferEnconding header. When researching about this problem I found a great post from my friend Yuri Diógenes that explains why this problem happens: According to RFC if a server is using chunked error 13 encoding it must set the Transfer-Encoding header to "chunked". In order to compress the content we need to accumulate all the chucks and then compress. When it works, TMG knows that all that content is part of the same HTTP request since it says in the HTTP Response Header; therefore it waits for the entire content, compress and send it back to the client. On the failing server we receive the first answer that doesn’t say data is invalid that the content is chucked and right after that we receive other chucks, since HTTP Compression is enabled it fails to reassemble all the content since it doesn’t know that they belong to the same content." - Yuri Diógenes at: http://blogs.technet.com/b/yuridiogenes/archive/2010/12/22/3292163.aspx Solution If possible, the best way to solve it is by asking the web site administrator to change the "TransferEncoding header" parameter on the web server to "chunked". See How to enable chunked transfer encoding with IIS. Workaround If you cannot wait for the website administrator to change this, you can workaround the problem by disabling HTTP Compression for the destination site. Disabling HTTP Compression altogether will cause higher bandwidth consumption and may cause other kinds of Internet access errors, so the better solution is to keep this service enabled and adding the destination IP as an exception: To add exclude a destination IP from HTTP Compression Open the Forefront TMG Management Console and go to Web Access Policy On the left hand side, click Configure HTTP Compression under Tasks. On the Request Compressed Data tab, click the Add button next to Exceptions To exclude a single IP, add a Computer for the destination IP address you want to exclude. Alternatively, you can create a new Address Range or Computer Set to exclude more than one IP addresses. I created a new Computer Set called ‘HTTP Compression