I am trying to email a PDF report, but it is simply sending a login page screen shot. Anyone know how to resolve this?
Easiest way is to use the admin account in the hidden advanced section of the schedule wizard. We tried using AD accounts or any other accounts and could only get it working with Admin. Might be different for others though. Test and see what you get using Admin.
This is not fixing it for me. Used the built-in Admin account as well as other domain-based and local accounts with full administrative rights. Tried the "current user" route while logged in as admin as well as manually inputting the admin password. All PDF's are still just login screens.
Embedded HTML displays fine and links work, too. Just a matter with PDF's. Guess it is time for a support case...
Try a restart of all services.
This one is a PITA indeed.
I should also note, these PDF's DID work prior to upgrading to NPM 12.1
Oh dear god.
Don't tell me this is a new 12.1 feature.
I have 400+ monthly PDF reports scheduled for 60 clients.
I've duplicated this issue with two different 12.1 or 6.4 updates so far.
I was having the same issue.
In my case, the IIS had binding 443, and the Websites table primary website record had port 443 and SSLEnabled column as 1, as expected after running the configuration wizard. However, the ReportJobs table used by reports schedules, was using an old Website ID from previous configuration wizard using port 80 and SSLEnabled 0 (zero). I created the port 80 binding manually and now is working.
The issue is! When you run configuration Wizard a new record is created in table Websites with a unique WebsiteID, but the reports schedules, defined in the ReportJobs table, keep looking at the OLD WebsiteID record picked when they were created instead of updating the records with the new WebsiteID. I opened case #1128094 and worked with aaguilar from SW. Long story short, he have a Feature request for this issue. I still think, and agree with @orioncrack that this is a bug, but from way back, not from version 12.
Your suggestion is for the entire NPM package the operate correctly, not just for this particular issue.
But definitely a good suggestion for general NPM knowledge for people new to Solar.