Forgot to confirm that this was resolved by the article mentioned previously:-

http://blogs.msdn.com/b/psssql/archive/2009/03/03/troubleshooting-sql-server-2005-2008-performance-counter-collection-problems.aspx

Currently: internal politics over the way in which patches are tested and applied. Personally I want them applied because there are a few other bugs that I know get...

I'm aware that it's an old version; however both servers are identical in terms of patching at the OS and SQL level, so I don't believe upgrading will cure at...

Both are fairly old versions; but I don't think it's a version issue as both servers are running the same: 10.50.1600.

It used to work on one and now doesn't; and...

sqlbuddy123 (3/27/2014)

I was thinking about alert notifications. How are you using...

You don't need an operator set to trigger an alert.

I have a test alert set as follows:-

EXEC msdb.dbo.sp_add_alert @name=N'Test Alerts',

@message_id=0,

@severity=16,

@enabled=1,

@delay_between_responses=0,

@include_event_description_in=0,

@event_description_keyword=N'Test Alert Error',

@category_name=N'[Uncategorized]',

@job_id=N'00000000-0000-0000-0000-000000000000'

GO

I...

I've only ever received that error once and it was entirely to do with the disk controllers on the server.

Have you checked the windows os logs to see if any...

Shrinking a file is the only way you will regain the space that file is using.

After shrinking, be sure to rebuild your indexes on that file as they will most...

I tried this, but no definitely nothing to do with the log shipping configuration. It seems far more to be to do with alerts in general; I know this...

These are configured.

To be clear; the alert is not firing, not that emails aren't being sent. The alert was previously working. The only change I've made since the last time...

The alert is the stock one created when configuring log shipping as follows:-

EXEC msdb.dbo.sp_add_alert @name=N'Log shipping Primary Server Alert.',

@message_id=14420,

@severity=0,

@enabled=1,

@delay_between_responses=0,

@include_event_description_in=1,

@category_name=N'[Uncategorized]',

@job_id=N'00000000-0000-0000-0000-000000000000'

The job successfully raises the...

OK cool; well there was only a handful of rows in the table, so the cap won't have been hit. The check at the end of the maintenance task...

Hm, ok well in that case, the work around really doesn't make any sense, because it requires having two alerts set up for the same error?

"When the second alert...

Doh, found the problem; I hadn't set up the SQL Server Agent on that server to send emails. I knew it would be something simple!

Can you post your DDL also?