Hi,

in a customer environemnet we get executing

exec [Microsoft.SystemCenter.Orchestrator.Maintenance].[MaintenanceWorker]

this error:

Error: 9617, The service queue "MaintenanceServiceQueue" is currently disabled.

Msg 50000, Level 1, State 60

Looking at sys.service_queues is_receive_enabled and is_enqueue_enabled is set 0:

When we execute

ALTER QUEUE MaintenanceServiceQueue WITH STATUS = ON

we get this error:

Msg 15151, Level 16, State 1, Line 1
Cannot alter the queue 'MaintenanceServiceQueue', because it does not exist or you do not have permission.

How to enable this service queue?

Regards,

Stefan

More and news about System Center at stillcool.de and sc-orchestartor.eu .

Hi,

I am new to this. I have a SQL Service broker and there is a service  S1 

Now I have 2 SQL Agent jobs  each job calls the same service but calls different procedure P1 in job1 , P2 in job 2 via same services  . aim is to run 2 jobs in parallel.

Is there any way that I can find out which stored procedure is called via service in both jobs  . actually in job1 , I need to execute  a step after procedure P1 processing has finished

and similarly in job2, I need to execute a step ,after procedure P2 processing has finished

so how to find if P1/P2 processing has finished 

Thanks in advance

I'm running a .net 4.6.1 application against a Microsoft SQL Server Standard Edition (64-bit) 10.50.1600 RTM, where I use SqlDependency on simple queries (SELECT Column1, Column2, Column3 FROM [dbo].Table WHERE Active] = 1).

I'm using my own Queue and Service:

