Skip to main content

Event Viewer: how to send notification E-Mail messages with Powershell

Since its introduction in the first Windows NT Server, the Event Viewer has always been an essential tool for any System Administrator as the primary source to detect, locate and review a vast majority of issues related to Windows programs, services, frameworks, and even third-party installed software in order to improve the performances and the overall stability of any virtual or physical machine.

It’s almost sad that, despite all these years, this tool is still affected – at least in my humble opinion – by at least two major issues:

  • the constant slowness, due to the fact that all logs are basically stored in log files which are then parsed in real-time by the application itself resulting in a severe performance impact.
  • the unconfortable location, nested inside the Control Panel > Administrative Tools since it’s meant to be used by admins only.

These two issues are often the reason why the Event Viewer is still not always used by many users & admins who tend to forget about its existence, leaving errors and warnings that could easily be solved as they pile up.

This post shows a way to avoid this undesirable behavior by setting up a simple e-mail notification system of all the system event as soon as they’re made available to the Event Viewer. The system will also allow the user to choose the event log file (Application, Security, Setup & more) and/or the event type (Information, Error & more) and/or the event ID: let’s see how to achieve such result.

Read More

FileZilla: ENETUNREACH – Network unreachable – how to fix

A couple days ago I had to solve a strange issue regarding one of our machines seemingly unable to connect to a public FTP server: the PC in question was trying to connect using FileZilla, the well-known open-source FTP Client by FileZila Project available here.  The given error was the following:

ENETUNREACH – Network unreachable

Since the FTP server was perfectly reachable by other machines – also using FileZilla themselves as well – I started to look closer on the client. To cut it short, it turned out that the problem was related to the Kaspersky Antivirus TCP filter, which incorrectly behave with a FileZilla estabilished connection breaking it out.

Read More

Visual Studio 2013 and 2015: Unable to start debugging on the web server. Could not start ASP.NET debugging – How to fix that

If you’ve stumbled upon this post you most likely experienced the following error message when you tried to run your web application in debug mode:

Unable to start debugging on the web server. Could not start ASP.NET debugging. More information may be available by starting the project without debugging.


If you’ve recently upgraded your system to Windows 10 I strongly suggest to jump down to the URL Rewrite Module Broken paragraph and follow the advices below: otherwise, keep reading.

Despite what the error message says, starting the project without debugging won’t give you more informations. Luckily enough, the issue is fairly known to ASP.NET developers thanks to many threads on IT resources websites such as StackOverflow. The cause has almost always something to do with the Application Pool used by your web application – usually the DefaultAppPool, unless you’ve chosen otherwise – which stopped working for no apparent reason.

Read More

MySQL – Convert all Tables of one or more Database(s) from MyISAM to InnoDB and vice-versa

Have you ever needed to convert one, some or all the tables of a MySQL Database from MyISAM to InnoDB or the other way around?

Here’s a couple queries you can use to achieve such results. As you will notice, they won’t execute the commands – they will basically create a list of the actual queries you’ll need to perform to actually execute the change, so you can review it just before it goes live. To execute the queries, just cut-paste the resulting row and execute them (each row is a single working query).

To convert all DBNAME’s InnoDB Tables to MyISAM

To convert all DBNAME’s MyISAM Tables to InnoDB

To convert all InnoDB Tables to MyISAM (all databases)

To convert all MyISAM Tables to InnoDB (all databases)


Once again, these commands will build a list of queries you will have to execute to actually perform the conversion: to actually perform the change you’ll have to execute them.

That’s all for now: happy conversion!

SQL Server – Retrieve Product Key from an existing installation

Sometimes you’ll need to retrieve your SQL Server Product Key from an existing installation on your Client or Server machine: the most common scenario takes place when you have an old Server to move or relocate and no one around you seem to remember where the license are… or if you’ve simply lost the Service Key post-it.

Luckily enough, you can easily get this information back thanks to this neat PowerShell script made by Jacob Bindslet:

Read More