Is there a more elegant way to catch a generic exception than using try-catch block?
@HristoYank is correct, you shouldn't catch exceptions that you can't handle. What you are doing is basically just ignoring the error, which will make it difficult to trace bugs.

If I call a method called ParseNumberOutOfString, I will expect to get a number back. If the function can't return a number, I need to know that, so that I can react appropriately. 

Depending on the situation, I may want to use a default value, ask the user for new input, or abort with an appropriate error message. 

If the function just swallows the error and logs it somewhere, I will continue processing with invalid data (null in this case), which will result in all sorts of bugs down the line. As only a generic error message and no stracktrace is logged, debugging will also be rather difficult.

Misc


match doesn't actually throw an exception, so you will never get into the catch.
don't uppercase your variable names.