Folks i have been dumped into the frying pan. Put in hours and hours of work and research over it already but still can't seem to figure out what the heck is going on. Can an expert listen to my troubles and perhaps share some hints. Thank you so much for reading. Enviroments Windows 2003 SP2 x64 SQL 2005 SP2, Reporting service IIS6 no SSL/Cert with .NET SP1 Both ReportServer and ReportManager was working prior to an unfortunenate event, installing Exchange 2008. Immediately after the installation of Exchange 2008 we experienced 2 problems 1. SSL certs was now required, which we resolved by unchecking the SSL required option in IIS6 2. After SSL, execution not found occured in ReportManager Immediately after we discovered the Execution error, we went over logs after logs to see whats going on. Nothing worked We have, uninstalled Exchange, Uninstalled Reporting service, Reinstalled reporting service, updated report viewer to sp1, increased the timeout limit to 5 minutes, checked and rechecked our login/password on sql asp w3k reporting and till now still no go. <-- Error messeage --> This error msg in reporting service i believe is the reason why we are getting Execution not found. w3wp!session!1!01/23/2008-11:14:02:: i INFO: LoadSnapshot: Item with session: g4bqhtq0pvzpxh55leja4445, reportPath: /Report Bank/Deposit by Account, userName: NT AUTHORITY\NETWORK SERVICE not found in the database and w3wp!library!1!01/23/2008-11:14:02:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: Execution 'g4bqhtq0pvzpxh55leja4445' cannot be found, ;Info: Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: Execution 'g4bqhtq0pvzpxh55leja4445' cannot be found <-- Error messeage --> After reading tons of info, In our case our reports are simple reports, i can generate the report without problem from ReportServer in less than 10 seconds, just without the bells and whisles. But the second i hop on Report manager it will fight me till death with Execution. I think in our case, Its throwning a Username not found in database which might be preventing the creation of session key or the error is causing the render not to happen. If render dosen't happen then no key can be assigned to it? We have tried to use impersonate via the web.config and also changing Windows account logins etc but none of them work. One thing that is consistent is that the userName: NT AUTHORITY\NETWORK SERVICE not found has NEVER changed even if we impersonate or manually hardcode the username. Can anyone please help us out here!! Thank you.

Hi, We had a similiar problem and I tried some suggestions in this link: https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2551406&SiteID=1 We also installed the SQL2005 Cumulative Update 5 which we had to request from Microsoft. http://support.microsoft.com/kb/943656 After trying the suggestions above, installing the service pack and rebooting the server it seemed to solve the problem. I hope this helps!

THank you Picachone, but however that did not resolve the issue. I am still at square one with all SP and fix installed. Odd.

Hi Jim, we are having the same issue here. Have you ever found out on to solve it? Thanks, Jonathan

Jonathan we did eventualy resolve the issue. It took a long time but we did get it resolved.We compeltely uninstalled all SQL reporting instanceRemove all SQL service packsuninstalled all .NETRebootupgraded SQL to latest service packupgraded 2003 to latest updatesreinstalled reporting instancereinstalled .NETinstall .net updatesRebootThen we changed the certificate info and set it up where EACH user is controlled by their access level with the windows 2003 server. we created user groups defining Departments, within reporting manager we had to link the department with the correct report rights etc.Lots of work. The key is to have a clean install. Keep it clean when you can.

This 'execution <GUID> not found' problem must be down to a single thing. Re-installing everything isn't fixing the problem as such. How do we know the problem might re-appear after the clean installation? I need to know the CAUSE and the CURE for this. We can't afford to carry all this re-installation work out since we have multiple customers on the same server.Can anyone provide a simple, solid solution to this problem? Is there anyone who might know how to solve this problem? I mean, why on earth would reporting services and the viewer work 95% of the time?? We need this resolved because we've had the problem on and off for months and the customer is complaining about it.

I was getting this error when I was using ASP.net impersonation on the page that the reportviewer control was on. I was using impersonation so I could encrypt the username/password of the user that would connect to SSRS & ultimately the SQL Server. What was happening was that I would get an authentication token for the session with the impersonation page and then the reportviewer would do a window.open when I would try to export and I would receive this error. I removed the impersonation and stored the user connection information securly in SSRS and it has resolved this error for me.I hope this helps some of you, I know I spent hours trying to figure this out.

I was getting this error when I was using ASP.net impersonation on the page that the reportviewer control was on. I was using impersonation so I could encrypt the username/password of the user that would connect to SSRS & ultimately the SQL Server. What was happening was that I would get an authentication token for the session with the impersonation page and then the reportviewer would do a window.open when I would try to export and I would receive this error. I removed the impersonation and stored the user connection information securly in SSRS and it has resolved this error for me. I hope this helps some of you, I know I spent hours trying to figure this out. Hi Milo, Could you please describe how did you do that ? I am having the same problem with SSRS everything was working fine for years but suddenly this error has starting poppping up. It is intermittent though. Thanks in advance

This is a possible solution (it worked for me): 1. On the server, edit C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config 2. Set <EnableAuthPersistence> in rsreportserver.config to False: <EnableAuthPersistence>False</EnableAuthPersistence> Regards, M.R.