This turns out to be a problem with how the URL for the PersistenceServer is built when running under Windows 2003 Server. We'll have it fixed in our September release.
Until then you have several options:
- you can use Remoting instead of WCF for an IIS implementation
- you can continue with WCF and IIS but on another OS
- you can use either the ServerConsole or ServerService instead of IIS
- you can contact support if you positively must have this working before September :)