(Well basically I complained, they fixed, and I tested, so the work was all them!) I want to give a big thank you to Adobe's Michael Collins and the other engineers who worked with me to get this corrected. The hotfix also includes a fix for ColdFusion 7. If you try to use the CFC without the hotfix, you will get an attribute validation error for the tag. Here is an example of it in use in my CFC: To fix this bug, Adobe has released a hot fix that actually adds a new attribute to the cfhttp tag (great, the WACK is now out of date): multiparttype While it worked fine when initially released, some engineer at YouTube decided to tighten up some code some place and that change revealed a bug with ColdFusion and CFHTTP when doing multipart form posts.

Once that was done, we could trigger a failover manually with only one interruption in the application as CF dropped one connection to get the other connection.For a while now the YouTubeCFC component has not been able to upload videos to YouTube. The reason that the SID is important is that if a failover happened (or were manually triggered from SSMS) then the user credential used by the application would lose all of its mappings and permissions in the database. Use the user credential username and password that you created that has the same SID on both servers. SelectMethod=direct sendStringParametersAsUnicode=false MaxPooledStatements=1000 AlternateServers=(xxx.xx.xxx.YYY:1433) jdbcbehavior=0 The Driver Class is and the Driver Name doesn't seem to be used.

Here is the JDBC URL: jdbc:macromedia:sqlserver://xxx.xx.xxx.XXX:1433 databaseName=theDatabaseName The only difference is this:ĪlternateServers=(xxx.xx.xxx.xxx:1433) You can edit the new-datasource.xml file to add this or when creating the datasource in CF Admin use the type 'Other' as the driver type to manually enter the JDBC URL. ) In ColdFusion, the database connection string is almost identical to the regular MSSQL server connection string but has only one extra parameter in the neo-datasource.xml configuration file. You must set up the user credential on the Principal server then run a command to fetch the username, hashed password, and SID then inserting those three things into the Mirrored server.

The first step is to create a user credential in SSMS that is allowed to access the database(s) in question. We finally got the connection string in place so that the application is communicating with the mirrored servers. I'll post here in hopes it might help someone else figure this out too. We had this issue with Adobe ColdFusion 2016 and MSSQL Server 2008 R2. To expand on this answer, I'd like to add the following:

Adobe coldfusion 11 youtube