Subscription Contains Invalid Parameters In RS2000
Dec 3, 2007
Occasionally I have this error happening in some of my subscriptions: Subscription contains invalid parameters.
What is actually happenign, one of the parameters has lost the value on which it was previously running without problems. If I open subscription the first parameter, of more, is having no value. The value that is usually lost is first option in drop down list, being for ALL of bellow values. When the error happens it has no value, and that option normally doesn't exists as a parameter value. (If you go creating new subscription that same parameter doesn't have empty values as options to be selected. I usually return ALL and then other individual values.)
For example, one report is having paramteres that returns values from the stored procedure, and the return dataset would be:
Value Label
----------------- -----
'SP1','SP2','SP3' ALL
'SP1' SP1
'SP2' SP2
'SP3' SP3
So, when the error happens, in no reason (no changes to proc, to report design, to subscription,...)
usually those subscriptions that had ALL for this parameter have lost the value, the option is BLANK, and is treated as invalid value, which is correct, as my query also doesn't return BLANK value.
I have to manually go into subscription and set up the value back to ALL and then it's OK, untill next time.
Has anyone experienced this problem?
Does anyone now the fix for this? We thought that hot fix on SP2 may solve this, we applied on dev server but it didn't.
We successfully migrated our RS2000 to RS2005. But we run into an issue €“ trying to modify an existing subscription that was created on RS2000 (We do not have this problem if the subscription is created on RS2005).
The error message is:
An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help. The specified @name (€˜B3F7CB60-6636-4F67-93CF-B94C052DFD29€™) already exists.
The call stack is: w3wp!library!d!02/05/2007-14:31:10:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.Data.SqlClient.SqlException: The specified @name ('B3F7CB60-6636-4F67-93CF-B94C052DFD29') already exists. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery() at Microsoft.ReportingServices.Library.SqlAgentScheduler.CreateTask(Task task) at Microsoft.ReportingServices.Library.SqlAgentScheduler.UpdateTask(Task task) at Microsoft.ReportingServices.Library.SchedulingDBInterface.UpdateTaskProperties(Task task, Boolean updateSqlAgentSchedule) at Microsoft.ReportingServices.Library.TimedSubscriptionHandler.ValidateSubscriptionData(Subscription subscription, String subscriptionData) at Microsoft.ReportingServices.Library.SubscriptionManager.ValidateSubscriptionData(Subscription subscription, String eventType, String subscriptionData) at Microsoft.ReportingServices.Library.SubscriptionManager.SetSubscriptionProperties(Guid id, String eventType, String matchData, ExtensionSettings extensionSettings, String description, ParameterValueOrFieldReference[] parameters, DataRetrievalPlan dataSettings) at Microsoft.ReportingServices.Library.RSService._SetSubscriptionProperties(String subscriptionID, ExtensionSettings extensionSettings, String description, String eventType, String matchData, ParameterValueOrFieldReference[] parameters, DataRetrievalPlan dataSettings) at Microsoft.ReportingServices.Library.RSService.SetSubscriptionProperties(Guid batchId, String subscriptionID, ExtensionSettings extensionSettings, String description, String eventType, String matchData, ParameterValueOrFieldReference[] parameters, DataRetrievalPlan dataSettings) --- End of inner exception stack trace ---
The error message is raised from the stored procedure sp_verify_job:
-- NOTE: We allow jobs with the same name (since job_id is always unique) but only if -- they originate from different servers. Thus jobs can flow from an MSX to a TSX -- without having to worry about naming conflicts. IF (EXISTS (SELECT * FROM msdb.dbo.sysjobs WHERE (name = @name) AND (originating_server = @originating_server) AND (job_id <> ISNULL(@job_id, 0x911)))) -- When adding a new job @job_id is NULL BEGIN RAISERROR(14261, -1, -1, '@name', 'name') RETURN(1) -- Failure END
which is called by another stored procedure sp_add_job.
Question: Is there anyway that I can workaround this issue? Or is there anyway that I can re-create existing report server subscriptions (I have 300+ subscriptions) programmatically.
I had reports using the HTML Viewer working in RS 2000. The servers were both O/S Windows 2000, SQL Server 2000, IIS 5.0, Reporting Services 2000) The default toolbar and parameters area were formatted and looked fine.
We just migrated to new servers with Windows 2003 Server, SQL Server 2005, IIS 6.0, Reporting Services 2005. I have the reports working fine...except the toolbar and parameters areas look as if there is no formatting at all...as if the style sheet isn't being applied (not even the default one --see below).
Although I don't think this is necessary....I tried the following to resolve the issue....
I have two SQL 2000 Server running on Windows 2003 Standard Edtion. I am using merge option to replicate database as Transactional option is excluding some tables. Both server are not in Active Directory and I am trying to replicate over the internet. I got following error message while using Merge option:
Error Message:
The subscription to publication 'XXX' is invalid.
Error details:
The subscription to publication 'XXX' is invalid. (Source: Merge Replication Provider (Agent); Error number: -2147201019) --------------------------------------------------------------------------------------------------------------- The remote server is not defined as a subscription server. (Source: x.x.x.x (Data source); Error number: 14010) ---------------------------------------------------------------------------------------------------------------
Any help regarding the same will be appricated. Thanks.
(NOTE: FROM a NON-IT PERSON) We've implented SQL 2005 and Reporting Services, but our subscriptions only work internally: when we try to send reports via subscriptions to valid external email addresses, we get a message: invalid email address and the entire subscription does not work.. PLEASE ADVISE. IT WILL BE GREATLY APPRECIATED!
I've set up a data-driven subscription on a report but it's not sending and the error log says it's because:
Default value or value provided for the report parameter 'CSRFaxID' is not a valid value.
For the particular dataset record causing the error I'm passing the value Null to the report parameter. The report parameter CSRFaxID is set up with "Allow Null" and with a default value of Null. I can run the report in my browser with CSRFaxID set to null, but the scheduled subscription is not able to produce the report with the same parameter value. Does anyone have any idea what the problem is and how I can fix it?
Hello, i am trying to subscribe to a report that has dependant parameters, for example Country->City and Year-> Month. Those values are coming from a Analysis Services cube dimensions. when i come to it in the subscription window, some of the parameters are populated and some are not. I cannot detect a pattern. Does anyone know what can be the problem? thank you.
I would like to set up a subscription that has two date parameters, I would like the end_date to be today and the start_date to be (today - 1 Month). The interface does not seem to support expressions?
I saw some documentation that said to use defaults in the report but that does not help because I may want multiple subscriptions with different params like 1 person may want (today - 2 months) as the start date ...
I have a package that let me to import data from a excel book to a Sql server data base. When I try to run this package like a step into a SQL server Job it show me the next error.
"The command line parameters are invalid. The step failed."
the "command line" looks like this
/FILE "C:ProjectPackage.dtsx" /CONNECTION ConexionExcel;"Provider=Microsoft.Jet.OLEDB.4.0;Da ta Source=;Extended Properties=""EXCEL 8.0;HDR=YES"";" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI and in my excel conexion is:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=;Extended Properties="EXCEL 8.0;HDR=YES"; When i run the "Command Line" in the "Command window" the error is more expecific
"EXCEL 8.0;HDR=YES;" is not valid So I chanded the "Command Line" in order to run it in de command window(look the double quote in the excel properties)
/FILE "C:ProjectPackage.dtsx" /CONNECTION ConexionExcel;"Provider=Microsoft.Jet.OLEDB.4.0;Da ta Source=;Extended Properties="EXCEL 8.0;HDR=YES";" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI then the package RUN, but when i tried to do the same thing in the sql wizzard, it just dont work and it lost the threat from de package and the errors says this time:
Couldn't find the package
Some one who knows the answer or has any idea to helpme please?
I've been asked to set up a data driven subscription for a number of reports which use multi value parameters. For example, show me all transactions against the following departments: IT, Building Services, Accounts.
As an interactive report it's simple, the user just selects the relevant departments, but as a data driven subscription I can't seem to find the correct format to pass the selections through.
Using RS2005, how should multivalue parameters be stored in a database field so that a data driven subscription can properly read and use them? I have so far had no luck using syntax of:
1) parm1, parm2
2) parm1,parm2
Do single qutoes need to explicitly wrap the values? Can you please provide an example and a SQL INSERT statement using parm1 and parm2 to demonstrate what to store in the database field?
We have many reports with cascading multivalue parameters. The reports and the parameters work as expected within the BI development and when deployed to the RS server. The issue we are having is that when we go to the Report Manager webpage for one of these reports and create a New Subscription the report parameters in the subscription field fail to populate. The first one or two parameters may properly populate but the 3rd, 4th, and 5th fail to populate. As a result we can not select the parameters to submit the subscription.
We have two example reports where one report uses only sql (text) and the other report uses only stored procedures. Both reports have 2 or more cascading parameters.
Any known issues with cascading multivalue parameters in the Report Manager subscription view?
Microsoft confirmed that the error message "The command line parameters are invalid" issue mentioned above is a bug and has been resolved in the next "drop" of SQL Server 2005.
has this error been fixed by microsoft. Cos i still get this error!!!!!!!!!
I am also trying to run the package from command line and when i click on execute the package it runs half way and hangs. What could be the problem????.
But when i run it from my Studio and stored package it works fine!!!
I have an SSRS report with parameters for Created On Start and Created On End. Users run this manually and choose the date range to display records for.
I would like to set up two different subscriptions
1) to send weekly on Monday morning for "last weeks" records and 2) to send monthly to send "last month's" records.
I created a SSIS package that has a flat file manager whose connection string is a package variable, the reason is that there is a foreachfile container loop to loop thru CSV format files in a directory and load them to a sql table.
The package execution is working in the designer studio as well as in the management studio-- a copy was saved to a sql 2005 server where a sql job is deployed to run the package. However when I ran the job, it claims successful but doesn€™t do anything in reality. If I checked the box failing the package upon validation warming, the job will fail with the error: the command line parameters are invalid. The command line looks like below:
One thing that I think maybe wrong is on the data source tab of the job step GUI, the flat file manager€™s connection string is blank, compared to other connection managers having related values.
I have a Sql agent job which will exeute a SSIS package. While, one of my data sources is an excel file. I scriptted the sql agent job and recreate on a test server, it fails with The command line parameters are invalid.. The command line has the following for the excel data source, and that is the place fails the job. /CONNECTION UserDataExcel;"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\myserverUserDataUserData.xls;Extended Properties=""EXCEL 8.0;HDR=YES"";" I guess it has something to do with the double-quote inside, Please advise.
I created a SSIS package to import an excel spreadsheet into my data warehouse. When I run the package it runs fine. When I created a SQL Job to run the package I get the following error:
Option "Source=D:HelpDeskImportBook2.xls;Extended" is not valid. The command line parameters are invalid.
Now if I look at my source connection string in the job it looks like the following:
We want to start working with Reporting Services on a Windows Server 2003 (SP1) server that has SQL2000 (SP3) Standard Edition. I thought I could load RS from the CD but it does not appear to be on there. I seem to remember that Microsoft added RS to SQL2000 in the last year or so. Can I download a copy of it, or how do I go about getting a copy and how to I show my boss that it is a legit copy? Thanks...
We just applied SP2 to our Windows 2003 server & it has had an odd impact RS2000. When trying to change the data source of a report to a shared data source, the browse button when clicked does not take you to the page to enable selection! It does nothing!
Does anyone have any ideas on what's going on there?
Here's the situation we're facing. Our organization is going to consolidate into a single domain. The plan of action is to disband the old domain, and create an all new domain. Most of our servers will also be renamed in the process.
We've got something of a two-server setup, with one machine handling SQL Server, and the other hosting various intranet sites, including Reporting Services 2000.
SQL Server itself shouldn't be a huge problem to migrate - the machine only has about half a dozen Windows logins set up. In my experience, though, Reporting Services is a much more fragile animal. Just getting it up and running on Win2003 SP1 and coexisting with ASP.NET 2.0 was enough of a stunt already. What will I have to watch out for to make sure this doesn't completely hose our installation? Would it be too optimistic for me to hope that I'll just have to reconcile any domain service accounts, change the connection string for the report server catalog database, and be done with it?
I've got a RS2000 report from Analysis services 2000. This report is working fine but after the upgrade to SQL2K5, i'm having issues with changes to parameters.
Basically i'm passing DateQuarter, CustomersLevel as parameters to the following mdx script. I've tried to change mdx script in RS2005 but no luck yet. I don't much about the parameter level changes in sql2k5. So can anyone suggest what is wrong in the script.
Code Block RS2000
="with " & "member [Measures].[Ex Price] as 'coalesceempty([Measures].[Ex Price After Trade Discount - Detail],0.00)' " & "set [Rolling Quarters] as '" + Parameters!DateQuarter.value +".lag(4):" + Parameters!DateQuarter.value + "'" & "SELECT " & "{[Measures].[Ex Price]} ON COLUMNS , " & "filter({CrossJoin([Items by Class].[Item Class Description].members, [Rolling Quarters])}, [Measures].[Ex Price] > 0) on Rows " & "FROM Sales " & "WHERE (" & Parameters!CustomersLevel.Value & ")"
RS2005
with member [Measures].[Ex Price] as 'coalesceempty([Measures].[Ex Price After Trade Discount - Detail],0.00)' set [Rolling Quarters] as '@DateQuarter' +'.lag(4):' + '@DateQuarter' SELECT {[Measures].[Ex Price]} ON COLUMNS , filter({CrossJoin([Items by Class].[Item Class Description].members, [Rolling Quarters])}, [Measures].[Ex Price] > 0) on Rows FROM Sales WHERE STRTOSET(@CustomersLevel)
We're using RS2000 and there are some reports that are having problems exporting to Excel after having been rendered.
The reports have no more than 30,000 rows, but are about 150 columns wide. The reports run (execute and redner) very quickly in Reporting Services, but when exporting, the "blank rendering window" (the one with the URL: "http://ServerName.Reportserver?ReportName&rs%3aCommand=Render&rs%3AFormat=EXCEL) is open for about half an hour, and the w3wp process pummels our 8 proc box (CPU between 50 and 90% for that time) and memory goes past 1.5 GIG (of the total 8 GIG) usage.
Sometimes we'll get a message asking the user to log in after about 10-15 minutes, after which it fails, other times it makes it to the dialog box asking if you want to open or save the spreadsheet. If it makes it to this dialog, it's OK, if not, it fails on the export. The resulting spreadsheets are only between 25 - 32 MG, not very big at all.
Are there any settings we can tweak to speed this up, or at the very least, be sure it always makes it to the Open/Save dialog?
Hi There I've not managed to find an answer already about this, and so I know you guys will be able to help me out becuase your great!!!
Our Reporting Services portal is acting strangely, all the existing reports we have subscriptions for are running fine.
However should we change the list of contacts or the dates or times of any exisiting schedule this stops our reports from being delivered, infact the report run time will pass, but the report will not run and even in the Subscriptions table of RS the last status will only show "New Subscription".
So whatever is happening, it is not triggering the correct work flow. (Thats my thought at least) We examined SQL Agent logs to uncover that the Login used to run the reports was running the existing reports without issue, however the new subscriptions would give the following error:
[298] SQLServer Error: 8198, Could not obtain information about Windows NT group/user 'SERVERNAMEREPORTING_ACCOUNT'. [SQLSTATE 42000] (ConnIsLoginSysAdmin)
The server name and account have been changed to protect the gullible and innocent.
I do hope someone else can provide some insight into my issues
we're all pretty fluent with 2005 products, but must enhance our legacy 2000 RS product, and prefer to use vs2003. Does anyone recall how we used to get vs2003 to allow RS2000 design. We dont believe we saw such an option in installation of vs2003, but since installing the db preceded that, arent sure if we would have been given such an option had vs2003 been installed prior to the 2000 db.
I want to query data from a cube in analysis services with parameters in reporting services. I'm not sure how to make my select statement. Can someone help me please
It seems to me that if a scheduled SSRS report subscription fails ( Status Message - An error has occurred during report processing) , that I actually need to delete the subscription and reconfigure it from scratch. The scheduled job doesn't try to run again automatically (say the next Monday on a weekly Monday schedule).
Is there a way to "reset" a failed subscription without have to recreate the entire subscription?
Existing subscription already contains table included in the new subscription.
What are the possible causes of this merge replication error? Could it be caused by a SQL Server Compact Edition User trying to sync their .sdf file after their subscription has already expired on the SQL Server?
Would you expect to see a different message if a SQL Server Compact Edition user tried to sync a subscriber database (.sdf file) with merge replication if it's been longer than the subscription retention period since their last sync?
