Urgent: SBS 2011 no incoming mails from external addresses

This is an "old" installation and had worked previoucly. No outlook says connected to Exchange and internal mails works but can't receive emails from external sources. I can see that the firewall is still forwarding smtp traffic to the server. No external (new) mails at the owa too.

The win firewall is off at the server.

No obivous reason why it stopped working. When I restart the Microsoft Exchange Active Directory Topology service I can see plenty of these warnigs:

Log Name:      Application
Source:        MSExchangeTransport
Date:          25.3.2015 11:17:29
Event ID:      12028
Task Category: TransportService
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      SERVER1.company.local
Description:
The process with process ID 6360 is holding the performance counter connections current Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6360 StartupTime: 130716789241580739 from instance default server1(AD5817A) RefCount=0 SpinLock=0 Offset=2776 and category MSExchangeTransport SMTPReceive while running processes are: Processes running are:
3348 silsvc
7828 tv_w32
1376 spoolsv
568 lsass
980 w3wp
7372 MSExchangeThrottling
10236 w3wp
13780 iexplore
5716 srmhost
576 lsm
1560 dfsrs
8256 OWSTIMER
6856 Microsoft.Exchange.ServiceHost
8056 fsorsp
372 svchost
6872 w3wp
13476 tv_x64
3324 svchost
2696 msexchangerepl
3716 SPWRITER
3028 MSExchangeMailSubmission
2532 sqlservr
1940 FSHDLL32
560 services
3908 svchost
8180 fsaua
14544 TeamViewer
14672 WmiApSrv
6268 Microsoft.Exchange.Search.ExSearch
1736 fsgk32
14048 TeamViewer_Desktop
1340 exfba
10992 mmc
1928 inetinfo
1728 fswebuid
11224 w3wp
4484 w3wp
740 svchost
148 svchost
8224 svchost
10784 VSSVC
3888 svchost
4212 conhost
3688 wsstracing
4080 fssm32
1912 lmgrd
10380 Microsoft.Exchange.AddressBook.Service
332 svchost
9488 dllhost
3000 MsExchangeFDS
12924 taskhost
3944 w3wp
916 svchost
11356 dwm
8032 mad
8596 msdtc
6428 SMSvcHost
12724 mmc
15204 msftefd
8196 svchost
15484 Microsoft.Exchange.RpcClientAccess.Service
3268 ntfrs
1492 certsrv
1884 conhost
8384 svchost
304 smss
3848 sqlwriter
16144 MSExchangeADTopologyService
1876 FSMA32
1084 svchost
492 winlogon
13492 vmtoolsd
7384 svchost
2064 store
1472 svchost
4820 iexplore
2652 SMSvcHost
3524 WmiPrvSE
6784 w3wp
2252 mqsvc
1660 fsgk32st
4220 conhost
15932 TrustedInstaller
2444 sqlservr
4336 mssdmn
15164 w3wp
1848 lmgrd
3620 mssearch
10384 explorer
7952 fdhost
11692 iexplore
7552 fdhost
4596 dfssvc
13048 ExTRA
456 wininit
7744 fdlauncher
15336 dns
15540 MSExchangeMailboxAssistants
8076 vds
7884 FSM32
8920 wuauclt
448 csrss
14992 WmiPrvSE
10364 wbengine
10796 Microsoft.Exchange.ProtectedServiceHost
3988 MSExchangeTransport
3396 WSSADMIN
2144 w3wp
9864 mmc
6712 svchost
4180 DataCollectorSvc
12640 Microsoft.Exchange.EdgeSyncSvc
12452 w3wp
3980 TeamViewer_Service
12268 w3wp
2204 msftesql
824 svchost
10920 dllhost
3580 wsusservice
10080 iexplore
2396 sqlservr
8304 iashost
1408 Microsoft.ActiveDirectory.WebServices
12624 Microsoft.Exchange.AntispamUpdateSvc
13420 console
16176 WmiPrvSE
9760 SearchIndexer
3172 vmtoolsd
396 csrss
1984 ismserv
9272 fsav32
14984 svchost
964 svchost
3752 svchost
14256 MSExchangeMailboxReplication
4536 FSHDLL64
4 System
8080 fdlauncher
1184 ptc_d
12600 WmiPrvSE
0 Idle
 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeTransport" />
    <EventID Qualifiers="32772">12028</EventID>
    <Level>3</Level>
    <Task>12</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-03-25T09:17:29.000000000Z" />
    <EventRecordID>826999</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER1.company.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>6360</Data>
    <Data>connections current Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 6360 StartupTime: 130716789241580739</Data>
    <Data>default server1(AD5817A) RefCount=0 SpinLock=0 Offset=2776</Data>
    <Data>MSExchangeTransport SMTPReceive</Data>
    <Data>Processes running are:
