none
Forefront UAG Activation

    Question

  • I've run an install of Forefront UAG and have gone to activate the configuration (with no actual configuration changes made from the default install) and am getting the following issues logged:

    The Web site [WebMonitor] could not be started. Make sure ports configured for this site are not already in use.
    The Web site [Defailt Web Site]  could not be started. Make sure ports configured for this site are not already in use.

    Event Viewer shows the following after running the activation:

    Event ID 163
    Service DA SessionMgr cannot be started. Error: -2147024891.

    Event 136
    The Web site [WebMonitor] could not be started. Make sure ports configured for this site are not already in use.

    Event 136
    The Web site [Defailt Web Site]  could not be started. Make sure ports configured for this site are not already in use.

    When I go into servicew the World Wide Web Publishing service has not started automatically. When I attempt to start it manually it comes up with the following:

    Windows could not start the World Wide Web Publishing Service service on Local Computer
    Error 1068: The dependency service or group failed to start.

    Following that, the following Error is shown in Event Viewer:

    Event 163
    Service DA SessionMgr cannot be started. Error: -2147024891

    Other events that have been logged since install:

    Event 5048
    The application '/InternalSite/M' belonging to site '1' has an invalid AppPoolId 'InternalSiteMobile' set. Therefore, the application will be ignored.

    Any help would be greatly appreciated.

    Wednesday, July 03, 2013 10:28 PM

Answers

  • In case anyone else suffers from this same issue, I have the answer.
    It turns out that this problem was related to the build in the virtual environment. The original UAG server's I'd been working with had been created from a vm template of server 2008. By manually creating the server from scratch (and using a new download of the UAG iso) I was able to successfully install and activate the configuration.

    Now comes the hard part of actually getting UAG to do what we need :)

    • Marked as answer by IHC_NZ Tuesday, July 30, 2013 10:54 PM
    Tuesday, July 30, 2013 10:54 PM

All replies

  • Hello,

    Could you check if all dependencies required for the World Wide Web Publishing  service are up and running and try to start it again. Did you make OS hardening before installing Forefront UAG ?


    Follow me on Twitter http://www.twitter.com/liontux | My Blog (French/English) : http://security.sakuranohana.fr/

    Thursday, July 04, 2013 9:26 AM
  • Yes all dependencies are running and the server has not  been hardened in any way, both the server 2008 install and the uag install are untouched.

    I have since run all service packs and rollup patches up to SP3 which has made no difference.

    Looks like it all revolves around not being able to start the Microsoft Forefront UAG Session Manager (which is what gets reported as 'Service DA SessionMgr' in the Event Viewer.

    There seems to be no one experiencing these reported problems making it difficult to analyse.

    Any ideas?

    • Edited by IHC_NZ Friday, July 05, 2013 4:02 AM update
    Thursday, July 04, 2013 9:02 PM
  • Hi,

    To resolve this issue, activate the configuration a second time.

    Source http://technet.microsoft.com/en-us/library/dd772157.aspx

    Thanks & Regards,

    ZB

    Wednesday, July 17, 2013 5:12 PM
  • Thanks for that but I have tried to activate the configuration many times but it still comes up with the same errors;
    The Web site [WebMonitor] could not be started. Make sure ports configured for this site are not already in use.
    The Web site [Defailt Web Site]  could not be started. Make sure ports configured for this site are not already in use.
    Which I believe are purely symptoms of the Forefront session manager not starting (because it's a dependency for the www service amongst other things)

    Wednesday, July 17, 2013 6:40 PM
  • In case anyone else suffers from this same issue, I have the answer.
    It turns out that this problem was related to the build in the virtual environment. The original UAG server's I'd been working with had been created from a vm template of server 2008. By manually creating the server from scratch (and using a new download of the UAG iso) I was able to successfully install and activate the configuration.

    Now comes the hard part of actually getting UAG to do what we need :)

    • Marked as answer by IHC_NZ Tuesday, July 30, 2013 10:54 PM
    Tuesday, July 30, 2013 10:54 PM