Specifying an invalid data provider or failing to resolve a custom data provider for a SqlDataSource doesn't lead to an exception or even logging the problem in the trace. The Reporting engine simply tries to use the default System.Data.SqlClient and if it fails, the error from the SqlClient provider may be misleading like indicating an invalid connections string: "Exception: System.ArgumentException: Keyword not supported: 'authentication'"