Outlook 2013 completely stuck!

I installed Outlook 2013 as part of Office 2013 Pro on 10 computers recently for a charity.
There was a powercut 2 days ago and since on one of them they can no longer get Outlook to work at all. Emails open but no new ones can come in or go out. Send and Recieve no longer works.
I cannot seem to post a screen dump on here but when you go into to the FILE option you get the following messages.
The first one is a "Metered Connection warning" stating that the that we are on a metered connection and there may be charges if Outlook has to go online. This is rubbish of course. Its on a LAN with ADSL broadband.
The second one in Red below that states UPGRADE IN PROGRESS. Your mailbox is currently being optimized as part of upgrading to Outlook 2013. This one time process may take more than 15 min.
If I try and go into Account settings it doesnt open anything.
I have tried the following
An office repair from control panel (no change)
Sytem restore (this failed as it always does in Windows 7)
Restore the outlook PST file from a backup prior to the crash. (just the same error)
I dont know what to try next apart from completely re-install everything. The computer is only a couple of month old running Windows 7 Pro and Office 2013 Pro. AV is MS Security Essentials.
Thanks

Hi,
Have you tried starting Outlook in safe mode to check if this problem persists? Press Windows key + R, type
outlook.exe /safe in the Run command and press Enter.
Did Outlook create a new mail profile after you perform a system restore? If not, please try to create a new mail profile to check the result:
http://support.microsoft.com/kb/829918/en-us
In addition, please have a look at the thread below and check if the solution works for you:
http://www.techsupportforum.com/forums/f57/solved-outlook-2013-and-metered-connection-warning-748217.html
Hope this helps.
Regards,
Steve Fan
TechNet Community Support

Similar Messages

Outlook 2013 email stuck in outbox and after restart outlook deletes them

We're running outlook 2013 + Exchange 2010 SP3.
I have a user that twice now has called helpdesk to say his email is stuck in his outbox. His client was in cached mode but connected to the exchange server. The first time, after trying a manual send/receive, I exited outlook and very quickly saw the outbox
empty of the 9 items that were there. I went over to sent items expecting to see them there and they weren't. The recipients never received the emails.
Today, the same thing happened (it's 2 weeks later and he hasn't had the problem since) but this time we saved everything before exiting outlook. When outlook started again, the messages in outbox were deleted. I did message tracking on the transport servers
and they never made even made it to the hub transport. However, because I had a record of the precise emails he was responding to this time, I search for them and they actually show that he has replied at X:XX time, but they were never sent.
I think this has something to do with cached mode so I've switched his client to online mode in the meantime but I was wondering if anyone has seen anything like this. It's the first time I've ever seen outlook (Any version) actually delete email.

I'm getting the exact same thing with one of my users.
We're using Gmail connecting to outlook through a add-in (Google Apps Sync).
The user in question has this occur about once a month. As we don't use exchange it can't be the link to exchange that's causing this. I think it's got to be down to something in the local mail cache, OST file?
We have a lot of users in our business, none have reported this issue apart from this one user. The only thing which differentiates this user from the rest is that she has a lot of PST files mapped and open at any time. I'm talking like 30+ which is
killing performance. I know this is a huge NO NO in terms of operations but this user is adamant that she needs each and every PST open. She has management back her up with this so my hands are tied. I'm wanting to abolish outlook and just use gmail, just
so that I have an excuse to get all her mail in the cloud.
But anyway, this has to be something to do with the local mail store running out of memory or something like that.
If I ever get mails into the cloud, I'll let you all know if this issue stops occurring.

Outlook 2013 mail stuck in Outbox

We just started using Outlook 2013 and Exchange 2013 (Fresh install) but we got a problem with additional mailboxes.
When you open additional mailboxes on your exchange account settings where you have send as permissions and full access and then send an e-mail from that mailbox it stays in the outbox. Sending an e-mail in owa works fine from the mailbox.
What can this be?

We need to try basic steps for this mail stuck in outbox issue as below:
Work offline, move the stuck mail into another folder. Restart Outlook and Work online to send it again.
Temporarily uninstall or disable firewall and antivirus software.
Test in Outlook safe mode.
Create a new profile and re-setup your account.
Let me know the resualt. Thanks.
Tony Chen
TechNet Community Support

