Repl.Pending Xacts Question

We have VLDBs running on a SQL 2005 server. Some users have questioned speed and response times. When I investigated the server (W2K3) using the perfomrance monitor, I noticed an interesting questionabel result. The Repl. Pending Xacts showed 44,000,000 transactions waiting to be delived to the distribution databse. Problem is - we do not have replication tunred on on any of the db's on the box. In my research, I have not noticed anyone with a similiar issue. Does this amount of transaction take up space, or is it simply a counter that I don't have to be worried about?

Further info:

After running the following script, I found that the master and model dbs contained 22,000,000 each. Also, when applying the script to other SQL 2005 servers, the exact same results were obtained. When I ran it on SQL 2000 servers, they returened a zero (0). Is this inherent to 2005? Is this taking up space? Can I get rid of it? Will this be problem in the future if I want to start actual replication? Just some things that keep me awake at night....

SELECT

CAST(RTRIM(INSTANCE_NAME) AS VARCHAR(15)) as [database],

CAST(RTRIM(COUNTER_NAME) AS VARCHAR(31))as [Counter],

CAST(RTRIM(CNTR_VALUE) AS VARCHAR(10)) as [Value]

FROM MASTER..SYSPERFINFO

WHERE [Counter_Name] like '%XActs%'

|||

Probably a perfmon bug of some sort, not replication. master and model cannot be replicated anyways.

|||

Please excuse this intrusion. Have you learned any more about this issue? We've encountered the same problem; replication is not being used but a HUGE value for that counter.

Thank you for your time.

Bill