The forum operates in read-only mode.
Please head to StackOverflow for support.
I had a similar problem today and what fixed my problem was:- Go to adobe.com and download a Flash plugin uninstaller- Uninstall Flash plugin- Reinstall Flash pluginThis fixed the problem with i/o error on flash uploader.hope this helps others...
@anyone experiencing the #2038 error:CKFinder 2.2 has just been released. The most important feature: HTML5 uploads should solve the problem with flash uploads forever.Older versions of IE (including IE9) will still use flash, but because the (in)famous cookie bug in Adobe Flash does not affect IE, the #2038 error should be hopefully gone forever. Opera users will still see the flash uploader, but only till the release of Opera 12.I'd like to apologize for having to wait so long for a solution for this annoying issue however it turned out there is really no way to workaround the cookie (and SSL) bug in certain situations, so we just had to finish HTML5 uploads, which we did not manage to introduce in 2.1.1.Note for Safari users: the multiple file upload feature in HTML5 is currently disabled. Starting from version 5.1 there is a bug in Safari browser, which breaks the multiple file uploads. We need to wait for Apple to fix this bug. You can still upload many files at once if you drag&drop them though.
CTO, CKSource - http://cksource.com
Follow CKEditor on: Twitter | Facebook | Google+
Sorry for necroing the thread, but I am still receiving the 2038 error. It is happening on Windows 7, IE 9, with CKFinder 2.3 php version with the flash uploader plugin enabled. I have attempted to disable the flash uploaded, but doing so causes other problems as I outlined in this thread. Is there any solution for this?
I was getting the same error on my ASP.net version. I turned off the flash uploader and thats when i got the following error. “Maximum request length exceeded”. When i goggled that, i found the issue was in my webconfig i needed to add the following code:
<httpRuntime maxRequestLength="102400" />
Once added the issue went away. http://msdn.microsoft.com/en-us/library/e1f13641%28v=VS.100%29.aspx