DBCC CHECKDB FAILED on SQL2k5x64 active\passive cluster

When using an active\passive sqlserver 2005 cluster (standard edition) on MS Server 2003 R2 Enterprise x64 with SP2 and I run the DBCC CHECKDB commands on any of the system databases I receive this error:

Check Database Integrity (selio)
Check Database integrity on Target server connection
Databases: All system databases
Include indexes
Task start: 2007-06-06T16:50:38.
Task end: 2007-06-06T16:50:38.
Failed-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "The database could not be exclusively locked to perform the operation.
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Command:USE [master]
GO
DBCC CHECKDB WITH NO_INFOMSGS
GO
USE [model]
GO
DBCC CHECKDB WITH NO_INFOMSGS
GO
USE [msdb]
GO
DBCC CHECKDB WITH NO_INFOMSGS

I don't receive this error when I run CHECKDB on the system databases on our test environment x64 box (same OS and hardware).

The file system needs to be NTFS for database snapshots. FAT will fail.|||the file system is using NTFS. This is a new cluster setup and sql installation. I just restored a user database to the cluster and tried DBCC CHECKDB on the user database and received the same error message. Part of the error message mentions "Result Set property not set correctly" as a possible solution. Do you know what this is referring to?