Export to PDF

Are you using HTTP or HTTPS for access to your Orion server?

HTTP

I have found that Load Balancing causes havoc when using this feature.  if you are using LBs, try to hit the server directly.

We are not using Load Balancing, all connections are direct

ok, I had a ticket opened for this.  the following worked for me:

let me know if the following steps help, if not i would need a copy of
the diagnostics and screenshot on how you configure the send as pdf in a
doc file and export to us, so we can send for discussion:
Orion NPM will use NPM Server’s local Browser to do that,
By Default Windows Server 2003 shipped with security locked down by
default.
 < http://msdn.microsoft.com/en-us/library/ms537180%28VS.85%29.aspx
<http://msdn.microsoft.com/en-us/library/ms537180%28VS.85%29.aspx> >
http://msdn.microsoft.com/en-us/library/ms537180(VS.85).aspx
<http://msdn.microsoft.com/en-us/library/ms537180(VS.85).aspx>
 
Steps to perform:
1. Log into Orion Web Site, Goto Admin Tab and Clear the Cache.
2. Clear Internet Explorer temporary internet files.
3. Be sure that ActiveX is enabled.
4. Add the ORION to the "Trusted Sites" in Internet Explorer Security
settings.
5. You may also need to edit some of Security Settings & Privacy Tabs in
IE.
          In the IE, go to: Tools > Internet Options > Privacy; and
under the 'Advanced' button
choose: 'Override automatic cookie handling', and flag 'Always allow
session cookies'.

He also had me run the permissions checker.  (FYI I'm running 2008, so locations may be different)

can you also let us know
what happens when you run the orion permission checker at
program files -> solarwinds -> orion -> OrionPermissionChecker.exe
if there is errors, please fix it. and retry the report

Im also running Orion on 2008,

There is no OrionPermissionChecker.exe found on the server

the Orion website is already in trusted

If you look on the SolarWinds server under drive:/Program Files/SolarWinds/Orion I believe it is called permissionchecker.exe

ok other then AnonymousUser read access to a reg key and write access to the temp asp.net folder everything is fine

Seem to have solved the problem, we need both Windows authentication and forms authentication enabled at the same time, the only problem now is we have to log in with windows creds twice to access the web console.