3348 silsvc
7828 tv_w32
1376 spoolsv
568 lsass
980 w3wp
7372 MSExchangeThrottling
10236 w3wp
13780 iexplore
5716 srmhost
576 lsm
1560 dfsrs
8256 OWSTIMER
6856 Microsoft.Exchange.ServiceHost
8056 fsorsp
372 svchost
6872 w3wp
13476 tv_x64
3324 svchost
2696 msexchangerepl
3716 SPWRITER
3028 MSExchangeMailSubmission
2532 sqlservr
1940 FSHDLL32
560 services
3908 svchost
8180 fsaua
14544 TeamViewer
14672 WmiApSrv
6268 Microsoft.Exchange.Search.ExSearch
1736 fsgk32
14048 TeamViewer_Desktop
1340 exfba
10992 mmc
1928 inetinfo
1728 fswebuid
11224 w3wp
4484 w3wp
740 svchost
148 svchost
8224 svchost
10784 VSSVC
3888 svchost
4212 conhost
3688 wsstracing
4080 fssm32
1912 lmgrd
10380 Microsoft.Exchange.AddressBook.Service
332 svchost
9488 dllhost
3000 MsExchangeFDS
12924 taskhost
3944 w3wp
916 svchost
11356 dwm
8032 mad
8596 msdtc
6428 SMSvcHost
12724 mmc
15204 msftefd
8196 svchost
15484 Microsoft.Exchange.RpcClientAccess.Service
3268 ntfrs
1492 certsrv
1884 conhost
8384 svchost
304 smss
3848 sqlwriter
16144 MSExchangeADTopologyService
1876 FSMA32
1084 svchost
492 winlogon
13492 vmtoolsd
7384 svchost
2064 store
1472 svchost
4820 iexplore
2652 SMSvcHost
3524 WmiPrvSE
6784 w3wp
2252 mqsvc
1660 fsgk32st
4220 conhost
15932 TrustedInstaller
2444 sqlservr
4336 mssdmn
15164 w3wp
1848 lmgrd
3620 mssearch
10384 explorer
7952 fdhost
11692 iexplore
7552 fdhost
4596 dfssvc
13048 ExTRA
456 wininit
7744 fdlauncher
15336 dns
15540 MSExchangeMailboxAssistants
8076 vds
7884 FSM32
8920 wuauclt
448 csrss
14992 WmiPrvSE
10364 wbengine
10796 Microsoft.Exchange.ProtectedServiceHost
3988 MSExchangeTransport
3396 WSSADMIN
2144 w3wp
9864 mmc
6712 svchost
4180 DataCollectorSvc
12640 Microsoft.Exchange.EdgeSyncSvc
12452 w3wp
3980 TeamViewer_Service
12268 w3wp
2204 msftesql
824 svchost
10920 dllhost
3580 wsusservice
10080 iexplore
2396 sqlservr
8304 iashost
1408 Microsoft.ActiveDirectory.WebServices
12624 Microsoft.Exchange.AntispamUpdateSvc
13420 console
16176 WmiPrvSE
9760 SearchIndexer
3172 vmtoolsd
396 csrss
1984 ismserv
9272 fsav32
14984 svchost
964 svchost
3752 svchost
14256 MSExchangeMailboxReplication
4536 FSHDLL64
4 System
8080 fdlauncher
1184 ptc_d
12600 WmiPrvSE
0 Idle
</Data>
  </EventData>
</Event>
RimFire007Asked:
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.

RimFire007Author Commented:
I can see apx 70MB file at the queye folder.
Queue-folder-contents.JPG
0
cpmcomputersCommented:
Exchange server enters back pressure mode and refuses external mail when available disk space drops to around 2%.

If there is no obvious reason for your server to be running out of space, check that your backups are running properly as otherwise your exchange transaction logs will eventually fill your disk.
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
David AtkinTechnical DirectorCommented:
As per cpmcomputers coments.  

Check the disk space on all drives.  If its gone below 4.5GB then Exchange will stop accepting external emails and start to fil the queue file.

If you are running low on disk space - Read this article on how to reclaim it:
http://blogs.technet.com/b/sbs/archive/2010/03/02/recovering-disk-space-on-the-c-drive-in-small-business-server-2008.aspx

It refers to SBS2008 but is still valid in SBS2011.

If you're disk space is ok then you can disable 'back pressure' although its not a long term fix.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

RimFire007Author Commented:
Thanks

Yes, the disk space is very low and I start actions to have more space. That should be the reason why incoming mails aren't working.
0
cpmcomputersCommented:
Some suggestions to try to get email flowing again quickly

1) Try the disk cleanup from ccleaner

http://www.piriform.com/ccleaner
 
this will free up any temp files - really a desktop cleaner but I have used it many times on sbs2011 without any issues

2) Use the wizard in the sbs console to relocate the wsus content if you have alternative space

3) Windirstat will help identify what the disc's are being used for and likely candidates to cleanup or move

http://windirstat.info/

Caution do not delete anything you are unsure about
You do have backups ?

Cleaning up the wsus service takes a fair while so other than moving the content (if possible)
I would look to other areas first
0
RimFire007Author Commented:
Thanks

I was able to delete some installation package files etc. and end up having 24GB free of 499GB. The mails started to flow normally.
 
No I have new disks installed and moved WSUS-folder via SBS Console: "Backup and Server Storage / Server Storage / Move Windows Update Repository Data" to new disks.

So, i just moved the WSUS folder and I wonder why I still see apx. 73MB file (mail.que) at the "C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\data\Queue" -folder?
0
cpmcomputersCommented:
The mail.que file temporarily stores all emails before it is delivered to the target. It is an ESE database which means it is similar in architecture like an Exchange mailbox database, the edb file.

You can reset it but as this is a single server You may have mail loss whilst doing it
At 73MB I would accept it as it should not be a cause for concern
0
cpmcomputersCommented:
Is this sorted now
0
RimFire007Author Commented:
Thanks

There very first answer by cpmcomputers  were the best (C-drive full). By deleting some big files  (3rd party installation packages), that is freeeing up space, I were able to have incoming mails working.  I added new disks and then moved WSUS location via SBS Console.
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
SBS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.