Images in notification not displaying
I have a problem with my notfications.
Images are not displayed and are all replaced in the message by:
<p style="margin: 0px"><img src="cid:Image_1" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"></p>
I don't have any proxy configured on Archer Control Panel.
I have tried:
- configure images in header, footer and body onf the message
- Using images on Archer instance or external images
Always the same result.
Could you check for any errors in the Archer logs during the notification sending?
Yes, I have for example this message in one of the errors:
<ExceptionType>System.Net.WebException, System, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
<Message>The remote server returned an error: (401) Unauthorized.</Message>
<StackTrace> at System.Net.HttpWebRequest.GetResponse()
at ArcherTech.Notifications.ExtensionMethods.EmailMessageExtensionMethods.GetImage(SessionContext sessionContext, KeyValuePair`2 imageName, Notification notification)</StackTrace>
Ok, now I have enabled anonymous authentication and I am in the cas described in your first link....
But I don't have external images, all are on the Archer server. Adding the server IP address to the host file had no efect...
I don't see any service account on my Windows server.
How can I check which service RSA uses ?
IIS has been reset and nothing changed.
You can check under Windows > Services and see who is running your JobEngine. It is either service account or SYSTEM. Depending on what you defined during installation. Also, you need to check identity running your AppPool.
Job engine is run by system.
My Archer Applications are mapped to the default AppPool, which is configured as integrated.
when I look at my w3wp process I see that DefaultAppPool is running the process and SYSTEM has Read & Execute rights.
I don't know if there is more to check...
It is recommended to have separate AppPool Identity assigned for Archer, not default, and use either System or Service Account credentials for it. If that would not help, time to call to Support for debugging.