Can't move "completed" items into folders using Outlook 2013 on a Microsoft Office 365 Home Premium Account using a work Exchange 2010 address

I've been in touch with several Microsoft support teams about this issue, and the latest move was to shove me off onto Pro support, but since I'm using a personal Office account, I'm hoping that through the community I can find a way to resolve this issue without
escalating through our IT department. I do not think this is an Exchange issues because I have previously used this product and method without resulting in this error on a Windows 7 32-bit AMD computer and a Windows 8 and 8.1 Professional 64-bit Intel computer.
Here's my current specs:
Windows 7 Professional 64-bit, service pack 1
AMD A6-5400 3.6 GHz
8GB RAM
Microsoft Office 365 Home Premium
Office updates automatically, version 15.0.4551.1512
About Outlook shows "Microsoft Outlook 2013 (15.0.4551.1511) MSA (15.0.4551.1508) 32-bit/Part of Microsoft Office 365 Home Premium"
Here's how to reproduce the issue:
1) Open View Settings
2) Select "Other Settings..."
3) Disable "Use compact layout in widths smaller than XX characters" and enable "Always use single-line layout"
4) Select "Columns..."
5) Under "All Mail fields" add "In folder"
6) Select any email
7) Context-menu -> Find Related -> Emails in this Conversation
8) Select "more"
9) Sort by folder
10) Select all messages from Inbox.
11) Use Outlook's preset "Done" function and select a destination folder
12) Watch Outlook fail to run "Done" and reset your UI without producing an error.
The first attempt to resolve this issue was to set up a new Outlook profile. This seemed to exacerbate the problem and resulted in Outlook providing an "Unknown error" before resetting the UI.
The second attempt to resolve this issue was to run "outlook.exe /resetnavpane". However, the nav pane does not appear immediately relevant to this issue.
The following similar steps also result in a crash, this time with an error:
11) Flag all select message as Complete.
12) Move all messages from Inbox to a destination folder.
This change in procedure results in the error "Cannot move the items. Some items cannot be moved. They were either already moved or deleted, or access was denied."
Help me, Microsoft Community. You're my only hope.

