Content Staging: The incoming request has too many parameters.

Josh Cossiboon asked on March 2, 2018 14:40

We are using Content Staging and it works great except we are experiencing an error syncing an extended version of the Article page type.

It appears to be generating a long query and ultimately the error is: Caused exception: The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.

Has anyone experienced this or have any suggestions how to resolve this?

Thanks in advance!

The query it fails on is but there are 2100+ NodeAliasPath criteria listed in the query.

SELECT [postidpath] FROM   forums_forumpost 
WHERE  ( [postforumid] IN (
 SELECT [forumid] 
     FROM   forums_forum 
 WHERE  ( [forumcommunitygroupid] IS NULL ) 
 AND [forumdocumentid] IN 
         (SELECT [documentid] 
         FROM view_cms_tree_joined AS V WITH (nolock, noexpand) 
         LEFT OUTER JOIN com_sku AS S WITH (nolock)
         ON [V].[nodeskuid] = [S].[skuid] 
         WHERE  ( [nodealiaspath] LIKE @NodeAliasPath 
                    OR [nodealiaspath] LIKE @NodeAliasPath1 
                    OR [nodealiaspath] LIKE @NodeAliasPath2 

                    ....

                    OR [nodealiaspath] LIKE @NodeAliasPath8873 
                    OR [nodealiaspath] LIKE @NodeAliasPath8874 ) 
                                                       )) )

content staging staging

Recent Answers

Brenden Kehren answered on March 2, 2018 15:08

What version are you using?

Secondly, the error is complaining about the forum module and not an article page type. Are you sure it's from the article?

Lastly, have you made any customizations to the base forum module or content staging?

0 votesVote for this answer Mark as a Correct answer

Josh Cossiboon answered on March 2, 2018 15:19

Hello Brenden - thanks for the response!

We are working with version 10. And yes, this error occurs when attempting to sync the Article Page Type. We don't use the base forum module. We haven't made any customizations to forum or content staging.

I recognized that in the query too and was researching how to disable the forum module.

Everything else syncs fine it's just this one object.

Thanks in advance!

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on March 2, 2018 15:46

Was the site upgraded from an older version?

Are they any custom queries linked to the Article page type you're staging?

Have you reviewed the staging task raw data to see what's in there before staging it?

0 votesVote for this answer Mark as a Correct answer

Josh Cossiboon answered on March 2, 2018 20:33

@Brenden - No this is a brand new setup. no upgrades applied

yes, there is a custom query configured on the page type. A very simple select query. nothing nested and not related to forums.

I'm not sure how to look at the staging task raw data. Can you provide more information? Is there a link I can follow? I didn't find anything in the documentation.

I should note, we have moved on from this issue but I want to get to the bottom of it so I can avoid this issue again.

Again, thanks for your help.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on March 3, 2018 06:29

On the individual staging task click the green eye. It will open a new window and let you review the raw data. Some areas are single lines while others are in a text area and you'll need to scroll left to right and up and down in that area to see all of the info.

0 votesVote for this answer Mark as a Correct answer

Josh Cossiboon answered on March 13, 2018 21:50

Brenden - I found the problem.

The target server had Continuous Integration enabled. The stack trace revealed that the error occurred while serializing the page type.

CI doesn't need to be enabled.

0 votesVote for this answer Mark as a Correct answer