Resource Security (Sandbox) and Data Source.

[rapidray]

OK, I think that this is new and may be a possible bug...  I have CF9 (standard) Update 1, hotfix 1 installed on Windows Server 2008 R2.  Everything was working fine.  I turned on resource security, disabled a bunch of tags, disabled a bunch of functions and left only my working datasource enabled.  These settings match a working Windows Server 2003 install with CF8.  Suddenly, my datasouce did not work.  It complained about the instance not working or not existing.  I turned Resource security off and my datasource was again enabled.  I turned resource securtity  back on, reset all of it's settings to allow everything (i.e. <<All Datasources>>, all functions, all tags etc.), with the idea of disabling un-needed functionality one-item-at-a-time until I uncovered the offending setting.  I restarted the CF service and once again, the datasource failed to connect even though all the resources were wide-open.  Disabling sandbox, restarting the CF service, restored the datasource.  Has anyone else experienced this issue, and/or found a work-around?

[rapidray]

OK, it is a bug... It was reported by Miguel Fernandez (#84928)  After reporting the bug (which only applies to a SQL server that is being referenced by Server\Instance) he found a work-around.  Instead of referring (in the CF administrator) to the database as Server\instance on port 1433, Use the instance's port number (get this from your DBA) and leave off the Instance reference to the SQL Server:  For example instead of MySQLServer\MyInstance (on port 1433) refer to it as simply MySQLServer (on port 15999 [or whatever port is assigned to the MyInstance instance].  I have verified that doing this corrects the issue of the data source failing when you turn-on Sandbox security.  Thank you Mr. Fernandez.