Outlook 2010 unter Exchange 2010: Kontakte nach Excel exportieren

Hi all,
a user wants to export contacts from a shared folder to Excel. He gets following error message:
"An ODBC error has occurred in the Microsoft Excel 97-2003 translator while opening a file to build a field map.
[Microsoft] [ODBC Driver Manager] Data source name not found and no default driver specified."
No problem to Export to a *.pst file or to a *.csv file. Also no Problem to export  his own contacts to Excel.
I found the problem often described in the World Wide Web, but no solution. Does anybody know, how to solve the Problem? Or have users to live with the workaround (*.csv)?
Cheers,
Lisa
Hallo zusammen,
ich wurde mit folgendem Problem konfrontiert: Anwender will Kontakte aus dem freigegebenen Ordner seines Chefs nach Excel exportieren, erhält aber eine Fehlermeldung:
"An ODBC error has occurred in the Microsoft Excel 97-2003 translator while opening a file to build a field map.
[Microsoft] [ODBC Driver Manager] Data source name not found and no default driver specified."
Export in *.pst- oder *.csv-Datei funktioniert. Export der eigenen Kontakte in Excel-Datei ist ebenfalls kein Problem.
Der Fehler wird im Internet häufig beschrieben, jedoch habe ich keine Lösung gefunden. Vielleicht ist euch eine Lösung bekannt? Oder gibt es keine und man sollte sich mit dem Export nach *.csv abfinden?
Viele Grüße
Lisa

Please try to hold on CTRL and right click Outlook.exe to launch it with Administrator to test the behavior.
Test if we can go into excel and import an access database.
Test if we can export the calendar from outlook to a .csv file.
Try to disable add-ins from within Outlook, File > Options > Add-ins > Go
Try to reboot the machine through msconfig (without any non-Microsoft programs/Servise running).
Based on my experience, this programs might be caused by ODBC related, check if we have the enough permissions of the ODBC drivers and go to the ODBC Data Source Administrator window (Start | Control Panel| Administrative Tools | Data Sources (ODBC)), check
if there is Excel File entries under the DSN, if no, add it manually.
At last, we may also run ProcMon and find the clue  from procmon logs. Feel free to post it back. Have a good time.
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]

