Outlook 2013 won't start with Exchange 2003 on the network

Hello All,
I have outlined my problem below, If someone could please help me that would be great!
Environment
==========
SBS 2003 Server Running AD and Exchange 2003
Clients are Windows 7 with Office 2013 and Outlook 2007 (to connect to existing 2003 Server)
Issue
=====
I am in the process of Migrating off of SBS 2003 to Office 365. The situation is that my customer needs to keep the SBS 2003 server until end of life where they will at that time determine a upgrade path. They however do not want to use Exchange
anymore. I have migrated their mailboxes successfully to Office 365.
The problem that I am running into is with Outlook 2013. Because Exchange 2003 server still exists in the network I am unable to launch Outlook 2013. I get a Message
"The Resource that you are trying to use is located on an unsupported version of Microsoft Exchange Contact your e-mail administrator for assistance"
I have tried to create a new Outlook profile. However since the exchange server exists still it auto discovers the server for the account.
Questions
========
1. What is the best workaround for this situation? My customer still needs to keep their SBS sever for their domain and plans on retiring the server before Server 2003 End of Life this coming server. (Upgrade is not an option, nor is getting
rid of the Domain, they are a small company).
2. If I disabled the Exchange services on the server would this work? Would outlook 2013 not detect Exchange
2003 on the network?
Basically I need to force Outlook 2013 to look at Office 365.
3. Configuring Outlook 2013 to manually connect to Office 365? The problem here is that how do I locate the server name for the manually connection? I have found some blogs that say to use Remote Connectivity Analyzer https://testconnectivity.microsoft.com/
but I cant seem to get that to work.
Any ideas?
Thanks!

Hi,
Please refer to the following article to check your migration steps from Exchange 2003 to Office 365:
http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx
If all mailboxes are moved to Office 365, Outlook 2013 would use Autodiscover service to connect to your Office 365. Please make sure your Autodiscover service is configured correctly in Office 365. Also
verify that all the DNS records and Public Folder are updated and pointed towards Office 365 services. If there is any question about migration to Office 365,
we can ask a question in Exchange Online forum for more suggestion:
https://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

Outlook 2013 slow to start with Outlook 365 on Windows 7

Hi,
I get to work, start up my PC. It's windows 7.
The first thing I do is kick off Outlook 2013 which piggy backs off office 365.
It takes a minute for the splash screen to appear, another minute of watch dots fly across the splash page then a minute while add-ins get applied.
Why does it take so long for the first two phases to complete?
What add ins do I actually need? I've disabled those I think surplus to requirements, but in reality if Outlook 2013/0ffice 365 need them why do they need to be added in at all?
Thanks.
K
Note: this post was originally at
http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/outlook-2013-slow-to-start-with-outlook-365/45b18f1c-5c70-4d69-aea7-4562efbe147f?rtAction=1392808530575
but I have since been advised to post it here to.

Hi,
According to your description, outlook 2013 connects to Exchange online server very slowly.
If yes, we can try the following methods to narrow down the cause of the slow performance:
1. Try start your Outlook in safe mode, and check the launch speed;
2. Check if you have enabled Cache Exchange Mode, if no, enable it and try start Outlook, and check the launch speed;
3. Create a new profile with no email account, try start Outlook, and check the launch speed;
4. Create a new Profile with the other email account, try start Outlook, and check the launch speed;
Since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Thanks for your understanding in advance.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

HELP! my work ipod touches won't synch with Exchange anymore after the 5.1.1 upgrade

HELP! my work ipod touches won't synch with Exchange anymore after the 5.1.1 upgrade

I may have solved it from another post....the "sync music" tab wasn't clicked under "Summary/Music". I had recently downloaded a more recent version of iTunes, and it may have defaulted to that....sigh.....

Outlook 2013 can't communicate with Exchange 2013

we're just finishing migration to Exchange 2013 and found some Outlook 2013 clients (migrated from Exchange 2010) can't communicate with Exchange 2013. even if i recreate the Outlook profile.
what worked is to reinstall Office 2013. just want to get ideas why a reinstall fixed the problem.
same outlook proxy is there in the account settings.

Hi,
What was the symptom that Outlook couldn't communicate with Exchange 2013? Could you please detail this a bit?
If the Account Settings are completely same before and after the reinstallation, we can say the cause is not on the Exchange side. While I can't guarantee the root cause based
on the provided information. A reinstallation fixes the corrupted or missing components/files in Office, but it's hard to say what has been fixed during the reinstallation.
If you still have some Office 2013 clients that have not been reinstalled, try to run Microsoft Office Configuration Analyzer Tool to quickly identify problematic configurations in Outlook:
https://www.microsoft.com/en-us/download/details.aspx?id=36852
Regards,
Melon 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 click
here.

