MSSQLDataWriter bcp utility

Hello,

I’m having troubles inserting data from one database into another.
http://doc.cloveretl.com/documentation/UserGuide/index.jsp?topic=/com.cloveretl.gui.docs/docs/mssqldatawriter.html
The first parameter is ‘Path to bcp utility’. The value I enter is ‘C:/Program Files/Microsoft SQL Server/110/Tools/Binn/bcp.exe’.
When I run the program this error is shown :

11:53:23,083 INFO [WatchDog_18] Pre-execute initialization of connection:
11:53:23,083 INFO [WatchDog_18] DBConnection driver[org.jetel.connection.jdbc.driver.JdbcDriverImpl@58b625c4]:jndi[null]:url------ … OK
11:53:23,083 INFO [WatchDog_18] Pre-execute initialization of connection:
11:53:23,083 INFO [WatchDog_18] DBConnection driver[org.jetel.connection.jdbc.driver.JdbcDriverImpl@58b625c4]:jndi[null]:url------ … OK
11:53:23,101 INFO [WatchDog_18] Starting up all nodes in phase [0]
11:53:23,102 INFO [WatchDog_18] Successfully started all nodes in phase!
11:53:23,625 ERROR [WatchDog_18] Component [MSSQLDataWriter:MSSQLDATA_WRITER] finished with status ERROR. (In0: 635 recs)
bcp utility has failed.
11:53:23,625 ERROR [WatchDog_18] Error details:
org.jetel.exception.JetelRuntimeException: Component [MSSQLDataWriter:MSSQLDATA_WRITER] finished with status ERROR. (In0: 635 recs)
at org.jetel.graph.Node.createNodeException(Node.java:582)
at org.jetel.graph.Node.run(Node.java:558)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: org.jetel.exception.JetelException: bcp utility has failed.
at org.jetel.component.MsSqlDataWriter.execute(MsSqlDataWriter.java:633)
at org.jetel.graph.Node.run(Node.java:520)
… 3 more

Why does the bcp fail?
Thanks in adavance,
Vince

Hi Vince,

The error message unfortunately does not tell us anything about the reason why bcp utility failed. It just means that the bcp utility returned an error code to CloverETL. If you want to find the real cause, try to use bcp parameters errFile and outputFile and find more information there.

I hope this helps.