cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Simon_S
Engaged Sweeper

The images in mails sent from the helpdesk are not showing, they show an error "The linked image cannot be displayed. The file may have been moved, renamed, or deleted. Verify that the link points to the correct file and location"

I have checked and in the ticket view on the site, the images are showing. We are using IIS Express on the same server as the scanning service / mailing service. Rights on the folder seem to be correct. (checked via this link: https://community.lansweeper.com/t5/troubleshooting-your/file-and-image-upload-errors-and-sla-calcul...)

 This started last friday. Anyone else have this issue?

5 REPLIES 5
andejo55
Engaged Sweeper II

Having the same issue as well after upgrading to v 10.4.1.0.

Obi_1_Cinobi
Lansweeper Tech Support
Lansweeper Tech Support

Hello there!

If you haven't done so already, please log a support case with Lansweeper support so we can gather more information on the root cause: https://www.lansweeper.com/contact-support/

Obi_1_Cinobi
Lansweeper Tech Support
Lansweeper Tech Support

Hello there!

Multiple users are starting to report this, so please log a support case with Lansweeper support so we can gather more information on the root cause: https://www.lansweeper.com/contact-support/

Simon_S
Engaged Sweeper

for us it was also after the update to 10.4.1.0, we have restarted the services, and have rebooted the server, but to no avail. What we do see however, is that in "old" tickets, the images can be loaded in the mail, and the default signature in mails sent out for new ticket creations is being displayed. Only new images in new tickets are not shown. Really strange..

Chris394
Engaged Sweeper

We are experiencing the same issue. This just started occurring for us after updating from Lansweeper version 10.2.5.1 to 10.4.1.0. We however are not using IIS Express but IIS. I have verified our settings are correct with the link you provided. We have restarted the services as mentioned in another post but that didn't resolve the issue. We haven't performed a reboot on the server but will do a reboot on the server later this afternoon.