Taskkill – Kill All Process’s Of A Certain Name

So you may have run something thats spawned a whole bunch of processes,  iexplore.exe  or cscript.exe ,  you need to kill them all and fast.   Heres how

1

taskkill /F /IM iexplore.exe

Useful Windows Run Commands

A whole bunch of very useful Windows commands
Read more

Task Scheduler – The following error was reported: 2147944309.

This common task scheduler message is cryptic, and means nothing without some digging,  you can see below how we find the true answer to what it means,  but the short answer is:

Account Is Locked Out

Why?
0n2147944309 = 0x80070775
Facility: 8007 = Win32 (it’s a “Win32″ status code)
Status: 0x775 = 0n1909
Q:\>net helpmsg 1909
The referenced account is currently locked out and may not be logged on to.

T-SQL Setting Date Format

Occasionally you need to run a DATEDIFF or DATEADD against some dates that are in a reverse format, ie Day:Month:Year instead of Month:Day:Year, theres a simple way to set this in your query without having to string handle it all, using the SET DATEFORMAT parameter.

1
2

SET DATEFORMAT dmy
SELECT DATEDIFF(MINUTE,'29-01-2010 09:13:18','29-01-2010 09:18:18')

Windows Task Scheduler – Corrupt Image Error Fix

For some reason now with Vista and Windows Server 2008 when ever you seem to create a scheduled task, but close it before saving it, you get a “Corrupt Image” error that will not go away unless you remove the “Corrupt Image” from the registry.

Heres how to fix it

1. Open The Registry (Start > Run > regedit)
2. Browse to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache
3. Under the “Tree” folder, find the scheduled tasks that you are having the error with and delete their folder.

Thats it, now re-open task scheduler and the error should be gone.

Pinger! – The Mass Host Ping Tool

Current Version v1.3 – Download Now

Pinger! is a tiny ping utility (13KB) that is used to quickly ping a large list of hosts and save the resulting successful and failure host lists into a text file.

Why?

When developing scripts and applications that will touch a large number of hosts,  if many of those hosts are offline or no longer exist, the timeouts involved with this can slow down execution time and dramatically slow down your script or application.

In my case, I was presented with a list of 600+ servers that needed to have the exact same script run against them, a successful server took only several milliseconds to finish,  a failed host took around 4 seconds to time out, clearly I needed to find out which servers were alive and which weren’t and further again I needed to list the successful servers in a clean text file, 1 host per line, so I could import this into my application as an array.

And hence Pinger! was born

Usage

Very simple, Pinger.exe when run looks for hosts.txt in the same directory. Simply enter in your list of host names in this text file,  one per line and Pinger! will run over them 1 by 1 and output the results.
Simply extract the .zip containing Pinger.exe and hosts.txt to the same directory and open Pinger.exe.

Output

2 files are outputted.  these are:

• success.txt  – The list of successfully pinged hosts, in per line format
• failure.txt – The list of hosts that failed to ping, in line by line format.

Download v1.0

IIS7 and Classic ASP – Enabling Error Messages

Recently iv switched a lot of my web apps from an IIS6 to an IIS7 server although this came with a few headaches, one of which was that now, I was unable to debug my code from the browser on my remote machine, instead just seeing an “Error Code 500 – Internal Server Error” message,  which is basically useless.

Iv found the solution, although it involves a few steps,  heres how.

1. In your IIS7 control panel, under your site home area, double click on the “ASP” icon (In the bottom half, on my window).
   Expand the Debugging Properties toggle , and switch the Send Errors To Browser option to TRUE.
2. Open up a command line and run this command:
   %windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpErrors -errorMode:Detailed
   
3. If your using Internet Explorer, go into  Tools > Internet Options > Advanced , find the “Show friendly HTTP error messages” under the “Browsing” section and disable it.
4. Thats it!  Your done.

FireFox NTLM Authentication – Windows Authentication

Maybe its just me, but having to switch between Internet Explorer and Firefox to access Internal and External sites is a hassle.  Particularly the SharePoint based sites on Firefox.

So iv found a solution ..  If you want to use FireFox for all sites heres what I did to get it working.

In FireFox

Enable auto NTLM authentication for the internal sites that require domain accounts.

1. Open FireFox and type about:config hit enter
2. In the filter box type NTLM , find the key -  network.automatic-ntlm-auth.trusted-uris
3. Add a comma separated string of URLS here .. Example http://intranet,http://somelocalsite,http://sharepoint
4. Restart firefox

When you visit these sites now, you will be authentication in the same way you are with Internet Explorer without being prompted to login.  This is absorbed from your domain account.

Register ASP.NET Version In IIS

If your IIS Web Service Extensions list is not showing your correct version of ASP.NET, ie It may only show version 1.1.3822 where as your using version 2 in your application, click start > run and then enter this command , replacing the .NET Framework version with your desired version.

1

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -I

Windows 2008 Perfmon Crashes – Reset User Defined Data Collector Sets

I discovered this very annoying bug in Windows Server 2008 when attempting to import an XML file with 100 servers and counters in it.
No doubt one of the server had an issue and therefore and for some stupid reason, perfmon or Reliability And Performance Monitor, as its called now in 2008 is unable to handle this , and completely falls over.
Now, when you open Perfmon and try to view the User Defined Data Collector Sets, or run logman.exe from the command line, the application completely freezes and your unable to delete the corrupt dataset you just imported or even click elsewhere in the window.

In 2003, a reboot would fix this problem, but in 2008 it does not. The solution lies in the registry. Here’s how to fix the problem.

1. Make sure your logged in as admin or with admin rights
2. Close any open perfmon (Reliability and Performance Monitor) windows you have open.
3. Click Start > Run then type  regedit hit enter
4. Goto: HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Windows\PLA
5. You will see your Data Collector Sets in here, delete the one you created that caused the problem (or just delete them all if your not sure) **NOTE** Dont delete the “System” folder.
6. Your done now, re-open perfmon, or logman and your problem should be solved.