Veeam needs better error handling procedures. Two dialog box examples illustrate this issue:
1 Title: VBK Extract
Text: Unexpected error in Extract.exe
Ok, there is an error, any log file one should check? Any related KB article on the Veeam website?
2 Title: Veeam Backup and Replication
Text: Object reference not set to an instance of an object
Hum, is this circular reasoning? I should have paid more attention in philosophical logic lectures.
Error messages should always have a lookup number, where one could be pointed to a related KB article.
-
- Service Provider
- Posts: 44
- Liked: 8 times
- Joined: Dec 05, 2017 6:56 pm
- Full Name: François Picard
- Location: Montréal, Qc, Canada
- Contact:
-
- Veeam Software
- Posts: 3626
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Better error handling procedures
Hello Francois! Thank you for the idea about possible improvements of error messages! It's always useful to have clear and precise error messages. However, both of mentioned messages can appear due to many different causes and workarounds/solutions might be different as well and it would be challenging to describe all possible causes and solutions in a single KB. Usually, such errors need to be investigated by our support team. Thanks!
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Better error handling procedures
Especially #2 this one can happen literally for millions of reasons due to something missing.
Who is online
Users browsing this forum: bytewiseits, Google [Bot], Majestic-12 [Bot], Semrush [Bot] and 87 guests