Import the calendar and contacts in Outlook.com. For contacts, export from Outlook as csv and import into Outlook by choosing the Other option (https://people.live.com/import/other?biciid=ImportCatalog)
You'll need to save the calendar as an ics file to import it. Select the calendar folder, the File, Save as an save as an ics.
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter

Outlook 2013 with Exchange 2013: Mails stuck in Outbox

Hi everybody,
I am using Outlook 2013 connecting an Exchange 2013 server. After sending a mail, all outgoing mails remain in the outbox. After removing the cache files it works for a while until the problem occurs for the next time (approx. once every two days).
I already re-installed Windows 8 to test it on a completely clean environment...OWA works fine, the problem only exists with Outlook.
Additional note: It might be interesting that after sending a mail, the "Send/Receive progress" window states "sending [email protected] - complete" but the Mail is still in the outbox and was not delivered to the recipient. Safe mode doesn't work
for me. Other users connecting with Outlook 2010 don't have a problem with this exchange server.
Do you have any ideas? If I can provide you with further information, please let me know.
Greets,
Basti

Thanks for your answer. Here are the requested information:
>What addins are you using?
No 3rd party addins, at the moment "Microsoft Exchange Add-In", "Microsoft VBA for Outlook Addin",
"OneNote Notes about Outlook Items" and "Outlook Social Connector 2013" are activated. But the problem also occurs if no addin is active (or even in Safemode).
>Antivirus
scanners can prevent Outlook from moving messages to the sent folder.
I will try to deactivate the virus scanner the next time. (Avira is used)
>Can
any address trigger this behavior or does it happen with certain addresses?
No, it does happen with any address by random. Once the problem occurs, I can try to send as much mails as I want to
any address - nothing leaves the outlook client.
>Is
this your mailbox or a shared/secondary mailbox?
It is a user's mailbox, nothing shared.

Outlook 2013 stuck at splash screen even on safe mode

I was trying to add in an IMAP account to my Outlook 2013, when it hanged, so I forced-stop it via Task Manager and tried to restart the application. But right now, it's forever stuck at "Loading Profile" the splash screen. I tried to restart it
in safe mode too, but experiencing the same problem.
Help?

Hi altern4te,
First, perform a clean boot to find out about programs which are interrupting the Outlook. So, you will accurately understand the cause of this hang up.
It can be antivirus programs or something else.
For more about clean boot in Windows:
http://support.microsoft.com/kb/331796
Note:
As you are not able to open Outlook in safe mode, you cannot disable the add-ins which generally cause behind such types of disturbance.
Hopefully clean boot method will solve it, otherwise this can happen due to corrupt Outlook Data File or Outlook profile.
To fix corruption and its issue:
http://support.microsoft.com/kb/2652320
Thanks
Clark Kent

Outlook 2013 / Exchange 2013 : Shared mailboxes - Mail stuck in outbox (non-cached), Mail sends but doesn't get received (cached).

Hello,
We are currently experiencing some weird behaviour in Outlook 2013 since we added Shared Mailboxes.
When we run Outlook 2013 with cached mode
enabled:
- I create a new e-mail and send it.
- The e-mail goes to the outbox, and get's 'send'.
- None of the recipients receives the e-mail.
When we run Outlook 2013 with cached mode
disabled:
- I create a new e-mail and send it.
- The e-mail goes to the outbox, but remains there.
Now to make things even more bizarre:
When I switch from 'cached'-mode to 'non cached'-mode, I see all the e-mail that were 'send' in cached-mode stuck in the outbox.
Note: The DNS server configuration in Exchange is correct.

Hi,
How about sending on OWA? Does the issue exist?
To troubleshoot the issue, let's run Outlook in Safe Mode to determine if 3rd-party add-ins are related:
Press Win + R and type “outlook.exe /safe” in the blank box, then press Enter.
If there’s no problem sending emails in Safe Mode, disable the suspicious add-ins to verify which add-ins caused this issue.
Please also disable the firewall and anti-virus program to send the emails again, in many scenarios the protection may cause the issue.
Please also keep Exchange and Outlook patched to the latest.
Regards,
Melon Chen
TechNet Community Support

Populating Outlook 2013 auto-complete addresses via PowerShell

Hello,
I would like to use PowerShell to add auto-complete e-mail addressees to Microsoft Office Outlook
2013. My understanding is that since Outlook 2010 was released, the NK2 file has been retired in favor of integrating the auto-complete addresses with the PST file (see link below). With that in mind, how can I manipulate the PST file to accommodate
the auto-completion? Is there any documentation on the PST file structure that would allow me to inject this information into an existing PST? If a user has multiple PST files, how do you know which one contains the auto-complete entries — are they aggregated?
http://social.technet.microsoft.com/Forums/office/en-US/f1edb3db-e28c-404b-8817-a3c001555b2d/missing-nk2-file
Cheers,
Trevor Sullivan
If this post was helpful, please click the little "Vote as Helpful" button :)
Trevor Sullivan
Trevor Sullivan's Tech Room
Twitter Profile

"The NK2 file has been retired in favor of integrating the auto-complete addresses with the PST file"
- I think this discription is not exactly.
In fact, Outlook 2010/2013 reads the autocomplete stream
from a message in the Associated Contents table of the Inbox of the mail account’s delivery store. (In another word, it is stored in mailbox site but is not on local). This
hidden message has a message class and subject of IPM.Configuration.Autocomplete. The autocomplete stream is stored on this message in the PR_ROAMING_BINARYSTREAM property (PidTagRoamingBinary
Canonical Property).
Go back to your quesion, the autocomplete data, whatever belongs which mail account’s delivery store, is temporarily cached in an autocomplete .dat file located in %USERPROFILE%\AppData\Local\Microsoft\Outlook\RoamCache.
More Reference:
http://msdn.microsoft.com/en-us/library/office/ff625288.aspx
An useful tool - NK2Edit to
http://www.nirsoft.net/utils/outlook_nk2_edit.html
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Cheers,
Tony Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please contact
[email protected]

Outlook 2013 Issues (Emails go missing when stucked in Outbox after restarted Outlook)

