A client recently upgraded their Exchange 2007 environment with cummulative update 18. Upon reboot, the owa was non operational. The quickest fix for a damaged owa is:
Beside the regular culprits, an offline database will cause Intellisense to fail as well.
Every now and then I'll throw a Response.Write() in my code to do some debugging. It always messes up the entire layout of the page when I do that, but I never really bothered to know why. After all, it’s just a temporary situation.
It appears that our run of fairly benign VS SP’s is over…
First and foremost, if you're using Office 2010, Paradox support has been removed (http://technet.microsoft.com/en-us/library/cc179181.aspx). You'll need Access 2007 or earlier.
Ah, the DELL rebranded EMC Clariion AX4 (AX4-5SC, AX4-5, etc). It's awesome, but man do those Vault drives (and DELL/EMC support) make it so unfriendly.I’ll skip most of the background, and just get right to it.
First and foremost: This is an account of my experiences. Your experience will probably differ, and you’ll probably lose all of your data. Try this at your own risk.
We picked up a couple of these devices through an acquisition and they simply didn’t have drives large enough for our intended use. Upgrading the non-Vault drives is simple… pull out, plug in. Of course, you have to use EMC formatted drives (non-EMC SAS/SATA/FC drives will NOT work), which are pretty hard to procure from EMC directly without a valid support contract. It turns out that DELL is actually pretty well aligned to get these. Some of our other suppliers had month+ waits, but DELL had them to us in a few days.
Now, the Vault drives: The Vault drives are the first 4 drives in the AX4-5 (0,1,2,3). You can identify them by the little yellow stickers that warn you not to move the drives from their location. And you shouldn’t. The Vault drives contain OS, config and other information. If you pull these drives from the system, it will not fully boot (you can still connect via serial). If these drives fail in a certain sequence, the same fate will ensue. Simply put, you need them to be healthy.
If you do happen to trash the Vault drives for any reason, you can buy the 4-pack formatted and pre-loaded through DELL/EMC, but there is a premium, and finding someone who can actually get the part numbers is difficult at best.
Upgrading the Vault drives is generally a taboo subject for the end user, and I don’t condone it either. I’m sure it voids your warranty, lights Churches on fire, and brings Justin Bieber to haunt you in your sleep… but if you’re not using them in a production environment, or you buy them second hand on eBay, what the heck, right? I’m in.
This is not about upgrading Vault drives by using new Vault drives, as I don’t have any experience with that. When we put in a new 4-pack of Vault drives, we just swap them entirely and destroy any arrays/pools that are already created because we generally are putting in larger disks and want to be able to utilize the entire space.
EMC Powerlink is EMC’s customer portal. http://emc.powerlink.com
You can sign up for a free account, register your AX4-5, and then access firmware, downloads, support, etc.
Anyway, upgrading the Vault drives by using non-Vault drives:
1) The AX4-5 should already be fully initialized. If it’s not, there is a tool that comes with the system to do this. It can also be downloaded from the EMC Powerlink site. Navisphere Storage System Initialization Utility.
2) I’m 99% sure that all of the Vault drives have to use the same interface as each other, and you probably want to match the old Vault drives too. If you have SAS vault drives, use new SAS drives. SATA = SATA.
3) The size of the new drive has to be greater than or equal to the old Vault drive size.
4) DISCONNECT all hosts attached to the device via Fiber or iSCSI.
I don’t know when it started or why, but I love Halloween (and autumn for that matter). So keeping the tradition of Halloween alive, I’ve decided to share some “horror” stories from the software/IT field over the next few weeks.
A post just came across the forum I frequent regarding Hexadecimal to Floating Point conversion. Strangely there appears to be no direct way to do this in .NET, and the solutions I found were pretty lame and tedious… so it became my mission to get it done the .NET way, and here is the result:
With all the hype surrounding 3D desktop interfaces these days, it's always fun to take a look back at some of the projects that have helped us to get where we are now: http://research.microsoft.com/adapt/taskgallery/