locked
E2K7 and OCSW 2007 on Server 2003 64-bit RRS feed

  • Question

  • I've just start an OCS implementation and would like to using the existing E2K7 hardware (not use 2K3-32bit OS).

     

    I've search groups and forum... however, I'm trying to resolve reoccuring ASP errors and Exchange Addressbook sync issues. Attached is the reoccurring ASP error from the OCS/E2K7 box as well as the page result of browsing to: https://Server1.domain1.com/Abs/Int/Handler/F-09fd.dabs

     

    Example1

    Event Type: Warning
    Event Source: ASP.NET 2.0.50727.0
    Event Category: Web Event
    Event ID: 1310
    Date:  1/3/2008
    Time:  7:52:19 AM
    User:  N/A
    Computer: Server1
    Description:
    Event code: 3008
    Event message: A configuration error has occurred.
    Event time: 1/3/2008 7:52:19 AM
    Event time (UTC): 1/3/2008 2:52:19 PM
    Event ID: 4e3f6569794e4d27b0279e0dbad02cf2
    Event sequence: 4
    Event occurrence: 1
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/1/Root/Abs/Int/Handler-1-128438455396808559
        Trust level: Full
        Application Virtual Path: /Abs/Int/Handler
        Application Path: D:\Program Files (x86)\Microsoft Office Communications Server 2007\Web Components\Address Book Files\Int\Handler\
        Machine name: Server1
     
    Process information:
        Process ID: 4380
        Process name: w3wp.exe
        Account name: Domain\SIPService
     
    Exception information:
        Exception type: ConfigurationErrorsException
        Exception message: Could not load file or assembly 'abserverhttphandler' or one of its dependencies. An attempt was made to load a program with an incorrect format. (D:\Program Files (x86)\Microsoft Office Communications Server 2007\Web Components\Address Book Files\Int\Handler\web.config line 8)
     
    Request information:
        Request URL: https://Server1.domain1.com:443/Abs/Int/Handler/F-09fd.dabs
        Request path: /Abs/Int/Handler/F-09fd.dabs
        User host address: x.x.x.x 
        User: Domain\Administrator
        Is authenticated: True
        Authentication Type: Basic
        Thread account name: Domain\SIPService
     
    Thread information:
        Thread ID: 1
        Thread account name: Domain\SIPService
        Is impersonating: False
        Stack trace:    at System.Web.Configuration.ConfigUtil.GetType(String typeName, String propertyName, ConfigurationElement configElement, XmlNode node, Boolean checkAptcaBit, Boolean ignoreCase)
       at System.Web.Configuration.HttpHandlerAction.InitValidateInternal()
       at System.Web.Configuration.HttpHandlersSection.ValidateHandlers()
       at System.Web.Configuration.HttpHandlersSection.FindMapping(String verb, VirtualPath path)
       at System.Web.HttpApplication.GetHandlerMapping(HttpContext context, String requestType, VirtualPath path)
       at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
       at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
     
     

    Example 2

    Server Error in '/Abs/Int/Handler' Application.

    Configuration Error

    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

    Parser Error Message: Could not load file or assembly 'abserverhttphandler' or one of its dependencies. An attempt was made to load a program with an incorrect format.

    Source Error:

    Line 6:    <system.web>
    Line 7:      <httpHandlers>
    Line 8:        <add verb="*" path="*.lsabs" type="Microsoft.Rtc.ABServer.AbsHttpHandler, abserverhttphandler"/>
    Line 9:        <add verb="*" path="*.dabs" type="Microsoft.Rtc.ABServer.AbsHttpHandler, abserverhttphandler"/>
    Line 10:     </httpHandlers>

    Source File: D:\Program Files (x86)\Microsoft Office Communications Server 2007\Web Components\Address Book Files\Int\Handler\web.config    Line: 8

    Assembly Load Trace: The following information can be helpful to determine why the assembly 'abserverhttphandler' could not be loaded.

    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
    


    Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

     

    Thursday, January 3, 2008 3:05 PM

All replies

  • Here is some additional error info, I enabled assembly load tracing.

     

    Server Error in '/GroupExpansion/Int' Application.

    Configuration Error

    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

    Parser Error Message: Could not load file or assembly 'McppAdAuthorization' or one of its dependencies. An attempt was made to load a program with an incorrect format.

    Source Error:

    Line 57:                 <add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
    Line 58:                 <add assembly="System.Web.Mobile, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
    Line 59:                 <add assembly="*"/>
    Line 60:                 <add assembly="System.Runtime.Serialization, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL"/>
    Line 61:                 <add assembly="System.IdentityModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL"/>

    Source File: C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\Config\web.config    Line: 59

    Assembly Load Trace: The following information can be helpful to determine why the assembly 'McppAdAuthorization' could not be loaded.

    === Pre-bind state information ===
    LOG: User = Domain1\SIPService
    LOG: DisplayName = McppAdAuthorization
     (Partial)
    LOG: Appbase = file:///D:/Program Files (x86)/Microsoft Office Communications Server 2007/Web Components/Group Expansion/Int/
    LOG: Initial PrivatePath = D:\Program Files (x86)\Microsoft Office Communications Server 2007\Web Components\Group Expansion\Int\bin
    Calling assembly : (Unknown).
    ===
    LOG: This bind starts in default load context.
    LOG: Using application configuration file: D:\Program Files (x86)\Microsoft Office Communications Server 2007\Web Components\Group Expansion\Int\web.config
    LOG: Using host configuration file: \\?\C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\aspnet.config
    LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\config\machine.config.
    LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
    LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework64/v2.0.50727/Temporary ASP.NET Files/groupexpansion_int/849085ba/abf036d/McppAdAuthorization.DLL.
    ERR: Failed to complete setup of assembly (hr = 0x8007000b). Probing terminated.
    

    Thursday, January 3, 2008 8:23 PM
  • Hi,

    I have exactly the same problem.Do you have any solution please?

     

    PT

    Wednesday, June 11, 2008 9:16 PM
  • Reinstall .NET 2.0Sp1

    Wednesday, June 11, 2008 11:12 PM
  • I've had the same problem...

    It's not possible to install OCS and Exchange 2K7 on the same machine, because Exchange 2K7 uses x64 operating system and ASP.Net x64... OCS is not able to work with ASP.net x64 so you need a x86 operating system...

    You can install a x86 operating system on a VirtualServer 2005 on the Exchange Machine to install the OCS Front End.

    Thursday, June 12, 2008 1:14 PM
  • Installing OCS on Exchange box is not supported

    Exchange UM role and OCS use the same ports so that also won't work besides the .NET problem

    Thursday, June 12, 2008 3:38 PM