Hi,
I have being using Outlook 2013 for email but i have face for two main issues as below which is quite annoy me sometime.
1. Email stucked at Outbox (even is just a normal email without attahcment). Those emails which were stucked at Outbox will goes missing if i just close the Outlook and re-open the Outlook again.
2. Outlook will hangs/ freeze (showing Not Responding) when half way I just viewing my email in Inbox or I click on Calendar.
I have tried to some of the suggestion across other forums such as:
- Disable the add-in (example: Social Outlook Connector/ Lync Meeting (which i dont have it to use) and etc.)
- Checked on the Program Features and clear all the office plugin
- Change the Aero Setting in Windows
- Disable Anti Virus (Just guessing)
- Reinstalled the Office 2013 (Outlook 2013)
- recreated the Outlook profile
However after tried, the first two issue still happened and the critical part is the email will goes missing after i reopen the Outlook.
More Info:
- When the email stuck at Outbox, the Outlook is show "Connected to Exchange"
- My company is using Exchange Server 2007 R2 (not sure got any related or not)
Anyone can get help on this?!!! Thanks a lot!!!
The reason I re-posted this issue as the previous as remarked as answered but somehow after that no more ppl reply.. i need more ppl's suggestion here!!
Thank you

Hi,
Generally for emails stuck in Outbox issue, we need to try basic steps as below:
1. Work offline, move the stuck mail into another folder. Restart Outlook and Work online to send it again.
2. Temporarily uninstall or disable firewall and antivirus software.
3. Test in Outlook safe mode.
4. Create a new profile and re-setup your account.
As you have tried to disable Anti-virus, we also remind you to disable the firewall to test.
Please run MFCMAPI to check if there are emails or corrupted items that are stuck in Outbox, if yes, please delete them.
http://mfcmapi.codeplex.com/releases/view/101020
Here are some articles which use MFCMapi from where you can get some step by step guidance:
http://exchangeshare.wordpress.com/?s=mfcmapi
We can also perform a clean boot to determine if background programs are interfering with Outlook:
http://support.microsoft.com/kb/929135#appliesto
Regards.
Melon Chen
TechNet Community Support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Outlook 2013 stuck in 'updating inbox' cycle

I have a problem with a couple of users and I have never been able to find a definitive fix and its incredibly irritating.
I know a few people have has this problem, a users mailbox works fine and then suddenly it will stop sending emails, it then gets stuck in a 'updating mailbox' 'Last updated at xx:xx' cycle. This is a local install of Outlook 2013 connecting to a hosted
exchange server.
Recreating the mail profile has been done with one user at least twice and the problem still persists. It was fine last week and then this morning it stopped again. I am trying to recreate the problem on another PC for this one user as I am trying to work
out if its a connection problem or PC problem.
Any ideas?

Hi Derrick,
Are you using Cached Exchange mode or Online mode? If the user is in Cached Exchange mode, what's the size of his/her mailbox (.ost file)?
The issue may be caused by some network issue. Please check the Outlook connection status when this issue happen again. To do this, press and hold down Ctrl key, click on the Outlook icon on the system tray area, and then choose Connection Status.
Or, if possible, simply connect Outlook to a different network, then verify result.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Outlook 2013 sending replies stuck in outbox problems

I have Outlook 2013 with a maddening problem! Please keep in mind that any solutions you may have should be answered so that
mildly tech savvy such as myself can understand. The problem mostly happens when I'm replying to an email but sometimes with a fresh email. When I hit send the email just stays stuck in my outbox and I get an error message 0x800ccc0F.
I'll open up the stuck email and hit send again and nothing still stays stuck. I spent a long time chatting with MS tech support and he had me uncheck/disable all of my add ins and all my emails sent! Great! Next day without making any changes I was back
to the same problem, then later they would send fine, a day later same problem - you get the picture for the last few weeks. Rechecking and unchecking the add-ins or restarting outlook or my computer sometimes helps but the problem persists. One interesting
note while on tech support I was replying to my own test emails to myself and they were staying stuck in my outbox, but also showing up in my inbox and not showing up in my sent mail folder -WTH??? Lastly I use Go-daddy SMTP email and did tech support
with them to check all of my outgoing settings and even tried some alternate settings which made no difference. Please help as I use Outlook for work all day and have spent countless hours trying to figure this out.