Lion Mail.app won't sync with Exchange 2003

Hello,
After upgrading to Lion, I am having an issue with my Exchange email in Mail.app. I get new emails, however if I file any emails from the Inbox into another folder and then leave view another folder or exit Mail, when I return the emails are back in the Inbox again. It is as if Mail is not syncing my changes up to the Exchange account.
This issue did not begin until I moved to Lion. I have compared my settings to another co-worker, who is also on Lion and connecting to Exchange 2003 and everything appears to be the same.
Thoughts? Solutions?

RevRangwar,
Yes, I think I was. I went ahead and removed my Exchange account from Mail and re-created it as Exchange IMAP, and it appears to have resolved the issue.
Thanks for the help.

Imac G5 won't start with Isight plugged into the firewire port.

I went to turn on my Imac today and it wouldn't start. After checking all the usual culprits (power strip, outlet and power chord) which were not the problem, I proceeded by unplugging all the external devices from the back ports. After unplugging the computer for a few seconds and plugging it back in (which I read resets any power issues), it turned back on. I plugged my Isight camera back in and turned it on and the computer suddenly shut off. I reproduced this quite a few times and it did the same thing. It won't even turn on if any device is plugged into the firewire port. Does anyone have a clue of what this conflict could be or experienced anything similar.
I would greatly appreciate any input.
Thanks in advance,
Daniel

Welcome to Discussions - try resetting your PRAM, if that doesn't work, I'm afraid there is something wrong with your logic board, where the firewire bus is located. The best thing to do would be to take it in for servicing.

Outlook 2007 won't start with 10.1.3 installed

Hi,
I'm trying to a do a fresh install of 10.1.3 on a windows XP machine that is running outlook 2007. The install goes ok but when I start Outlook I get the following error
"Cannot start Microsoft Office Outlook. Cannot open the Outlook window. The set of folders cannot be opened. Either you don't have sufficient permissions, the server does not support creating folders in this location or the server does not support certain characters in the folder name. Please try moving the folder or renaming it”
Does anybody know what could be causing this?
Thanks

Hi,
The user is an administrator on the PC.
I'd already tried installing into a fresh profile but I still get the same error message. I looks like something is trying to create a new folder when Outlook starts up and the Oracle Collaboration Suite does not like it But I can't work out what that could be. I can't turn on logging either because Outlook exits as soon as I acknowledge the message.
Thanks

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 will not start up

Outlook 2013 Will not start. Get the following message:
"Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The information store could not be opened."
We have Microsoft Office 365 Home Premium edition. We are using an exchange server for email. We have confirmed that the email has been set up correctly and we do know that Microsoft was able to fix it once. After they left the remote
session, we shut down Outlook and restarted it. We received the same error message as written above.
Microsoft did tell us it was an Outlook software issue.

Hi,
Please check if Outlook can start with the switch "/resetnavpane":
Press Win + R and type “outlook.exe /resetnavpane” in the blank box, then press Enter.
If this issue persists, we need to create a new profile to setup the account, then test if this issue still exists:
http://support.microsoft.com/kb/829918/en-us
Regards,
Melon Chen
TechNet Community Support

Outlook 2013 crashes at start -

Outlook 2013 crashes at start. ntdll.dll error
Tried with:
Programs&Feature / Office 2013 - REPAIR
Creating new Outlook profile
Creating new local profile
Please help.
With best regards
bostjanc

Hello again bostjanc,
Doing an online scan is a lazy approach and still holds doors open for viruses to survive the scan. Most smart viruses will detect if a scan is in progress and thus hide themselves from
the scanner. Corollary: You can NEVER trust an online scan even if it finds viruses! (there might be others too).
A better but yet not foolproof way is to do an offline scan where any possible virus is not given the chance to start executing itself and thus hiding from any virus scan. The virus
scan software database must be updated and hold all possible existing viruses (which is of course impossible). It's, however, a better approach than letting a possible virus dictate the outcome of an online scan.
With the hope that you will reconsiderate your IT Policy ...
Best regards George

OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.

hi ALL
OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
Exchange environment contains 2 Exchange Mailboxesserver ,( one Failed , virtual Machine)
2 cas Servers
first databases could not be mounted but after we run the below command , users can use OWA but outlook could not connect
Start-DatabaseAvailabilityGroup -Identity DAG -MailboxServer MBX1
please support
thanks

Hi,
According to your description, I understand that Outlook client cannot connect to Exchange server 2013 while one member of DAG failed.
If I have misunderstand your concern, please do not hesitate to let me know.
I want to double confirm whether all account store in MBX1 experience this issue, users in MBX2 works fine.
Please run following command to double check the database status:
Get-MailboxDatabase –Status | select Name,Mounted,MountedOnServer
If it works in OWA, the issue may be related to Outlook side. Please run “Test E-mail AutoConfiguration” and “Outlook Connection Status” to get more details, expecial the setting of proxy server, it’s more helpful
for further troubleshooting.
Additional, please try to recreate a profile for testing. Besides, please move active DB back to MBX1.
Best Regards,
Allen Wang

