Hi Bill Fry,
I would run a SQL Profiler trace. Use the instructions and recommended templates that you can find in the Knowledge Base. For SQL Server 2008/2008 R2, see KB 967955.
This could be caused by any number of things.
- permissions (run bfgroup script)
- problem with communicator trigger
- custom trigger/custom who knows what
Also try a different user, or different workstations, different version of IE, different document, etc... to try and narrow down the cause.
Let me know what you find.