Here were the issues and how it was resolved. It was due to it being installed on a 64 bit server which had exchange/sharepoint 2011 installed.
1-The web.config was missing much info. Make sure all relevant AO Web assemblies are listed in the add modules section of the config.
2-Created a new app pool for AO Web, integrated type and enabled 32 bit applications and set AO Web to run in it.
3-When trying to run it got a 503 service not available error. Followed the steps in this article:
A few things it was missing. When editing the application host file you also need to add the preCondition="bitness64" to the two following:
<filter name="Exchange OWA Cookie Authentication ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\owa\auth\owaauth.dll" enabled="true" preCondition="bitness64" />
<filter name="Exchange ActiveSync ISAPI Filter" path="C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\sync\bin\AirFilter.dll" enabled="true" preCondition="bitness64" />
Also it shows how to remove the compression mosdules from the site but I needed to change it to use the app name since it was a virtual directory. To get a list of app named so this:
c:\Windows\System32\inetsrv>appcmd.exe list sites
c:\Windows\System32\inetsrv>appcmd.exe delete module staticcompressionmodule /ap
p.name:"Default Web Site/AOWeb"
MODULE object "StaticCompressionModule" deleted
c:\Windows\System32\inetsrv>appcmd.exe delete module dynamiccompressionmodule /a
pp.name:"Default Web Site/AOWeb"
MODULE object "DynamicCompressionModule" deleted
If you get a lock violation open the applicationhosts config file again and change lockitem to false for these
<add name="DynamicCompressionModule" lockItem="true" />
<add name="StaticCompressionModule" lockItem="true" />
Then it should start working.