Windows Phone 7 syncing to online Exchange results in Error 85010014

I upgraded my phone to the Mango update yesterday. Everything went fine except or so I thought. This morning I noticed that my phone hadn’t synced to the company’s Exchange account (Microsoft BPOS) for over 10 hours. When I forced a sync, it resulted in the following error message:

Not Updated
There’s a problem with red001.mail.microsoftonline.com. Try again later.
Last tried xx seconds ago
Error code: 8510014

I screwed around with the configuration for more time than I should have. I tried reentering the server. I tried entering the password again. I even removed the account from the phone and recreated it.

I even went to the Mobile Devices section on OWA and removed the device and then removed the account AGAIN.

Nothing worked.

This evening I stumbled onto something that did work.

I recreated the account on the phone (for the fourth or fifth time) and received the error again. On a whim, I unchecked all the content types under the Content to Sync section (Email, Contacts, Calendar and Tasks). I then issued a sync and it worked! I then added Email and re-synced. That worked! I continued to add the other three items, one at a time and followed by a re-sync.

Now everything is good again.

Installing SQL Server “Denali” CTP3 on Windows 8 Preview

I, and I’m sure many other developers, have been eager to begin experimenting with developing on Windows 8 and building Metro style apps. I was fortunate to attend //build and receive one of the Samsung 700T tablets with Windows 8 and Visual Studio 11 already loaded. Unfortunately my wife and daughter also enjoy the tablet so it’s not available to me for long programming sessions.

So in order to make everyone happy, I have installed the Win8 Preview in a VM under VMware Workstation 8. Here’s the configuration:

Host: Windows 7 running VMware Workstation 8
Guest: Windows 8 Preview (build 8102), 2GB RAM, 2 processors and 40 GB SCSI hard drive

I installed Visual Studio 11 without any problem other than the fact that it installed SQL Server without giving me any choice for the configuration. The easiest way to remedy that was to uninstall SQL Server and then reinstall it.

You can probably guess that the reinstall didn’t go smoothly. If it had, there’d be no reason for this post, eh?

I started by download the installer from MSDN. There are a few choices depending on whether you wanted 32bit or 64bit, with or without tools. I pulled down the 64bit package that had the tools.

Then I copied it to the VM.

I double-clicked the .EXE, it unpacked into a temporary folder, a command windows briefly flashed and then nothing. So I did what anyone would have done. I double-clicked the .EXE again and watched the same sequence of events unfold. “Ah!” I said. I must need Admin privileges! No problem, I launched a command window as Administrator, navigated to the folder and ran the .EXE.

Same results as before.

I was confused because SQL Server had already been installed on the machine. I had just uninstalled it!

In the process of poking around on the machine, I ended up in the “Turn Windows features on or off” section of the Uninstall dialog. It was in there that I noticed that .NET 3.5 was not enabled. I enabled it, went back to the command prompt and retried the installer.

Something happen this time:

The installer can’t find .NET 4.0 but 4.5 is on the box! I hit Continue and the SQL Server Installation Center dialog appeared on the screen.

It was easy sailing from this point!

By the way, you’ll see this windows pop up a lot!

The installation continued without any problem and I was able to successfully install SQL Server “Denali” CTP3.

The unhandled exception dialog appeared again when I tried to close the SQL Server Installation Center dialog:

Hitting the Quit button finished closing the dialog.

If you’re curious, here are the SQL Server apps as they appear on the Win8 Start page:

And here’s the new SQL Server Management Studio

Notes from //build/ - Windows 8

I attended the Microsoft //build/ conference last week. This was the public world’s second introduction to the next version of company’s OS, Windows 8. It was also the first time that any real depth about the product was provided. The general consensus from those I spoke with was they were very pleased with the features shown.

Metro style apps

First, and most obviously, the Metro style from Windows Phone 7 has been brought forward as the primary user experience in Windows 8. Along with that, the OS has been optimized for touch but the stylus, mouse, and keyboard are all still supported.
 

(Attribution: Microsoft Corp.)

Note: It was pointed out that the correct capitalization is “Metro style apps” with a lowercase “S” on style and a lowercase “A” on apps.

The Start button has been morphed from a popup to an entire screen that consists of 1x1 or 2x1 “Live” tiles.
 

The Start screen has all the apps that were pinned. There is an Apps screen that can be reached via Search. It contains all the apps that are installed:
 
You can imagine that this screen could become quite crowded once a user starts installing apps. To help with this, Microsoft has introduced Semantic Zoom. Semantic Zoom used the “pinch zoom” gesture but instead of making the image larger, the entire view can be changed, providing something that is useful.

Using Semantic Zoom on the Apps page changes the view to:
 
Semantic View was demonstrated on the Start page for the keynote, but it has been disabled in the Windows 8 preview that Microsoft released to the public.

Live Tiles

The content of the tiles can change to reflect information that is important to the user. The intent is to create a personal connection with the user. For example, the Stocks application will cycle the most recent information for each stock symbol that the user has added to the application. This will continue even if the application has been suspended.

 

Suspended?

Yes. When the user navigates away from an app, the app will be suspended. The app will be notified that it is being suspended and given an opportunity to save any transient state. When the app is launched, it will be given an opportunity to restore that state. This is the Tombstone functionality that is currently used by Windows Phone 7 applications.
There is no concept of closing an app within the Metro style. Windows 8 will take of that for you.

Developing apps

A controversy was created when Windows 8 was first introduced to the public. Microsoft announced that HTML5 and JavaScript were the tools that would be used to create the new Metro style apps. At //build/ we learned the truth: Use what you know.

“Use what you know” was the tagline attached to the conference title and the message that Microsoft was delivering. At //BUILD/ Microsoft introduced a new development platform for Windows: Windows RunTime or WinRT. Using WinRT, a developer can create Metro style apps using:

-    C/C++
-    C#, VB.Net
-    HTML5 & JavaScript
 

(Attribution: Microsoft Corp.)

The best way to think of WinRT is as the Base Class Libraries for Metro style apps.
I plan to do another article that addresses WinRT.

And .NET?

.Net is still an applicable platform for developing both Metro style and Desktop (think traditional) apps. Not all of the .Net framework is exposed when developing a Metro style app. Where there is functionality that is duplicated with WinRT, or not allowed, those .NET APIs have been hidden.

Is Silverlight dead?

Microsoft did not deliver any message about Silverlight during the conference. Silverlight will be supported in the Desktop version of IE (The Metro style version of IE does not allow any plugins, for security and stability). I don’t expect Microsoft to make any announcement about Silverlight in the near term. This is a preview version of Windows 8. We are a long time from RTM.
There are still a lot of solutions to deliver, and since Silverlight will continue to be supported by Windows 8, I feel that Silverlight is still a valid solution platform.

Is a Metro style app written in HTML5 & JavaScript accessible via the browser?

Nope. A Metro style app is not a web page. They must be installed from the App store (consumers) or side-loaded (Enterprise).  Don’t let the HTML5 & JavaScript fool you. This is just the choice of presentation platform and language. It is no different from choosing XAML and C#.

Getting started

The keynotes, and most of the sessions, were recorded and are available on the //BUILD/ website (www.buildwindows.com).
The preview of Windows 8 can be downloaded from the Windows Dev Center (http://msdn.microsoft.com/en-us/windows/apps/br229516). One download contains a preview of both Visual Studio Express 11 and Expression Blend. If you’d rather install them yourself, you can download them separately from the Visual Studio website: (http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27543).