locked
WebComponent/WebScheduler Error RRS feed

  • Question

  •  

    Just installed WebComponent and WebSchedurele for WebConferencing and when i try to logon

    to https://serverocs/Conf/Int with administrative account I get this error:

     

    Server Error
    A server error has occurred. Please contact the administrator.
    Error Source: System.DirectoryServices
    Error Type: System.Runtime.InteropServices.COMException
    Error Message: An operations error occurred.
    Error Code: -2147016672

     

    Any idea ?

    Thanks, Sandro

    Friday, May 11, 2007 2:57 PM

Answers

  • This error is cause by not activating the web scheduler.

     

    Server Error

    A server error has occurred. Please contact the administrator.

    Error Source: System.DirectoryServices

    Error Type: System.Runtime.InteropServices.COMException

    Error Message: An operations error occurred.

    Error Code: -2147016672

     

    1.       After installation is complete, you need to activate Web Scheduler using the same user name and password that you used to activate Web Components on the computer. If you do not remember the user name used to activate Web Components, use the following steps. Open IIS Manager (%SystemRoot%\system32\inetsrv\iis.msc), and then navigate to Local Computer, Application Pools, and LSGroupExpAppPool. Right-click LSGroupExpAppPool, click Properties, and then click the Identity tab. Note the user name under Configurable identity type. You only need the name part of the string. If the user name string is Domain\RTCComponentService, RTCComponentService is what you need to use in the activation procedure.

    a.         To activate Web Scheduler on Standard Edition, use the following command line:

    LcsCmd.exe /web /action:Activate /role:Meeting /poolname:<pool_name> /User:<user_name> /Password:<password>.

    LcsCmd.exe tool is located under %CommonProgramFiles%\Office Communications Server 2007. Use pool_name = name of the computer (for example, computer1).

    b.         To activate Web Scheduler on Enterprise Edition, use the following command line:

    LcsCmd.exe /web /action:Activate /role:Meeting /poolname:<pool_name> /User:<user_name> /Password:<password> /guest:<guestuser> /guestpassword:<guestpassword>

    Use pool_name = Enterprise Edition Pool name (for example, pool1) of which Web Components is part. For the guest user and guest password, use the same guest user account name and password you used to activate Web Components on the computer.

     

    Louis H

    Friday, May 25, 2007 10:35 PM

