Spell Check Handler Server Error 500 with external Dictionary Path

[Markus Wolff]

Hi there,

I'm using the RadEditor for ASP.net from the 2012.1.215.40 Release with SpellChecking enabled in a .Net 4.0 Web Application.

The scenario is that various web servers should use the same dictionaries (especially to share the custom dictionaries).

Everything works fine as long as the dictionary folder resides on the same server. But spell checking fails when it is on a different one.

DictionaryPath is set like "\\server-name\share", same on all systems.

Error Message in Response and EventLog is:

No dictionary loaded. Set the DictionaryPath property from the spell checker settings or copy the dictionaries to ~/App_Data/RadSpell/

The share's security settings are lowered by now to "Everyone" having full access.

Any suggestions on how to set this up correctly or how to find the proper cause for the error?

Kind regards,
Markus

[Rumen]

Hi,

Try to configure the shared folder as a virtual folder of your web application in IIS. You can see the following KB article for more information: Uploading images and files to a Shared Drive.

Greetings,
Rumen
the Telerik team

[Markus Wolff]

Hi,

thanks for the fast reply.
Seems this was not the solution for the problem. The VirtualDirectory setup works, but only on the machine where the physical directory is located. On remote IIS machines the error remains... 

I assume it's some kind of security issue but can't find out what's missig.
I placed a test.html page inside the virtual folder and could view it through any remote iis url, so it's not a general issue.
Which credentials are used when RadSpell is accessing the dictionary path?

Kind regards
Markus

[Rumen]

Hi,

For your convenience I have recorded a video demonstrating how to share and give permissions to the shared dictionaries folder, make it a virtual folder in the root of the local web site and set the DictionaryPath property to point to it. Here it is: http://screencast.com/t/qhYi1M3khg.

All the best,
Rumen
the Telerik team

[Markus Wolff]

Hi Rumen,

thanks for your reply. We finally spotted this to be an authorization problem. Since we use NTLM only, the server hosting the application wasn't able to pass the request to the server containing the dictionary folder. We solved this using local folders on each server in the load balancing scenario and by replicating the users' dictionaries among them.

Best regards
Markus