I am currently experiencing an issue with SSRS 2005 that I have not been able to resolve. Hopefully someone in the forum has experienced a similar issue and has some advice. The issue seems to be that my custom assemblies are not working correct in a subscription. The custom assembly performs several tasks for us. One of the tasks it helps with is to generate MDX statements for use as data sets in the report. The reports work fine in designer. The reports work great on the server when using report manager. The reports great when accessed via a custom ASP page we developed to assist with Ad-hoc reporting. The reports do not work as a subscription. When the report is executed as a subscription calls to the assembly generate errors. It starts with a call to the SSRS web.config file that contains an App Settings section with a connection string. The error is Format of the initialization string does not conform to specification starting at index 0. System.Data at System.Data.Common.DbConnectionOptions.GetKeyValuePair(String connectionString, Int32 currentPosition, StringBuilder buffer, Boolean useOdbcRules, String& keyname, String& keyvalue) at System.Data.Common.DbConnectionOptions.ParseInternal(Hashtable parsetable, String connectionString, Boolean buildChain, Hashtable synonyms, Boolean firstKey) at System.Data.Common.DbConnectionOptions..ctor(String connectionString, Hashtable synonyms, Boolean useOdbcRules) at System.Data.SqlClient.SqlConnectionString..ctor(String connectionString) at System.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous) at System.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(String connectionString, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions) at System.Data.SqlClient.SqlConnection.ConnectionString_Set(String value). So for some reason the query string that works in report manages, custom ASP and designed does not work in subscription or the subscription does not have access to the web.config file. I am leaning towards the later. Has anyone else experienced anything like this before? Any ideas on how to resolve the issue? Any insight will be greatly appreciated. My only other alternative is going to be writing a .Net application to replace subscriptions. I would rather not have to do that. Thank you in advance.