Error 3221684229 Installing Exchange 2007 (Mailbox Role) - On Windows Server 2008 R2 and OWA not working

Hi,

this post is composed by a couple of issues that can appear when migrating exchange 2003 to 2007.
Since Exchange 2007 is an old software if you install it today on a Windows 2008 R2 Server you can get this error: Error 3221684229 Installing Exchange 2007 Mailbox Role.

I found this post that helped me out.

http://www.petenetlive.com/KB/Article/0000262.htm

Solution as easy as running the installer on Vista  compatibility mode.

This generated next problem, it was a typical install and all roles where installed except the mailbox.
After changing compatibility mode I added Mailbox Role.

Then we starting trying the server and OWA web page appeared but it didn't authenticate.
Finally I found two posts that help me out:

http://exchangeserverpro.com/modifying-exchange-server-2007-roles-breaks-outlook-web-access

http://itproafrica.com/technology/exchange/owa-broken-on-exchange-2007-on-windows-2008-red-x-appear-instead-of-web-pages/

We needed to install Exchange SP3 and review IIS prerequisites.

VMWARE VIEW Problem cloning master image for linked clones on v5.1

On a small new installation of Vmware View 5.1 we had problems when creating linked clone pools.
It is a lab install on SATA disk and cloning takes about 70 minutes.
It always finished with an error "Connection Server - View Composer Fault: VC operation exceeded the task timeout limit of 0 mins set by the View Composer for <VM instance>"
So after googling a lite bit I  founf some post on Vmware communities   that solved the problem.

http://communities.vmware.com/message/2063937

Thanks to hettefagh I could solve my problem.

Here you can read the solution:


1. Stopped the View Composer service.

2. Made a backup copy of C:\Program Files (x86)\VMware\VMware View Composer\SviWebService.exe.config and saved in the same folder.

3. Edited the SviWebService.exe.config and changed the line

<VirtualCenter PropertyCollectorTimeout="60" />

to read

<VirtualCenter PropertyCollectorTimeout="60" VcTaskTimeout="90" />

4. Saved the change and restarted Composer.  Confirmed the service is running again without error.

Esxi5 disconnected and responding ping.

Recently we have some serious problems on a small project implementation.


We had 2 Cisco UCS C200 M2 servers, 2 Cisco MDS9148 and a EMC VNX5100 storage array.
The servers used Qlogic 8GB Fiber channel cards. The problem appeared always on heavy storage use (backup tasks mostly), but it could be once a week.

When accessing to the esxi console you could write user and password but you could not enter.

After that you needed to restart the Esxi and Virtual Machines were down.

I opened a SR on VMware but solved the problem before they answer.

After looking at vmkernel.log I searched on Google for info about errors appearing and finally I founded a KB Article that was very interesting:

vHBAs and other PCI devices may stop responding in ESX/ESXi 4.1 and ESXi 5.0 when using Interrupt Remapping

Also I founded at Vmware  communities   some  threads with same case:

http://communities.vmware.com/message/1983041 (Cisco servers)

http://communities.vmware.com/thread/341512  (IBM, Supermicro) 

We execute the actions in the KB and everything is working fine after 20 days.

Hope this helps others on searching solutions!!

VMWARE Data Recovery Plugin: Error could not connect to the Data Recovery Service on the Appliance

Some times after installing Data Recovery Plugin you can't connect to the appliance. You get this message:  Error could not connect to the Data Recovery Service on the Appliance.
The curious thing is that you can't connect from vSphere client installed on VCenter or other desktops.
I found a solution on Vmware communities. You need to rename some dlls and it will work again.

Renaming  C:\Windows\System32\libeay32.dll and C:\Windows\System32\ ssleay32.dll and rebooting - all works fine.

I found that on this thread:  http://communities.vmware.com/thread/3283373

error mounting replica LUNS on VMWARE ESXi5

Hi,

a days ago I had some problems trying to test replicas between two EMC arrays connected to different vSphere 5 clusters.
I openned a request with EMC and they told me replica was fine.

I tried to mount the datastore by using esxcli the next command:

esxcli storage vmfs snapshot mount -u "4xxxxxx-99xxx-b555-001xxxxxx8"

It faulted with error and redirected me to vmkernel.log.

I reviewed vmkernel.log and I saw an error “Denying reservation access on an ATS-only vol”, I search for this error (and many others).

Finally I got this KB article on Vmware. It is not really same case but I tried it on a nonproduction server and finally VMFS5 datastore could be mounted.

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&externalId=2006858

After disabling these features I finally could mount snapshots of replica, and the replica itself when testing promote.