Openquery in SQL Server 2012, How can I make this work correctly after migrating from SQL Server 2008(r2)?

Current situation:  Migrating From SQL Server 2008(r2) to SQL Server 2012.

After migrating stored procedures to MSSS 2012 some of them have stopped working, they worked fine on SQL Server 2008(r2)

Elements:
Linked Server LS1
View - v_A
Executed from within v_A - p_B


v_A: Below is the code in v_A where the problem occurs

select * from OPENquery([LS1], 'set fmtonly off SET NOCOUNT ON  
Exec qsc.dbo.p_B  
''NewBerry,Franklin,Quirp,Crasswell'', ''AUTOMATED,CDP_AWK,POND'',''facility_attr26'',''facility_attr27'',''facility_attr19'', ''facility_attr25'',''AVGVGY0,7DAVGVGY0,VGY0,VGT0,PSTAT0,SPDAY,BBLSJY,PCUBE0,PVASE0,INSMDG0''')lom


Below is the error I receive:

Msg 11526, Level 16, State 1, Procedure sp_describe_first_result_set, Line 1
The metadata could not be determined because statement :
'insert into #flak_Table (flakId, flakman, flakRoute, flakAPI, flakCenter, flakPond, flakType, flakCat' in procedure 'p_B' uses a temp table.
 


There seems to be an issue with the procedure 'sp_describe_first_result_set'  in 2012.
I have tested LSA and able to pull data from it just fine.
rhservanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
0
Guy Hengel [angelIII / a3]Billing EngineerCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rhservanAuthor Commented:
Thanks angelIII you hit the nail on the head:

http://technet.microsoft.com/en-us/library/ms188332.aspx 

Section M is the correct syntax for my problem everything is again working.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.