Hi,
Please use your webmail to check whether the email stuck in your Outbox or Draft folder. If the issue only happens in Outlook, please disable all anti-spam or any related mail programs to have a try. Also try to create a new Outlook profile:
http://support.microsoft.com/kb/829918/en-us
If it doesn't work, please change a computer to configure your email account in Outlook to check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support

Messages stuck in Outbox until restart on Outlook 2013

hi,
We are experiencing issues with Outlook 2013 on an onpremise Exchange 2013 system.
the issue only affects users with Outlook 2013 and messages queue up in the outbox until we restart Outlook. 2010 users are fine.
The article http://support.microsoft.com/kb/2862523 describes the issue exactly but i wanted to know if anyone has fixed this issue without disabling SPI on the firewall. The article says it is a temporary workaround as it puts the clients at risk and
the last update was July 2014.
Microsoft have already verified the on premise Exchange setup as we opened a call with the Exchange team before we discovered the article.
sg

Hi Yoshi,
1. Would you please let me know whether your customer has same scenarios described by the KB (Move Sent Items from OST to local PST file) when the issue occurs?
2. Whether the issue always occurs and can be reproduced? If the issue can be reproduced, please let me know the steps which reproduced the issue
3. If the issue can always be reproduced, please let me know whether the issue occurs if you use OWA to send email or use Outlook Online Mode to send email.
~~~~~~~~~~~~~~~~
Mike Shen
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact [email protected]
~~~~~~~~~~~~~~~~

Saving a .pdf file into the network shared drive from Outlook 2013

Hello sirs,
I have one client that having the file saving issue into the shared drive from outlook 2013.
I have isolated the network portion and confirmed that there is nothing to do with the network. They have 1 host server which has 2 VMs inside (DC & FS). Whenever they want to save .pdf file into the shared drive, "Saving" message box popped up and showed for about 1 min to complete the file saving. I have tested with .xlsx & .dcsx but no error saving those files. only for this particular extension that facing this slowness problem. It has been on going for a month already and I couldn't figure it out what could be the issue.
Please if anyone experienced this issue, I would really appreciate your suggestions & guidance.
Thank you.
This topic first appeared in the Spiceworks Community

