This is one of the most frustrating errors I’ve got to fix. I’m using rad editor for my aspx pages and in some pages, it works like a charm but some just doesn’t. Whenever I tried to update the page, it threw this error, “An error has occurred. Refresh the screen and try again”, in the rad editor content area.

My first thought was, the files much be read-only and hence to make writable to the files but it wasn’t the case. So I checked my code, cross check with another working page, recheck again and again, but I found no difference in code and doesn’t work. Then I created a new “test.aspx” file and pasted the same code and tested it. Strange enough, it works!

So I thought may be my page got corrupted, so I deleted that page and recreated a new page with the same name, paste the code back in. Then it’s not working again. The same god damn code in “test.aspx” is working and not in the other page.

Something was really fishily wrong! Since they are the exact same code, the only difference I can think of now is the file name. But I can’t change all the file names without knowing whether that’s the actual cause of the problem. So my final option, turn to google for help and there it was!

(ID#250) “An error has ocurred. Refresh the screen and try again”

PROBLEM
When saving the content from r.a.d.editor directly in the ASPX/ASCX the following error appears:
An error has ocurred. Refresh the screen and try again.

SOLUTION
When saving the r.a.d.editor content directly in the ASPX/ASCX the page name should not contain “(“, “)”, “-”, or ” ‘ “. If such names are obligatory, r.a.d.editor’s content should be saved in a database.

Link: Telerik KB Article

So stupid error. My error files are named using the “-” dash. Once I removed the dash, all working. It’s just so lame error message and even in the KB no explanation about why it cannot use a dash in the file names. Well you can use dash if you saving content in DB, but why not in the actual file? I just not satisfy with that KB solution explanation. Nevertheless, it solved my problem and thank god for that. Took hell lotta time from me. I guess next time, I better google first then check on my code. Hmm.

No related posts.