Duplicate messages were being created by one or more Query Publishers. When comparing the two created messages (Message A, and Message B) we noticed that Message A had recently added fields amended to the end of the message. Where as Message B had the newly added fields listed in alphabetical order as expected. Since the fields were listed at the end of Message A, this tells us that the new metadata was added after the publisher was created. A newly created publisher will display the fields in alphabetical order as the metadata is available when the publisher is created and can therefore be properly configured.

The customer noticed Message A  looked like a message from an old query publisher that had been deleted leading us to believe that a previously soft deleted publisher was creating the duplicate message. We then used Microsoft SQL Server Management Studio to review the Scribe.Bridges table located in the SCRIBEINTERNAL database. While reviewing the Scribe.Bridges table we noticed that a few of the problematic query publishers had the same names to the old soft deleted query publishers. In the Scribe.Bridges table the value 0 in the ISDELETED field means the publisher is Active, and the value 1 means the publisher has been soft deleted. A hard delete removing the old soft deleted publisher from the database should resolve the issue. 

A deleted publisher with the same name as an existing publisher can cause duplicate messages to be created.

TIBCO Scribe Insight

1. Create a backup of the SCRIBEINTERNAL database before proceeding in case you make a mistake and need to restore the database.
2. Query the top 1000 rows of the Scribe.Bridges table to review the publishers.
3. If soft deleted publishers have the same name as active publishers, delete the soft deleted publishers from the database using the following SQL script

4. After performing the delete restart the 5 Scribe services for the database changes to take affect.
5. Test to make sure existing publishers are now only creating a single message.