Skip to main content
Solved

Mailing reports with Smtp


Forum|alt.badge.img+3

Hi There,

We have used the report mailer (TSFReportMailer) for mailing the report to users with smtp. In windows it is working well but unfortunately when we deploy it on our IIS webserver the follewing error shows

 


Does anyone have experience with this?

The next step is to deploy to a azure enviroment! 

Reguards

 

Ronald

Best answer by Bart Metselaar

Hello Ronald,

Besides the important note from my colleague Erik;

(I also replied this on your bug report); I notice in your screenshot that your report seems to be searched on a ‘C:\’ folder. Can you make sure that, instead of using ‘C:\’, you use the complete FQDN path? 

If you request the web GUI to give back a report, it is likely that the web server searches for a different meaning for the alias ‘C:\’ than the windows server, which can be the reason that you run into different results on the windows and web server.

The alteration of the report location in the SF to a full FQDN location was the solution for my comparable situation a couple of months ago. I hope this helps you too.

Kind regards,

Bart

View original
This topic has been closed for comments

Erik Brink
Moderator
Forum|alt.badge.img+5

Hi Ronald,

What type of reports do you use? Notice that we do not support Crystal Report reports on Azure.

Is "Invoice” the name of the report file, maybe?

Regards,

Erik


Bart Metselaar
Moderator
Forum|alt.badge.img+3

Hello Ronald,

Besides the important note from my colleague Erik;

(I also replied this on your bug report); I notice in your screenshot that your report seems to be searched on a ‘C:\’ folder. Can you make sure that, instead of using ‘C:\’, you use the complete FQDN path? 

If you request the web GUI to give back a report, it is likely that the web server searches for a different meaning for the alias ‘C:\’ than the windows server, which can be the reason that you run into different results on the windows and web server.

The alteration of the report location in the SF to a full FQDN location was the solution for my comparable situation a couple of months ago. I hope this helps you too.

Kind regards,

Bart


Forum|alt.badge.img+3
  • Apprentice
  • June 23, 2020

Hi Bart,

 

Thanks for the answer. 

 

However we already solved the problem. There was a rights issue in Azure. Now we use the right directory and everything works good

 

Kind regards,

 

Ronald

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings