Enterprise Vault – Error: 0×80070780 “The file cannot be accessed by the system”

Enterprise Vault thumbnail image - a filing cabinetI experienced this error when trying to delete or overwrite placeholders left by Symantec Enterprise Vault.

The scenario was that we’d migrated our shared data drive from one VM to another by means of copying/attaching the VHD to a new fileserver VM. The new VM didn’t have the Symantec File System Archiving (FSA) agent installed, and therefore also didn’t have the NTFS filter drivers installed.

FSA uses “Reparse Points” to create placeholders for archived files. You’ll see this error if the File Blocking driver and Placeholder drivers aren’t installed.

Even though I’m not going to be using FSA on the new server, I had to install the Enterprise Vault FSA agent. That resolved my problem, and I was then able to restore the files over the top of the placeholders.

Posted in SysAdmin | Tagged , | Leave a comment

NLB on a Hyper-V host

Just a quick gotcha I came up against when I was trying to set up a CAS array on my Exchange 2010 boxes. I kept getting errors when trying to set up a unicast NLB cluster, and the nodes wouldn’t converge.

I ended up figuring out that I had to enable MAC address spoofing on the virtual NICs. The cluster needs to assign the same MAC to both cluster NICs, and this isn’t possible without having that checkbox ticked. This feature is only available in Hyper-V since Server 2008 R2 was released.

I was going to write a more detailed article about it, but as usual, Paul Cunningham’s great blog has it covered already in detail with screenshots.

Posted in Exchange Server, Virtualisation | Tagged , , , , | Leave a comment

Some good Hyper-V and Failover Cluster tips on TechNet

I’ve been browsing the Hyper-V related articles on TechNet while planning to move over to a failover cluster, and have found some useful tips. The TechNet articles are a literal goldmine of information if you can be bothered reading through it all.

They answer some of the initial questions I had when first implementing Hyper-V

If you change the configuration of a virtual machine, we recommend that you use the Failover Cluster Manager snap-in to access the virtual machine settings. When you do this, the cluster is updated automatically with the configuration changes. However, if you make changes to the virtual machine settings from the Hyper-V Manager snap-in, you must update the cluster manually after you make the changes. If the configuration is not refreshed after networking or storage changes are made, a subsequent failover may not succeed or may succeed but result in the virtual machine being configured incorrectly. original here…

For iSCSI: If you are using iSCSI, each clustered server must have one or more network adapters or host bus adapters that are dedicated to the cluster storage. The network that you use for iSCSI cannot be used for network communication. In all clustered servers, the network adapters that you use to connect to the iSCSI storage target should be identical, and we recommend that you use Gigabit Ethernet or a faster network adapter. original here…

You cannot use teamed network adapters, because they are not supported with iSCSI. original here…

On a failover cluster that uses Cluster Shared Volumes, multiple clustered virtual machines that are distributed across multiple cluster nodes can all access their Virtual Hard Disk (VHD) files at the same time, even if the VHD files are on a single disk (LUN) in the storage. original here…

Software requirements for using Hyper-V and Failover Clustering: All the servers should have the same software updates (patches) and service packs. original here…

Posted in Virtualisation | Tagged , , , | Leave a comment

Windows Phone 7, one month in

A month ago, I thought it would be good to try out Windows Phone 7 to see if I liked it. The plan was that I could always revert to my trusty iPhone 3GS if I didn’t. That plan came unstuck when my iPhone got wet whilst I was out running. The phone works well, except for the SIM card reader, and is deemed “irreparable”

One of the things that was holding me back from moving away from the iPhone was that RunKeeper hadn’t yet been released on WP7. It was released on the 9th of March, but I didn’t realise how limited the functionality was compared to the iPhone version until I actually used it.

I bought a Samsung Focus on eBay for around $330 AUD landed and unlocked, and so began my journey. I already started having issues with the phone as soon as it arrived; I needed to ring Microsoft to activate it. This is unusual, and I assume it’s because my phone is running a pre-release version of WP7, 7003. I discovered this after powering on the phone for the first time.

ATT-focus

The Samsung Focus itself is actually quite nice. It doesn’t have the quality feel of an Apple device, but it’s light and has decent specs. I put in a 16GB MicroSD card, so I’ve got around 22GB of total storage. It’s light, and the OLED screen is bright and easy to read.

Now that AT&T have released the “NoDo” update for WP7, I’m still unable to update my phone. It’s not a stolen “demo phone”, but still Microsoft feel the need to block updates to 7003 devices – even though my Focus the same physical phone as others that are receiving updates.

Here’s my list of things that I like about the phone, as well as what I dislike. I’m actually really looking forward to moving back to an iOS device as soon as possible. Apart from the things mentioned on the list below, there are other things I miss such as the Juniper JunOS Pulse VPN client, being able to connect to my work’s hidden WPA-PEAP WiFi network, and stable RunKeeper and Endomondo apps amongst other things.

