nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Open Deploy Error : DEPLOYMENT_NOT_QUEUED

janaki

Hi.!

I'm getting following error while deploying into database.

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment ddcfg_uds_mhr.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
***ERROR - Starting deployment.
Reason from server: DEPLOYMENT_NOT_QUEUED
Details : Deployment ddcfg_uds_mhr is already running. Request to start it now cannot be done. Rejecting request.

I used "iwodcmd" for deployement. This command works absolutely fine on one server but fails on another server giving the above error.

Kindly suggest me..

Thanks in advance..

Find more posts tagged with

Comments

Migrateduser

Hi,

You seem to be running the same deployment multiple times simultaneously.
Can you please post you deployment command as it seems that you are not using the instance number for concurrent deployment.

Flat File DataSource.png

Flat File Details on iServer.png

RPTDESIGN Details on iServer.png

MukeshYadav

Please check if any other instance is running for that particular deployment. If any instance is not active and you are getting the same error, please share the command for invoking the deployment.

Thanks,
Mukesh

Adam Stoller

Hi.!

I'm getting following error while deploying into database.

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment ddcfg_uds_mhr.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
***ERROR - Starting deployment.
Reason from server: DEPLOYMENT_NOT_QUEUED
Details : Deployment ddcfg_uds_mhr is already running. Request to start it now cannot be done. Rejecting request.

I used "iwodcmd" for deployement. This command works absolutely fine on one server but fails on another server giving the above error.

Kindly suggest me..

Thanks in advance..

Rohan_t1

Janaki,

Are you still facing this issue?

Rohan_t1

Hello,

We have our OD base and reciever versions as Base Server: 6.0.2 and
Receiver Server: 5.6.0. Which paramters should be useful for us? I guess pendsession wont work as our odbase is of higer version
Would it be necessary to include the parameter in rcvr.xml as well? Or only changing the base should be enough.

Any help is highly appreciated.

Thanks

Adam Stoller

Hello,

We have our OD base and reciever versions as Base Server: 6.0.2 and
Receiver Server: 5.6.0. Which paramters should be useful for us? I guess pendsession wont work as our odbase is of higer version
Would it be necessary to include the parameter in rcvr.xml as well? Or only changing the base should be enough.

Any help is highly appreciated.

Thanks

What you should probably do is upgrade both your base and receivers to 6.2.0 - at the very least, upgrade your receivers to 6.0.2. The longer you stay out of sync, and "behind the times" - the harder it will be for you to get support (both official from Interwoven, and unofficial from these forums).

Rohan_t1

Thanks Ghoti,
Yes we are in planning stage for the upgradation of our receiver server. But at this moment we needed this to figure out within the current setup.
Please let me know if you have any info. on this.

Adam Stoller

Thanks Ghoti,
Yes we are in planning stage for the upgradation of our receiver server. But at this moment we needed this to figure out within the current setup.
Please let me know if you have any info. on this.

pendSessions is an available setting for the 6.0.2 Base Server - so that should work okay - however, depending on what you're trying to do - you might be able to accomplish "success" by using a '-inst instance-string' flag on your invocation of the deployment.

Rohan_t1

Yes you are right. To resolve this we tried implementing -inst instance-$TaskID flag on invocation of the deployment.Each deployment job is now recognised by its unique task id appended to it. And this has worked!!! Our next focus would be on upgrading the base and rcvr versions to the latest.

Thanks for all the help.

retesh

Yes you are right. To resolve this we tried implementing -inst instance-$TaskID flag on invocation of the deployment.Each deployment job is now recognised by its unique task id appended to it. And this has worked!!! Our next focus would be on upgrading the base and rcvr versions to the latest.

Thanks for all the help.

Hi,

I am also facing concurrent deployment issue:
I understand the resolution thru instance variable. This is very much achievable thru perl scripts.

QUERY: Now my question is that how have u appended inst in java based OD task in wf modeler. I tried adding inst in OD task variable but it didn't worked.

Can u please tell how did u mention inst?

Thanks,
Retesh,
TS 6.7.1 SP2
WFM 1.0.0.1
OD 6.1 SP1