Expression based connection strings

Hi Folks,
I am having difficulty using expression based connection strings. I have
followed the instructions in this posting
http://blogs.msdn.com/bimusings/archive/2006/07/20/673051.aspx
, and as far as I can tell, I have everything set up correctly, but when I
put in the ServerName parameter and run the report I get an error,
"An error has occurred during report processing.
Cannot create a connection to data source 'AWDQuery'.
For more information about this error navigate to the report server on the
local server machine, or enable remote errors "
When I send the connection string to a text box to check it, it is fine. I
even copied it out of the text box and inserted it into another report to
ensure there wasn't a stray control character embedded. Here is the data
source connection string from the XML file.
"data source=" & Parameters!ServerName.Value & ";initial catalog=AWDQuery;"
ServerName is a valid parameter on the report.
I am using SQL Server 2005.
Any ideas?
Thanks,
BobHere is the error message from the log.
w3wp!processing!b!1/30/2007-13:29:49:: e ERROR: Data source 'BrandNew': An
error has occurred. Details:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'BrandNew'. -->
System.ArgumentException: Format of the initialization string does not
conform to specification starting at index 0.
w3wp!processing!b!1/30/2007-13:29:49:: e ERROR: An exception has occurred in
data source 'BrandNew'. Details:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'BrandNew'. -->
System.ArgumentException: Format of the initialization string does not
conform to specification starting at index 0.
w3wp!processing!b!1/30/2007-13:29:49:: i INFO: Merge abort handler called
for ID=-1. Aborting data sources ...
w3wp!processing!b!1/30/2007-13:29:49:: e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error has occurred during report processing., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error has occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'BrandNew'. -->
System.ArgumentException: Format of the initialization string does not
conform to specification starting at index 0.
-- End of inner exception stack trace --
w3wp!webserver!b!01/30/2007-13:29:49:: e ERROR: Reporting Services error
Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has
occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An
error has occurred during report processing. -->
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'BrandNew'. -->
System.ArgumentException: Format of the initialization string does not
conform to specification starting at index 0.
"Bob McDermott" wrote:
> Hi Folks,
> I am having difficulty using expression based connection strings. I have
> followed the instructions in this posting
> http://blogs.msdn.com/bimusings/archive/2006/07/20/673051.aspx
> , and as far as I can tell, I have everything set up correctly, but when I
> put in the ServerName parameter and run the report I get an error,
> "An error has occurred during report processing.
> Cannot create a connection to data source 'AWDQuery'.
> For more information about this error navigate to the report server on the
> local server machine, or enable remote errors "
> When I send the connection string to a text box to check it, it is fine. I
> even copied it out of the text box and inserted it into another report to
> ensure there wasn't a stray control character embedded. Here is the data
> source connection string from the XML file.
> "data source=" & Parameters!ServerName.Value & ";initial catalog=AWDQuery;"
> ServerName is a valid parameter on the report.
> I am using SQL Server 2005.
> Any ideas?
> Thanks,
> Bob
>