1 GB message stuck in queue. Can't get rid of it

Need some advice here. We have a 1GB message stuck in the transport queue. Its in an Active state but it's been there for a while. Other messages seem to be working their way around it. I can't get rid of it. I tried removing it and it just goes into a Pending Removal state and stays there.  Rebooted the server and it goes back to Active. If its in an Active state, it should just be delivered. Its going to our Journal mailbox. This mailbox is located on its own database and there is plenty of space there so thats not the issue. There are no limits on the mailbox itself. Shouldn't this message just eventually get delivered. If you are wondering how a 1GB message got into the queue, we had no global limits set due to a migration we were doing from another platform and we forgot to impose global limits afterwards. They are in place now but its too late for this message. What are my options here?
shadowtuckAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TMekeelCommented:
On 2010 you can create a new queue.  What version are you running?

Stop transport service.  
Find the queue folder and rename it.
Restart transport service.

Edit, this may work for other versions but I am only familiar with 2010 and 2013.
0
shadowtuckAuthor Commented:
Running 2010 SP3. I am trying to avoid that if possible. I found this link which tells you how to
create a new queue database along with the logs.

http://technet.microsoft.com/en-us/library/bb125177.aspx

 My confusion is why the message is just not being delivered.
0
TMekeelCommented:
1GB file...probably not fully uploaded from whoever sent it?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

TMekeelCommented:
Actually I take that back....it's going to the journal account but from where?
Where was the message originally destined for, and was it delivered?  Though you had no limit I cant imagine the receiver has no limit.
0
shadowtuckAuthor Commented:
Looks like he sent it to his gmail account and a copy goes into our Journal mailbox. I think the copy to his gmail actually went out because its not in the Send Connector queue.
0
TMekeelCommented:
Did he get a bounce from gmail?  They have a 25MB limit so I'd imagine so.
Is the message still in his outbox? Ask and if so, delete from there.
Probably the reason a reboot restarts the delivery as active (although I'm guessing.)
If it is in the outbox still, I can also surmise that Outlook or whatever client he's using isn't working well at the moment.

I still think the best approach is to rename the queue folder and restart transport.  You've already rebooted the server, doing so will not incur as much downtime as that.
0
shadowtuckAuthor Commented:
Interesting. I just took a look at his mailbox. There is nothing in his Outbook. He has two NDR's from Exchange stating the message is too big but it looks like he got these messages after I went in and set Global Send/Receive limits in Exchange. The NDR's also came about 12 hours after he sent the messages. So, even though the messages were in the queue for delivery, they respected the global limits I applied but I just looked and the messages are still in the queue marked Active. They are set to expire tomorrow morning at 8:40 AM so I am curious to see what will happen at that time. To be honest, I don't think they ever left the Exchange server. Our gateway probably would have bounced them back if they did get past Exchange.
0
TMekeelCommented:
Take Outlook offline and see if the message has fully been sent to the Exchange server.

If you take it offline it should show up in the Outbox (although since it's been so long I doubt it will.)

Other than that, wait for expiration if you do not want to recreate the queue (or another expert may have a better suggestion.)

Good luck!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
shadowtuckAuthor Commented:
Thanks. Making some progress. It has moved off of one CAS to another and will probably at some point get delivered to the Journal mailbox. I am just going to let it take its course. The Journal mailbox is on a database which is mounted on a server in a site different from the user so one CAS had to send it to another before it goes into the Journal mailbox. Eventually, it will be delivered to the Journal mailbox or expire.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.