Dec 262011

Ever since I updated my Samsung Focus, to Windows Phone 7 (Mango), I’ve been having troubles downloading attachments on the fly from my Exchange account on my server.

Typically I would open an e-mail, click on the attachment, and it would fail stating: Cannot download attachment. A work around I found for this was to hit “Back” hit the sync button, then the attachment would be available. However this was SUPER annoying.

Another feature that didn’t work was to search for items on the Exchange Server.

I did a bunch of research on this and found numerous other people who had the same issue. Their fixes would often temporarily resolve the issue, but typically the issue would come back.

Today; I installed Service Pack 2 for Exchange 2010 on my server. After doing this, I noticed that on the fly attachment downloading is now working, along with searching the Exchange Server.

To resolve this, simply install Exchange 2010 Service Pack 2.

Nov 102010

Hi guys,

I come to you today to tell you a little story about a struggle I’ve been having with BES and users who are receiving the “Attachment Server not Found” error message on their handhelds.

For a few weeks now, a few users have reported issues with opening attachments, EVERYTHING else works perfect. I updated BES, checked everything, still couldn’t find out what was wrong. The only thing I had to go on, was a few very odd log entries inside of ASCL log file.

Example of entries in ASCL log:

[10000] (11/10 18:22:53.234):{0x21B0} [thr:0x21B0] CHALogic::_group_of_extensions_t::add_server_extensions(0) – no data
[10000] (11/10 18:22:53.236):{0x21B0} [thr:0x21B0] CHALogic::_list_of_servers_t::Add(0,…) – no need to add empty STRINGS_SET
[10000] (11/10 18:22:53.236):{0x21B0} [thr:0x21B0] CHALogic::_group_of_servers_t::AddServer(0,…) – _preferred.Add() failed with rc=1007
[10000] (11/10 18:22:53.244):{0x22AC} [thr:0x22AC] CArznDelayedAttachmentResultVisitor::Uninitialize() – begin
[10000] (11/10 18:22:53.245):{0x22AC} [thr:0x22AC] CArznSocket::Close() – m_connectSocket = 0xFFFFFFFF, after
[10000] (11/10 18:22:53.245):{0x22AC} [thr:0x22AC] CArznDelayedAttachmentResultVisitor::Uninitialize() – end
[10000] (11/10 18:22:53.245):{0x22BC} [thr:0x22BC] CArznSocket::Close() – m_connectSocket = 0xFFFFFFFF, after
[10000] (11/10 18:22:53.248):{0x22C8} [thr:0x22C8] CArznDelayedAttachmentResultVisitor::Uninitialize() – begin
[10000] (11/10 18:22:53.248):{0x22C8} [thr:0x22C8] CArznSocket::Close() – m_connectSocket = 0xFFFFFFFF, after

I spent a few days googling the error “Attachment Server not found”, and came across numerous KB articles that wanted us to try this, try that, bla bla. Everything was configured properly, and the service was running. So all of these did not apply to me!

Finally I took a LONG hard stare at the errors in the ASCL log shown above, and put 2 and 2 together and realized it probably had something to do with TCP/IP communication. I finally STOPPED the attachment service, opened a command prompt and issued:

netstat -ano |find /i “Listening”

Even though the Attachment server runs on 1900, 1999, and 2000 (I could be wrong if it’s those specific ones), but even after stopping the service I noticed that there was still something listening on 2000. I used the PID issued by the -o switch on netstat, opened task manager, showed all tasks from all users, and changed the view settings to show the PID column.

BAM! Turns out some other piece of software was listening on 2000. Go Figure!

To Resolve this:

1) Log on to the BlackBerry Administrative Web Site

2) Under “Servers and components”, except the Solution topology, expand Domain, Server View, Server_Name, and select “Server_Name_AS_11”

3) Select “Edit Instance”, and then proceed to change the port (in my case, 2000 was conflicting, so I changed 2000, to 2001).

4) Restart the server!

You’re now good to go!

Aug 312010

For those of you who have tried installing Exchange SP2 on SBS 2008 but have had it fail during its initial steps, this blog post is for you!

Microsoft has created a tool that you can download and install which permits you to install Exchange SP2 on SBS 2008.

For more information on the procedure and to download the tool please see:

I cannot stress enough on the importance of a backup in case things go wrong. I have performed this at numerous client locations, most successful; however in one instance while SP2 was installing, the update failed and totally removed Exchange from SBS 2008. This was unrecoverable and a full restore from a backup would have been needed (thankfully this was the configuration of a new server so we just restarted the implementation).

Aug 202010

If you’ve tried configuring your Windows Mobile device to connect to your exchange server, but have been receiving errors on the lack of a certificate issue, this may help.

Keep in mind it’s always best to contact your local IT department to find out if they have an easier way of doing this, or a better way.

If your desktop computer at work is joined to the domain, chances are you have a certificate installed that authenticates various systems on your network. By extracting this certificate and installing it on your Windows Mobile device, chances are this will solve your issues.

Keep in mind that if your IT department did not generate your Exchange SSL cert from the domain certificate authority this won’t work.

Now let’s get started…

  1. Open Internet Explorer
  2. Press the “Alt” button to expose the menu
  3. Select “Tools” then “Internet Options”
  4. Select the “Content Tab”, and hit the “Certificates” button.
  5. Select the “Trusted Root Certification Authorities”.
  6. Now look through the list and look for something that may contain your Company’s name in it, or the name of one of your network servers.
  7. Once you find this, click once to highlight, and select the “Export” button.
  8. Go through the wizard and leave all defaults. At the very end where it asks you to choose a file, save it on your desktop and call it “cert.cer”.
  9. Copy this file to your Windows Mobile Device (using a Memory Card, or a Sync function).
  10. On your Windows Mobile device, use the File Explorer to browse to the location where you saved your cert.cer file, and select it to run. It should say “You have successfully installed a certificate”.

Now go ahead and configure your Exchange account and chances are it should work!

Keep in mind that some carriers lock down devices to avoid the installation of untrusted certificates. I haven’t run in to this issue, but I have heard about it happening. If this is the case, you will need to do some research on your phone and find a way to bypass this security block.