Error 13 The Data Is Invalid Event Viewer
Contents |
360 games PC games error 13 the data is invalid vpn Windows games Windows phone games Entertainment All Entertainment
Windows Process Activation Service Error 13 The Data Is Invalid
Movies & TV Music Business & Education Business Students & educators
Error 13 The Data Is Invalid Windows Event Log
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Event Viewer Cannot Open The Event Log Access Is Denied (5)
Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All event viewer cannot open the event log or custom view. verify that event log service is running Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
navigationHome Exchange News Tutorials Solutions Videos & Podcasts Books Certificates Office 365 News Tutorials Solutions Videos & Podcasts PowerShell Exchange Office 365 Outlook Tutorials Solutions Videos & Podcasts Windows News Tutorials event viewer cannot open the event log not enough storage Solutions Videos & Podcasts More… Kemp Load Balancers Cisco HP Symantec VMware event viewer cannot open the event log the request is not supported 50 SuperTekBoy In The News Search SuperTekBoy...Windows Process Activation Service - Error 13: The data is invalid February 16, 2015 event viewer cannot open the event log or custom view windows 7 By Gareth Gudger 11 Comments 11 Shares Share Tweet +1 Share RedditI ran into a strange error recently on an Exchange 2013 server. The WWW Publishing Service was stopped. When I https://support.microsoft.com/en-us/kb/972999 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 13: The data is invalid. The Event Viewer was littered with equally cryptic Event IDs, such as WAS https://supertekboy.com/2015/02/16/windows-process-activation-service-will-not-start-error-13-the-data-is-invalid/ 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 problem? Maybe something similar? Do you know what causes this? Drop a comment below and let me know how you fixed it. Click for Print FriendlyLast updated by Gareth Gudger on October 23, 2015.11 S
Without the Cruft: Windows 10 LTSB (Long Term Servicing Branch), Explained Subscribe l l FOLLOW US TWITTER GOOGLE+ FACEBOOK GET UPDATES BY EMAIL Enter your email below to http://www.howtogeek.com/howto/windows-vista/fixing-event-viewer-cannot-open-the-event-log-when-viewing-system-logs/ get exclusive access to our best articles and tips before everybody else. RSS ALL ARTICLES FEATURES ONLY TRIVIA Search How-To Geek Fixing "Event Viewer cannot open the event log" When Viewing System Logs As any geek knows, one of the first things that you do when troubleshooting a Windows problem is look into Event Viewer's Application or System logs, which typically are rich with information on what event viewer the problem is. But what if the event log itself is corrupted? I came across this exact situation the other day, where I was getting the error "Event Viewer cannot open the event log or custom view. Verify that Event Log service is running. The data is invalid (13)"… but the error only happened when trying to open the System log, while the Application log was working just fine, event viewer cannot and restarting Event Log or rebooting didn't help. What you can do in this situation is clear the system log, saving it to a file in the process. This will usually "reset" the log so that future events will be viewable. Clearing the System Log Here's an example of the error message that I've been getting: You can right-click on any of the logs and choose "Clear Log" from the menu. You'll want to choose "Save and Clear" when prompted just in case you need to access those events. Give the logfile a useful name, and then click the Save button to continue. Note that you probably won't be able to open the log with Event Viewer, but you could open it in a text editor and try and find some information in it. Now that I've cleared the log, you can see that I'm able to view the events in the System log again.
Extra Note: The problem I was encountering ended up being because I had 9 USB devices plugged into a machine with a very pathetic power supply. Moving the devices onto a Powered USB hub fixed the problem, and I've since upgraded the power supply. JOIN THE