| Author |
Topic |
|
chris_cs
Posting Yak Master
223 Posts |
Posted - 2007-04-24 : 04:35:48
|
| Hey guys,I'm trying to run a job that will convert a load of data but it keeps failing at the first step. If I run the scripts in each step on their own then they run fine. The error message I get is 'The process did not produce any output. Process exit code 1. The step failed'. I think this may be some kind of security problem but I cannot see where. The command I'm using for the first step is as follows:OSQL -SCRLONSQL01 -DINPRO -Usysadm -Pcarpmaels -i"C:\Program Files\CPA Inpro Database\Scripts\dropinteg.sql" -o"C:\conversion\output\dropinteg.txt" -nAny pointers would be most helpful. |
|
|
bpgupta
Yak Posting Veteran
75 Posts |
Posted - 2007-04-24 : 04:49:58
|
| what is the out of your jobs when u run from the query analyser.I think you are not creating the jobs in proper way1) Execute Stored proc2) in advance tab mention the out put filefinish |
 |
|
|
chris_cs
Posting Yak Master
223 Posts |
Posted - 2007-04-24 : 05:22:48
|
| I've just noticed that in the output file of the job the following is produced:[ODBC Driver Manager] Data source name not found and no default driverspecifiedI'm assuming this has something to do with the error but not sure what. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-24 : 09:45:09
|
| Is the script on sql server's c:\ drive? |
 |
|
|
chris_cs
Posting Yak Master
223 Posts |
Posted - 2007-04-24 : 11:25:05
|
| It is yeah. Within SQL we use the following CmdExec to execute the script file:OSQL -SCRLONSQL01 -DINPRO -U###### -P###### -i"C:\Program Files\CPA Inpro Database\Scripts\dropinteg.sql" -o"C:\conversion\output\dropinteg.txt" -nWithin the ouput file for the first step of the job I get the following error:[ODBC Driver Manager] Data source name not found and no default driverspecifiedAll ODBC entries are set up on the server correctly so I'm not sure what the issue is. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-24 : 12:42:15
|
| You don't need odbc in this case, tried this?OSQL -S CRLONSQL01 -D INPRO -U ###### -P ###### -i"C:\Program Files\CPA Inpro Database\Scripts\dropinteg.sql" -o"C:\conversion\output\dropinteg.txt" -n |
 |
|
|
chris_cs
Posting Yak Master
223 Posts |
Posted - 2007-04-25 : 06:48:09
|
| Still unable to run the job. Same error. |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-25 : 10:13:44
|
| What's your sql version? What's mdac version on the server? |
 |
|
|
chris_cs
Posting Yak Master
223 Posts |
Posted - 2007-04-25 : 10:59:45
|
| We're running SQL Server 2005 and we have the latest version of MDAC (2.8). |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-04-25 : 16:27:58
|
| Tested on my sql2k5 sp2 machine, works ok. Seems mdac issue to me, possible to install mdac again on the server? |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-04-25 : 16:42:41
|
| Since this is SQL Server 2005, use sqlcmd.exe instead of osql.exe.isql.exe was for SQL Server 7.0 and earlier.osql.exe was for SQL Server 2000.sqlcmd.exe is for SQL Server 2005.Perhaps it won't error if you use sqlcmd.Tara Kizerhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
chris_cs
Posting Yak Master
223 Posts |
Posted - 2007-04-26 : 05:43:55
|
Thanks tkizer that was the problem. Using sqlcmd.exe works perfectly! Thanks for everybody's input. I've certainly learnt a few things! |
 |
|
|
|