Outlook 2013 Contacts sharing in exchange

I am trying to share my contacts in Outlook 2013 and keep getting the message "error trying to send your sharing message" can you help please.
I have checked the other questions and have picked the name from the GAL, made sure I am an administrator and am trying to share my main contacts.

Hi,
Please make sure your Outlook 2013 is using Exchange Cached mode and try to create a new Outlook profile to have a try:
http://support.microsoft.com/kb/829918
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

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 contacts backup

Hi,
we are using outlook 2013 for email communication.Our account is pop account.I want to take the backup of contacts in outlook 2013.
Please share your ideas how to take the backup of contacts of email outlook 2013.
Regards
Pradeep

Follow the steps below to take the backup of Outlook 2013 contacts:
1. Click File > Open & Export > Import/Export.
Import/Export command in the Backstage view
2. Click Export to a file, and then click Next.
3. Click Outlook Data File (.pst), and then click Next.
4. Select the account you want to export by clicking the name or email address
5. If you want to export everything in your account, including mail, calendar, contacts, tasks, and notes, ensure the Include sub-folders box is checked
6. Click Next.
7. Click Browse to select where to save the Outlook Data File (.pst) and to enter a file name. Click OK to continue.
If you are exporting to an existing Outlook Data File (.pst), under Options, specify what to do when exporting items that already exist in the file.
8.Click Finish.

OUTLOOK 2013 permission shared calendar Free/Busy doesn't work for some the users Exchange 2010 and Exchange 2003 that use outlook 2007/2010

Hello,
We are in coexitence organisation (transition Migration) Exchange 2003 sp2 and Exchange 2010 sp1.
Users in Exchange 2003 use outlook 2007 and outlook 2010
Users in Exchange 2010 use outlook 2007, outlook 2010 and outlook 2013.
Issue: users in Exchange 2003 can't open outlook 2013 user calendar when he has Busy/Free information as default permission in his calendar.
User in Exchange 2010 with outlook 2007 can't also open outlook 2013 user calendar when he has Busy/Free information as default permission in his calendar.
Is it normal ? or exist some configurations to do in order to coexist all thoses clients and servers ?
Thanks in advance

Hi,
Does this issue occur on Outlook only or both Outlook and OWA?
Since you have double checked the permissions via multiple methods, it seems there is nothing problem on permission. Please make sure the migration from Exchange 2003 server completed successfully.
If in OWA everything goes well (cannot see details), it should be an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I suggest re-create profile to refresh the caches.
Thanks
Mavis
Mavis Huang
TechNet Community Support

After upgrade to outlook 2013 Contacts have the default picture in reading pane

I'm using Windows 8 on a domain (using a domain account not a Microsoft account) connecting to Exchange, all my Contacts were outlook contacts with pictures and other data, I could see the picture of the contact in the reading pane and people pane while
using Outlook 2010.
After the upgrade to Outlook 2013 the contacts are not lost (I can see them in the People Hub) but it appears that they are unavailable in the reading pane because all I can see is the default picture (the default picture picture is also visible in the notifications).
If I put the mouse over the name of the people while in the reading pane all I can see is the card with the default info (the only data visible is that the contact is available in the next 8 hours), if I compose a new message and hover the name of the contact
i can see the card with all the data (picture, company, etc.).
Is this the default behavior in Outlook 2013 if you are in a domain and not connected to any service or there is a way to show the picture of my contacts in every part of outlook?

No, it should be available still. Did you recreate this mail profile after the upgrade?
Try forcing a complete update of the Office Line Address Book via the Send/Receive tab-> Send/Receive Groups-> Download Address Book
Otherwise, reset the OAB by renaming your oab-file to .old when Outlook is closed. You'll find them here:
C:\Users\%username%\AppData\Local\Microsoft\Outlook\Offline Address Books\<Account GUID>
Robert Sparnaaij
[MVP-Outlook]
Outlook guides and more: HowTo-Outlook.com
Outlook Quick Tips: MSOutlook.info

Outlook 2013 (Only) - Shared Mailbox - Not Syncing

