DSXchange

So, are you saying you upgraded your Server component but not the Client? They are a matched pair and there is very liitle wiggle room for them to be out of sync. If that's the case you need to install the new Client!

Sorry, got that backwards. You need to get out of your specific project and into the main UV account:


Then try again.

That does sound like an installation issue. I found this post, it may help in spite of it being in the Quality Stage forum: m Particularly, the mention of the 'distribution of the required files' and Installation Guide manual bits. Your best bet is still your official support provider, that's why yo...

And if you search the forums for that option, you'll see it comes with HUGE caveats, so make sure you understand exactly what it does before you enable it!

'LOGTO <YourProject>' first.

Ignoring the Server jobs, can you run other PX jobs? If so, what's different about this one PX job than all of the others, does it do something 'unique' or use a config file that none of the other jobs use?

Search the forums for 'The system cannot locate the resource specified', from what I recall that XML blurb indicates a permissions error.

[sigh]

No-one can help until you stop repeating the little bit you've been repeating and explain in detail the problem you are facing. What exactly do you mean by 'different metadata'? Can you provide examples of these differences?

The 'not connected' part is a result of the other errors. Suggest you run this by your Oracle DBA and see what they have to say about it.

Why would that be 'very urgent'? Please explain why you cannot compile your Sequence through Designer or why you think you need urgently to do this from the command line.

Can't really help directly, but two suggestions... 1. Search the forums for 'Licensing error' or 'could not find a license' to see if others have reported or solved this in the past. 2. Involve your official support provider if you haven't already. Question - does this only happen with one particula...

From what I recall, the parser reported it as "Illegal XML character: 0x3" and what we found was the control-C in a block of text. Removing it solved the problem, or at least shut up the parser.

Hmmm... search for the 81002 error turned up a few posts, inlcuding this one: m As for the 141 error, you'll need to search the forums for that one as well, however I don't believe any conclusive reason was found for it. You'll probably need to take that to your official support provider for resolut...

What about it? Is that why you are asking about nohup - you are getting timeout errors? The client can disconnect or timeout without effecting any of the background processes it started.

There's no need for that. The dsjob command with none of the wait options already spawns a nohup'd background task.