Synchronization group error during project deployment

[Former Member]

Hi,

When I'm trying to deploy the project I'm working on I get an error like this:

Verify failed for deployment with mode Can not add entity ... to Synchronization group [Dynamic]

See attachment for full error.

Anybody have and idea.

Thanks

[Jitendra_Kansal]

Is this issue resolved?

[midhun_vp]

Do you have multiple sync groups?

Is this is the first time project is deploying to the server?

Which is the backend ?

Try these steps,

* Refresh the MBO's and operations if any. If it didn't happen, give default input values and refresh.

* Delete the existing queries if any.

* uncheck and check primary keys if any.

* Deploy the project.

- Midhun VP

[Former Member]

Hi Midhun

I tried the steps, but none of them worked.

Regards,

Adam

[midhun_vp]

What is the error you are getting in the sever?

To which DB you are using for MBOs?

Is this is the first time you are deploying a project to the server?

- Midhun VP

[Jitendra_Kansal]

sounds weird, but can you restart sup server and then try?

[Former Member]

I get this error on the server: “com.sybase.sup.admin.common.ServerException”

The MBO's are being deployed using a SAP server.

It was not the first time I was deploying the project, but I disabled and deleted the existing package on the server, so actually it's like I'm deploying it for the first time, right?

Regards

Adam

[Jitendra_Kansal]

It was not the first time I was deploying the project, but I disabled and deleted the existing package on the server, so actually it's like I'm deploying it for the first time, right?

yes, right.

[Jitendra_Kansal]

Hi,

Please make sure sup and backend server is up and running.

uncheck primary keys and check

remove unwanted obj queries.

restart workspace

Rgrds,

Jitendra

[Former Member]

Hi,

When I uncheck the PK's, I get errors that the objects must have a PK.

Regards,

Adam

[Jitendra_Kansal]

Its not mandatory to have PRIMARY KEY in a mbo but 8t is recommended to have one.

That could be a warning not should be an error.

Uncheck and check primary key and then try with deployment

Rgrds,

Jitendra

[Former Member]

Unfortunately it gives an error, it doesn't even give me the option to finish the deployment because of these errors.

Regards

Adam