Solution patch disabled to be edited after creation.

[Former Member]

Hi experts.

We have a problem with a solution , this is what we did:

* Create a solution

* Create BAC element ( we did not deployed the BAC element before assamble & download )

* assemble & download

* create a patch

but the patch is not available to be edited and correct the mistakes.

we can't check out the solution

Exception of type 'SAP.Copernicus.Core.Protocol.ProtocolException' was thrown.

[Former Member · Accepted solution]

The status seems to be In Deployment, however that has failed according to the implementation manager. Restart your SDK first as SAP.Copernicus is basically the add-on to Visual Studio.

In the implementation manager please can you click on Version History Tab, then click on the failed version and show that screenshot. However this will probably require a ticket opened for SAP to fix it if you can't edit anything.

Regards,

Will

[Former Member · Accepted solution]

Hil Will, this is the version history.

thanks

[Former Member · Accepted solution]

Can you click Activation (After Patch Creation Log) and then the bottom list/table should be filled, please find where the error is and post that screenshot please.

Sometimes you can fix these errors, but most likely an incident with SAP will need to be opened referencing AP-RC-ANA-DT

Regards,

Will

[Former Member · Accepted solution]

this is the detail of the error.

thanks!!

[Former Member · Accepted solution]

Can you ensure that the Business Analytics work centre is assigned to your user please.

Then please try and activate it again.

Regards,

Will

[Former Member · Accepted solution]

Hey Will!

thanks a lot , the issue was solved by adding the work center ( products )  because this solution is an embedded component to a product list.

now we can edit the patch , assemble  & download.

[sunil1101]

Hi

As per status, you patch has been created but after patch activation got stuck.

It seems something went wrong, which you can see in log, click on 'See log file' link which may give the details what went wrong.

I don't think now you can do anything to fix it so you should raise an incident to SAP.

Regards

Sunil