Novell Platespin Portability Suite – Cannot connect to IIS with http or https.
Myself, along with two of my colleagues, went on a day trip to this year’s IPEXPO Earls Court in London where we were shown a demo of esXpress at PHD Virtual Technology’s booth. We were very impressed by the presentation and some of the futures of esXpress. We were especially interested in the File Level Recovery features of their data De-Duplication appliance.
When I got back home from IPEXPO on Thursday, I decided to test the product for myself. So, I went on to download a 30 day evaluation from http://www.phdvirtual.com/ and I can surely say that I’ve been putting PHD Virtual esXpress 3.6 through some vigorous testing for the past few days. To start off with, I found esXpress easy to deploy and I was quite impressed with it. However I must confess that when I really started to dig into how esXpress goes about its business I started to have some concerns about it. However, I have decided not make any my concerns public until I have had a good chat with some people at PHD Virtual as I think that they will have an answer to most of my questions.
Those of us who have tried running Veeam FastSCP on 64-bit Windows found that it installs perfectly, but once you try and run the application, it comes up with an error. Someting like "Unable tp connect to (local\VEEAM)".
It's sad to say, but Veeam FastSCP does not support 64-bit operating systems at this moment in time. However I found a little workaround that will allow you to use the application on 64-bit Windows, at your own risk and unsupported it has to be said.
So here's how:
1. Download the Microsoft .NET Framework 2.0 SDK (THE 64-BIT VERSION!) from the Microsoft Website. This download is about 300MB if I remember correctly.
2. Install the SDK on the 64-bit machine that you would like to run Veeam FastSCP on.
3. Now, open a command prompt (Start -> Run -> Type "cmd" -> OK)
4. Change directory to: C:\Program Files\Microsoft.NET\SDK\v2.0 64bit\Bin
5. Now Run: corflags "C:\Program Files (x86)\Veeam\Veeam Backup and FastSCP\VeeamShell.exe" /32BIT+
6. Now when you try and run Veeam FastSCP again, it should work fine.