Hi
After searching this forum and many other forums online, I have decided to ask my question here as I cannot find a solution.
We are migrating from Exchange 2003 to Exchange 2010 at the moment. All of a sudden our Outlook 2013 users (All of them) cannot update Shared Mailboxes. When you select that folder it says "Updating this Folder" but nothing is happening. Only happens
with their open Shared Mailbox not with their own Mailbox. I have done the following tests:
Users can open the Shared Mailbox and sync properly using OWA.
Users can open the Shared Mailbox but cannot sync via Outlook 2013.
Users can open and sync the Shared Mailbox via Outlook 2010.
Ran OST repair tool, no luck.
Completely deleted the profile and wiped all the files in the outlook folder and recreated the profile, no luck. (Not syncing straight away.)
Users can sync the Shared Mailbox when they are running outlook in Online mode. (I dont wanna do this coz they want to save their sent emails from a Shared Mailbox into the respective "Sent Item" folder which only works in Cached Mode.
Everything used to work fine and suddenly stopped for everyone. Can you please guide me on how to fix this?
Thanks in advance.
With regards
M
PS
I just realized that my Build Version is "Version 14.1 (Build 218.15)"
I am downloading the Service Pack 3, and it might help?

Hi,
It seems that the issue only happens in Outlook 2013 Cached mode. If you add secondary mailboxes to your profile through the Advanced
tab in the Microsoft Exchange dialog box, please check whether the “Download Shared Folders” is enabled in the Advanced tab.
If it is, the Sync issue occurs may because Outlook 2013 locally caches (in your Outlook data file [.ost]) all folders to which you have access in the secondary mailbox. To resolve it, we can refer to the detailed solution in the following KB:
http://support.microsoft.com/kb/2297543/en-us
Thanks,
Winnie Liang
TechNet Community Support
Hi,
I found this little tick yesterday and did clear it. So now people can still have their own mailbox cached and the rest online. But thank you for the link coz I couldnt find it before and it is good to know that it is a known issue rather than being a misconfiguration
at server level :) I have marked your post as the answer. Thanks again.

Outlook 2013 (365) shared mailbox sent items

We have a new 365 installation with Outlook 2013 clients and Exchange 365. We have a number of shared mailboxes with delegated full access as required. We have applied the "DelegateSentItemsStyle " registry key in Office 15.0/Outlook/Preferences
but this is not working to place a users sent mail in that mailboxes sent items, in either OWA or the desktop clients. Any clues?

Hi,
How did you modify the registry key?
Please follow the steps below to modify the key, check the result:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully.
For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft
Knowledge Base:
322756 How to back up and restore the registry in Windows
Press Win + R, type regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Preferences
On the Edit menu, point to New, and then click
DWORD Value.
Type DelegateSentItemsStyle, and then press Enter.
Right-click DelegateSentItemsStyle, and then click
Modify.
In the Value data box, type
1, and then click OK.
Exit Registry Editor.
Regards,
Melon Chen
TechNet Community Support

Outlook 2013 treating Shared Calendars differently

I did try to ask this in a
different forum, but was pointed to this one:
This question encompasses a few Microsoft products, but I think this is the best place to ask the question because the actual issue is Outlook 2013 for Windows desktop.
We have Outlook connecting to a couple of different kinds of Shared Calendars. The problem is it is only performing appointment reminders for one of the kinds.
The one that IS working: a shared calendar created by creating a Room on a Windows Phone. When anyone in the Room creates an appointment with a reminder on that calendar, the reminder goes off in each user's Outlook 2013.
The one that IS NOT working: a shared calendar created in Exchange Online. When any member of that shared mailbox creates an appointment with a reminder on that calendar, the reminder DOES NOT go off in each user's Outlook 2013.
The question: How do we get the reminders to work in the second case?

Are the room calendar appointments added to the user's default calendar in Outlook? If so, they will get a reminder in Outlook. (They aren't added to my calendar here - I only get a reminder on my phone - the Room lives only on my phone.)
Shared calendars are in another mailbox and reminders don't fire in those mailboxes. If the user has owner permissions and opens the shared mailbox by adding it to their profile they should get reminders. File, Account Settings, double click on the
account, then More Settings - select the shared mailbox to add it to the profile.
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter

Outlook 2013 cannot connect to Exchange 2010 SP2 server, Outlook 2010, OWA work fine. Ideas?

After upgrading a laptop from Outlook 2010 to 2013 it can no longer connect to our Exchange 2010 SP2 environment. OWA works, Outlook 2010 works, but Outlook 2013 will not create a profile via AutoDiscover. The first two checks go, the last check
Log On To server will not.
We can take the laptop to a different network and it works fine with Outlook 2013.
What is different with Outlook 2013 where it will not connect.
Jason Meyer

Does it work when we recreate a new Outlook profile?
At this point, We high recommand that we run Microsoft Connectivity Analyzer Tool from the folloing link to check what was happening
https://testconnectivity.microsoft.com/
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]

Trying to connect a home computer using Outlook 2013 to my business Exchange server 2010.

