Terry Schmitt's Blog

I used to develop entirely on development servers. This was fine until I started working 100% remotely about 5 years ago. At first I still used Homesite+ via RDP and continued to write code on the dev servers. Then I started using Eclipse/CFeclipse for my IDE. I have no regrets making that switch, but I was then limited to using Windows mapped drives to connect via a slow VPN connection (No RDP for CF5). Not Good! Eclipse was really-really slow doing anything over this connection. Somewhere in that time-frame I also started using Subversion and if I installed Subclipse it would literally kill Eclipse while it refreshed a project. I now use various virtual machines running in VMWare Workstation. This is a terrific way to program locally on your PC, but still have the flexibility to configure just about anything that you want for a development setup. I typically use a much smaller database in the this dev scenario, as moving 10-20 GB of data over that same slow VPN connection is not any fun. Well, today it bit me.

Ever get this error with MS SQL2000? Microsoft would have you doing all sorts of shenanigans with Active Directory.

In my case, xp_sendmail would work fine from one server, but not another. They both used the same AD account, so that didn't seem too logical of a fix.

Restarting SQL Server Agent service didn't help. Simply running these 2 stored procedures fixed it:

All I can figure is that there was a communication breakdown between my SQL server and Exchange and SQL doesn't recover very gracefully from that.