Dislikes:

  1. No multi-tasking
  2. No phone backups like in iTunes, so if you have to nuke your phone or swap phones you’ll be spending hours reconfiguring
  3. No inbuilt e-book reader. All e-book reader apps (for generic e-books, not Kindle) are rubbish
  4. Slow. Apps stutter when scrolling though lists. Not just one app, but the majority of them
  5. No task integration in Outlook. Come on, Exchange and WP7 are both MS products
  6. No mass storage mode when plugged in to a PC. Even the iPhone gives you limited access to just photos and videos. WP7 expects you to have Zune installed and paired
  7. Apps get featured on the marketplace even though they’re buggy and don’t work properly. Looking at you, Endomondo
  8. Hardly any live tile support for major apps. Facebook? no Twitter? no. No push notifications for these apps at all
  9. Live tiles are buggy. The AU Weather Pro app has heaps of issues with live tiles, and their devs blame the platform so I’ll tend to believe them
  10. This one really pissed me off – no iCal sync via web calendar URLs. Hello?
  11. Can’t connect to hidden wireless networks. This is supposedly for security purposes.
  12. Limited theme colours. The available colours get old pretty quickly
  13. Hardly any quality apps. Heaps of junk on the marketplace
  14. Apps are limited compared to their iPhone counterparts due to limited hardware access in WP7. You only need to look at Microsoft’s own developers releasing PhotoSynth on iPhone first, due to the fact that they couldn’t do it on WP7 at the moment
  15. If you configure a passcode lock, you can’t disable it without wiping the phone
  16. Address book lookups don’t work properly for all Exchange accounts
  17. Too easy to touch music player controls on the lockscreen if you’re carrying your phone around
  18. Microsoft’s refusal to update 7003 devices, even if they’re a non-developer device
  19. Hard to navigate around with more than 10 rows of live tiles on the home screen
  20. Navigating the marketplace and finding top apps in certain categories is painful.
  21. Can’t select multiple photos in order to share or delete them
  22. No tethering over Bluetooth, or easy tethering using the cable. I know it’s possible to tether with the Samsung Focus, but it’s not a simple menu item. You have to do into the diagnostic menu to enable it.
  23. In typical Microsoft fashion, many apps require you to give them “run under lockscreen” permissions. Why should then end-user care about this? Just make it work, and don’t bother them with it.

Likes:

  1. Better looking than the iPhone interface. iOS’ interface is starting to look dated
  2. People hub integration with Facebook, etc is excellent. Being able to merge info from multiple accounts is great.
  3. Predictive text system is better than the iPhone’s. It offers better suggestions, and a better method for picking between those suggestions. Also, editing words you’ve typed previously is easier on WP7
  4. Dedicated camera button, and the fact that you can take photos without unlocking the phone
  5. Being able to block caller-id sending to people who aren’t in your contact list is a really simple and smart idea
  6. SkyDrive integration is good for photos
  7. Sharing photos is easy, as accounts integrate into the “Share” menu. If you’ve configured your Facebook account, you get a share option for Facebook.
  8. Pinning stuff to the homescreen is handy. Pin your favourite contacts, or an office document.

Other stuff:

  • Mobile IE7 works fine. I didn’t have any issues browsing sites.
  • Phone functionality works well
  • There are hardly any kid’s games available on the marketplace at the moment. I had a whole page full installed on the iPhone that were very handy for keeping my daughter amused when I took her with me to the barber, for example.
  • Music functionality works well

One thing that I’ve observed it that it seems harder for people to transition between two different smartphone platforms, as opposed to moving from a “dumb” phone to a smartphone. You’re used to the apps that were available on the old phone’s platform, and the way your old phone did things.

As it stands, I wouldn’t recommend WP7 to anybody. I just recommended an Android phone to my brother last week as an upgrade from his Nokia N8. Once the “mango” update comes out, Nokia get on the bandwagon properly, and another year or so has passed, I think the platform will be a compelling alternative to Android/iOS. Just not yet.

Posted in Uncategorised | Leave a comment

IIS 7.5, WCF Error: "the requested content appears to be script and will not be served by the static file handler"

Had a problem developing a WCF service to grab data out of Sitecore, which is running on IIS 7.5 in my dev environment. I published the service in the config-free manner, but was getting an error:

the requested content appears to be script and will not be served by the static file handler

After searching around for a bit, I found a post on the MSDN forums that responded to a different error message, but the solution worked for my problem also:

You will need to run ServiceModelReg.exe -i from the “%windir%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation” directory to register the script maps

To quote MSDN:

Registers this version of WCF and update scriptmaps at the Internet Information Services (IIS) metabase root and for all scriptmaps under the root. Existing scriptmaps of lower versions are upgraded to this version.

Installing: Machine.config Section Groups and Handlers (WOW64)
Installing: Machine.config Section Groups and Handlers
Installing: System.Web Build Provider (WOW64)
Installing: System.Web Compilation Assemblies (WOW64)
Installing: HTTP Handlers (WOW64)
Installing: HTTP Modules (WOW64)
Installing: System.Web Build Provider
Installing: System.Web Compilation Assemblies
Installing: HTTP Handlers
Installing: HTTP Modules
Installing: Protocol node for protocol net.tcp (WOW64)
Installing: TransportConfiguration node for protocol net.tcp (WOW64)
Installing: ListenerAdapter node for protocol net.tcp
Installing: Protocol node for protocol net.tcp
Installing: TransportConfiguration node for protocol net.tcp
Installing: Protocol node for protocol net.pipe (WOW64)
Installing: TransportConfiguration node for protocol net.pipe (WOW64)
Installing: ListenerAdapter node for protocol net.pipe
Installing: Protocol node for protocol net.pipe
Installing: TransportConfiguration node for protocol net.pipe
Installing: Protocol node for protocol net.msmq (WOW64)
Installing: TransportConfiguration node for protocol net.msmq (WOW64)
Installing: ListenerAdapter node for protocol net.msmq
Installing: Protocol node for protocol net.msmq
Installing: TransportConfiguration node for protocol net.msmq
Installing: Protocol node for protocol msmq.formatname (WOW64)
Installing: TransportConfiguration node for protocol msmq.formatname (WOW64)
Installing: ListenerAdapter node for protocol msmq.formatname
Installing: Protocol node for protocol msmq.formatname
Installing: TransportConfiguration node for protocol msmq.formatname
Installing: HTTP Modules (WAS)
Installing: HTTP Handlers (WAS)
Posted in ASP.NET | 2 Comments