DSXchange

What's different about the data in the 'other scenarios' when it fails compared to when it succeeds? What is going on in-and-around line 139 in the code that it points to in the message? Do you know where to find JOB.82185807.DT.1407164135.TRANS3 for job number 319? You should...

one more concern is is there any wrong with the dsr_sched.sh file in the respective projects and what is the file permission for that Shouldn't have to worry about anything like that that I've ever seen. i tried according to u And my unix administrator have not given the Direct Log in option for th...

Or perhaps purposely not waiting because of the (removed) multi-instance capabilities... as long as all the InvocationIDs were unique.

That all goes out the window with MI disabled.

Specifically, you can't check for status until it has completed. Well, you can but you won't get what you are thinking you are getting. DsErrCode = DSSetParam(JobHandle1, ParamName, ParamValue) ErrCode = DSRunJob(JobHandle1, DSJ.RUNNORMAL) ErrCode = DSWaitForJob(JobHandle1) R...

Ummm... where's the 'Wait for the job to complete' part?

I diasabled the mutli instance option long back. Only for the first value of the csv file, the job is running successfully. But for 2nd onwards, it is showing the following warning in the main job: <jobname>..Transformer_0 (DSRunJob): Job control error (-2) (DSRunJob) Job <sequencejob> is not in a ...

Oh well.

Just a guess, but try setting the Isolation Level on the Transaction Handling tab to Read Uncommited and see if that helps.

That assumes that the two client versions were installed to two completely separate locations on your PC. If your old client was upgraded to the new version (the default), then this is not an option.

Unless you reinstall the old client. To a different location, of course.

Well, as it says - you passed 3 arguments to the DSLogFatal routine and it only wants 2.

thirupri wrote:It gives me a error.

Any particular error? Or are you keeping that a secret?

Do you have an eCase number to go with this, something other than just the name of the dll? That's typically how these things are tracked and/or requested - by eCase number.

It's right on the Home page under the topic of Charter Membership... or you can click here.

You haven't said what database this is... guessing SQL Server. And you've also not said if you have ever used this particular ODBC connection before or not. Googling up 'SQLSTATE=S1C00' returns all kinds of information, did you give that shot? Common theme seems to indicate you've set a bad option i...