Open a command window and try running the command directly from there. That will allow you to see the window and error messages as they occur. Another option is to use -o outputfile option. That will allow you to capture the output of the command into the file that you define after the -o. That's an "oh", not a zero.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning