eSearch widget and printing problems

[MattPohl]

I am having an issue with printing after doing a search with the eSearch widget. Here is the situation. I do all my development on a hosted server directly in the wwwroot folder. when I hit this over the internet all searches and printing after searches work great. Once I am done with development, I move my applications inside a ASP.NET application (on the same hosted server) so that I can control users/roles and logins being that I have several clients needing their own level of security. Once I move the project into the ASP.NET app I can perform searches without problems, but can not print once a search is completed. I get the following error:

Error executing print task:

[RPC Fault faultString="Error performing execute operation" faultCode="500" faultDetail=""]

I don't make a single change to the configuration of the project when I move it into the ASP.NET app. Being that it works wonderfully when its just inside the wwwroot folder, I figure it would work when moving it into the ASP app.

I am currently using Viewer 3.0 with the latest eSearch version (3.0.17). Any thoughts on this one would be greatly appreciated. Or if anyone else is using a FelxViewer project inside an ASP.NET app and could test this to see what happens, it to would be appreciated.

Thanks,

Matt

[RobertScheitlin__GISP]

Matt,

  I just wanted to respond as the developer that I have not tested this with embeding the viewer in an ASP.net app so I make no claims that it should or will function in this capacity. Your use case is not in the norms of this widgets use and I have no idea what might be the issue with printing.

[RhettZufelt]

Have you tried it with a different browser?  One of the microsoft updates a while back killed all my print tasks from the old webADF format using .net and IE.

Still print fine out of firefox and chrome, maybe try one of them and see if it is the issue.

ESRI support still working on a "fix".

Just a thought,

R_

[MattPohl]

Robert,

As always, thanks for a quick response. I am lost on even where to start looking for a problem area on this one. Like I said the viewer is residing inside an ASP.NET app and no changes are made to the project other then the addition of an index.aspx into the viewer project (attached for example).

rzufelt,

Thanks for the suggestion. I had already tried different browsers, but ended up with the same results. Do you have any of your viewers inside an ASP.NET application?

Matt

[RhettZufelt]

Matt,

No, I don't.  Sorry I can't be of more help, just wanted to make sure it wasn't the browser issue, one could chase that forever.

R_