locked
'RECEIVE MSG' not supported in this version error RRS feed

  • Question

  • From Joel Roberts (@joel_roberts ) via Twitter who tweets:

    “When migrating bit.ly/1Saa6uR - Statement 'RECEIVE MSG' is not supported in this version of SQL Server. Pls Help!”

    Below is the associated error:

    Tweet URL: https://twitter.com/AzureSupport/status/685836846505439232 

    Appreciate if you can advise the customer on this matter.

    Thanks,
    @AzureSupport


    • Edited by F C (MSFT CSG) Saturday, January 9, 2016 3:03 PM Amending image quality
    Saturday, January 9, 2016 3:03 PM

Answers

All replies

  • I creating the following MSDN forum post for this issue as well:

    https://social.msdn.microsoft.com/Forums/azure/en-US/a056e23a-419e-46fb-91ad-cc2e4ca625ad/statement-receive-msg-is-not-supported-in-this-version-of-sql-server?forum=windowsazurewebsitespreview

    Found this as well on StackOverflow without a solution:

    http://stackoverflow.com/questions/33693020/azure-sql-server-error-statement-receive-msg-is-not-supported-in-this-version/34695066#34695066

    Saturday, January 9, 2016 3:17 PM
  • Here are the only errors I get during migration. Azure SQL rejected the CREATE PROCEDURE and the transaction was rolled back, so I don't see how they could be causing the exception, although it is the same exact error.

    1/9/2016 1:04:26 AM --> Error #: 40510 -- Statement 'RECEIVE MSG' is not supported in this version of SQL Server.

    CREATE PROCEDURE [SqlQueryNotificationStoredProcedure-8c56d3ea-c86b-47f2-8718-3f7023b8f209] AS BEGIN BEGIN TRANSACTION; RECEIVE TOP(0) conversation_handle FROM [SqlQueryNotificationService-8c56d3ea-c86b-47f2-8718-3f7023b8f209]; IF (SELECT COUNT(*) FROM [SqlQueryNotificationService-8c56d3ea-c86b-47f2-8718-3f7023b8f209] WHERE message_type_name = 'http://schemas.microsoft.com/SQL/ServiceBroker/DialogTimer') > 0 BEGIN if ((SELECT COUNT(*) FROM sys.services WHERE name = 'SqlQueryNotificationService-8c56d3ea-c86b-47f2-8718-3f7023b8f209') > 0) DROP SERVICE [SqlQueryNotificationService-8c56d3ea-c86b-47f2-8718-3f7023b8f209]; if (OBJECT_ID('SqlQueryNotificationService-8c56d3ea-c86b-47f2-8718-3f7023b8f209', 'SQ') IS NOT NULL) DROP QUEUE [SqlQueryNotificationService-8c56d3ea-c86b-47f2-8718-3f7023b8f209]; DROP PROCEDURE [SqlQueryNotificationStoredProcedure-8c56d3ea-c86b-47f2-8718-3f7023b8f209]; END COMMIT TRANSACTION; END

    -- Success: SET ANSI_NULLS ON 

    -- Success: SET QUOTED_IDENTIFIER ON 

    1/9/2016 1:04:26 AM --> Error #: 40510 -- Statement 'RECEIVE MSG' is not supported in this version of SQL Server.

    CREATE PROCEDURE [SqlQueryNotificationStoredProcedure-d4e64b5d-ea75-45da-a1f2-eed75045a27e] AS BEGIN BEGIN TRANSACTION; RECEIVE TOP(0) conversation_handle FROM [SqlQueryNotificationService-d4e64b5d-ea75-45da-a1f2-eed75045a27e]; IF (SELECT COUNT(*) FROM [SqlQueryNotificationService-d4e64b5d-ea75-45da-a1f2-eed75045a27e] WHERE message_type_name = 'http://schemas.microsoft.com/SQL/ServiceBroker/DialogTimer') > 0 BEGIN DROP SERVICE [SqlQueryNotificationService-d4e64b5d-ea75-45da-a1f2-eed75045a27e]; DROP QUEUE [SqlQueryNotificationService-d4e64b5d-ea75-45da-a1f2-eed75045a27e]; DROP PROCEDURE [SqlQueryNotificationStoredProcedure-d4e64b5d-ea75-45da-a1f2-eed75045a27e]; END COMMIT TRANSACTION; END

    Saturday, January 9, 2016 3:21 PM
  • Hi,

    SQL Database does not support Service Broker, so you will have to remove respective objects before migrating to SQL  DB.

    Thanks,

    Mihaela

    Monday, January 11, 2016 8:14 PM
  • Yes, I filed a support ticket with Azure and they told me the same.  Thanks.

    Friday, January 15, 2016 4:59 PM