Campaign Classic v7: can't find the default recipient schema | Community
Skip to main content
H
hansangy1377908
Level 2
July 20, 2018
Solved

Campaign Classic v7: can't find the default recipient schema

  • July 20, 2018
  • 3 replies
  • 2904 views

We just migrated from v6.1 to v7 and now I'm getting an error when trying to update/preview any custom schemas, which says campaign cannot find the factory recipient schema definition.

Has anyone come across this situation? We have literally not changed anything else but attempting to preview gives this:

So the schema preview looks like this

This worked fine before:

The same happens with an extension to the recipient table - I tried deleting it and recreating the same one, but still get the same 'schema not found'

Anyone have ideas?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by vraghav

    Hi hansangy13779089,

    We saw that you have reached out to support team for assistance on this.

    To help the broader audience, the issue has been resolved now.

    Problem was that someone (not clear who) had deleted the recipient schema on your instance.

    We had to contact our hosting team to rung postupgrade -force and get the schema restored.

    The issue should be resolved now for you. Please check.

    Regards,
    Vipul

    3 replies

    vraghav
    Adobe Employee
    vraghavAdobe Employee
    Adobe Employee
    July 20, 2018

    Can you show us the recipient schema? Seems the schema has been deleted or corrupted.

    vraghav
    Adobe Employee
    vraghavAdobe EmployeeAccepted solution
    Adobe Employee
    July 20, 2018

    Hi hansangy13779089,

    We saw that you have reached out to support team for assistance on this.

    To help the broader audience, the issue has been resolved now.

    Problem was that someone (not clear who) had deleted the recipient schema on your instance.

    We had to contact our hosting team to rung postupgrade -force and get the schema restored.

    The issue should be resolved now for you. Please check.

    Regards,
    Vipul

      H
      hansangy1377908Author
      Level 2
      July 20, 2018

      Hi Vipul,

      Yes it seems that the recipient table was corrupted/deleted somehow during the upgrade, restoring it did the trick.

      Thanks team

        Terms & ConditionsAccessibility statement

        Loading footer...