I ran across an issue installing RealDropzone on a Windows 2003 Small Business Server. After a successful installation, an attempt to run the application resulted in the error seen below.
The issue is that for some reason RealDropzone.exe does not want to see it's configuration file, RealDropzone.exe.config, despite the fact that it exists and is configured correctly and the logged in user has access rights to it. I spent 8 hours trying to figure out WHY the application is not loading the file and finally I gave up and decided to try a work around.
As a work around, I was able to open up the machine.config file located at C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config and add the following line in the <ConnectionStrings> portion of the file, defining the connection string at the machine level instead of the application level.
Line added:
<add name="RealDropzone.My.MySettings.RDConnectionString" connectionString="Data Source=.;Initial Catalog=DNNRDSDHDBLOCAL;Integrated Security=True;Connection Timeout=240;" providerName="System.Data.SqlClient" />
Exception received at startup:
Exception: The ConnectionString property has not been initialized.
Source: System.Data
Method: PermissionDemand
Stack Trace: at System.Data.SqlClient.SqlConnection.PermissionDemand()
at System.Data.SqlClient.SqlConnectionFactory.PermissionDemand(DbConnection outerConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at RealDropzone.RDGlobal.Startup() in C:\RSSource\RealDropzone\RDGlobal.vb:line 47
at RealDropzone.RealDropzoneMDI.RealDropzoneMDI_Load(Object sender, EventArgs e) in C:\RSSource\RealDropzone\RealDropzoneMDI.vb:line 43
Because I was unable to reproduce this error on any other machine, I am logging it is a known bug with a known work-around, and will park it until it is encountered again.
-Matt Christenson