Crescent Connection error: Cannot create a connection to data source EntityDataSource
-
Friday, August 05, 2011 9:06 PM
I've got a bizarre Crescent issue. At least once a day none of my Crescent reports will work from doc librarys or the pivot gallery. However, I've determined that one of my crescent reports in the gallery does work and if I run that report first, the rest of the crescent reports start to work and I'm able to create new crescent reports from my BISM data sources. I really want to get to the bottom of this as it is driving me crazy. Seems as though something is cached security wise and then expires and I have play all my crescent reports in the gallery until it starts working again. I have noticed that re-running reports from a regular doc library will never work until I get one report working in the pivot gallery so the issue has some relation to the pivot gallery. I've tried playing around with the config file for the claims to windows service which has helped as initially I could not create any crescent reports or BISM connections prior to that change.
Chad Dotzenrod SWC | TECHNOLOGY PARTNERS 1420 Kensington Road, Suite 110 Oak Brook, Illinois 60523-2144 http://www.swc.com
All Replies
-
Friday, August 12, 2011 6:15 PMThis problem has transitioned from an irritation to a complete blocker. I am no longer able to create new crescent reports or run old cresent reports. The error message is as follows: Cannot create a connection to data source 'EntityDataSource' I used to be able to get around this error by running existing crescent reports in the gallery. My existing reports no longer work due to a change I made to my BISM data source (renamed some measures). I'm pretty much dead in the water with Crescent now. Any ideas how I can resolve this error?
Chad Dotzenrod SWC | TECHNOLOGY PARTNERS 1420 Kensington Road, Suite 110 Oak Brook, Illinois 60523-2144 http://www.swc.com -
Friday, August 12, 2011 7:16 PM
Here's the error in the SharePoint log: System.ComponentModel.Win32Exception: Access is denied at Microsoft.SharePoint.Utilities.SecurityContext.SaveThreadTokenAndRevertToSelf() at Microsoft.SharePoint.Utilities.SqlSession.OpenConnection() at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior, SqlQueryData monitoringData, Boolean retryForDeadLock) at Microsoft.SharePoint.SPSqlClient.ExecuteQueryInternal(Boolean retryfordeadlock) at Microsoft.SharePoint.SPSqlClient.ExecuteQuery(Boolean retryfordeadlock)
Cannot complete this action. Please try again.
Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'EntityDataSource'. ---> System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for system.net/webRequestModules: An error occurred while attempting to impersonate. Execution of this request cannot continue. ---> System.Web.HttpException: An error occurred while attempting to impersonate. Execution of this request cannot continue. at System.Web.ImpersonationContext.GetCurrentToken() at System.Web.ImpersonationContext.ImpersonateToken(HandleRef token) at System.Web.ApplicationImpersonationContext..ctor() at System.Web.Confi...
Chad Dotzenrod SWC | TECHNOLOGY PARTNERS 1420 Kensington Road, Suite 110 Oak Brook, Illinois 60523-2144 http://www.swc.com -
Monday, October 10, 2011 8:36 PM
This seems to be isolated to our first eval env. Other environments we build do not have this issue.
Chad Dotzenrod SWC | TECHNOLOGY PARTNERS 1420 Kensington Road, Suite 110 Oak Brook, Illinois 60523-2144 http://www.swc.com- Marked As Answer by Chad - SWC Monday, October 10, 2011 8:36 PM

