PROBLEM RESOLVED.

What was causing this was an addition of a linked server insert... a single row insert to a table on another server, to the activated stored procedure.

Even though no...

The user has the necessary permissions as a login and a user in that database to execute procedures and update some tables. This has all been verified by logging in...

The exact error in the SQL Server log is:

The activated proc [dbo].[QSVThreatAssesmentProcessor] running on queue [Errors].[dbo[.[QSVInputQueue] output the following: 'Login failed for user 'xxxxxx'.'

The procedure is being activated and executed...

I would need to look at a lot more details of the queries, the business logic and the database design, but generally I can pass along some general information.

Basically, you...

That way will work fine also. You'll just have to make sure those drive letters always auto-mount after reboot and before SQL server starts up.

generate a script with the commands to add the Server2\user to ABC database and grant the user the necessary permissions.

You could script that user and his roles & permissions on...

how did you know it was the "first"?

actually, that join would set descr = to the "2nd" description...

One approach would be to set the additional variables to a value that would include all rows if they are not supplied. For example:

if @keyword1 is NULL

...

try usin brakets around the name: [Database_Name]

One other thing... make sure "WITH NO_LOG" is not being used somewhere in a job statement (or maintenance plan). That will break your log chain also.

be sure there are no other jobs which would truncate the transaction log. I found a similar situation on one server I worked on, where someone must have been concerned...