This behavior isn't supported. What you can only do is to configure 2 listeners for the logging category you will use so that it will log using both trace listener regardless whether the previous trace listener fails.
By the way, there's a bug with the Event LogTrace Listener. If logging using that trace listener fails, succeeding trace listener won't get triggered to write to their destination sink so make sure to put this trace listener at the last.
Global Technologies and Solutions