Similar Messages

  • Problems with a shared calendar using Outlook 2007 and Exchange 2010

    Hello all,
    We are having a problem with sharing a calendar using Outlook 2007 and Exchange 2010.
    I will start with some background. I have just started my position with this company. I have been working with networks for awhile at the small business level. I have not had much production experience with exchange. There is only myself and my supervisor
    who has inherited a midsized network which was built by five previous techs that are no longer with the company. Of course, the previous techs did not leave much documentation, so the original hows and whys for our system setup has been lost.
    One of the managers has a calendar she shares with some of our users. I believe this calendar has been in use since sometime in 2006. A mailbox was created to hold this calendar to keep it separate from the managers calendar. I am not sure what version
    of exchange they were using at that time, but I assume there was one or two migrations of it getting to its current state on our exchange 2010 server. At some point it was observed that the other workers she was sharing with were not able to access it correctly.
    I am not fully sure what the original problem was (possibly some people not being able to see or connect to the calendar), but it was decided to give everyone who needed access to this calendar full access permissions through exchange. Correct me if I
    am wrong, but I believe that gave everyone connected the ability to do anything with the calendar. Of course the manager was not happy about that. This is where I started working on the problem.
    I removed everyone, except the manager who wants to control the calendar, from having "Full Access Permissions". This did have the effect of making some people just able to see the calendar and not make changes. Though there were others that were
    able to connect to the calendar who I thought would not be able to. The manager that originally created the calendar did try to manage access to it through the Outlook interface, though it currently does not seem to be fully in effect.
    So, to get to the point of what we are trying to do, is there a way to get the original manager back into control of the calendar though Outlook? It would be preferred to be able to keep the history of what they tracked of this calendar, so starting a new
    one would be something we would rather avoid. After that, getting all of the users that need to connect to the calendar reconnected with the correct access permissions and making sure they are all synchronized.
    I realize this is a big mess, and your help would be greatly appreciated.

    Hi Nigel,
    How is the impact, just one user or all users, Outlook or OWA?
    If just one user, it seems like an issue on the Outlook Client side.
    Please trying to re-create new profile to fresh the caches.
    Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
    Found a similar thread for your reference:
    Calendar Sharing not available error message
    http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
    Hope it is helpful
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Import contacts outlook web app exchange 2010

    How to import contacts into outlook web app exchange 2010 ? Or how to import vcard files into outlook web app ?

    It is correct. Vcard and Vcalendar is a feature of Outlook.
    You should import Vcard with Outlook.
    How to use the vCard feature in Outlook
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Sync Sharepoint 2013 task on outlook running on Exchange 2010

    Sync SharePoint 2013 task on outlook running on Exchange 2010,Getting error:
    "We weren't able to sync your tasks. This could be because your mailbox is on an Exchange server that isn't supported for syncing tasks. Please contact your administrator for more help."..Please
    help!!
    SharePoint 2010 task list sync with outlook running on exchange 2010 works successfully without any error...But how to do with sharePoint 2013

    Hi Mohit,
    The "Sync to Outlook" button is a new feature in SharePoint 2013 and is different from the "Connect to Outlook" button in SharePoint 2010, and this feature also needs the Exchange Server 2013 installed in your environment, you can read the following article
    for details.
    You can get the "Connect to Outlook" button back (like SP2010) by disabling the "Exchange Task Sync feature" from CA without installing Exchange 2013, the following is extracted from the white paper.
    "How to disable SharePoint Server and Exchange Server integration.
    To disable it, you turn off the Farm Level Exchange Task Sync feature by going to Central Administration -> Manage farm features. This action deletes the timer job and disables the UI integration, bringing back the legacy sync behavior to Outlook. "
    http://support.microsoft.com/kb/2876938
    http://www.microsoft.com/en-us/download/details.aspx?id=38799
    Thanks
    Daniel Yang
    TechNet Community Support

  • Support Forefront Protection 2010 for Exchange 2010 SP3

    Hi
    I have a simple question: Is there a full support of FPE 2010 (Version 11.0.727.0) for Exchange 2010 SP3 (and Rollup Updates)?
    Thomas

    Hi,
    It seems that FPE 2010 for exchange 2010 SP3 is supported and you need to install the Rollup 4. For more detailed information, please refer to the link below:
    Hotfix Rollup 4 for Microsoft Forefront Protection for Exchange
    Updates for Microsoft Forefront and Related Technologies
    Hope this helps!
    Susie

  • Outlook 2010 using Exchange 2010 - cannot send this item after updating draft email

    I have a client who has the following setup.
    SBS 2011 server (Exchange 2010) and a Windows 2008 R2 Terminal Server (with Office 2010 SP1 installed).
    This particular user has a Windows XP PC with Office 2010 SP1 installed (joined to SBS 2011 domain).
    This user creates a email at their office on their PC and saves it in draft to continue working on it when they get home.
    At home they RDP into the terminal server and load outlook and start updating their saved (Draft) email.  They then try to send it and the following error pops up.  "Cannot send this item".
    If they try to save the changes they have made it pops up with "The operation failed".
    I have tried various settings all with the same results.
    Office 2010, Office 2010 SP1, Online mode and Cache mode (on the Windows XP PC).
    Any ideas? 

    Hi Rajkumar,
    OK. After further testing I have narrowed it down to the email signature?
    If I save a draft email in Outlook on the Fat client (Windows XP + Office 2010), then go straight into Drafts folder and open the email and add one line of text and try to send or save again it fails.
    If I don't have a signature, it works fine.
    I currently trying to determine what part of the signature it doesn't like (it is quite a large signature, multiple images and a disclaimer etc).  I'm having mixed results - I can remove the signature totally from the draft email and then it will save
    or send fine. 
    Strange that it can save the email to Draft in the 1st place but doesn't like updating it a 2nd time???
    I have also created a new outlook profile (online mode) with the same results.

  • Unable to open Public Folders in Outlook or OWA (Exchange 2010)

    Exchange 2010 Public folders can not be opened from Outlook or from OWA, in the ADIS I do not see Folder Hierarchies.  Under the public folder Management Console,i get an error that states "You cant perform this operation because public folder
    database isnt mounted.  Please mount it and try afain,  It wsas running the command ger-publicfolder -getchildren -identity "\"-server 'MBXserver'"

    Run "Get-PublicFolderDatabase" and see what it says the status of the database is.  This error implies that the database in offline.  You will also want to find the status of your public folder copies.
    Get-PublicFolder -Recurse | Ft
    or
    Get-PublicFolder -Recurse | Export-Csv PublicFolderStatus.csv -NoTypeInformation
    The first will work if you are checking a small number of folders, but you'll want the latter if you have many of them.

  • Problem with Assigning Policy button in Outlook 2010 and Exchange 2010

    First of all, I'm posting here because I'm not sure how to post in the previous version of Exchange forums.
    Secondly, I'm re-posting this from the Outlook forums as I'm not getting any responses there despite of views.
    Hi,
    I'm having an issue in Outlook 2010 where I can't assign personal policies to folders. I have setup personal tags and added the mailbox to the right policy. I have also ran Start-MangedFolderAssistant in Exchange 2010 Shell against the mailboxes.
    When I go into OWA, everything shows up perfectly, I can right-click and assign policies at will, but when I open Outlook 2010 then the Assign Policy button never appears. I force added it to the ribbon and I can see from there that the button stays grayed
    out irregardless of where I click in the folder structure. I have even assigned the mailbox user Owner rights to all the folders to see if it will  make a difference.
    If anyone can help me solve this problem I will very grateful, I'm pulling my hair out here and I'm certain I could just be missing something very obvious somewhere,
    It might be worth mentioning that the company has been using .prf files to configure Outlook thus far, I'm
    looking to eliminate that. I'm not sure if that will have any effect on my current problem.
    Thanks for your time.
    Nico

    Thanks for the reply Max, that's a pretty good link.
    Like is I said though, I have the policies all set up in the Exchange configuration side of things, when I use OWA all the options for applying tags appear. It's just in Outlook 2010 Standard that the Assign Policy button stays grayed out.
    Thanks.
    EDIT:
    This has been solved, looks like version problem with Outlook.
    http://office.microsoft.com/en-us/outlook-help/license-requirements-for-personal-archive-and-retention-policies-HA102576659.aspx

  • Help needed with buggy Outlook 2013 and Exchange 2010 trashing profiles

    Hi All,
      I have a customer who has eschewed MOLP and buys all their Office OEM from Dell.  So as a result they are starting to have more and more office 2013 be deployed.  They have a SBS 2011 server with Exchange 2010 and it is patched to the latest
    rollups and service packs.  (SP3, RU2)  Their Outlook 2010 and earlier clients are just peachy on this.  But the Outlook 2013 clients are having problems.
      What is going on is that periodically I'll get a complaint from a user that their Outlook 2013 is randomly crashing.  In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default
    and going back into Outlook 2013 and letting it rebuild the cached data on the PC.  This seems to happen a few times a month with random users on the network.
      I told the customer it was probably people not logging out of Outlook 2013 at night and their machines being power spiked but I think that's highly unlikely since it doesen't happen to the Outlook 2010 clients.
      I don't know if any Microsoft developers read this but if you do, please take it back to your bug database.  Any other suggestions would be appreciated (other than scotch Outlook 2013 - while I'd appreciate that, my customer wouldn't)

    In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default and going back into Outlook 2013 and letting it rebuild the cached data on the PC. 
    The Outlook 2013 crash problem would be fix after you re-create a new profile and re-sync the data from Exchange, right?
    When we meet the same problem in next time, I suggest we run the Outlook Product Stability Diagnostic tool to isolate known causes of crashes in Outlook. The Outlook Product Stability Diagnostic also creates a diagnostic report outlining the data it collected
    and recommendations on possible steps you can take to reduce or eliminate Outlook stability issues.
    Please click the following link to run the Outlook Product Stability Diagnostic tool in the Microsoft Fix it Center Pro portal:
    Outlook Product Stability Diagnostic:
    https://wc.ficp.support.microsoft.com/SelfHelp?knowledgebaseArticleFilter=2764035
    Other troubleshoot steps for Outlook 2013, please refer to the link below.
    Let me know the result.
    http://support.microsoft.com/kb/2632425/en-us 
    Tony Chen
    TechNet Community Support

  • Outlook 2007/2010 with Exchange 2010 missing tasks operation has failed only on PC not OWA

    We have searched this topic to no success I'm baffled as to how to resolve this problem.
    End user software: Outlook 2007 and Outlook 2010,
    Server side: MS Server 2012 R2 with MS Exchange 2010
    Scenario: We have merged 2 forests together to a new forest. Months before hand had rolled out exchange 2010. A majority of users in
    forest2 still are on Office 2007 where as users in
    forest1 are nearly all on Office 2010.
    Now so far we have 3 users (from Forest2) whom have reported 'missing tasks' with the message 'Operation has Failed' when attempting to view their tasks. 
    We have ran the outlook commands related to this type of issue that clear the reminders and resetting them with - No Success.
    They have no issue when using OWA, or Outlook via mobile device. The issue only occurs on PC. We have tried profile rebuilds, fresh SOE, the issue appears to be resolved but the next time the user opens Outlook the problem comes back.
    On the server we have ran all the integrity checks no corruption has been found in any way.

    Hi,
    I recommend that you try the following method on client PC and then check the result:
    Click Start >> Click Run >> Type outlook.exe /resettodobar
    >> Click OK. 
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Outlook 2010 to Exchange 2010 connectivity problem

    We have a single Exchange 2010 server running DB, CAS, and HT this lives at our Corp HQ. We have 12 offices connected across MPLS and 2 offices connected across a Metro-e 100mb connection. We have had this environment in place for almost 2 years with no
    issues. 
    Today in the office connected across the 100mb metro-e connection had a momentary network hiccup where all uses lost data momentarily.   Connectivity to data and network resources restore immediately, but after that time, none of those users could
    connect to Outlook 2010.   When they try to connect outlook times out with an error that it cannot connect to the server.
    I can ping the exchange server by name and ip.   Response times are less than 7ms.  Utilization on that connection is less than 10%.  DNS is resolving.
    Users can connect to OWA and get access to email.
    The problem is only happening in only the one office.  All other remote sites are functioning fine. 
    Users can access all other network resources with no issues, including OWA and Intranet/Internet sites both HTTP and HTTPS.  
    I believe that it may be something is blocking the RPC connection.   If I try to run the Connection which also fails to connect. 
    I have rebooted the Exchange server
    I have rebooted the local DC in the remote office with the problem.  Also reset DNS.   And on clients tried flush/register DNS. 
    No server changes have been made on any of the servers involved. 
    Only changes taken place prior to the network "hiccup" happening was network admins implemented QOS on the routers to give priority to SIP/voice traffic.  According to them, this will have no impact on other data. 
    Any ideas or suggestions on next steps for troubleshooting?

    Hi
    Did you they not make any routing changes? Can you ask them to check that all ports for exchange are open and also ask them if they made any other changes?
    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Outlook 2013 with Exchange 2010

    we upgraded from Outlook 2010 to 2013 x64it and the exchange server is the same 2010
    when trying to cleanup public folders the Clean Up tool is grayed our and it says "outlook 2013 this feature is not available because you are running in online mode and connected to microsoft exchange server 2007 or earlier" none of this is true.
    It works fine when you are in your own inbox, only grays out in Public folders, this worked fine with Outlook 2010
    David

    Hi David,
    Sorry for the late reply.
    Since Outlook 2010 works well, just Outlook 2013 has this issue, I still believe this issue related to the Outlook 2013 Client side.
    I suggest also create a thread on Outlook Forum so that we can get more professional suggestions.
    For your convenience:
    https://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
    If this issue really related to the Exchange 2010 server side, I suggest re-setting the default public folder database for testing.
    Please make a back up for the current setting in case of some crash. If it doesn't work, please back to the current setting.
    Then please follow following article to change the default public folder database:
    Change the Default Public Folder Database for a Mailbox Database
    http://technet.microsoft.com/en-us/library/bb629522.aspx
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Outlook 2010 and Exchange 2010 SP3

    Hello,
    we are planning to upgrade from Exchange 2010 sp1 to SP3, most of client PCs has Windows XP sp3 and Oultook 2010 with VSTO addins working with mapi properties.
    I need to know if there are any known issues between this client environment and Exchange 2010 SP3 ??
    thanks a lot,
    Mauricio.
    Mauricio

    Windows XP is not supported in any scenario, so yes, I'd call that a known issue.
    Mike Crowley | MVP
    My Blog --
    Planet Technologies

  • OST corrupt when moving Mailbox from Exchange 2010 to Exchange 2010

    Anyone come across this?
    Moving a mailbox on Exchange 2010 to Exchange 2013 - the outlook client wont connect, if you remove the OST and allow outlook to recreate it comes good again.
    outlook client knows the mailbox has moved as it connects to the new server
    Not happening to every mailbox
    thak=nks

    Hi,
    After you move mailbox from Exchange 2010 to Exchange 2013, Outlook should still work.
    Is there any error message when these affected users try to connect? If there is, please post here for further analysis.
    I saw someone failed to connect to the new Exchange server after they moved mailbox, then they restarted the Microsoft Exchange Information Store service and restarted Outlook, it worked.
    If you haven't tried this, you can restart the Microsoft Exchange Information Store service to check the result.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Lync 2010 with Exchange 2010-2013 Migration?

    We are installing Lync 2010 for the purpose of internal LAN and Internet/Federated instant messaging, video chat and desktop sharing.  
    There is no telephone integration and there is no Unified Messaging used in Exchange 2010.
    Within a few months after rolling out Lync 2010, Exchange 2010 is going to be migrated to Exchange 2013.  Outlook will remain at Office 2010 and Lync client will be 2010.  We will continue to not use Exchange Unified Messaging after Exchange is
    upgraded to 2013.
    Are there any steps required to keep Lync 2010 working normally after the Exchange environment is upgraded from 2010 to 2013 in this scenario?

    Hi 
    During the migration and post migration to EWS URL for the user i reachable by the Lync 2010 Client 
    And the outlook client is able to establish a Mapi session with the mailbox all should be fine
    as best practice please have the Lync 2010 and outlook 2010 client update to the latest CU update 
    There is known issue when migrating from Exchange 2007 to 2013 good to know information 
    http://silbers.net/blog/2013/12/19/lync-ews-broken-during-exchange-20132007-transition/
    Please remember, if you see a post that helped you please click ;Vote As Helpful" and if it answered your question please click "Mark As Answer" Regards Edwin Anthony Joseph

Maybe you are looking for