I have a new Dell XPS with Outlook 2013 installed and the native email client installed. I was able to enter in my exchange 2010 credentials to the native email client and it worked. when I try to enter the credentials for Outlook 2013 I received an error
message.
"the name cannot be resolved. the connection to Microsoft Exchange is unavailable.
outlook must be online or connected to complete this action"

Hi,
To narrow down the cause, I’d like to recommend the following troubleshooting:
Check if you can connect to your Exchange server externally with another account.
Double confirm the error message when test your RPC over HTTP connectivity.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Outlook 2013 not connect with Exchange server 2013 in internal network

Hello All,
I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network.
Can you please suggest as soon as possible.
Thanks,
Parvez

Hi,
Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
Thus, let’s try the following resolutions:
1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
3. Check if the above host name is in your certificate.
Thanks,
Angela
Angela Shi
TechNet Community Support

Changing outlook 2013 contact so they will not receive winmail.dat files - missing settings

trying to change email properties of a contact in outlook 2013 who keeps receiving winmail.dat from one of our guys , trying to get to internet format to change that setting.
I have made the registry change suggested here http://www.slipstick.com/outlook/use-outlooks-contacts-contact-cards/
but though I can get to properties now, I still do not see Internet Format.
I do not even see it when I create a new contact.
what am I missing?

Hi,
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Best Regards,
Steve Fan
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

Outlook 2013 Contact manager cannot create database

Hi,
I have installed my Office 2013 Home & Business on a Windows Server 2012 R2. My outlook 2013 is working. Thereafter I downloaded the 2013 Contact manager and tried to create a database.
An error message from Business Contact Manager for Outlook 2013 Database Tool says
'Cannot retrieve the list of SQL Server instances. Please make sure that SQL Server 2005 or greater is installed and that the service is running.'
I have also installed an older versions of SQL Server 2008 - I have the same error message. It seems that the BCM software cannot detect the older SQL server 2008 also.
Any pointers for me to resolve this?
I dont find any thread that deals with my problem. Since then, I have installed the SQL Server 2008 and it still does not read the application. The error is as below.

Hi,
Please refer to this kb below:
https://support.microsoft.com/en-us/kb/942496
Althought the kb is for Outlook 2007, it can still be a reference in your scenario:
This problem may occur if the SQL Server (MSSMLBIZ) service is not running. The SQL Server service is required by Business Contact Manager. This problem occurs because the Windows Welcome screen may prevent the SQL Server service from starting when you first
restart the computer after you install Office Outlook with Business Contact Manager.
Please try if this helps:
Exit Outlook.
On Desktop, right-click This PC, and then click Manage.
Click Services and Applications.
Double-click Services.
In the services pane, click SQL Server (MSSMLBIZ).
Click Restart the service.
Exit Computer Management, and then start Outlook.
If the issue persists, what does the event log messages say? If there's not much private, please post the logs in the forum.
Regards,
Melon Chen
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]

Only sync Outlook 2013 contacts to iCloud?

I don't want sync calendars, mails to iCloud, I just want to sync contacts in Outlook 2013 to iCloud. Can I choose that?
Thanks

Since you only want to sync Contacts -- what about using iTunes? Here's some info. Obviously, it has some issues ... but maybe you'll have better luck?
Then someone posted this in another forum -- please note I don't know if it works as #2 concerns me:
1. Un-installed iTunes.
2. Deleted the AppData/Roaming/Apple Computer folder (***Careful: This contains all the back-ups. You can do a copy of this folder, but delete it from AppData/Roaming.)
3. Re-started Windows.
4. Downloaded and installed latest version of iTunes.
5. De-activated all plug-ins from outlook except for the iTunes plug-in.
6. Plug-in your iPhone and sync

Outlook 2013 not automatically configuring Exchange (2007) account when running the Auto Account Setup

In previous versions, once I launched Outlook, it would automatically detect/passthrough my username and email address into the fields so that I could just click next and be done. In Outllok 2013 on Windows 2008 R2 this doesn't appear to be working even
thought I am able to successfully resolve my autodiscover domain.

Hi,
Is there any error when you can’t connect your Outlook 2013 to Exchange 2007?
If the autodiscover service is configured correctly, please change a computer to have a try. In this local windows 2008 R2, please check the following settings in Internet Explorer:
Click Settings > Internet Options > Connections > LAN settings, please make sure there is no proxy server set there. Only “Automatically detect settings” option is checked.
Regards,
Winnie Liang
TechNet Community Support

Outlook 2013 Contacts sharing in exchange

Similar Messages

Maybe you are looking for