Yes, I am saying that those events are in the System log on the failing server. Yes, event occurs every day around PM and events , , and are logged during reboots. The two servers in question are identical servers in different sites; Server R2 Standard, SP1, 64 bit, identical patches.
It doesn't make sense that one would work and not another. I suspect it is a configuration 'difference' but what? I have a workaround for this issue. Clear the System Event Log. There is some event that has occurred and has been logged to the System Event Log that causes an AppCrash event to occur. The failure only occurs when additional switches are used against a system that has some X event in the System Log. My guess is that the X event might be "The previous system shutdown at time on date was unexpected" is causing the issue where the additional events cannot be determined.
I don't believe that is what is cusing. I have teo systems with crash records. I just tested to see. The uptim utility reports as normal although it may not give an accurate number with crash records present. It is possible that teh event log can become corrupted. Clearing it will fix this in most cases.
Keep an eye on it. You may also have found an off case wher a mix of conditions does cause uptime to fail. There are numerous utilities claiming to give accurate uptime reports. I ssupect all have some fault or another. IMO, if the program finds any events, it should abort, because as soon as there are these events, it is impossible to determine the accurate up-time.
I think this makes the whole 'uptime' program academic, because surely you're really interested in the problem servers, the ones that do crash? Thanks for the input. I concur that the events will impact the ablility to calculate availabilty. Since we are looking to calculate uptime as close as possible your point is well taken. So, the workaround of clearing the logs on servers that fail to run the utility, puts the server back in a state where the calculation will be accurate.
Using uptime. Since we are fortunate enough to rarely have "abnormal shutdowns" we can get a good sampling from this tool. We do not need the historical details of reboots beyond that. Note: In our cases, many servers have events "abnormal shutdowns" yet the tool still successfully runs albeit the availability statistics may be skewed. We just needed a way to get the servers that were failing to to work again.
Clearing the System Log worked for us. Just clear the logs, reboot the server, and run uptime. Hopefully, this will help some others looking to get uptime working again regardless of how accurate it may be perceived. Office Office Exchange Server. Not an IT pro?
Script Center. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. The Official Scripting Guys Forum!
If your answer is "yes," you know what to do. Dive in and help somebody! If your answer is "no," welcome to our fun little world! We'd recommend that you first head over to the Script Center, get your feet wet, and then come back to either ask or answer questions. We can't be everywhere at once we know—shocking! This utility is perfect for quickly querying uptime on any Windows version. The major benefit of this tool is the convenience factor. If you find yourself using this many times per day you may want to consider this method.
After downloading the tool, extract uptime. Then open up a command prompt and simply type uptime. This script allows you to provide a computer name as a parameter. It will then parse the System event log of the computer and find both a start and stop event to compare the two. It will then return the total time the server was online until the event log has rolled.
Below is an example of using this script on a server. It will return the total uptime for all of the events the server has in the event log, including the current uptime. This script is a quick way to find the uptime of a single server across many days. But what if you need this information for lots of servers at once?
To do this, you can gather up a list of servers and then pass each computer name, one at a time, to this script. As an example, define all your servers in an array in the PowerShell console.
In reality, though, you might be pulling server names from Active Directory, Hyper-V, or a text file. Add a server name to the output like below using a calculated property. We now have an excellent little tool that can provide us a quick report on uptime for our servers over time!
Choose the best one for your own context. Get this interactive comic book to learn how Veeam and AWS can help you fight ransomware, data sprawl, rising cloud costs, unforeseen data loss and make you a hero! ATA is known for its high-quality written tutorials in the form of blog posts. Adam the Automator. Twitter Facebook LinkedIn. Table of Contents. Finding Windows uptime with task manager. Uptime tool.
0コメント