CREATE QUEUE MyQueue
CREATE SERVICE MyService ON QUEUE MyQueue ([http://schemas.microsoft.com/SQL/Notifications/PostQueryNotification])

After that, I start the SQLDependency:

SqlDependency.Stop(Configuration.ConnectionString, "MyQueue");
SqlDependency.Start(Configuration.ConnectionString, "MyQueue");

Once that is done, I run all of the queries that I want to watch:

// Create Command...
SqlCommand command = new SqlCommand("SELECT Column1 FROM [dbo].Table WHERE Active = 1", _connection);

// Create SqlDependency...
SqlDependency dependency = new SqlDependency(command, "service=MyService", 60);
dependency.OnChange += onDependencyChange;

// Run the query (this will activate the SqlDependency)
// and pass the results to the onChange delegate
using (SqlDataReader reader = command.ExecuteReader())
{
  ProcessReader(reader);
}

But instead of being notified whenever something changes in that table, I only receive Change/Client/Error or Change/Timeout/Error notifications.

If I use the 1-parameter SqlDependency consturctor (thereby using the default service/queue), all seems to be working correctly. =

I did not notice this behavior on my Dev system, but it does show on multiple test systems. Could the SQLServer configuration have something to do with this?

I'm using SQL2016 SP2. My objective is to a create Service Broker service using internal activation stored proc., that every time it gets any error, it will just rollback, store the error message into another table, skip that error message, and the service can process the next message. Unfortunately, I found when an error occur, the queue will also be disabled automatically, then I need to manually clear the queue by executing END CONVERSATION WITH CLEANUP for each error message inside the queue, otherwise I can't enable the queue again. But actually I don't want any manual intervention to enable the queue again. So my question is how can I stop SQL Server from disabling the queue even an fatal error occurred inside the internal activation stored proc.? Below is my testing:

USE master;
GO
CREATE DATABASE [SBTEST3];
GO
ALTER DATABASE [SBTEST3] SET ENABLE_BROKER;
GO
USE [SBTEST3]
GO
CREATE MESSAGE TYPE [TestPoisonMessage] VALIDATION = NONE;
GO
CREATE CONTRACT [TestPoisonContract] ([TestPoisonMessage] SENT BY INITIATOR);
GO
CREATE QUEUE [dbo].[TestPoisonQueue] WITH STATUS = OFF;
GO
CREATE SERVICE [TestPoisonInitiator] ON QUEUE [dbo].[TestPoisonQueue];
GO
CREATE SERVICE [TestPoisonTarget] ON QUEUE [dbo].[TestPoisonQueue] ([TestPoisonContract]);
GO
CREATE TABLE [dbo].[SBAuditLog] (
	[message] nvarchar(4000) NULL,
	[logTime] datetime2(2) NOT NULL DEFAULT GETDATE(),
	[err_num] int NULL,
	[err_msg] nvarchar(4000) NULL
)
GO
CREATE OR ALTER PROC [dbo].[uspTestPoison]
AS
SET NOCOUNT ON;

DECLARE @message_type varchar(100), @dialog uniqueidentifier, @message_body nvarchar(4000);
  
BEGIN TRY

	BEGIN TRAN;	

	WAITFOR ( 
		RECEIVE TOP(1)
			@message_type = message_type_name,
			@message_body = CAST(message_body AS nvarchar(4000)),
			@dialog = [conversation_handle]
		FROM [dbo].[TestPoisonQueue]
	), TIMEOUT 500
	;

	IF (@@ROWCOUNT != 0 AND @message_body IS NOT NULL)
	BEGIN
		IF @message_type = 'TestPoisonMessage'
		BEGIN
			INSERT INTO SBAuditlog ([message]) VALUES (@message_body);

			-- Fatal Error
			RAISERROR ('Fatal Error', 25, 1) WITH LOG;
		END

		END CONVERSATION @dialog;
	END

	COMMIT;

END TRY
BEGIN CATCH

	DECLARE @error int, @message nvarchar(4000);
	SELECT @error = ERROR_NUMBER(), @message = ERROR_MESSAGE();

	-- Uncommitable transaction
	IF XACT_STATE() = -1
	BEGIN
		ROLLBACK;
	END
	-- Commitable transaction
	ELSE IF XACT_STATE() = 1
	BEGIN
		COMMIT;
	END

	-- Failure audit log
	INSERT INTO SBAuditlog ([message], err_num, err_msg) VALUES (@message_body, @error, @message);

	-- End Conversion with Error
	END CONVERSATION @dialog WITH error = @error DESCRIPTION = @message;

END CATCH
GO
ALTER QUEUE [dbo].[TestPoisonQueue] WITH STATUS = ON, ACTIVATION (STATUS = ON, PROCEDURE_NAME = [dbo].[uspTestPoison], MAX_QUEUE_READERS = 1, EXECUTE AS OWNER);
GO

DECLARE @Handle UNIQUEIDENTIFIER;
BEGIN DIALOG CONVERSATION @Handle
FROM SERVICE [TestPoisonInitiator]
TO SERVICE 'TestPoisonTarget'
ON CONTRACT [TestPoisonContract]
WITH ENCRYPTION = OFF;
SEND ON CONVERSATION @Handle
MESSAGE TYPE [TestPoisonMessage] (N'Testing Message');

After running the above SEND command, the queue will be disabled. I need to run below command to generate the END CONVERSATION WITH CLEANUP statement(s), in order to clear it, and then I can re-enable it. (BUT THAT'S NOT WHAT I WANT!):

SELECT name, is_receive_enabled, is_enqueue_enabled FROM sys.service_queues;
SELECT 'END CONVERSATION ''' + CAST([conversation_handle] AS varchar(100)) + ''' WITH CLEANUP;' FROM [dbo].[TestPoisonQueue];
END CONVERSATION '...' WITH CLEANUP;
ALTER QUEUE [dbo].[TestPoisonQueue] WITH STATUS = ON;
SELECT name, is_receive_enabled, is_enqueue_enabled FROM sys.service_queues;

Hello,

I have a SQL Server 2016 standard editon with AlwaysOn  setup.
I was asked to enable the broker. In order to do that I had to remove the database from AlwaysOn AG group , enable the broker and add the database back to AG group.
ALTER DATABASE [NameOftheDatabase] SET NEW_BROKER WITH ROLLBACK IMMEDIATE;

After the broker was enabled I start getting the following errors :

Hi All,

In SQl Clustering Environment when i have SQL 1, SQL2 Active & Passive

When doing hardening

SQL Server Configuration Manager 

Disable the “Named Pipes” network protocol, The   SQL For both side break and encounter error SQL Can't be access

Any one have any ideal or article realated to this?

Thanks

WHEN changing the collation getting the below error .what is the cause and solution

Used the following commands to change the collation 



Hi All,

How do we use SERVICE BROKER ENDPOINT FOR 2 SQL INSTANCES ON SAME SERVER . How do we migrate the ENDPOINT WITH CERFICATE FROM SQL SERVER 2008 to SQL SQL 2016 . 

The following facts was tested and reproduced on 3 completely different environments and with SQL 2005, 2008, 2008R2, 2012 and 2016.

• When DB mail send email to Postfix(2.10.1 and 3.1.2) SMTP servers report several  errors  “lost connection after CONNECT” and a percentage of them will result in email lost.
• When DB mail send email to a non-Microsoft email relay software(http://emailrelay.sourceforge.net/) installed on a Windows server will report events ID 1002 “winsock select error: 10053“.
• A packet capture shows a specific behavior from DBmail that didn’t exist with other systems . DBmail initiate one or multiple  TCP connections depending of the number of mail to send then in a matter of micro or millisecond forsome of those TCP connections, it send a FIN/ACK  then a RST/ACK, which is interpreted as a lost connection from Postfix and the majority of SMTP daemons.  Those TCP connections  that didn’t have a FIN/ACK complete normally. 
• When DBMail is talking to a Microsoft SMTP, it begins the same way including the FIN/ACK for some of the TCP connections but the SMTP conversation will continue under a different TCP source port and are followed by the sequence number. So Microsoft SMTP do not drop the whole SMTP connection when the initial TCP connection is dropped.
• So for some SMTP conversation, the source port changes during the conversation usually just after the 220 Welcome message which cause a lost connection for the majority of the SMTP services.
• SQL Database mail didn’t see any errors even when mails are lost.

I was always on the assumption that the SMTP protocol is a single TCP connection by design as described in RFC 821.

Right now the only work around we found was to configured DBmail to send emails to an IIS SMTP service which relay to our main Postfix server. We would like to get rid of the middle man if possible.

Can the EXE behind DBmail (Databasemail.exe) be replaced by something else more standard in term of SMTP conversation ?

Any help or suggestion are welcome?

I used the example "Completing a Conversation Between Instances" from SQL Server 2008 Books Online, but when I try to send a message, it does not go through, and in sys.transmission_queue.transmission_status I see the above error.

I tried this between two different computers, and also between a desktop and a VPC running on it, I tried various ports, but nothing helps.

On the profiler I see no activity on the target side.

Thanks for any help.

Can anyone explain this concept to me:

In Service Broker (SQL Server) a queue can be configured with an "activation" procedure. This is a procedure that will execute when message arrive in the queue.

Guidance on how to write such a procedure generally involves using the WAITFOR RECEIVE statement to get a message from the queue, and to wait if there are no messages.

So, the question is -- why are we waiting for the message to arrive in the queue inside the procedure that is executed when messages arrive in the queue?

Or, another way of putting the same question -- how can the arrival of the message trigger a procedure to wait for the arrival of a message?

Thanks for any perspective on this. I just don't understand how this is really working.

I am creating some error handling for the `'SQL/ServiceBroker/Error'` `MessageType` within my queues `Activation Stored Procedure`.  While, I have information on how to access the following exception fields:

 - Code (e.g. Error Number)
 - Description (e.g. Error Message)

I am having trouble finding information on how to access (other) 'standard' error fields from the 'SQL/ServiceBroker/Error' schema, fields like:

...I am having trouble finding information on.

Does anyone know...

 - Where I can get information of the access these fields from the
   'SQL/ServiceBroker/Error' schema?

FOR EXAMPLE:
For those who need to see code ...

    ---------------
    -- HANDLE ERRORS: for Error MessageTypes
    ---------------
    ELSE IF @MessageTypeName = N'http://schemas.microsoft.com/SQL/ServiceBroker/Error'
    BEGIN

        -- CLOSE CONVERSATION
        END CONVERSATION @ConversationHandle;
    END

Hi All,

I am trying to configure service broker external activator service on SERVER2 ,in my database server (SERVER1) i have two installations of sql server one is 2012 and another one is 2017, i have enabled and created all the objects related to service broker in 2012 instance (SERVER1\SQL2012). But after starting the service broker external activator  service i am getting the below error in the EATrace.log file. 

1/16/2019 3:42:44 PM======================================================================================
1/16/2019 3:42:44 PM======================================================================================
1/16/2019 3:42:44 PMINFOThe External Activator service is starting.
1/16/2019 3:42:44 PMINFOInitializing configuration manager ...
1/16/2019 3:42:44 PMINFOReloading configuration file C:\Program Files\Service Broker\External Activator\config\EAService.config ...
1/16/2019 3:42:44 PMINFOReloading configuration file completed.
1/16/2019 3:42:44 PMVERBOSERunning recovery using recovery log file C:\Program Files\Service Broker\External Activator\log\EARecovery.rlog ...
1/16/2019 3:42:44 PMVERBOSECheckpointing recovery log C:\Program Files\Service Broker\External Activator\log\EARecovery.rlog ...
1/16/2019 3:42:44 PMVERBOSECheckpointing recovery log completed.
1/16/2019 3:42:44 PMVERBOSERunning recovery completed.
1/16/2019 3:42:44 PMINFOInitializing configuration manager completed.
1/16/2019 3:42:44 PMVERBOSEStarting worker threads...
1/16/2019 3:42:44 PMVERBOSEWorker threads are successfully started.
1/16/2019 3:42:44 PMINFOThe External Activator service is running.
1/16/2019 3:42:44 PMVERBOSEHeartbeat-Thread is starting...
1/16/2019 3:42:44 PMVERBOSECM-NS-Thread is starting...
1/16/2019 3:42:58 PMEXCEPTIONERROR = 30, The connection to the notification server failed.
1/16/2019 3:42:58 PMEXCEPTIONDETAILSInner Exception:
1/16/2019 3:42:58 PMEXCEPTIONDETAILSSystem.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean withFailover)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject, Boolean withFailover)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at System.Data.SqlClient.SqlConnection.Open()
1/16/2019 3:42:58 PMEXCEPTIONDETAILS   at ExternalActivator.NotificationService.get_Connection()

my EAService.config looks like below

<?xml version="1.0" encoding="utf-8"?><Activator xmlns="http://schemas.microsoft.com/sqlserver/2008/10/servicebroker/externalactivator"
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xsi:schemaLocation="http://schemas.microsoft.com/sqlserver/2008/10/servicebroker/externalactivator EAServiceConfig.xsd"><NotificationServiceList><NotificationService name="AUDIT_NOTIFICATION_SERVICE" id="100" enabled="true"><Description>Tracking Notification Service</Description><ConnectionString><!-- All connection string parameters except User Id and Password should be specificed here --><Unencrypted>server=SERVER1\SQL2012;database=SBEA_DB;Application Name=AuditTrailMessageReceiver;Integrated Security=true;</Unencrypted></ConnectionString></NotificationService></NotificationServiceList><ApplicationServiceList><ApplicationService name="AuditTrailMessageReceiver" enabled="true"><OnNotification><ServerName>SERVER1\SQL2012</ServerName><DatabaseName>SBEA_DB</DatabaseName><SchemaName>dbo</SchemaName><QueueName>AUDIT_REQUEST_QUEUE</QueueName></OnNotification><LaunchInfo><ImagePath>C:\HostedApplications\AuditTrailMessageReceiver\AuditTrailMessageReceiver.exe</ImagePath><CmdLineArgs></CmdLineArgs><WorkDir>C:\HostedApplications\AuditTrailMessageReceiver</WorkDir></LaunchInfo><Concurrency min="1" max="1" /></ApplicationService></ApplicationServiceList><LogSettings><LogFilter><TraceFlag>All Levels</TraceFlag><TraceFlag>All Modules</TraceFlag><TraceFlag>All Entities</TraceFlag><TraceFlag>Verbose</TraceFlag></LogFilter></LogSettings></Activator>

To check the database connectivity from SERVER2 i have created a small console application and it was able to connect to database server without any issues. The following is my app.config file connection string settings

<connectionStrings><add name="SBEACS"
    connectionString="Data Source=SERVER1\SQL2012;Initial Catalog=SBEA_DB;Integrated Security=True"/></connectionStrings>

Please any one help me to correct this issue.

Thanks in advance 

Arun