This a known issue with the service gui currently.  We are fixing.  Data collect works from the console itself.  This will seems a little tricky, but this should allow you to collect the logs from the console and then download them from the service gui.  1. Login to the console with the same service/service ( name/password ) defaults.   2. First can we make sure the system CPUcurrent enough?  Can you run this command?  It should say sse4_2 somewhere on that output or the physical ESX server hardware is too old to run.  If too old, you will need a newer machine. > grep flags /proc/cpuinfo  Ex output: flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc aperfmperf pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm ida arat epb xsaveopt pln pts dtherm  3.  Secondly I would like to verify that your pci devices are in the correct place.  If you run "lscpi -nn" you should see this list at the end of that output.  Can you verify that your system matches this?  If this does not match, then did you change any of the settings of the VM before you powered on? 02:00.0 Ethernet controller [0200]: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) [8086:100f] (rev 01) 02:01.0 Ethernet controller [0200]: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) [8086:100f] (rev 01) 02:02.0 Ethernet controller [0200]: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) [8086:100f] (rev 01) 03:00.0 Serial Attached SCSI controller [0107]: VMware PVSCSI SCSI Controller [15ad:07c0] (rev 02) 0b:00.0 Serial Attached SCSI controller [0107]: VMware PVSCSI SCSI Controller [15ad:07c0] (rev 02) 13:00.0 Ethernet controller [0200]: VMware VMXNET3 Ethernet Controller [15ad:07b0] (rev 01) 1b:00.0 Ethernet controller [0200]: VMware VMXNET3 Ethernet Controller [15ad:07b0] (rev 01)  4. Lastly, if not the cpu version issue and you are not missing any controllers, you can run svc_dc manually from the console command prompt and that will create the same logs as the gui would.  5. Log back in to the GUI and attempt the service action again to get the collects.  A popup should tell you that the system found a previous collect gathered.  That should be the one you just did manually.   6. Save that one locally and we can take a look.
The initial GUI that comes up wants to use the service account, not admin and the password listed in the install document does not work with either admin or service.
Virtual VNXe (vvnx) Default passwords in the install document does not work