rstuemke
asked on
Exchange 2010 SP3 - Queue Viewer Keeps Aborting
Hello,
I am re-submitting this question as a new question, since the original question got very muddled.
Ok... here goes...... Have new Server-A. Did clean install of Windows 2012 Server, followed by all updates. Then installed Exchange 2010 SP3. Installed additional updates. Configured Exchange 2010 SP3 as part of an existing Exchange 2010 organization. Prior to new Server-A, Exchange 2010 SP2 (latest rollup) running on Windows 2008 R2 Server, with no problems.
Server-A now seems to be running fine, except the Queue Viewer keeps aborting with the following error message:
Cannot process argument transformation on parameter "BookmarkObject". Cannot convert the "Microsoft.Exchange.Data.Q
"Microsoft.Exchange.Data.Q
Do not what this means.
So, have now purchased Server-B. Repeated the steps shown above for Server-B.... Win 2012 Server install, updates, Exchange 2010 SP3 install, additional updates. Running fine, except the QUEUE VIEWER now aborts with the SAME error message on this server also.
By aborts, I do not mean it terminates, but throws the error message and the queue information goes away. When I give the error message and OK, it will go away for awhile, then will return again shortly.
Typically the error happens when I try click on a queue to look at messages. Does not happen on the Win 2008 R2 Server running EX2010 SP2.
Need some assistance. Please advise. Thanks.
I am re-submitting this question as a new question, since the original question got very muddled.
Ok... here goes...... Have new Server-A. Did clean install of Windows 2012 Server, followed by all updates. Then installed Exchange 2010 SP3. Installed additional updates. Configured Exchange 2010 SP3 as part of an existing Exchange 2010 organization. Prior to new Server-A, Exchange 2010 SP2 (latest rollup) running on Windows 2008 R2 Server, with no problems.
Server-A now seems to be running fine, except the Queue Viewer keeps aborting with the following error message:
Cannot process argument transformation on parameter "BookmarkObject". Cannot convert the "Microsoft.Exchange.Data.Q
"Microsoft.Exchange.Data.Q
Do not what this means.
So, have now purchased Server-B. Repeated the steps shown above for Server-B.... Win 2012 Server install, updates, Exchange 2010 SP3 install, additional updates. Running fine, except the QUEUE VIEWER now aborts with the SAME error message on this server also.
By aborts, I do not mean it terminates, but throws the error message and the queue information goes away. When I give the error message and OK, it will go away for awhile, then will return again shortly.
Typically the error happens when I try click on a queue to look at messages. Does not happen on the Win 2008 R2 Server running EX2010 SP2.
Need some assistance. Please advise. Thanks.
ASKER
First.... I gave some bum information..... Server-A was (prior to it being reloaded) our primary Exchange 2007 server, running EX2007 SP(latest) on Windows 2008 Server X64 (not R2). We then migrated to a completely new server (Server-X), running Win 2008 Server R2 and EX2010 SP2. All was well. Then, Server-A was reloaded with Win 2008 Server R2 and EX2010 SP2, just like the primary EX server and we ran that way for a couple of months with no problems. Then, when EX2010 SP3 became available,. did a full reload of Server-A with Win 2012 Server and Ex2010 SP3. That is when the problems started with Queue Viewer.
Problem never occurred on EX2007 or EX2010 SP2. Only when EX2010 SP3 was installed on Win 2012 Server. Does not happen on current primary EX server running EX2010 SP2 on Win 2008 Server R2.
Have several domain controllers. Most were updated with the latest Windows fixes in the last week and all have been rebooted. Will reboot the other two and see what happens...... more info coming in a while....
Problem never occurred on EX2007 or EX2010 SP2. Only when EX2010 SP3 was installed on Win 2012 Server. Does not happen on current primary EX server running EX2010 SP2 on Win 2008 Server R2.
Have several domain controllers. Most were updated with the latest Windows fixes in the last week and all have been rebooted. Will reboot the other two and see what happens...... more info coming in a while....
When you removed and reinstalled Exchange, did Exchange come out clean, and did you change the computer names at all?
I am wondering if there is something from the old installation hanging around which is interferring with the new build. That would also cause bookmark type issues (bookmark is an AD thing, around the computer names and the like).
Simon.
I am wondering if there is something from the old installation hanging around which is interferring with the new build. That would also cause bookmark type issues (bookmark is an AD thing, around the computer names and the like).
Simon.
ASKER
The removal of Exchange 2007 and later Exchange 2010 SP2 from Server-A were both clean. Did the normal Exchange uninstall and it went thru its prerequisite checks for removal.
Maybe you have hit on something...... When I run EXBPA it flags this error:
THE OFFLINE ADDRESS BOOK SITE PUBLIC FOLDER STORE WAS DELETED
The public folder store where offline address book "Default Offline Address List" is hosted has been deleted. Current public store:
"calvaryspringfield.org/co
DEL: a0ee...............6d"
This started awhile ago and I think it is residue from EX2007.
Also, rebooted all domain controllers.
Checked the Queue Viewer. Email in SUBMISSION Queue (stuck) another part of the puzzle that has only happened on Ex2010 SP3 & Win 2012 Server (Get intermittent jobs hung in the queue with the error: Storage transient failure occurred during content conversion" So I click on the message and then the old Bookmark error noted in the original post shows up. Do not know if job in queue is the cause or a symptom.
Maybe you have hit on something...... When I run EXBPA it flags this error:
THE OFFLINE ADDRESS BOOK SITE PUBLIC FOLDER STORE WAS DELETED
The public folder store where offline address book "Default Offline Address List" is hosted has been deleted. Current public store:
"calvaryspringfield.org/co
DEL: a0ee...............6d"
This started awhile ago and I think it is residue from EX2007.
Also, rebooted all domain controllers.
Checked the Queue Viewer. Email in SUBMISSION Queue (stuck) another part of the puzzle that has only happened on Ex2010 SP3 & Win 2012 Server (Get intermittent jobs hung in the queue with the error: Storage transient failure occurred during content conversion" So I click on the message and then the old Bookmark error noted in the original post shows up. Do not know if job in queue is the cause or a symptom.
ASKER
Just a note..... I think the email stuck in the queue has been there since I installed EX2010 SP3. It just moved to Server-B this morning when it became fully operational. Again, not sure if it is the cause or the victim. But it is suspiciously present.
You have an email stuck in the queue? That sounds like a suspect queue database.
Stop the Exchange Transport Service, then delete everything in:
C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\
Then restart Transport and new queue databases will be created.
Simon.
Stop the Exchange Transport Service, then delete everything in:
C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\
Then restart Transport and new queue databases will be created.
Simon.
ASKER
I removed the stuck email with a command. Watching for another stuck email to see if viewer will give error message when I try to open stuck email.
ASKER
Let me get to the bottom line of my concern...... I am wanting to move all the user mailboxes over to the EX2010 SP3 server, so I can reload the current EX server with Win 2012 Sever and EX2010 SP3. Then will move everything back to that server. The purpose of all this is to have both Exchange servers running Win 2012 Server and Ex2010 SP3 so I can then begin to utilize Data Availability Groups, which I cannot do on Windows 2008 Server (standard) R2. Have just been leary of doing this with those queue viewer error, thinking there may be a more serious problems somewhere......
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Problem was the database. When I created a new server and database, problem disappeared.
Unusual to cross servers, so that points to the issue being outside of Exchange.
Simon.