Skip to main content
B
blercher1-Visitor
1-Visitor
January 13, 2015
Solved

Deleting viewset on locked productive server

  • January 13, 2015
  • 2 replies
  • 2351 views

Hi all,

how can I delete viewsets on a integrity server, locked by a staging server?

I was unable to migrate viewsets from staging to productiv server, if there names was the same

So I tried to delelte the old viewset on the productiv server, but it was not allowed.

Thanks for your help,

many greetings

Bernd

    Best answer by blercher

    Hi,

    I solved the issue:

    I have to delete the published viewset on the staging server, then I migrate the delete action to the production.

    After this I create a new viewset on the staging, publish this on the staging, migrate this viewset to production.

    It works, maybe it'S not the right way....

    2 replies

    B
    blercher1-VisitorAuthor
    1-Visitor
    January 19, 2015

    Are there any ways to update a viewset on a locked productive server or to rename viewsets?

    K
    KaelLizak16-Pearl
    16-Pearl
    January 19, 2015

    Hello Bernd,

    What release of Integrity are you using?

    This doesn't sound like a problem that has come up recently. It might be best to contact PTC Integrity Support to help with this issue.

    Regards,

    Kael

    B
    blercher1-VisitorAuthor
    1-Visitor
    January 22, 2015

    we are running 10.5

    thanks for your answer

    J
    jgorsline1-Visitor
    1-Visitor
    February 3, 2015

    Bernd,

    If you are publishing a viewset from staging to production, you should not get an error that the viewset exists, it should update the viewset.

    Do you have viewsets on the production server that do not exist on the staging server?

    B
    blercher1-VisitorAuthorAnswer
    1-Visitor
    February 11, 2015

    Hi,

    I solved the issue:

    I have to delete the published viewset on the staging server, then I migrate the delete action to the production.

    After this I create a new viewset on the staging, publish this on the staging, migrate this viewset to production.

    It works, maybe it'S not the right way....

    Terms & ConditionsAccessibility statement