Let's see... how to start. Let's start with the facts. I've gone and looked up your ticket to see what had already been attempted with Outlook 2010. Here are the facts as I see them in the ticket.
[i]
Also, a caution. I do watch the forums regularly but there are times when I get side tracked doing other work. It's probable that you might not see a response from me for a few days. The best thing you can do if you feel like I'm taking too much time is to send me an email (cupcake@codeweavers.com). It would be best if we could solve this publicly so that if someone else stumbles on the same issue they might not go through the same trouble as you.[/i]
Alright, back to 'the facts':
This (your) system is Ubuntu 10.04 32bit running CrossOver 11.0.3 and attempting to run Outlook 2010 (no service pack)
Adding an account fails, miserably
Private Corporate Exchange Server
And the forum post from yesterday:> (quote:480323)
I recently purchased Crossover and had it returned because I could
not get my account to connect.
I am having the same problems now, minus the random crashes.
I just can NOT seem to connect to our exchange and use this.
For your reference (although they won't mean much) we have been working through some problems similar to what you are seeing.
Bug number 9289 is a crash of Outlook 2010 when connecting to an Exchange Server. This bug is resolved internally (not yet in a release). Unfortunately, it's resolution has revealed another nasty bug. This resolution was included with the build we asked you to test... after testing that nightly build you reported that you had tested it, it didn't work and that you wanted a refund. We provided the refund as quickly as we could; note that it takes 3-5 business days from our side and then the time your banking entity takes to release those funds.
Bug number 9518 is a dependency on MSVC++ 2008 to re-enable all of the frames in Outlook. Unfortunately adding this dependency slows Outlook 2010 to a crawl. We believe we have a resolution for this bug as well but need some time to test it's stability and verify that no other catastrophic bugs have been caused by it.
Now, that's everything I've gleaned from your ticket(s) in our system, our internal bug tracker and your forum post here. Nothing more. If I have anything in error, please let me know. What follows are my thoughts.
My first question... you say that you are having the same problems sans the random crashes. Does that mean the Exchange Server is now connecting for you? The only problems that I see are problems with trying to connect to an Exchange Server. I'm confused by 'the same problems minus the random crashes' because I was under the impression that you were never able to connect at all. Is Outlook just freezing when you try to connect now?
My second question/thought. You also state that you've looked through the Tips & Tricks here... there are only two. Have you looked into the Tips & Tricks for Outlook 2007? Quite a few of those apply to Outlook 2010. Some that stick out: "Can't login to Exchange Account on Linux", "Re-set Exchange Account" & "Connection Issues"
My third thought... and for this I have to dig through my personal notes. There are two parts to this. First, I always (ALWAYS) forget to verify that I have libnss-mdns on my Ubuntu setups (lib32nss-mdns on 64bit Ubuntu systems). Second... if your Exchange server is privately hosted, you may need to add it to your "/etc/hosts" file. It should be pretty straight forward, the first field should be the numerical address, the second is the actual server name (what you would add when you manually configure rpc over http). It should be:
XXX.XXX.XXX.XXX the.actualname.com
or
XXX.XXX.XXX.XXX the.actualname.local
The last two thoughts above are based on the assumption that you've never been able to get your Exchange Server to connect. If you've been able to connect and the issue you are now seeing is different, you'll need to describe what you are seeing in detail.
If you work through everything above (and we're not at a point where we're ready to let someone test the above solution for whatever reason) and it's still not working, I may need some log files.
Finally, I've assumed that you're reasonably tech savvy to accomplish some of the tasks in my post. If you need additional details to get something done please do not hesitate to ask. I need you to be blunt about what you've already tried... saying "I tried everything and it didn't work" does not help. Tell me what you tried piece by piece & don't leave out the details. If you did 'x' and something different happened, I want to know what that something different was.
Last parting thought... If something above does work, post back! You will undoubtedly save someone a ton of pain by doing so.