Exchange 2010 Content Index State - Failed

Look in perfmon at the copyqueuelength counter under the Msexchange replication object

what exactly am i looking at?

How much does perfmon say it is? Have you done test-replicationhealth ?

Why is this question called "exchange 2010 content index state"? Does it have anything to do with content indexing?

everything is 0 like it is not working and i have no clue how to troubleshoot to get it to work. it works with our other database but not this one.

it says content index failed i would assume that has something to do with seeding

there is no activity for copyqueuelength none what so ever. where do i go from here?

Are you looking on the server that is being seeded? What is the content index error is it in the event log?

Is the database being seeded set to "mount at startup"?

yes i looked on both servers

content index error is as follows:

Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
Mailbox Database: MDB01
Error Code: 0x80041606

do i need to enable exchange server monitoring service?

Exchange Search Indexer has temporarily disabled indexing of the Mailbox Database MDB02 (GUID = c0069daf-36a0-4b11-b977-17ad332f6ac2) due to an error (System.ComponentModel.Win32Exception: Catalog is being dismounted from RPC interface.).

http://support.Microsoft.com/?kbid=2322161

Ignore the content indexing event for now, Exchange can't index a DB until it exists, so I wouldn't worry about that error for now.

ok i think i am going to try and do a manul db copy do i need to copy the log files too or just the database?

Just the database should be sufficient.

ok once i copy the edb i can resume database copy then correct and it will copy over the log files? and copy queue length will go down? or should i just copy logs in as well? will it harm anything if i did or didnt?

The other thing you can do which is supposed to work is:
1.) suspend database copy
2.) dismount the active DB and checkbit is cleanshutdown with eseutil /mh
3.) delete all log files and check point file on active DB location (leaves just .edb)
4.) delete passive files completely
5.) mount active copy
6.) update copy

so remove the following
tmp.edb
*.jrs
*.chk
and then all temp files

Yeah if you just resume it should copy the log files, if not then update the copy and it should copy the logs

ok thanks i will try tonight and let you know.

Yep, remove everything apart from the .edb

so leave the temporary edb or remove that? the edb, mdb02.edb is on a nother drive

If you read around, this copyqueuelength issue seems to be quite common with DAG and it isn't the number of log files it has to copy, but the decimal equivalent of the highest log number you have. Sounds confusing, and it is, so I don't know why it has been done like that or is a bug...

not sure what you mean by the decimal equivalent

Move them out to another folder if you are worried about deleting them. Just leave the mailbox database .edb

thats what i was going to do

Log files are in hex notation. So 10.log = log 16
Have a look at calc.exe in scientific mode

Have a look at http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/f3e34d93-8587-4d54-bec9-81d87e5b8481/

hmm interesting. hopefully this works for me.

Any luck?

just finished it did work, only thing is it has about 20 copy queue and is going down slowly, but i think it might be the wan connection at the other site causing this. it keeps going disconnected and healthy on and off....any ideas?

Done a "ping -t" to see if the connection is timing out? You can restart the exchange replication service on the passive DAG server to see if it speeds up the copy. Rely on the perfmon counters and do a test-ReplicationHealth , but don't rely on the copyqueuelength figure from the test-ReplicationHealth

still does the disconnected and healthy for the one database, the other is fine

and both databases are replicated to the same DAG member?

None of your DAG members are virtual are they?

nothing is virtual, i broke down and called ms support they helped me narrow it down to be a networking issue, apparently DAGs do not support LAGs

err what is a LAG? not a network lag is it? Is it some hardware device? can you post a KB or technet article if MS referred you to one?

Network lag yes....link aggregation