I have a script that I am trying to cobble together, but I am stuck at attempting to execute an SQL query against and ADO connection. My code is as follows:Powershell $FQDNUpper = $Computer.ToUpper() + ".domain.dn1.dn2" $FQDNLower = $Computer.ToLower() + ".domain.dn1.dn2" $shell = New-Object -ComObject "Wscript.Shell" # for use later in script $cnn = New-Object -ComObject "ADODB.Connection" $cnn.ConnectionString = "Connection_String" $cnn.Open() $queryUpper = "SELECT CAST(ID AS nvarchar(50)) ID FROM Machine WHERE Name=$FQDNUpper AND Role = 0" $rs = $cnn.Execute($queryUpper,' ',1) #If statement that will qualify if $FQDNUpper returned anything else try $FQDNLowerWhen executing the code I receive an error:
PowershellArgument: '2' should be a System.Management.Automation.PSReference. Use [ref].At line:9 char:5+ $rs = $cnn.Execute(...

Outlook 2013 not compatible with Exchange 2003

Hello
Some of my customers bought SBS 2003 R2 just before SBS 2008 was released so they have systems which are only 4+ years old. SBS 2003 came with Exchange 2003 pre-installed. Outlook 2013 does not support Exchange 2003. So they cannot upgrade their Outlook
clients to 2013 version.
Microsoft, is this correct?!

If this post is hard to read, it's because of Dragonsoft!! (sometimes it is like auto-correct on the phone - "I said WHAT!??")
Overall I think this is the most interesting thread that I have ever read on Microsoft.com.
As a computer for professional for over 30 years, I've always followed the context that software products are designed for a three to five-year term, to have more is a luxury.
When I was first in the industry (1983), Microsoft had a tendency to change the software versions every year to two years. As we approached the era of Windows XP there was an expected lifetime use of three years. Every two years a new product would appear.
So, when windows XP lasted well beyond the three-year term, it was pretty exciting to not have to spend money on new product, and we all enjoyed the decade of Windows XP.
The new generation of IT professionals has somehow believe that software products should live more than five years, and it just blows my mind!
The reason that I make this post, is because I've used SBS ever since Back Office Server 4.5, and the versions of small business server (now called Small Business Server) have always appeared on the market 1 to 3 years after the primary versions of
Windows for which they are named. So I always felt that there was a disadvantage to using small business server in that the products appearing inside of SBS had been on the market for a few years before being incorporated into the SBS package. It
made me feel, at first, that Microsoft was waiting on the level of maturity within the product before creating the SBS package. Now that I look back on the whole process it made me think that the SBS team had some difficulty merging the products into a install
package which could handle the intricacies of the licensing limitations on the SBS system.
SBS 2003 was a great tool when it came out, but I found that it was riddled with security holes. To say the least some of my first SBS 2003 servers had their exchange system hacked by outside influences. (These were external facing servers who had websites
and exchange server running with public domain names, even though there were firewalls!) After a few patches, DNS modifications, reverse DNS entries, and some changes in the exchange system, I was finally able to make the system secure and solid.
My first real nightmare with SBS was when upgrading to SBS 2003 R2, which, yes, appeared around 2005. You cannot simply upgrade a machine from SBS to a new version. You must purchase a new server, install the new SBS version, and migrate your
entire installation to this new host. (While running SBS 2003 for several years and making backups on a tape, I realized that the new hardware on the market would not support a restore from my tape backup!) The whole process is rather daunting as not
all of the detailed steps to upgrade work as expected. I had to call, and pay, Microsoft to complete the process because exchange had trouble during the migration.
So off we went with our new installation of SBS 2003 R2. Then along came SBS 2008! I went through the same steps again... new hardware, new software, and, yes, paid Microsoft, again, for support to migrate.
When SBS 2011 appeared on the scene I was willing to upgrade again. Having gone through this, twice now, I fully prepared the client to purchase a new system and to purchase the new software. But because I was faced with the whole entire
nightmare of new hardware, migration, and having to call Microsoft to complete the process, I decided on a new approach. This time we were going to buy server which would run VMware. (I was not going to get stuck in a hardware box that I could not replace
if I ever needed to restore the operating system due to a massive failure.) So off I went, purchasing a new box, installing VMware, and installing my favorite operating system, Microsoft SBS!
Well, to say the least, it wasn't exactly as exciting as I had expected. Had some trouble getting VMware to settle into the new hardware, as there seemed to be some compatibility issues, but was able to work it out. Eventually, I was able to get started
on the migration. Things went well up until the point that I got to the exchange migration, and ran into a similar problem as before! A call to Microsoft revealed that it was even a little daunting for the support personnel, but as I documented the things
that they modified, and even performed a little cleanup, after they performed their cleanup! I can happily say that I'm no longer worried about hardware issues, when it comes to restoring my SBS server in case of a failure!
Overall I'm pleased with having used Microsoft SBS solutions over the past 10 years, but I would never expect, nor would I lead my customer to expect, that a product should last 10 years!
Previous comments have indicated that server should last seven years because they can be depreciated that way, I believe that to be entirely false! I live in Texas, and the state of Texas DIR program has adopted standards which state that
you should replace your hardware every five years! State agencies have this as a requirement, and it is not optional! Many state agencies have gone to leasing their equipment, which is a three-year term. (Where do you think off-lease equipment comes
from, anyway?)
One of my primary clients looked at me one day, and directly ask, "Okay, if we spend the $10,000 on the new server and software, how long should it last?"
Obviously, I wanted to say, "Forever!" But, remembering something that my mother had said (always plan for the worst and you always come out on top!), I said back to them, "I believe we should plan for a three-year lifespan, and if we get
any more than that, it will be a luxury." Needless to say, there have been some upgrades which lasted well more than three years, but there have been some which have been spot on.
The SBS server is a huge savings over purchasing the individual products separately. But there have always been some drawbacks during the upgrade process which makes the entire feasibility of the installation top-heavy when it comes to support costs.
I have noticed is that the SBS servers require more labor to keep them running smooth, especially with backup procedures and backup software, as SBS always requires a third-party product to make a "real" (restorable) backup.
A client's expectations should be that you are taking care of their business without them having to worry about what takes place in the tech room. They understand, and realize, that they can pay you a specific amount of money for your support without necessarily
having to purchase new hardware. But a good, healthy relationship with your client means that they should always be willing to upgrade, whether it is a workstation or server.
If you allow a client to be painted in a corner, then it's not their fault, it's your fault! Because, they have no idea what the new technology can do, and don't realize what's on the market. It's your job to keep up with what's current and to deliver
expectations which make them realize that each year has a dollar value attached to it, whether it is spent, or not.
If you have a client is unwilling to spend money to upgrade their equipment, then there's something else wrong with their business, and you should probably consider that they may not be in business for very long. So don't make it your problem when
they are unwilling to spend money. You don't work for free.
One last, quick example of the conversation that I had with a client who was unwilling to upgrade because things seem to be working so well. I put it like this, "You pay me to make certain that your business operates in good times and in
bad. Right now, everything is fine. If your building were to burn, and the only thing we had were the backups, I cannot go out and purchase new hardware and restore your system successfully. The equipment that we have operating here is no longer
available on the market. If I were to find the equipment, it would be out-of-date, and most likely, used, and I cannot guarantee its compatibility or functionality. So, if I can't restore your system to an operational status, then what would you do?
I don't believe there are any number of man-hours you can use to recover the information lost. You would probably have to go out of business! If your business becomes my business, then I would try to move to a position where my data is safe and my business
can continue in the case of catastrophe. The only way I can do this, is to purchase new hardware, new software, and put you back in a position of compatibility with the market. One of the things I always try to do is keep your business operations at a point
where if I die, someone else can come in and take my place. The whole idea here is to keep your business going."
It didn't take them long to come back and surprise me, "Make a list of what you need. Don't give us a list of what we need to get by, tell us what we need to be productive for several years. We don't want to patch this together
and always have problems."
And just as a note, your customer can write off $10,000+ per year for new equipment purchases. I think the number may be higher now. I had one customer who purchased a $15,000 system in December and wrote off $10,000 in one year and the other $5000,
a month later, in the next year!

Outlook 2013 - User cannot send email to one person

One of our users got a new computer and is running Outlook 2013. They can send emails with no trouble, except to one of our other users. It always
gets rejected and the sender gets an email telling them the one they tried to send was undeliverable. She's running Windows 8.1.
1. Both the sender and the receiver are using Exchange accounts
2. Both computers are on the same network, but neither are on a domain.
3. Error message: The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: ORD2HUB16.mex05.mlsrvr.com
IMCEAEX-_O=MEX07a_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=[REDACTED]@mex05.mlsrvr.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
Original message headers:
Received: from ORD2MBX01H.mex05.mlsrvr.com ([fe80::11f4:d169:375f:62d2]) by
ORD2HUB16.mex05.mlsrvr.com ([fe80::be30:5bff:feee:c7c4%15]) with mapi id
14.03.0169.001; Tue, 10 Jun 2014 11:47:07 -0500
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: [REDACTED[ <[REDACTED]>
To: "[REDACTED] ([REDACTED])" <[REDACTED]>
Subject: email
Thread-Topic: email
Thread-Index: Ac+Ey3p8UrbavpbVRTiY+U9PepgJ0Q==
Date: Tue, 10 Jun 2014 11:47:06 -0500
Message-ID: <[email protected]com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <[email protected]com>
MIME-Version: 1.0
X-Originating-IP: [23.24.160.6]

Hi,
How does the user fill the "To" field in a new message? If she fill it via auto-complete cache, please try to delete the auto-complete cache entry via clicking the "X" icon and then type the email address in the "To" filed. Send the email and check
if this issue continues.
For more causes and troubleshoot steps about this issue, please refer:
http://technet.microsoft.com/en-us/library/dn479208(v=exchg.150).aspx
Regards,
Steve Fan
TechNet Community Support

Outlook 2013 completely stuck!

Similar Messages

Maybe you are looking for