Chris Trina
Top achievements
Rank 1
Rank 1
Chris Trina
asked on 12 Feb 2009, 04:14 PM
My site is getting intermittent errors from the spell checker with the message "Invalid character in a Base-64 string". Any hints? Below is a trace of the error.
My runtime version is v2.0.50727
Thanks
Message: Invalid character in a Base-64 string.
Source: mscorlib
TargetSite: Byte[] FromBase64String(System.String)
StackTrace: at System.Convert.FromBase64String(String s) at Telerik.Web.Dialogs.DialogParametersSerializer.Deserialize(String serialized) at Telerik.Web.UI.DialogParameters.Deserialize(String source) at Telerik.Web.UI.SpellCheckHandler.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
My runtime version is v2.0.50727
Thanks
Message: Invalid character in a Base-64 string.
Source: mscorlib
TargetSite: Byte[] FromBase64String(System.String)
StackTrace: at System.Convert.FromBase64String(String s) at Telerik.Web.Dialogs.DialogParametersSerializer.Deserialize(String serialized) at Telerik.Web.UI.DialogParameters.Deserialize(String source) at Telerik.Web.UI.SpellCheckHandler.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
14 Answers, 1 is accepted
0
Hi Chris,
Do you use some other encoding for your page than UTF-8? If this is the case I suggest to change it to UTF-8 and run the Spell Check to see if this helps. Here is a forum thread discussing the encoding issues with the Spell Check:
http://www.telerik.com/community/forums/aspnet-ajax/editor/spell-check-handler-server-error-500-invalid-length-for-a-base-64-char-array.aspx
Regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Do you use some other encoding for your page than UTF-8? If this is the case I suggest to change it to UTF-8 and run the Spell Check to see if this helps. Here is a forum thread discussing the encoding issues with the Spell Check:
http://www.telerik.com/community/forums/aspnet-ajax/editor/spell-check-handler-server-error-500-invalid-length-for-a-base-64-char-array.aspx
Regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Chris Trina
Top achievements
Rank 1
Rank 1
answered on 24 Feb 2009, 10:55 PM
Rumen,
I already have <globalization requestEncoding="utf-8" responseEncoding="utf-8"/> in my web config. Based on what I've read this should handle the issue. Any other thoughts?
Chris
0
Hi Chris,
Is it possible to open a support ticket and send a sample working project that demonstrates the problem? If you are unable to isolate the problem, please provide a URL to the problematic page to see the error on our end. If this is an internal web application then check whether the requests for .axd files are not corrupted by something. The spellcheck handler is an axd file.
Kind regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Is it possible to open a support ticket and send a sample working project that demonstrates the problem? If you are unable to isolate the problem, please provide a URL to the problematic page to see the error on our end. If this is an internal web application then check whether the requests for .axd files are not corrupted by something. The spellcheck handler is an axd file.
Kind regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Chris
Top achievements
Rank 2
Rank 2
answered on 26 Jun 2009, 08:43 PM
Has there been any updates on this?
I'm having the same error. I've updated my web.config to include <globalization requestEncoding="utf-8" responseEncoding="utf-8" />.
I have a page that uses a RadEditor with RadSpell. The site is also using RadCompression.
Any help??
I'm having the same error. I've updated my web.config to include <globalization requestEncoding="utf-8" responseEncoding="utf-8" />.
I have a page that uses a RadEditor with RadSpell. The site is also using RadCompression.
Any help??
0
Chris Trina
Top achievements
Rank 1
Rank 1
answered on 30 Jun 2009, 11:26 AM
Sorry Chris, but I still receive these periodically even after adding the UTF-8.
Chris
Chris
0
Hi Chris,
Could you please remove the RadCompression HttpModule and see whether the error still persists?
You should also make sure that you are using the latest Telerik.Web.UI.dll version (Q1 SP2 2009).
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Could you please remove the RadCompression HttpModule and see whether the error still persists?
You should also make sure that you are using the latest Telerik.Web.UI.dll version (Q1 SP2 2009).
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Chris Trina
Top achievements
Rank 1
Rank 1
answered on 01 Jul 2009, 02:34 PM
I am not using rad compression. I will try upgrading and let you know. Unfortunately I never get this error in testing, it only appears sporadically in production.
0
Chris
Top achievements
Rank 2
Rank 2
answered on 01 Jul 2009, 07:41 PM
The project that I am using is using RadCompression but I can not just go in and turn it off this is a production environment. And very similar to other posts it is not easy to reproduce because it does not always happen. Yesterday my customer entered "Good afternoon" in the editor hit spell check and got the error, I tried it minutes later and received the error as well, but then shortly after that could not reproduce it, same site, same words.
To be honest this has REALLY become a HOT issue and is causing my customer too loose confidence in our coding ability, they don't understand, OR CARE that this is a Telerik component they just know the application they paid for is not working. So this is putting my in a very bad situation.
Given that this particular thread is now over 4 months old, and others like it are even older I'm really not sure how to address this.
Telerik your support is usually awesome, I hope you can come through with a solution to this!
Thank you,
Chris Evans
To be honest this has REALLY become a HOT issue and is causing my customer too loose confidence in our coding ability, they don't understand, OR CARE that this is a Telerik component they just know the application they paid for is not working. So this is putting my in a very bad situation.
Given that this particular thread is now over 4 months old, and others like it are even older I'm really not sure how to address this.
Telerik your support is usually awesome, I hope you can come through with a solution to this!
Thank you,
Chris Evans
0
Hi Chris Evans,
Our suggestion is to turn off RadCompression for the time being. The chance for this module causing the error is very high.
As you note yourself, the error is very sporadic and so far we have not been able to nail it down (other than being able to confirm that RadCompression has something to do with it).
Best wishes,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Our suggestion is to turn off RadCompression for the time being. The chance for this module causing the error is very high.
As you note yourself, the error is very sporadic and so far we have not been able to nail it down (other than being able to confirm that RadCompression has something to do with it).
Best wishes,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Rick
Top achievements
Rank 1
Rank 1
answered on 23 Oct 2009, 05:36 PM
I am also having this same problem. I am not using RadCompression. It started recently and only occurs in my QA environment. DEV and production are fine. We just recently converted the QA server to be a Virtual Machine. Is anyone else also using VM and, if so, does that lead to a diagnostic direction?
I have tried just about all the recommended resolutions.
Rick
I have tried just about all the recommended resolutions.
Rick
0
Rick
Top achievements
Rank 1
Rank 1
answered on 23 Oct 2009, 06:26 PM
Additional information:
It only seems to do this when I have altered the text in the editor or run the editor several times (3 - 4) with no change in the text. Also, I ran Fiddler - when it fails, the server is replying with a 302 HTTP code.
Once the spellcheck fails, trying to open any RadDialog on the page also fails with the error "Cannot deserialize dialog parameters. Please refresh the editor page." Like wise, I'm experiencing that just trying to open dialogs fails intermittently with the same error message without having run the spell check. And, once the dialogs fail, then the spell check fails.
It only seems to do this when I have altered the text in the editor or run the editor several times (3 - 4) with no change in the text. Also, I ran Fiddler - when it fails, the server is replying with a 302 HTTP code.
Once the spellcheck fails, trying to open any RadDialog on the page also fails with the error "Cannot deserialize dialog parameters. Please refresh the editor page." Like wise, I'm experiencing that just trying to open dialogs fails intermittently with the same error message without having run the spell check. And, once the dialogs fail, then the spell check fails.
0
BW
Top achievements
Rank 1
Rank 1
answered on 23 Oct 2009, 09:13 PM
I get this same error.
Here is the email I get from my error handler.
All I changed in the message was the page name where you see /.../
Here is the email I get from my error handler.
All I changed in the message was the page name where you see /.../
Server Error in 'http://.../Telerik.Web.UI.SpellCheckHandler.axd'
Source: mscorlib
Description: Invalid character in a Base-64 string.
Extended Description:
Stack trace:
at Telerik.Web.Dialogs.DialogParametersSerializer.DecodeString(String toDecode)
at Telerik.Web.Dialogs.DialogParametersSerializer.Deserialize(String serialized)
at Telerik.Web.UI.DialogParameters.Deserialize(String source)
at Telerik.Web.UI.SpellCheckHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
|
0
Hello,
See if the following forum post will help you about the editor dialogs issue - http://www.telerik.com/community/forums/aspnet-ajax/editor/cannot-deserialize-dialog-parameters.aspx
The spell checker parameters and the editor dialog parameters are encrypted when sent to the browser in order to prevent possible malicious modifications before they are sent back to the server (e.g. when you open a dialog). The encryption key is unique for each application instance and changes each time the web application is restarted. I assume that this is why you see the error only sporadically - when you browse to a page, the application is recycled, and then you try to spellcheck/open a dialog from that page the encryption key has changed and the control raises an exception. The above forum post explains how to set an encryption key that is unique to your application and will not change. This way you can keep the security of the dialog/spell parameters and avoid problems when the application is recycled.
Best wishes,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
See if the following forum post will help you about the editor dialogs issue - http://www.telerik.com/community/forums/aspnet-ajax/editor/cannot-deserialize-dialog-parameters.aspx
The spell checker parameters and the editor dialog parameters are encrypted when sent to the browser in order to prevent possible malicious modifications before they are sent back to the server (e.g. when you open a dialog). The encryption key is unique for each application instance and changes each time the web application is restarted. I assume that this is why you see the error only sporadically - when you browse to a page, the application is recycled, and then you try to spellcheck/open a dialog from that page the encryption key has changed and the control raises an exception. The above forum post explains how to set an encryption key that is unique to your application and will not change. This way you can keep the security of the dialog/spell parameters and avoid problems when the application is recycled.
Best wishes,
Lini
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
Rick
Top achievements
Rank 1
Rank 1
answered on 26 Oct 2009, 12:31 PM
Kudos to Lini and I'd like to express that toward the entire Telerik Support team. I did not follow your suggestion about using a fixed encryption key although I may incorporate that in the future. Your explaination about this symptom being caused by the App Pool recycling was the key. I should have looked at that earlier. My App Pool was recycling VERY frequently (like every minute or two). Your suggestion got me to look at the App Pool recycling frequency and, once that was fixed, the spell check problem was fixed.
For others with IIS hosted on a virtual machine, see KB article http://support.microsoft.com/kb/911716. I set garbage collection to workstation mode and the app pool recycling problem was resolved.
Rick