DSXchange

I think if it was T30FILE related you would get a different message. This, as far as I know, is just a sign of an overloaded machine bumping up against a hard-coded limit in the engine. You might want to define what 'multiple' means and describe your server's hardware. See this thread for an example.

Have you tried to help yourself out? Searching the forum yields several posts with similar messages, perhaps one of them might solve your problem... this one perhaps.

They mispoke - version doesn't matter. If you think you have the SP2 problem, get the patch, it will fix you right up. If that doesn't help, post back and we'll dig deeper.

Or, as a way to check that you've got everything you need to support the jobs in the other Project, actually compile them there. The 'quick' way is to use the Multiple Job Compiler found in the Manager, it will run through and compile them all for you.

Well, then at this point something about your assumptions is incorrect or it would be working... and we've done all we can to point you in the right direction. Double-check everything about that parameter and how you are setting it. Have someone else check, it's amazing what another pair of eyes wil...

Doesn't matter what you 'expect' it to be, what is the exact value you are attempting to set it to when it fails? Write sumFile1 to your log file first so you know.

Have you looked up what an error code of 4 means? It equates to DSJE.BADVALUE and means "Parameter Value is not appropriate for that parameter type".

So... what type do you have the parameter defined as and what value are you trying to set it to?

Stupid stage. Can you tell I hardly ever use it?

What about the Informix stage, does it support that concept? Without that, I'm afraid the OP would be out of luck unless there is a different answer to the problem other than having to set the lock mode.

In the 'Before SQL' tab of the stage.

You aren't doing all of this to generate a surrogate key, are you?

And the square brackets that sorta make it look like it might be a function are just the substring operator.

Hash, or "hash sign" or "hash mark". I know... was just kidding. When I am trying to use NVarchar i get the following error: ' Stage does not support UNICODE character set' True, the OCI stage does not. The DRS stage probably throws the same error when set to Oracle but what about when you set it t...

What do you call it, Ray... Hash? Square? Sharp? Shibboleth?

Besides, why make it more complicated than it needs to be? What's wrong with scripting something to execute the sp and triggering that inside your Sequencer job via a Routine Activity?

I was going to say - that is the sample. You did click on the link, did you not?