(Solved) MS Outlook 2010 Crashes on Virtual Desktop (Faulting application name: OUTLOOK.EXE)

Note:   This issue has been fixed in latest Zimbra Connector "ZimbraConnectorOLK_8.0.8.1180_x64.msi"
Removing old Zimbra Connector and installing the latest version resolved the Outlook Crash issue


Troubleshooting:-

1- Closed Outlook and launched it again.  (Crashed)

2- Reboot Desktop and launched Outlook.    (Crashed)

3- Logged in as Administrator, MS Office 2010 launched fine. (No Outlook profile configured) 

4- Deleted Outlook Profile from Control Panel > Users Accounts and Family Safety > Mail and Configured profile from scratch, but issue still persisted. 

5- Unassigned User from the VDI and assigned a new spare VDI to that User.

Solution:-

1- Deleted User's profile. (Note: Make sure you have a backup of the User's Profile so you can restore it.)

2- Login to problematic Desktop using Administrator and delete the User's Profile from .

3- Run gpupdate /force and reboot the Desktop (if there are any policies applied).
4- Ask User to login . Make sure new profile is created under .

5- Make sure Profile is created correctly i.e. it has My Documents, Desktop, Downloads etc.

6- Once profile is created, launch Outlook and configure new Zimbra Profile from scratch. 

7- It will start Synchronizing emails from the Zimbra Server. (Note, Sync will take it's time to import emails from the Zimbra Server).

8- Once Sync is completed on the Desktop, launch Outlook and this time it started smoothly.

9 To verify it works fine, closed the Outlook and Launch it again. It was working fine.

;)

(Solved) Problem with upgrading from ESXi 5.1 to 5.5 error “Cannot run upgrade script on host.”.

I was upgrading an ESXi 5.1 server via the update manager to version 5.5. I kept receiving following error during upgrade: “Cannot run upgrade script on host.” After seeing the error, the Host rebooted with version 5.1.

Exploration of the file/var/log/vua.log, showed me the following passage:


VUA exiting
Alert:WARNING: This application is not using QuickExit(). The exit code will be set to 0.@ bora/vim/lib/vmacore/main/service.cpp
--> Backtrace:
--> backtrace[00] rip Vmacore::System::Stacktrace::CaptureFullWork(unsigned int)
--> backtrace[01] rip Vmacore::System::SystemFactoryImpl::CreateBacktrace(Vmacore::Ref&)
--> backtrace[02] rip Vmacore::Service::Alert(char const*, char const*, int)
--> backtrace[03] rip Vmacore::Service::AppImpl::Init(Vmacore::Service::Config*)::do_quick_exit::invoke()
--> backtrace[04] rip /lib/libc.so.6
--> backtrace[05] rip /lib/libc.so.6
--> backtrace[06] rip /usr/share/vua/vua

Method 1: 

I fixed the problem by re-installing HA agents and then updating once more. This proved to be successful solution. 

Method 2: 

1. Disconnect Host from HA cluster
2. Delete/Switch off HA clusters (completely)
3. Execute the following command line on the Host:


cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp
chmod +x /tmp/VMware-fdm-uninstall.sh
/tmp/VMware-fdm-uninstall.sh

Above "Methods" resolves the issue.

Following link can be helpful for furthur details:
 http://virtualrealization.blogspot.ch/2013/12/vum-errror-during-remediation-of-esxi.html