Require Passcode Immediately with Exchange 2003 and iPhone 3.0?

Before I upgraded to iPhone 3.0 I was syncing with Exchange 2003 SP2 and I had set my passcode to be required after 1 hour, which was changed from the default of 4 hours. On the Exchange server we have a policy in place to have a max of 12 hours before a passcode is required which works on my WM phones.
After upgrading to 3.0, the phone now immediately requires a passcode every time I turn it on. I went into the settings to change it to be a little longer, but the only option is to have it Immediately and I have lost all of the other options. Is there a way to get back at least 1 hour or something that reflects the 12 hour setting on my Exchange server?

I can confirm that you just need to turn OFF Mail, Contacts and Calendar sync within the Exchange account, set the timeout 4 hours (or whatever - it will automatically shrink down if your Exchaange administrator's policy is more restrictive), and then turn back ON Mail, Contacts and Calendar sync.
Note you'll get a scary warning that says all your Contacts and Calendar data will be deleted from the phone - Outlook users can ignore if you're syncing with Outlook, since it will re-sync when done.

Unity 4.2 voice mail only with Exchange 2003

Hi Team,
we are replacing window 2000 OS with Win 2003 for unity 4.2. This is a single box solution. Exchange 2000 is installed on same unity server. Now we are upgrading the OS from 2000 to 2003. With window 2003 we have to installed the Exchange 2003. In unity installation 4.0(5) following paragraph is mentioned which means we need separate hardware for Exchange. Kindly advise whether we need a separate server for Exchange 2003 or we can install on the on unity box.
If you are using Exchange 2003, install Exchange 2003 administration software on the Cisco Unity server. (Exchange 2003 is installed on a separate server.)
If you are using Exchange 2000, you can install Exchange 2000 either on the Cisco Unity server or on a separate server. If you install Exchange 2000 on a separate server (typically for systems with a large number of subscribers), install Exchange 2000 administration software on the Cisco Unity server.
BR
Muhammad Irfan

Thank you Javalenc,
I can understand from following that Exchange 2003 can be installed on same server.
Voice Messaging
•Exchange 2003 on the Cisco Unity server or on a separate server. If you want to install Exchange 2003 on the Cisco Unity server, note the following:
–The Cisco Unity server must be running Windows Server 2003.
–Exchange 2003 can be installed only on the currently shipping servers supported for use with Cisco Unity 4.2 (MCS-78xx-x2, MCS-78xx-x3, or later, including IBM and HP equivalents). Currently shipping servers are listed in the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/
As you know we are just replacing the OS, from win 2K to 2k3. So any thing I need to take care to back up the existing Unity with win 2000 and exchange 2000..
I am taking the back up of my unity 4.2 installed on window 2000 with DiRT and will restore on unity 4.2 with win 2003 and Exchange 2003.
Kindly advise.
BR

Calendar entries made on my Windows 7 desktop in Outlook 2013 do not synch with my iphone

calendar entries made on my Windows 7 desktop in Outlook 2013 do not synch with my iphone
However, entries that I make on my iphone do update my computer.
I have setup and icloud account.

Hello bobeyay,
Thanks for using Apple Support Communities.
Please follow the steps in the article linked to below to troubleshoot this issue of your iOS devices not being recognized by iTunes.
iOS: Device not recognized in iTunes for Windows
http://support.apple.com/kb/TS1538
Take care,
Alex H.

My macbook pro won't start up. Instead of the apple logo appearing in the start up only a grey folder with a ? At the center appears

My macbook pro won't start up. Instead of the apple logo appearing in the start up only a grey folder with a ? At the center appears

Boubert,
the question mark in the folder typically represents the inability to recognize a valid filesystem on the volume being booted from. You can try this, although it might not make a difference: boot your MacBook Pro into Recovery mode by holding down a Command key and the R key as it starts up. Once the OS X Utilities menu appears, select Disk Utility. On the left-hand side of the Disk Utility window, select your internal disk’s boot partition (typically called “Macintosh HD”). On the right-hand side, select the First Aid tab if it’s not already selected, then press the Verify Disk button if it’s not greyed out; if it is greyed out, or if it reports that errors were found, press the Repair Disk button. Once the verification/repair is completed, exit Disk Utility and select Restart from the Apple menu to restart in normal mode. Is it able to boot normally now?

Outlook 2013 won't start with Exchange 2003 on the network

Similar Messages

Maybe you are looking for