All replies

  • Hi Sandro,

         I am having the same issue. It looks like (to me anyway) there might be some kind of trust or permissions issue when the OCS server is trying to authenticate the user against the primary AD server.

    Did you ever resolve this issue? I would really like to hear any information regarding the resolution of this one.

    Cheers.

    D

    Tuesday, May 15, 2007 11:33 AM
  • Sandro,

     

    I am confuse as to what you are trying to accomplish.  In my deployment the only thing I have in that directory is my Tshoot.html file and when I try to access with https://domain.com/conf/int/tshoot.html I have no problem.  So if there is an issue here it would be with IIS. 

     

    Are you just trying to connect to this site with IE or am I missing something?

     

    Louis H

    Thursday, May 24, 2007 9:03 PM
  • I had, and still have, this issue too, and just to be on the safe side, I just did a complete reinstall from the scratch, installed OCS 2007 (SE) as guided in the deployment guide, and still the same error pops up when logging on the the web site https://myserver/conf/int/

     

    So what can I do to fix this? And propably has something to do with this problem too, Office Live Meeting won't connect to my OCS at all, gives the following error when I click test connecton: "Cannot  connect to LiveMeetingServer because the information in the User Accounts dialog might be incorrect or improperly formatted. Please verify that this information is correct, and then click Test Connection. If you still can't connect, the server might not be available". The user account settings are the same as in Communicator which works just fine.

     

    No errors in system or application log in the server, in the client there are multiple ConfAPI errors and warnings (1015, 1017).

     

     

    Thursday, May 24, 2007 11:50 PM
  • I don’t understand what the correlation with this web site is to the problem.  I cannot connect to that website either without adding the /tshoot.html.  We can however, working on why you cannot connect to your OCS server using LiveMeeting.  Can you send me the confapi.log and pwconsole.log?  The pwconsole.log file is enable by default and is located in %temp% directory.  ConfAPI has to be enabled via the registry and it is located in %userprofile%\tracing.

     

     

    HKEY_CURRENT_USER\Software\Microsoft\Tracing\uccp\ConfAPI

     

     

    EnableFileTracing  = 1

     

    The confapi.log is the most important at this time because you are unable to test connection.

     

    Louis H

    Friday, May 25, 2007 12:07 AM
  • Hi Luis,

     

    I'll get you the logs as soon as possible.

     

    The website problem is not that simple, I can browse to https://myserver/conf/int/TShoot.html just fine, and also https://myserver/conf/int/login.aspx works, I can even login (it works, because only correct credentials work) but after login comes the error message mentioned in the first post. So there is something wrong with the website. If you don't have anything else than TShoot.html in that website, you propably don't have web scheduler installed?

     

    But, I'll try to get those log's posted here.

     

    edit:  Here's the confapi log (server, user and domain names changed, so don't mind them):

     

    Code Snippet

    05/25/2007|11:48:36.154 2EA8:216C WARN  :: module=uccp flavor=fre version=2.0.6090.0
    05/25/2007|11:48:36.154 2EA8:216C INFO  :: Initialization flags (1)
    05/25/2007|11:48:36.154 2EA8:216C INFO  :: Function: CUccPlatform::InitializeMedia
    05/25/2007|11:48:36.154 2EA8:216C ERROR :: Condition failed with 00000000: '(m_lFlags & 0x00000001) == 0'
    05/25/2007|11:48:36.154 2EA8:216C TRACE :: client[00149600] new sipStack[0014BE00]
    05/25/2007|11:48:36.201 2EA8:216C INFO  :: No registry setting, using default: "Mode" = 2
    05/25/2007|11:48:36.201 2EA8:216C INFO  :: No registry setting, using default: "NegotiateTimeout" = 5000
    05/25/2007|11:48:36.201 2EA8:216C INFO  :: No registry setting, using default: "Threshold" = 128
    05/25/2007|11:48:36.217 2EA8:216C TRACE :: CUccServerEndpoint::UpdateEndpointState - Update state from 1 to 2. Status 0. Status text (null).
    05/25/2007|11:48:36.217 2EA8:216C INFO  :: CUccSubscriptionManager::CreateSubscription - Sub mgr 0013E76C creating subscription 0017C600
    05/25/2007|11:48:36.217 2EA8:216C INFO  :: CUccSubscriptionManager::CreatePresentity - Sub mgr 0013E76C successfully created presentity 'username@mydomain.local' [00136B48]
    05/25/2007|11:48:36.217 2EA8:216C TRACE :: CUccSubscription::AddCategoryName add new category [serverconfiguration], this 0017C600
    05/25/2007|11:48:36.233 2EA8:216C TRACE :: CUccSubscription::AddPresentity adding presentity [sip:username@mydomain.local] to 5 map, this 0017C600
    05/25/2007|11:48:36.233 2EA8:216C TRACE :: CUccSubscription::Query - enter [0x0017C600]
    05/25/2007|11:48:36.233 2EA8:216C TRACE :: CUccAutoProvSubscription::GetCurrentSubscriptionBody - enter [0x001449B8]
    05/25/2007|11:48:36.311 2EA8:216C TRACE :: CUccAutoProvSubscription::GetCurrentSubscriptionBody - exit [001449B8]
    05/25/2007|11:48:36.311 2EA8:216C INFO  :: Outgoing 001153DC-<sip:username@mydomain.local>, local=sip:username@mydomain.local
    05/25/2007|11:48:36.311 2EA8:216C TRACE :: CUccSubscription::Query - exit [0017C600]
    05/25/2007|11:48:36.389 2EA8:216C TRACE :: SIP_MSG_PROCESSOR::OnDnsResolutionComplete[001153DC] Entered host ocsserver.mydomain.local
    05/25/2007|11:48:36.389 2EA8:216C ERROR :: SIP_STACK::MapDestAddressToNatInternalAddress m_pDirectPlayNATHelp is NULL.  Setting *pIsDestExternalToNat to FALSE
    05/25/2007|11:48:36.499 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: ASYNC_SOCKET::StartTlsNegotiationWorkitem TLS negotiation is in progress. Do not start another workitem, this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    << plenty of this >>
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: ASYNC_SOCKET::StartTlsNegotiationWorkitem TLS negotiation is in progress. Do not start another workitem, this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: ASYNC_SOCKET::StartTlsNegotiationWorkitem TLS negotiation is in progress. Do not start another workitem, this 0012E5F8
    05/25/2007|11:48:36.765 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.796 2EA8:216C TRACE :: Async work item posted for TLS negotiation: this 0012E5F8
    05/25/2007|11:48:36.953 2EA8:DFC TRACE :: SECURE_SOCKET: stream sizes: header 5 trailer 16 max message 16384 buffers 4 block size 1
    05/25/2007|11:48:36.953 2EA8:216C INFO  :: CSIPCompressor::StartCompressionNegotiation - Link test not yet performed, checking registry for compression settings
    05/25/2007|11:48:36.953 2EA8:216C INFO  :: CSIPCompressor::StartLinkSpeedDetectionUsingWindows - Testing link bandwidth using adapter info.
    05/25/2007|11:48:36.953 2EA8:216C INFO  :: Connection speed detected=6750000, Threshold=128000, returning fUseCompression=FALSE
    05/25/2007|11:48:36.953 2EA8:216C TRACE :: SIP_MSG_PROCESSOR::OnRequestSocketConnectComplete - Enter this: 001153DC, callid=(null), ErrorCode: 0x0
    05/25/2007|11:48:36.953 2EA8:216C INFO  :: Sending Packet - 192.168.99.221:5061 (From Local Address: 192.168.99.106:3311) 972 bytes:
    05/25/2007|11:48:36.953 2EA8:216C INFO  :: SUBSCRIBE sip:username@mydomain.local SIP/2.0Via: SIP/2.0/TLS 192.168.99.106:3311Max-Forwards: 70From:

    <sip:username@mydomain.local>;tag=f8c1029bac;epid=befeb3e0ccTo: <sip:username@mydomain.local>Call-ID: 0817959e80fa44a78fdc7b457411e306CSeq: 1 SUBSCRIBEContact:

    <sip:username@mydomain.local:3311;maddr=192.168.99.106;transport=tls>;proxy=replace;+sip.instance="<urn:uuid:713003D3-B9AF-508E-8D17-5257405B30D8>"User-Agent: UCCP/2.0.6090.0Event:

    vnd-microsoft-provisioning-v2Accept: application/vnd-microsoft-roaming-provisioning-v2+xmlSupported: com.microsoft.autoextendSupported: ms-benotifyProxy-Require: ms-benotifySupported:

    ms-piggyback-first-notifyExpires: 0Content-Type: application/vnd-microsoft-roaming-provisioning-v2+xmlContent-Length: 165<provisioningGroupList

    xmlns="http://schemas.microsoft.com/2006/09/sip/provisioninggrouplist"><provisioningGroup name="ServerConfiguration"/></provisioningGroupList>
    05/25/2007|11:48:36.953 2EA8:216C INFO  :: End of Sending Packet - 192.168.99.221:5061 (From Local Address: 192.168.99.106:3311) 972 bytes
    05/25/2007|11:48:36.953 2EA8:216C TRACE :: - encrypted buffer length: 993 bytes.  First 8 bytes:
    05/25/2007|11:48:36.953 2EA8:216C TRACE ::  17 03 01 03 DC B9 81 B3  :....ܹ³
    05/25/2007|11:48:36.984 2EA8:216C TRACE :: SECURE_SOCKET: decrypting buffer size: 623 (first 8):
    05/25/2007|11:48:36.984 2EA8:216C TRACE ::  17 03 01 02 6A B3 38 81  :....j³8
    05/25/2007|11:48:36.984 2EA8:216C INFO  :: Data Received - 192.168.99.221:5061 (To Local Address: 192.168.99.106:3311) 602 bytes:
    05/25/2007|11:48:36.984 2EA8:216C INFO  :: SIP/2.0 401 UnauthorizedDate: Fri, 25 May 2007 08:48:34 GMTWWW-Authenticate: NTLM realm="SIP Communications Service",

    targetname="ocsserver.mydomain.local", version=3WWW-Authenticate: Kerberos realm="SIP Communications Service", targetname="sip/ocsserver.mydomain.local", version=3Via: SIP/2.0/TLS

    192.168.99.106:3311;ms-received-port=3311;ms-received-cid=200From: <sip:username@mydomain.local>;tag=f8c1029bac;epid=befeb3e0ccTo:

    <sip:username@mydomain.local>;tag=4ED358570A0C8A576F1344CD01CA1FFECall-ID: 0817959e80fa44a78fdc7b457411e306CSeq: 1 SUBSCRIBEContent-Length: 0
    05/25/2007|11:48:36.984 2EA8:216C INFO  :: End of Data Received - 192.168.99.221:5061 (To Local Address: 192.168.99.106:3311) 602 bytes
    05/25/2007|11:48:36.984 2EA8:216C INFO  :: SIP_MSG_PROCESSOR::GetChallengeListForPlatform ProtocolsFromPlatform=0xf
    05/25/2007|11:48:36.984 2EA8:216C TRACE :: SIP_STACK::UpdateProviderSAContextAndSetAuthProtocol adding SA with TargetName: sip/ocsserver.mydomain.local Auth: 8 to provider at index 0
    05/25/2007|11:48:36.984 2EA8:216C TRACE :: SIP_STACK::AddSAToProvider SA added:sip/ocsserver.mydomain.local-00137B28 list entry 02F208D8, this 0014BE00
    05/25/2007|11:48:36.984 2EA8:216C TRACE :: SIP_STACK::FindProviderSAContext SA_CONTEXT found:sip/ocsserver.mydomain.local- 00137B28, SA list entry 02F208D8, this 0014BE00
    05/25/2007|11:48:36.984 2EA8:216C TRACE :: SIP_MSG_PROCESSOR::GetSAListEntry- SA not found for TargetName: sip/ocsserver.mydomain.local Auth: 8, this 001153DC
    05/25/2007|11:48:36.984 2EA8:216C WARN  :: SIP_MSG_PROCESSOR::AddSAToList cannot find SA [00137B28] in list, inserting list entry [02F20878] into list, TargetName sip/ocsserver.mydomain.local,

    Auth: 8, this 001153DC
    05/25/2007|11:48:36.984 2EA8:216C TRACE :: SIP_MSG_PROCESSOR::GetSAListEntry SA [00137B28] targetname sip/ocsserver.mydomain.local, auth 8, this 001153DC
    05/25/2007|11:48:36.984 2EA8:216C TRACE :: SIP_STACK::FindProviderSAContext SA_CONTEXT found:sip/ocsserver.mydomain.local- 00137B28, SA list entry 02F208D8, this 0014BE00
    05/25/2007|11:48:37.031 2EA8:216C TRACE :: Async work item posted for Init-SA: 0
    05/25/2007|11:48:46.130 2EA8:216C ERROR :: SIP_MSG_PROCESSOR::CompleteSAProcessingAndGetAuthHeader InitializeSecurityContext failed: 0x80090311

    05/25/2007|11:48:46.130 2EA8:216C ERROR :: SIP_MSG_PROCESSOR::OnSAInitComplete - CompleteSAProcessingAndGetAuthHeader failed 80ee00a6
    05/25/2007|11:48:46.130 2EA8:216C TRACE :: CSipSubscription::InitiateSessionTerminationOnError - enter, status 80ee00a6
    05/25/2007|11:48:46.130 2EA8:216C TRACE :: CUccSubscriptionBase::NotifySubscriptionStateChange - enter [0x001449B8]
    05/25/2007|11:48:46.130 2EA8:216C WARN  :: CSipSubscription::CreateOutgoingUnsub already in termianted state, this 001153D8
    05/25/2007|11:48:46.130 2EA8:216C ERROR :: CSipSubscription::SubscriptionStateChange already changed to state 4, input state 3
    05/25/2007|11:48:46.130 2EA8:216C TRACE :: CUccSubscriptionBase::NotifySubscriptionStateChange - exit [001449B8]
    05/25/2007|11:48:46.130 2EA8:216C TRACE :: CUccSubscriptionEventInfo::GetOperationInfo - enter [0x02F2C2F0]
    05/25/2007|11:48:46.130 2EA8:216C TRACE :: CUccSubscriptionEventInfo::GetOperationInfo - exit [02F2C2F0]
    05/25/2007|11:48:46.130 2EA8:216C TRACE :: CUccServerEndpoint::UpdateEndpointState - Update state from 3 to 4. Status 0. Status text (null).
    05/25/2007|11:48:46.130 2EA8:216C TRACE :: SIP_STACK::FreeProviderSAList deleting SA list entry [02F208D8] with SA [00137B28] from provider
    05/25/2007|11:48:46.130 2EA8:216C TRACE :: SIP_STACK::DeleteProviderProfile freed profile at index 0

     

    Friday, May 25, 2007 8:46 AM
  • You are correct I didnt have Web Scheduler install.  I installed and now I am getting the same error that you originally got in your first post, but it does not prevent my LiveMeeting from working.  So it looks like there is 2 issues one is the error trying to access the site and connecting to LiveMeeting.

     

    I will work on resolving the error on the website since I have a repro and in the mean while we can try to figure out why your LiveMeeting isnt working.

     

    I found the following error in the confAPI log.

     

    05/25/2007|11:48:46.130 2EA8:216C ERROR :: SIP_MSG_PROCESSOR::CompleteSAProcessingAndGetAuthHeader InitializeSecurityContext failed: 0x80090311

     

    0x80090311 is # No authority could be contacted for authentication.

     

    How are putting you credentials in the advance setting of LiveMeeting?

     

    Also I will you need to do some logging on the OCS server.

     

    Right click the Pool go to Logging and start a new logging session.

    Select SipStack

    All Flags

    All levels

    Select UserServices

    All Flags

    All Levels

    Start Logging

    Test Connection

    Once you have the failure

    Click Stop logging

    Then click View logs

    send me the sipstack.etl and sipstack.txt

    also the userservices.etl and userservices.txt

    on the client send me the confAPI

     

    Louis H

    Friday, May 25, 2007 6:06 PM
  • This error is cause by not activating the web scheduler.

     

    Server Error

    A server error has occurred. Please contact the administrator.

    Error Source: System.DirectoryServices

    Error Type: System.Runtime.InteropServices.COMException

    Error Message: An operations error occurred.

    Error Code: -2147016672

     

    1.       After installation is complete, you need to activate Web Scheduler using the same user name and password that you used to activate Web Components on the computer. If you do not remember the user name used to activate Web Components, use the following steps. Open IIS Manager (%SystemRoot%\system32\inetsrv\iis.msc), and then navigate to Local Computer, Application Pools, and LSGroupExpAppPool. Right-click LSGroupExpAppPool, click Properties, and then click the Identity tab. Note the user name under Configurable identity type. You only need the name part of the string. If the user name string is Domain\RTCComponentService, RTCComponentService is what you need to use in the activation procedure.

    a.         To activate Web Scheduler on Standard Edition, use the following command line:

    LcsCmd.exe /web /action:Activate /role:Meeting /poolname:<pool_name> /User:<user_name> /Password:<password>.

    LcsCmd.exe tool is located under %CommonProgramFiles%\Office Communications Server 2007. Use pool_name = name of the computer (for example, computer1).

    b.         To activate Web Scheduler on Enterprise Edition, use the following command line:

    LcsCmd.exe /web /action:Activate /role:Meeting /poolname:<pool_name> /User:<user_name> /Password:<password> /guest:<guestuser> /guestpassword:<guestpassword>

    Use pool_name = Enterprise Edition Pool name (for example, pool1) of which Web Components is part. For the guest user and guest password, use the same guest user account name and password you used to activate Web Components on the computer.

     

    Louis H

    Friday, May 25, 2007 10:35 PM
  • Thanks Louis H, the web conferencing site is now working.

     

    I have to look in to the live meeting client not connecting.

    Sunday, May 27, 2007 7:08 PM
  • Absolutely GREAT !!!

     

    Now it's working also for me !!!!!!!!!!!!!!

     

    Thanks you VERY VERY MUCH !

     

    Best Regards,

    Sandro De Matteis

    Monday, May 28, 2007 4:15 PM
  • I have the same issue as above, after activating the application using the LcsCmd I am unable to access /int, /ext or the tshoot page.  I cannot see any errors in the log files at all nor is any error presented in the browser when accessing these locations.  Any insight?

     

    Derek

     

    Thursday, July 26, 2007 12:04 PM