In Active Directory when you have an Exchange server a user or group, even a public folder can have multiple smtp email addresses associated with the entity (user/group/public folder etc.), but finding the non-default email address can be tedious. A great way to search for it is:

Go to Active Directory Users and Computers –> right click on the domain and click find –> in the find field, change the criteria to ‘custom search’ –> click the advanced tab where you can type in a LDAP query. If you are trying to find out who has sales@yourdomain.com, type proxyAddresses=smtp:sales@yourdomain.com.

Wildcards can be added to the email address portion, and you can also type a wildcard ie. *.yourdomain.com and then change the view to add the proxyaddress column to see all of the entities with their proxyAddresses (email addresses)

You have 2 options.

1. You can run the following SQL query:

   SELECT SERVERPROPERTY(’productversion’), SERVERPROPERTY (’productlevel’), SERVERPROPERTY (’edition’)
   

2. You can check the version of the sqlservr.exe file, below is a list of how the version breaks down:

   SQL Server 2005

   SQL Server 2005 RTM	2005.90.1399
   SQL Server 2005 Service Pack 1	2005.90.2047
   SQL Server 2005 Service Pack 2	2005.90.3042

   SQL Server 2000

   SQL Server 2000 RTM	2000.80.194.0
   SQL Server 2000 SP1	2000.80.384.0
   SQL Server 2000 SP2	2000.80.534.0
   SQL Server 2000 SP3	2000.80.760.0
   SQL Server 2000 SP3a	2000.80.760.0
   SQL Server 2000 SP4	2000.8.00.2039

After an upgrade from CRM 3.0 to CRM 4.0 I noticed that items no longer deleted immediately. It seemed as if they eventually deleted, but I couldnt tell you when. From what I’ve heard from Microsoft and others, the problem is a trigger that is supposed to be disabled or removed during the upgrade. The fix was this:

1. In SQL Management Studio, expand the dbo.QueueItemBase table within your CRM database.
2. Expand the Triggers folder.
3. Right-Click the t_update_queueitembase trigger and disable it. (Select “disable” from the menu).

This may not address items that you have already deleted that are still pending deletion. To correct those, perform the following SQL command:

UPDATE dbo.QueueItemBase
SET DeletionStateCode = 2
WHERE QueueId = ‘YOUR_GUID_HERE’

You’ll have to find the GUID of the Queue you’re trying to delete from, but it’s pretty straightforward after that.