The VIC has crashed on my a few times since updating to VC2.5U1. This is running on the Virtual Center server (W2003 Standard SP2) using remote desktop. It seems like just clicking around can do it, the vic just disappears when it happens.
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 4/16/2008
Time: 11:51:34 AM
User: N/A
Computer: SGVCENTER
Description:
EventType clr20r3, P1 vpxclient.exe, P2 2.5.0.1, P3 47f1523d, P4 mscorlib, P5 2.0.0.0, P6 4333ab80, P7 32f8, P8 21c, P9 system.io.ioexception, P10 NIL.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 76 00 70 00 78 00 .v.p.x.
0018: 63 00 6c 00 69 00 65 00 c.l.i.e.
0020: 6e 00 74 00 2e 00 65 00 n.t...e.
0028: 78 00 65 00 2c 00 20 00 x.e.,. .
0030: 32 00 2e 00 35 00 2e 00 2...5...
0038: 30 00 2e 00 31 00 2c 00 0...1.,.
0040: 20 00 34 00 37 00 66 00 .4.7.f.
0048: 31 00 35 00 32 00 33 00 1.5.2.3.
0050: 64 00 2c 00 20 00 6d 00 d.,. .m.
0058: 73 00 63 00 6f 00 72 00 s.c.o.r.
0060: 6c 00 69 00 62 00 2c 00 l.i.b.,.
0068: 20 00 32 00 2e 00 30 00 .2...0.
0070: 2e 00 30 00 2e 00 30 00 ..0...0.
0078: 2c 00 20 00 34 00 33 00 ,. .4.3.
0080: 33 00 33 00 61 00 62 00 3.3.a.b.
0088: 38 00 30 00 2c 00 20 00 8.0.,. .
0090: 33 00 32 00 66 00 38 00 3.2.f.8.
0098: 2c 00 20 00 32 00 31 00 ,. .2.1.
00a0: 63 00 2c 00 20 00 73 00 c.,. .s.
00a8: 79 00 73 00 74 00 65 00 y.s.t.e.
00b0: 6d 00 2e 00 69 00 6f 00 m...i.o.
00b8: 2e 00 69 00 6f 00 65 00 ..i.o.e.
00c0: 78 00 63 00 65 00 70 00 x.c.e.p.
00c8: 74 00 69 00 6f 00 6e 00 t.i.o.n.
00d0: 20 00 4e 00 49 00 4c 00 .N.I.L.
00d8: 0d 00 0a 00 ....
Did you perhaps install the VIC and Virtual Center 2.5U1 from the ZIP file released prior to the MD5 checksum fix? There is a thread out there detailing that there were problems with the MD5 sum on the ZIP file download that was causing problems for some people.
Why, yes I did. I'll have to get the new version and figure out what needs to be updated...
I would just completely uninstall Virtual Center and the VIC and do a fresh install if that is an option for you. Of course, if you are worried about your database, back that up first.
That's possible, but kind of a pain. So I looked to see what the differences are, to see how likely it is to have a software fix. After unzipping the new zip, and windiff'ing with the old directory, I only see four different files.
.\vpx\customlinks.xml only in D:\software\vmware\old\VCenter.2.5U1 ->>> DELL Oem links
.\vpx\vmpartnercustomize.cmd only in D:\software\vmware\old\VCenter.2.5U1 --> run's the VBS file
.\vpx\vmpartnercustomize.vbs only in D:\software\vmware\old\VCenter.2.5U1 --> modifies the MSI with partner (sets PARTNER_CUSTOMIZED_VC=1)
.\vpx\vmware virtualcenter server.msi different (D:\software\vmware\old\VCenter.2.5U1 is more recent, because it was partner customized).
I don't know what the effect of installing the partner customized version is, but it seems pretty clear to me that it should have nothing to do with my VIC crashes. Thanks anyhow, I'm going to call VMware support. It might be that the VIC isn't supported on W2003 in Terminal Server...
Hmm, well good luck.
I can tell you for a fact that VIC works well under Windows 2003 terminal services. I have never had a problem with it.
I have the same problem, but only when the Update Manager Plugin is enabled in VIC.
If I disable the plugin, VIC doesn't crash anymore.
Thread moved to the VirtualCenter 2.x forum
Tom Howarth
VMware Communities User Moderator
Just experienced the same problem. Once the update manager plug-in is enabled, the client is unstable with a mscorlib error in the event viewer. We installed from ZIP and not ISO. Any ideas?
We removed the update manager component and left the database intact and then reinstalled VMWare Update Manager. During the reinstall, the installer said that it had to upgrade the VMWare update manager database, so it looks like it never updated the update manager in the first place!
I have an open ticket with VM-Ware for this. As interim, we downgraded the infrastructure client to the one shipped pre update1. This works fine and we have no errors. I will hopefully get an answer whether upgrading the c,ient is necessary at all when upgrading to VC update 1.
/Daniel
hey man had the same problem and installed the new update manager client and was able to open the client
then i got this error
http://communities.vmware.com/thread/141902;jsessionid=C4614CDCACB30C2F714E3D79EC4F7E6B?tstart=1
folloed these instructions and everything is fine now