Unable to Access Page The value of a parameter contains a character that is not allowed or the value exceeds the maximum allowed length. Remove the character from the parameter value or reduce the value length and resubmit... - Answers - Salesforce Trailblazer Community
Trailblazer Community
Ask Search:
Bart RodenbaughBart Rodenbaugh 

Unable to Access Page The value of a parameter contains a character that is not allowed or the value exceeds the maximum allowed length. Remove the character from the parameter value or reduce the value length and resubmit...

When trying to reassign a case, we are getting the following:
Unable to Access Page
The value of a parameter contains a character that is not allowed or the value exceeds the maximum allowed length. Remove the character from the parameter value or reduce the value length and resubmit. If the error still persists, report it to our Customer Support team. Provide the URL of the page you were requesting as well as any other related information. 

Any ideas??
Best Answer chosen by Ed (salesforce.com) 
Bart RodenbaughBart Rodenbaugh
We determined it was related to an installed package where we let the licenses expire over the weekend.   We removed that package and all is working as expected.

All Answers

Pritam ShekhawatPritam Shekhawat
Are you calling some custom visualforce page there on case?
Patrick SullivanPatrick Sullivan
This usually means that the URL is too long to process. Are you using a custom button/action/link to do the convert? Sometimes people pass information through the URL to the next page to populate information. 
Bart RodenbaughBart Rodenbaugh
This is just the standard change owner button.

 
Bart RodenbaughBart Rodenbaugh
We determined it was related to an installed package where we let the licenses expire over the weekend.   We removed that package and all is working as expected.
This was selected as the best answer
Pritam ShekhawatPritam Shekhawat
Glad to hear you resolved it :) Thanks for letting us know !!
surabhi moresurabhi more
@Patrick Sullivan -- i am applying commandbutton by action attribute, then method is calling then i want to get id of current user login, so above mentioned error occured.
Keith ReedyKeith Reedy
That error manifests itself in many ways.  I just saw it come up and our fix was different.
We got the error trying to change opportunity owner.
Historically we have a lookup field on opportunity to account object that is called Partner.
It allowed any account, and on this opp an account was in that field.
We then added a filter to only allow accounts of type partner (makes sense).
Now if an account of not ype partner had been on an opp and you try to edit the opp you received an error stating the partner field does not match filter criteria....which is correct.
However, changing owner on the opp threw the error above about value parameter.   In reality, fixing the lookup field to have a value that was good did the fix.

Readers digest version:  Owner change is a little black box-ish in sfdc (like lead convert) and errors can be misleading.
 
Bart RodenbaughBart Rodenbaugh
New related situation I wanted to add as additional information.   I just received the same message when trying to update the Account Owner but this time it is related to a VR I have that requires a Contact to have a First and Last name.   One of the 4 contacts on this account had his full name in the Last Name field.   Once I corrected the name issue, all worked as expected.
Louisa ReynoldsLouisa Reynolds
I've just got the same error when I am trying to save a new Custom Activity field in a sandbox.
Jonathan DemoryJonathan Demory
I had this error message and I just close and open my org.
Andrea MarroquinAndrea Marroquin
I'm having the same as Louisa error when trying to add a Custom Field to Activity in SBX, any ideas how to solve it?
Louisa ReynoldsLouisa Reynolds
Andrea, when I had this issue it turned out to be because we had reached our limit for custom activity fields.   You can have up to 100 fields and it turns out that this total counts old custom fields that you had in the past, that have been deleted and are no longer showing in your deleted fields (so you have no idea that they exist and they are not shown in your activity limits).     I had to raise a case to Salesforce for them to purge these deleted fields that I didn't have access to.
Louisa ReynoldsLouisa Reynolds
Hi again Andrea - I just found the case comments from the support case that I raise and you might be able to resolve yours without raising a support case.      Do you see a "Purge" button?     This is the comment from support on my case:

Please confirm if you did the Purge action after deleting the fields. An object’s Deleted Fields detail page lists the recently deleted fields. These fields are removed from the object, but remain in the system until they are hard deleted. When you are at or above 75% of your custom field allocation limit for the current object and have fields indicated as ready to hard delete, Salesforce displays the Purge button. You can click the button to free up custom fields faster than the automated process.
Preeti RasalPreeti Rasal
Hello, I'm getting the same error on the page layout. Any idea how can I resolve it?
Brandon TolbertBrandon Tolbert
I too am seeing this vague error.  In my situation, I am simply changing the role of a user, and one specific role at that. I know that our role name does not exceed the 40 character limit, currently 16 including spaces.
Steps to replicate:
  • Select a user with Sys Admin profile
  • Update role to XXXXXXXXXXXXXXXXX
  • Click save
  • Error displays
Any thoughts?
Rob OBrienRob OBrien
I got this error creating a simple date field in production.  I was able to create in the sandbox but not production.  Any resolve?  Report to the Customer Support Team?
 
Christina PassChristina Pass
I got the same error. I am trying to create a simple checkbox custom field on case in production, which I was able to create in sandbox. We are no where near our field limit, and there are no deleted fields to purge.