SQL Server 2014 - calling sp_setapprole failing

Question

The corporation I work at has decided to start using the application role functionality in SQL Server.    We are able to successfully implement the app roles into the application (PowerBuilder 12.1) when running against a SQL Server 2012 database,
however the same code when running against a SQL Server 2014 database fails. 
Because PB execute everything from within a transaction we had to do some "interesting" code to get the approles working.  Here is the SQL that is being passed into the DB:
SET QUOTED_IDENTIFIER OFF
SET IMPLICIT_TRANSACTIONS OFF
SET ANSI_PADDING ON
create table "<generated temp table name>" (id int identity( 1, 1) not null, cookie varbinary(8000) not null ) 
declare @cookie1 varbinary( 8000)  exec sp_setapprole @rolename = '"+ <rolename>+"', @password = '"+<password>+"',  @fCreateCookie = 1, @cookie = @cookie1 output insert "+<generated temp
table name>+"( cookie) values( @cookie1)
So what happens is the approle is being called and the cookie stored in a temp table on the database.  This is because of the translation between SQL Server and PB with the Varbinary cookie that is created for the approle.  If brought into PB it gets
messed up and the unset approle doesn't work.
As stated, the code above WORKS in SQL Server 2012, not in 2014.  I run the profile trace on the server and I can see the temp table being created, the sp_setapprole proc being called and the statements inside being executed, but once hitting the function
setuser we get the error that the approle does no exist or the password is invalid.  I've been able to trace through the password being sent in and it's the same as that PB is sending across so it's not a corruption issues.
Running the SQL through SS Management Studio works.  The temp table created and the approle is set.  Additionally we have .Net applications using the same user/password, and retrieving a cookie, and they work as well.   
Does anyone know if there has been changes to the way approles are handled in 2014, or if there was a change to the setuser functionality that could be causing the approle to fail?

Answer 1

The call "SET QUOTED_IDENTIFIER OFF" was an attempt to get the DB working the same way our SQL Server 2012 database is set-up.  I've since removed it
from the code. Also each of the calls are executed separately:
ls_sql = "SET IMPLICIT_TRANSACTIONS OFF" 
EXECUTE IMMEDIATE :ls_sql USING atrTrans;
IF atrTrans.SqlCode <> 0 THEN
guMsg_handler.uf_message(TRUE, &
"Unable to connect to the database.~r~n" + &
atrTrans.sqlerrtext)
RETURN false
END IF
ls_sql =  "SET ANSI_PADDING ON"
EXECUTE IMMEDIATE :ls_sql  USING atrTrans ;
IF atrTrans.SqlCode <> 0 THEN
guMsg_handler.uf_message(TRUE, &
"Unable to connect to the database.~r~n" + &
atrTrans.sqlerrtext)
RETURN false
END IF
ls_sql =  "create table  "+atrTrans.isTempTableName+"( id int identity( 1, 1) not null, cookie varbinary(8000) not null ) "
EXECUTE IMMEDIATE :ls_sql  USING atrTrans ;
IF atrTrans.SqlCode <> 0 THEN
guMsg_handler.uf_message(TRUE, &
"Unable to connect to the database.~r~n" + &
atrTrans.sqlerrtext)
RETURN false
END IF
ls_sql = "declare @cookie1 varbinary( 8000), @password1 sysname = '" + ls_appRollPass + "'  exec sp_setapprole @rolename = '"+ ls_AppRoleName +"', @password = @password1,  @fCreateCookie
= 1, @cookie = @cookie1 output insert "+atrTrans.isTempTableName+"( cookie) values( @cookie1) " 
EXECUTE IMMEDIATE :ls_sql  USING atrTrans ;
IF atrTrans.SqlCode <> 0 THEN
guMsg_handler.uf_message(TRUE, &
"Unable to connect to the database.~r~n" + &
atrTrans.sqlerrtext)
RETURN false
END IF
atrTrans.AutoCommit = FALSE
ls_sql = "SET IMPLICIT_TRANSACTIONS ON" 
EXECUTE IMMEDIATE :ls_sql  USING atrTrans ;
ls_sql = "SET ANSI_PADDING OFF"
EXECUTE IMMEDIATE :ls_sql  USING atrTrans ;
commit using atrTrans ;
  EDIT: Note that the passing of the password as a variable was only for testing/validation to ensure that the password matched what was being sent from PB and NOT intended to be there in the actual implementation.