How do I allow the Report Scheduler the ability to log into Solarwinds?
Currently using a local orion account for the scheduler.
I'm experiencing the same issue, despite using known-good credentials. I've tried a local account and a Windows AD account and neither work.
I'm having the same problem after changing the Run As account for the job. I'm specifying an Orion user under the Orion Web Login tab, but even recreating the job from scratch produces the same problem.
All,
I've marked this for the PM to review. Hang tight.
Thanks!
DH
I am having the same issue. Version 2012.1.0
In looking further into this issue there appears to be a couple of things going on. First, the web service is only bound to the IPv4 address of the server but the resolver puts a higher priority on the IPv6 address when using a URL with a name. So I substituted the IPv4 address in the URL to force it to connect to the web service bound to the IPv4 address. This got the packets to the right place but I still got the "enable cookies" error. Using the FQDN name in the URL didn't work so I reverted to using the short name in the URL (which is where I started) and it worked. I have no idea why it didn't work initially but did work later. This should probably be triaged as a bug.
I have tech support case 352224 open for this too.
After looking at this with Support, it turned out I had to login to the Orion console from the Orion server using the RUN AS account the job was set to and this fixed the problem for me.
I know this is an old post, but did you receive any resolution on this? I am trying to create a report which would still run even when I am no longer supporting this software. No matter what I try, I still receive the cookies error and the PDF just shows the SW login screen.
No sorry, I've still not figured it out.
We're currently using windows accounts for authentication and I was having the same problem. I was attempting to login to the web page with the "domain\username" format and this was causing the above problem. When I switched the login credentials on the report scheduler to use the "username@domain" format, it worked. I'm also using the same credentials for both the web page login and the scheduled task. I'm guessing this is due to how the scheduler passes the credentials on via the URL.
Any other suggestions on this? None of the above fixed this for me. The strange thing is that it worked for a few days, then stopped.
Hopefully this will work for you as it did for me:
SolarWinds Knowledge Base :: Error in PDF Report: Your Browser Rejects Cookies
Wish it worked for me. Still tinkering with settings trying to find a fix. The hyperlink that the reports sends in the email takes me to the page/report. Still getting an unusable PDF. It's the standard login screen where you place local account or ad credentials. Below the login windows there is the caption "Enable cookies to login" in red text.
When I visit the webpage using the software the server resides on, the server loads report just fine. Its just some disconnect between opening the communication before the PDF does a "screenshot" of the file/webpage.
Image of the error is attached.
So far SolarWinds support hasn't been able to help me locate the issue
I tried a lot of solutions from this thread. Nothing worked.
Does anyone have a better solution?
On the host server do the following.
Go to:
Administrative Tools
Internet Information Services (IIS) Manager
Expand <Server Name>
Expand Sites
Choose SolarWinds <site info>
Go to Authentication
Double Click
Test with Anonymous Authentication Disabled
Determine if this is a state you can leave the IIS configuration in with your company.
Hi Stansellc,
Unfortunately, that did not solve the problem. All the reports I mentioned above, I still had saved. So I made the change, restarted IIS of course, and reports still failed.
I must say, I am very disappointed with SolarWinds.
There is a good community here between users and SolarWinds support. Are you creating an Orion account to do the reports? Or are you using AD credentials?
Is the issue the same when you tell it to save to a location on the hard drive of the server? Or is the issue related to e-mail? Perhaps you need to get a relay IP address from your exchange team to allow the e-mail traffic?
