Transactional Message template

Forum|Forum|1 year ago
March 12, 2024
3 replies
1976 views

Hi team,

I'm facing this issue while I publish this template. Kindly provide some ideas to get this resolved.

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

LakshmiPravallika

Community Advisor

Hi @vijaymvj ,

Could you also provide us the error logs screenshot by going to Home--> Monitoring-->Processes List --> web@default--> Open the log Journal and select todays date and give us the logs.

Sample log screen as shown below:

Regards,

Pravallika.

V

VijayMvjAuthor

Level 2

Hi @lakshmipravallika , thanks for your response!

Here is the log journal :

LakshmiPravallika

Community Advisor

Hi @vijaymvj ,

From the error Logs ,it looks like the connection for "mc" user is not valid.

To check the external account used in your Template, Please go to the Delivery Template Properties-> Routing and check the External Account being used there.

Below is the sample External account for Execution Instance.

Could you Please check the "Message Center execution instance " External account under "/Administration/Platform/External Accounts/" and "Test the connection" for "mc" Account used there.

This issue will occur for all the other Transactional Templates also if used the same Routing.

The fix for this would be to reset the mc Account password if the connection is not successful.

Regards,

Pravallika.

AkshayAnand

Community Advisor

Hi @vijaymvj

Based on the error message you provided, the issue is related to the LogonToRemoteInstance method of the nms:extAccount service. This method is responsible for logging into an external account, which is used by the workflow to connect to a third-party system or external application.

Here are a few steps you can try to resolve the issue:

Make sure that the username and password used to log in to the external account are correct. Also, check if the account is still active and not locked out.
Verify that the endpoint URL used to connect to the external account is correct and reachable. You can try accessing the URL directly from a browser or using a tool like Postman to make sure that the connection is working.
Review the server logs to see if there are any errors related to the nms:extAccount service or the LogonToRemoteInstance method. This may help you identify the root cause of the issue.
Check the message center workflow configuration: Ensure that the Message Center workflow is configured correctly with the correct External Account ID and other relevant details.

If the above steps do not resolve the issue, you may need to contact Adobe Support.

You can also take reference to the solved thread regarding a similar issue.

Thanks

Akshay