locked
Microsoft UCMA 4.0 API quickStart applications are not working RRS feed

  • General discussion

  • Hi,

    Microsoft UCMA 4.0 API quickStart applications are not working. I open project in Visual Studio 2013 and try to run. I enter all credentials and other info and i'm getting exception:

    + $exception {"Not authorized to perform the requested operation, request is refused"} System.Exception {Microsoft.Rtc.Signaling.AuthenticationException}

    We are using skype for business 2015. 

    I tried QuickStarts\AudioVideoCall\BasicAudioVideoCall and QuickStarts\AudioVideoCall\Recorder prebuilt apps

    • Changed type Eason Huang Wednesday, May 18, 2016 3:16 AM more related with SFB SDK
    Tuesday, May 17, 2016 7:01 PM

All replies

  • Hi,

    From the error log above, it seems that the issue is related with credentials. Please check if there is any credential set wrong.

    Also, as the issue is more related with Skype for Business SDK, you might post the issue on Skype for Business MSDN forum and more developing expert will help to solve it. Thank you for your understanding.

    https://social.msdn.microsoft.com/Forums/en-US/home?category=SfB

    Best Regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Eason Huang
    TechNet Community Support

    Wednesday, May 18, 2016 3:15 AM
  • credentials are 100% correct, the app even can get current credentials. 
    Wednesday, May 18, 2016 4:39 AM
  • Here are 3 logs from skype server security log when i run app:

    1)

    Special privileges assigned to new logon.

    Subject:
    Security ID: domain\user1
    Account Name: user1
    Account Domain: domain
    Logon ID: 0xBB323DD9

    Privileges: SeSecurityPrivilege
    SeBackupPrivilege
    SeRestorePrivilege
    SeTakeOwnershipPrivilege
    SeDebugPrivilege
    SeSystemEnvironmentPrivilege
    SeLoadDriverPrivilege
    SeImpersonatePrivilege


    2)

    An account was successfully logged on.

    Subject:
    Security ID: NULL SID
    Account Name: -
    Account Domain: -
    Logon ID: 0x0

    Logon Type: 3

    Impersonation Level: Identification

    New Logon:
    Security ID: domain\user1
    Account Name: user1
    Account Domain: domain
    Logon ID: 0xBB323DD9
    Logon GUID: {64005184-862e-ca8d-c468-3990f65e57af}

    Process Information:
    Process ID: 0x0
    Process Name: -

    Network Information:
    Workstation Name:
    Source Network Address: -
    Source Port: -

    Detailed Authentication Information:
    Logon Process: Kerberos
    Authentication Package: Kerberos
    Transited Services: -
    Package Name (NTLM only): -
    Key Length: 0

    This event is generated when a logon session is created. It is generated on the computer that was accessed.

    The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

    The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

    The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

    The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

    The impersonation level field indicates the extent to which a process in the logon session can impersonate.

    The authentication information fields provide detailed information about this specific logon request.
    - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
    - Transited services indicate which intermediate services have participated in this logon request.
    - Package name indicates which sub-protocol was used among the NTLM protocols.
    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.


    3)

    An account was logged off.

    Subject:
    Security ID: domain\user1
    Account Name: user1
    Account Domain: domain
    Logon ID: 0xBB323DD9

    Logon Type: 3

    This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer.
    Wednesday, May 18, 2016 8:19 AM