Expand my Community achievements bar.

We are excited to introduce our latest innovation to enhance the Adobe Campaign user experience — the Adobe Campaign v8 Web User Interface!
SOLVED

Campaign to Salesforce connector issue

Avatar

Level 1

Hello all,

I'm running the CRM connector in Campaign 6.1 in an attempt to get Campaign to connect to a Salesforce sandbox.

All of the table identification runs correctly and the process looks like it completes, but when I hit the close button on the modal window I get the following error message. (attached image)

and the account is not in the 'External account' window.

Has anyone seen this error before? If so how did you get around it?

1 Accepted Solution

Avatar

Correct answer by
Level 10

Hi,

Can you check with your administrator that the external account exists and you have the rights to view it?

Can you also check if there are other Salesforce external accounts created on the instance?

Finally, can you tell us what are your server and console build versions? You can check this from Help > About in Adobe Campaign. Unwanted problems can sometimes occur when the server build version is too old or when the server and console version numbers are too far away from each other.

Let me know,

Florent.

View solution in original post

3 Replies

Avatar

Correct answer by
Level 10

Hi,

Can you check with your administrator that the external account exists and you have the rights to view it?

Can you also check if there are other Salesforce external accounts created on the instance?

Finally, can you tell us what are your server and console build versions? You can check this from Help > About in Adobe Campaign. Unwanted problems can sometimes occur when the server build version is too old or when the server and console version numbers are too far away from each other.

Let me know,

Florent.

Avatar

Level 10

Hi,

Do you have any update on your issue? Were you able to resolve it?

Please let me know,

Florent.

Avatar

Level 1

Yes, issue was resolved, removed the account altogether and re did it as a new connection. Worked ok then.