Exchange Resource Manager

We are running ERM and we have one resource that is not accepting or declining meeting invitations.  It is not occuring on any other resource that we have in the company.  When I send it a meeting invite it puts it goes to the Inbox but it does not automatically accept or decline.  It just stays as tenative.  Is there something simply we can try?  We tried to Unmanage the resource and manage it again with no effect.  Thanks. 

Starting about a month ago, one of my resources stopped responding to meeting requests as well. The other resources behave normally, as do newly created resources. Toggling the management has no effect, meeting invites simply stack up in the resource's inbox, and the following events are logged on the Exchange server's Application event log:

Source: ERM
Event ID: 1458
Description: Could not open the query: 80040E14, "Syntax error (missing operator) in query expression 'szServer = 'servername' And  szMailbox = 'resourcename';'.", SELECT * FROM ERMResourceConfiguration WHERE  szServer = 'servername' And  szMailbox = 'resourcename';
 
Source: ERM
Event ID: 1009
Description: Cannot access resource configuration while processing file://./backofficestorage/servername/MBX/resourcename/Inbox/Test 9.EML
 
If it helps, the system is Exchange 2003 SP2 on Windows 2003 SP1. Any input is appreciated, thanks.

This ticket was resolved by the user after standard diagnostics were applied.  Permissions verified, ERM database verified for consistency.  The solution was ultimately that the mailbox was over size limit and not processing any mail.

There are a few possibilities as to what cause this type of issue.  Since it does not appear you have recently upgraded from an older version of Exchange, I believe we will need to review logs and setup diagnostic logging to find the root cause.

Issue resolved 

When the resource was created, the technician had used a "space" character in the username. SW support mentioned a possibility of special or reserved characters in the mailbox name, so once the account was renamed and the resource unmanaged/managed, meeting requests began responding again. Although it doesn't explain why it worked previously, I am not an advocate of unusual characters in a username, so this fix was acceptable.