Custom Application on different server than ReportServer

We are using forms authentication for our custom application. The site
connects to ReportServer and runs reports. This all works fine IF the
ReportServer is on the same webserver. If ReportServer exists on a
different web server, then we consistently get a logon ticket
authentication error.
I can confirm that the sqlAuthCookie is getting down to the browser
level, but it does not seem to get back to the server. It appears that
the ReportServer ignores the cookie and creates a new one.
Has anyone gotten this architecture to work? Both machines are on the
same network, firewalls turned off, and can see each other fine.Just in your web.config file where your asp.net code's are there, use state
server instead of InProc. This will enable to store the session and pass on
the same session variable (ie login id ) to the remote. I think the login Id
is not getting passed
to the remote server, that is why the error. Just try and let me know
whether it works.
Amarnath
"google@.landy.net" wrote:
> We are using forms authentication for our custom application. The site
> connects to ReportServer and runs reports. This all works fine IF the
> ReportServer is on the same webserver. If ReportServer exists on a
> different web server, then we consistently get a logon ticket
> authentication error.
> I can confirm that the sqlAuthCookie is getting down to the browser
> level, but it does not seem to get back to the server. It appears that
> the ReportServer ignores the cookie and creates a new one.
> Has anyone gotten this architecture to work? Both machines are on the
> same network, firewalls turned off, and can see each other fine.
>