# Missing Output Message from MSSQL Execute SQL Command

**URL:** https://www.finalbuilder.com/forums/t/missing-output-message-from-mssql-execute-sql-command/2661
**Category:** Bugs
**Created:** [August 16, 2006, 11:41am UTC](https://www.finalbuilder.com/forums/t/missing-output-message-from-mssql-execute-sql-command/2661 "2006-08-16T11:41:28Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![deleted\_user](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/deleted_user/32/937_2.png) [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [August 16, 2006, 11:41am UTC](https://www.finalbuilder.com/forums/t/missing-output-message-from-mssql-execute-sql-command/2661/1 "2006-08-16T11:41:28Z")

</div>

When a SQL script runs successfully in MSSQL Execute SQL   
the ouptut is dispalyed as 1\> 2\> 1\> 2\> 1\> 2\> 3\> 4\>. and the message is not displayed in the logs.  
  
If the script fails the message in the log is displayed as   
1\> 2\> 1\> 2\> 1\> 2\> 3\> 4\>   
Msg 3701, Level 11, State 5, Server Name Line 3  
Cannot drop the procedure ‘dbo.\_Test’, because it does not exist in the system catalog.  
1\> 2\> 3\> 4\> 5\> 6\> 7\> 8\> 9\> 10\> 11\> 12\> 13\> 14\>

---

<div class="post-metadata">

### Author: ![tate](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/t/e19b73/32.png) [@tate](https://www.finalbuilder.com/forums/u/tate)
#### Post date: [August 17, 2006, 9:50am UTC](https://www.finalbuilder.com/forums/t/missing-output-message-from-mssql-execute-sql-command/2661/2 "2006-08-17T09:50:42Z")

</div>

Hi Jody,  
  
Thanks for reporting this.  
  
Are you using ISQL or OSQL? It might be worth swapping to see if it makes any difference.  
  
FinalBuilder doesn’t actually do anything differently if the SQL script fails or succeeds, so I suspect the problem is caused by the ISQL (or OSQL) not flushing their stdout buffer. (and unfortunately if this is the problem, then there’s nothing we can do about it).  
  
You could also try using the ADO Execute SQL action, as this doesn’t rely on isql or osql and so won’t have this type of problem.  
  
hth.  
.t8