Comments on: Vizioncore vRanger 4.0 Pro Crashes vCenter 2.5 Update 3, 4 and 5

By: Virtualization Master

Virtualization Master — Sun, 11 Oct 2009 20:05:02 +0000

Well, it might help to look how these replication production compare. Check out how vizionCore esxReplicator compare to Veeam backup & replication at:
http://www.itcomparison.com/DR/VizioncorevsVeeam/VizioncorevsVeeam.htm

I hope that help some one,
Enjoy,
Erick

By: laez.nl » Vizioncore Releases vRanger v4.1 DPP

laez.nl » Vizioncore Releases vRanger v4.1 DPP — Mon, 28 Sep 2009 11:03:25 +0000

[...] the new version of vRanger. The reason why I’m really happy with that is that the issue that vRanger 4.0 DPP crashed Virtual Center at startup has been [...]

By: laez

laez — Fri, 11 Sep 2009 10:40:24 +0000

@PiroNet I definately agree that the patch or release should really come out soon. Vizioncore is taking really long to fix this -in my opinion- rather serious issue. It _WILL BE_ Mid-September next week, so I'm really anxious if they will make it in time!

By: Caipirinhaonice

Caipirinhaonice — Fri, 11 Sep 2009 10:24:31 +0000

I hit the same problem yesterday!

The following logs describe the Problem!

[2009-09-10 19:46:58.388 'App' 2156 error] Win32 exception: Access Violation (0xc0000005)
[2009-09-10 19:46:58.388 'App' 2156 error] Write (1) at address 0×000094
[2009-09-10 19:46:58.388 'App' 2156 error] eip: 0x17669fb esp: 0x3e3f680 ebp: 0x3e3f680
[2009-09-10 19:46:58.388 'App' 2156 error] eax: 0x3e3f694 ebx: 00000000 ecx: 00000000 edx: 0x3e3f601 edi: 0x781c5a4 esi: 0x3e3f730
[2009-09-10 19:46:58.481 'App' 2156 error]

vRange becomes more and more worse. We had so much trouble in the past with Version 4. I think we will change to anther vendor soon!

By: PiroNet

PiroNet — Fri, 11 Sep 2009 08:20:52 +0000

Glad to hear that Vizioncore will release a ‘patch’ or would I say an product update for mid-September. There is a simple workaround available but guys the bug is hanging around for +8 weeks now I would expect a patch released before a product update. Anyway better than a crappy patch quickly released and creating more bugs than it fixes…

@Josep, downgrade is not an option here. The differences between both products are huge. Just to mention that VCB is not used anymore in DPP.

By: snore mouthpiece

snore mouthpiece — Sat, 05 Sep 2009 01:27:12 +0000

snore mouthpiece…

This is guranteed to cure you snoring. No need for mouthpieces, sprays, surgery or other drastic measures. 100% natural…

By: natural cure for sleep and snoring problems

natural cure for sleep and snoring problems — Fri, 04 Sep 2009 16:14:57 +0000

natural cure for sleep and snoring problems…

If the problems of snoring are too much to bear please don’t rush out and get a snoring mouthpiece. These are usually ill fitting and don’t work. I found a 100% natural cure that is a lot more comfortable than trying to sleep with something stuffed i…

By: Jason Mattox

Jason Mattox — Sat, 29 Aug 2009 14:55:03 +0000

It would be in the upcoming 4.1 release in Mid-Sept.

By: laez

laez — Fri, 28 Aug 2009 10:42:53 +0000

@Jason Mattox Is the following solution mentioned in the "What is VMware or Vizioncore doing to resolve this issue?" section of the KB-article already implemented in the 4.0 DPP version? Or will it be fixed in the upcoming 4.1 release in Mid-Sept.? Quote from KB article: To combat this Vizioncore has added in additional API checks into vRanger Pro DPP to ensure that Virtual Center is fully ready for its VMware provided API’s. If not, vRanger Pro will wait, disconnect and reconnect to Virtual Center and try again until Virtual Center is fully started and is not providing a false positive about its readiness to serve VMware provided API’s, this will remove the issue with vRanger 4.0 and Virtual Center 2.5x.

By: Jason Mattox

Jason Mattox — Thu, 27 Aug 2009 21:48:42 +0000

If anyone is interested and you would like to read about the technical details, you can revisit the above KB, Thanks!