none
Lync2013内网客户端和外网客户端传输文件失败 RRS feed

  • 问题

  • Lync2013内网客户端和外网客户端传输文件失败,环境如下:内网三台Lync 2013前端,一台边缘服务器,使用外网客户端登录正常,在传送文件时报错

    2017年11月3日 3:52

全部回复

  • 你好 patriotabc,

    1.请问所有用户都有这种问题吗?还是个别用户有这个问题

    2.内部用户之间可以传输文件吗?

    3.可以把报错的图片上传下吗?

    运行下面的命令检查EnableUnencryptedFileTransfer 的值是否为true,如果不为true,您将不能与外部用户(不支持加密传输)传输文件

    Get-CsClientPolicy | select EnableUnencryptedFileTransfer

    检查下 您传输的文件是否被文件传输过滤,打开 Lync 控制面板 ->选择 IM 和状态 查看是否“启用文件删选器”,在“文件传输” 下拉列表中查看是否是“全部阻止”;如果是“阻止特定文件类型”,请确认传输文件的类型不包括在“阻止特定文件类型“中

    Regards,

    Leon Lu


    如果以上回复对您有所帮助,建议您将其.  “标记为答复””.
    如果您对我们的论坛支持有任何的建议,可以通过此邮箱联系我们:tnmff@microsoft.com.

    2017年11月3日 8:06
    版主
  • 你好 patriotabc

    对于这个问题有没有更新?如果答复对你有帮助,请尝试将其标记为答案,这将有助于其他有类似问题的人解决问题。



    Regards,

    Leon Lu


    如果以上回复对您有所帮助,建议您将其.  “标记为答复””.
    如果您对我们的论坛支持有任何的建议,可以通过此邮箱联系我们:tnmff@microsoft.com.

    2017年11月6日 1:27
    版主
  • 1.请问所有用户都有这种问题吗?还是个别用户有这个问题

    和外网的文件传输都有问题,内网的有个别有问题

    2.内部用户之间可以传输文件吗?

    内部用户可以传输

    3.可以把报错的图片上传下吗?

    报错信息为“传输失败”,没有其他提示。

    没有使用文件筛选,

    2017年11月14日 14:35
  • 您好,

     

    请问您传输的文件是什么类型的?比如.doc .xlsx

     

    请关闭PC上的杀软,并确认客户端的PC 上端口TCP Ports 6891 – 6901  是否开启

    请开启Lync 客户端的日志,您可以在以下路径,找到日志,用记事本打开把日志贴上论坛

    %userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\Tracing  寻找名为Lync-UccApi-#.UccApilog 的文件



    Regards,

    Leon Lu


    如果以上回复对您有所帮助,建议您将其“标记为答复”.
    如果您对我们的论坛支持有任何的建议,可以通过此邮箱联系我们:tnsf@microsoft.com.


    2017年11月17日 9:24
    版主
  • UCCLOG如下:测试的Lync账号test11@XXXXX.com.cn

    11/15/2017|09:33:26.461 B40:15E0 INFO  :: ******************************************************************************** ******************************************************************************** #######  module=UccApi flavor=fre version=15.0.4641.1000 ###### ************************************************************************************************************************ ****************************************

    11/15/2017|09:33:26.461 B40:15E0 INFO  :: Initialization flags (100) 11/15/2017|09:34:17.246 B40:15E0 TRACE :: CUccMediaManagerEventAdapter::Initialize Start Initialize message handler(...) 11/15/2017|09:34:17.282 B40:15E0 TRACE :: CUccMediaManagerEventAdapter::Initialize End Initialize message handler(...) 11/15/2017|09:34:17.292 B40:15E0 INFO  :: CHidManager::AddHidDevice - HID device <\\?\hid#vid_24ae&pid_1100&mi_01#8&2abf290a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}> is not a telephony device 11/15/2017|09:34:17.292 B40:15E0 ERROR :: CHidManager::AddHidDevice - CreateFile(\\?\hid#vid_24ae&pid_1100&mi_00#8&3a340526&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}) failed with 0x80070005 11/15/2017|09:34:17.292 B40:15E0 ERROR :: CHidManager::EnumerateHidDevices - AddHidDevice failed 0x80070005 11/15/2017|09:34:17.293 B40:15E0 INFO  :: MediaManager found 3 devices 11/15/2017|09:34:17.337 B40:15E0 INFO  :: Function: CUccAudioMediaDevice::InternalInitialize 11/15/2017|09:34:17.396 B40:15E0 ERROR :: HRESULT API failed: 80004005 = hr. ParsePidVidMi 11/15/2017|09:34:17.396 B40:15E0 INFO  :: CUccAudioMediaDevice::InternalInitialize - DisplayName set to 2- High Definition Audio - Log message too long! 11/15/2017|09:34:17.906 B40:15E0 INFO  :: Function: CUccAudioMediaDevice::InternalInitialize 11/15/2017|09:34:17.906 B40:15E0 ERROR :: HRESULT API failed: 80004005 = hr. ParsePidVidMi 11/15/2017|09:34:17.906 B40:15E0 INFO  :: CUccAudioMediaDevice::InternalInitialize - DisplayName set to 2- High Definition Audio - Log message too long! 11/15/2017|09:34:17.931 B40:15E0 INFO  :: CUccVideoMediaDevice::InternalInitialize - Integrated Camera camera with no special marks 11/15/2017|09:34:17.931 B40:15E0 INFO  :: CUccMediaDeviceManager::UpdateTelDeviceAdded - Checking if PnpName \\?\HDAUDIO#FUNC_01&VEN_10EC&DEV_0269&SUBSYS_17AA21FA&REV_1002#4&30ab2ace&0&0001#{0.0.0.00000000}.{3c2bf422-5091-4f67-a6ff-ffad30f55446}# has EndpointID or not 11/15/2017|09:34:17.999 B40:15E0 INFO  :: CUccMediaDeviceManager::UpdateTelDeviceAdded - Found endpointID. PnpName without EndpointID is \\?\HDAUDIO#FUNC_01&VEN_10EC&DEV_0269&SUBSYS_17AA21FA&REV_1002#4&30ab2ace&0&0001# 11/15/2017|09:34:17.999 B40:15E0 INFO  :: CUccMediaDeviceManager::UpdateTelDeviceAdded - Checking if PnpName \\?\HDAUDIO#FUNC_01&VEN_10EC&DEV_0269&SUBSYS_17AA21FA&REV_1002#4&30ab2ace&0&0001#{0.0.1.00000000}.{ff347d12-0f87-42c7-bc64-ee5031daedc7}# has EndpointID or not 11/15/2017|09:34:17.999 B40:15E0 INFO  :: CUccMediaDeviceManager::UpdateTelDeviceAdded - Found endpointID. PnpName without EndpointID is \\?\HDAUDIO#FUNC_01&VEN_10EC&DEV_0269&SUBSYS_17AA21FA&REV_1002#4&30ab2ace&0&0001# 11/15/2017|09:34:18.015 B40:15E0 TRACE :: CUccMediaDeviceManager::LoadDeviceVolumeCollection: Volume for deviceid = - Log message too long! 11/15/2017|09:34:18.016 B40:15E0 TRACE :: CUccMediaDeviceManager::LoadDeviceVolumeCollection: Volume for deviceid = - Log message too long! 11/15/2017|09:34:18.016 B40:15E0 TRACE :: CUccMediaDeviceManager::LoadDeviceVolumeCollection: Volume for deviceid = - Log message too long! 11/15/2017|09:34:18.016 B40:15E0 ERROR :: CUccMediaDeviceManager::LoadCustomTelephonyDeviceCollection: HRESULT failed: 80070002 = hr. Audio capture 11/15/2017|09:34:18.016 B40:15E0 ERROR :: CUccMediaDeviceManager::LoadCustomTelephonyDeviceCollection: HRESULT failed: 80070002 = hr. Audio capture 11/15/2017|09:34:18.016 B40:15E0 WARN  :: We did not find device based on Name and Moniker match. Let's try to find device based on only name match 11/15/2017|09:34:18.019 B40:15E0 INFO  :: CUccMediaDeviceManager::FireTelephonyDeviceCollectionChanged - Telephony device was added type=0x8 name=<[- Log message too long! 11/15/2017|09:34:18.033 B40:15E0 INFO  :: Function: CUccMediaDeviceManager::GetBoolProperty 11/15/2017|09:34:18.033 B40:15E0 TRACE :: Condition failed with 80ee0058: 'spProperty.IsValid()' 11/15/2017|09:34:18.033 B40:15E0 INFO  :: Function: CUccMediaDeviceManager::GetBoolProperty 11/15/2017|09:34:18.033 B40:15E0 TRACE :: Condition failed with 80ee0058: 'spProperty.IsValid()' 11/15/2017|09:34:18.033 B40:15E0 INFO  :: Function: CUccMediaDeviceManager::GetBoolProperty 11/15/2017|09:34:18.033 B40:15E0 TRACE :: Condition failed with 80ee0058: 'spProperty.IsValid()' 11/15/2017|09:34:18.033 B40:15E0 INFO  :: Function: CUccMediaDeviceManager::GetBoolProperty 11/15/2017|09:34:18.033 B40:15E0 TRACE :: Condition failed with 80ee0058: 'spProperty.IsValid()' 11/15/2017|09:34:18.033 B40:15E0 INFO  :: Function: CUccMediaDeviceManager::GetBoolProperty 11/15/2017|09:34:18.033 B40:15E0 TRACE :: Condition failed with 80ee0058: 'spProperty.IsValid()' 11/15/2017|09:34:18.033 B40:15E0 INFO  :: CUccMediaDeviceManager::FireDeviceChanged - Default device changed to <- Log message too long! 11/15/2017|09:34:18.033 B40:15E0 INFO  :: CUccMediaDeviceManager::FireDeviceChanged - Selected device changed to <- Log message too long! 11/15/2017|09:34:18.033 B40:15E0 INFO  :: CUccMediaDeviceManager::FireDeviceChanged - Default device changed to <- Log message too long! 11/15/2017|09:34:18.033 B40:15E0 INFO  :: CUccMediaDeviceManager::FireDeviceChanged - Selected device changed to <- Log message too long! 11/15/2017|09:34:18.033 B40:15E0 INFO  :: CUccMediaDeviceManager::FireTelephonyDeviceChanged - Default telephony device changed to type=0x8 name=<[- Log message too long! 11/15/2017|09:34:18.033 B40:15E0 INFO  :: CUccMediaDeviceManager::FireTelephonyDeviceChanged - Selected telephony device changed to type=0x8 name=<[- Log message too long! 11/15/2017|09:34:18.033 B40:15E0 INFO  :: CUccMediaDeviceManager::FireDeviceChanged - Default device changed to <- Log message too long! 11/15/2017|09:34:18.033 B40:15E0 INFO  :: CUccMediaDeviceManager::FireDeviceChanged - Selected device changed to <- Log message too long! 11/15/2017|09:34:18.034 B40:15E0 INFO  :: CUccMediaDeviceManager::FireDeviceChanged - Default device changed to <Integrated Camera> for category=0 media=2 direction=1 reason=2 11/15/2017|09:34:18.034 B40:15E0 INFO  :: CUccMediaDeviceManager::FireDeviceChanged - Selected device changed to <Integrated Camera> for category=0 media=2 direction=1 reason=2 11/15/2017|09:34:18.089 B40:15E0 TRACE :: SipStackGlobalInit - Doing WSAStatusup(1,1) 11/15/2017|09:34:18.089 B40:15E0 TRACE :: SipStackGlobalInit - WsaData fields: wsaVersion=1.1(0x101), wVersion=1.1(0x101), wHighVersion=2.2(0x202) 11/15/2017|09:34:18.089 B40:15E0 INFO  :: ProxyMessageHandler::Initialize: ProxyMessageHandler Initialized 11/15/2017|09:34:18.089 B40:15E0 TRACE :: client[000000E34EDEDF00] new sipStack[000000E34EFCC940] 11/15/2017|09:34:18.093 B40:15E0 INFO  :: SIP_STACK::QueryPlatformAuthCaps ProtocolsFromPlatform=0x2f 11/15/2017|09:34:18.099 B40:15E0 WARN  :: CUccPlatform::EnableTracing: tracing is already enabled 11/15/2017|09:34:18.581 B40:15E0 INFO  :: Crop=2  11/15/2017|09:34:21.666 B40:15E0 INFO  :: CUccServerEndpoint::Initialize - This endpoint is  sharing presentity data. 11/15/2017|09:34:21.667 B40:15E0 INFO  :: CUccEndpoint::put_TelephonyTypewrite - Set TTY enabled to false 11/15/2017|09:34:25.643 B40:15E0 INFO  :: Function: CUccEndpoint::Disable 11/15/2017|09:34:25.655 B40:15E0 TRACE :: Condition failed with 80ee0092: 'GetState() != UCCES_IDLE' 11/15/2017|09:34:25.659 B40:15E0 INFO  :: SIP_REGISTER::Unregistration already in unregister/ed state (0), this [000000E3586B3350] 11/15/2017|09:34:25.659 B40:15E0 INFO  :: SIP_STACK::DeleteSipEndpoint deleting sip endpoint 000000E3586B2CB0, this 000000E34EFCC940 11/15/2017|09:34:25.659 B40:15E0 INFO  :: SIP_ENDPOINT::Shutdown (586b2cb0) Shutdown 11/15/2017|09:34:25.681 B40:15E0 INFO  :: CUccDnsResolverManager::Stop MR-INFO - [000000E358670530] DNS resolver manager stopped 11/15/2017|09:34:25.702 B40:15E0 INFO  :: CUccPlatform::WriteStreamToLog: 11/15/2017|09:34:25.702 B40:15E0 INFO  :: <?xml version="1.0" encoding="UTF-8"?>

    <root>

      <Login>

        <Info><![CDATA[Created DefaultCredential: CManagedCredential[DEFAULT this=000000E34EE586C0]]]></Info>

        <Info><![CDATA[Adding new managed cred CManagedCredential[DEFAULT this=000000E34EE586C0]]]></Info>

        <Info><![CDATA[Created DefaultProxyCredential: CManagedCredential[DEFAULT this=000000E34EFAC2A0]]]></Info>

        <Info><![CDATA[Adding new managed cred CManagedCredential[DEFAULT this=000000E34EFAC2A0]]]></Info>

        <Info><![CDATA[GetBestManagedCredentialByType return the cred: 0000000000000000, type:specific, userId:PHO]]></Info>

        <Info><![CDATA[GetBestManagedCredentialByType return the cred: 0000000000000000, type:certificate, userId:OCS]]></Info>

        <Info><![CDATA[Starting bootstrap task: baseUrl=, pinBased=0, forceDownloadRootCert=0, deviceId=F3327F21-1A9B-5C38-BDDA-6E56BE71ED91, credType=0, cert=0000000000000000]]></Info>

        <Info><![CDATA[Bootstrap task queued]]></Info>

        <Info><![CDATA[Changed CBootstrapper status [10000] -> [10000]]]></Info>

        <Info><![CDATA[Bootstrap task completed with hr=0x0]]></Info>

        <Info><![CDATA[Changed CBootstrapper status [10000] -> [10006]]]></Info>

        <Lync-autodiscovery>

          <Info><![CDATA[GetBestManagedCredentialByType return the cred: 0000000000000000, type:specific, userId:LAD]]></Info>

          <Info><![CDATA[Discovery request sent to URL http://lyncdiscoverinternal.XXXXX.com.cn?sipuri=test11@XXXXX.com.cn, txn (000000E35427D7A0), task(000000E351EFA220)]]></Info>

          <Info><![CDATA[GetBestManagedCredentialByType return the cred: 0000000000000000, type:specific, userId:LAD]]></Info>

          <Info><![CDATA[Discovery request sent to URL https://lyncdiscoverinternal.XXXXX.com.cn?sipuri=test11@XXXXX.com.cn, txn (000000E35427D840), task(000000E351EFAAE0)]]></Info>

          <Info><![CDATA[GetBestManagedCredentialByType return the cred: 0000000000000000, type:specific, userId:LAD]]></Info>

          <Info><![CDATA[Discovery request sent to URL https://lyncdiscover.XXXXX.com.cn?sipuri=test11@XXXXX.com.cn, txn (000000E35427D860), task(000000E351EFBAA0)]]></Info>

          <Info><![CDATA[GetBestManagedCredentialByType return the cred: 0000000000000000, type:specific, userId:LAD]]></Info>

          <Info><![CDATA[Discovery request sent to URL http://lyncdiscover.XXXXX.com.cn?sipuri=test11@XXXXX.com.cn, txn (000000E35427D7E0), task(000000E351EFBE20)]]></Info>

          <Info><![CDATA[

    Starting LogonSession...

       Local interfaces: count=1, allExternal=0, someInternal=0, backend=0

       Cached endpoint config found but not used

       Using loaded endpoint config

    InitialEndpointConfig calculated...

       networksAvailable=1

       cacheAvailable=1

       takenFromCache =0

    Doing logon attempt with data:

       currState=10

       sipUri=test11@XXXXX.com.cn

       server=<auto-discovered name>, internal

       authModes=0x1000c

       with default Cred

       proxyAuthModes=0x3f

       epFlags=c8

       withAutoRetrials=1

       credsAvailability=valid

       redirectedServersList=

       newState=14

       statusCode=0]]></Info>

          <Info><![CDATA[CLogonCredentialManager::GetProxyCredentials()Requesting credential user 0x000000E34EE11E40 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]></Info>

          <Info><![CDATA[CLogonCredentialManager::GetProxyCredentials()Requesting credential user 0x000000E34EE11E40 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]></Info>

          <Info><![CDATA[CLogonCredentialManager::GetProxyCredentials()Requesting credential user 0x000000E34EE11E40 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]></Info>

          <Info><![CDATA[CLogonCredentialManager::GetProxyCredentials()Requesting credential user 0x000000E34EE11E40 id=15 asking for credentials with ProxyChallengeDetails[authModes=0, firewallName=, realm=]]]></Info>

          <Info><![CDATA[Discovery task(000000E351EFA220) sent to URLhttp://lyncdiscoverinternal.XXXXX.com.cn completed with hr=0x80f10045]]></Info>

          <Info><![CDATA[Discovery task(000000E351EFAAE0) sent to URLhttps://lyncdiscoverinternal.XXXXX.com.cn completed with hr=0x80f10045]]></Info>

          <Info><![CDATA[StopComponentForced called]]></Info>

          <ExecutionDuration>4002</ExecutionDuration>

          <SequenceID>1.1.1</SequenceID>

          <hr>0x80f10008</hr>

        </Lync-autodiscovery>

        <ExecutionDuration>7411</ExecutionDuration>

        <SequenceID>1.1</SequenceID>

        <hr>0x1</hr>

      </Login>

    </root>


    2017年11月20日 7:29
  • Hi patriotabc,

    感谢您的回复.

    对于您描述的外部用户与内部用户无法互相传文件的情况,我们再给予您一些排查建议:

    1.请查看下Lync边缘服务器中Event Log信息,在Event Lync server”目录下查看是否有报错信息,如果有请提供下具体的EventID和报错信息;

    2.您的边缘服务器是如何配置的,是为不同的服务(accesswebconferenceA/V)使用相同的FQDN配置不同的端口,还是配置不同的 FQDN

    如果使用单FQDN不同端口,请提供下配置的端口信息,另外请检查防火墙上对这些端口都开放。

    如果使用不同FQDN,请检查下各个FQDN名称配置正确以及对应端口在防火墙上都开放。

    端口主要有TCP/UDP 3478, 443.

     

    另外,根据您提供的Log信息,据我们分析这些内容只包含用户Logon时的一些信息,并没有记录到问题出现时的情况。我们建议您可以先退出客户端,删除Trace下文件,登陆Lync客户端复现问题,获取Log文件。您也可以使用Notepad打开分析log文件查看错误信息。



    Regards,

    Leon Lu


    如果以上回复对您有所帮助,建议您将其“标记为答复”.
    如果您对我们的论坛支持有任何的建议,可以通过此邮箱联系我们:tnsf@microsoft.com.

    2017年11月22日 8:42
    版主
  • 1.请查看下Lync边缘服务器中Event Log信息,在Event Lync server”目录下查看是否有报错信息,如果有请提供下具体的EventID和报错信息;

    在边缘服务器上没有看到相关错误信息,只在客户端上看到Lync事件号为11的日志

    Lync 发出的 SIP 请求意外失败 (状态代码 0)。下面的技术数据中提供了更多信息:
     
     RequestUri:   sip:zengyongchun@aa .com.cn;opaque=user:epid:0TdfqhMkklSBY4BavkGQ9QAA;gruu
    From:         sip:test11@aa.com.cn;tag=8848b504f0
    To:           sip:zengyongchun@aa.com.cn;tag=a0c0a68e7a
    Call-ID:      6fdb88cacc0e4ab0a9f0eb0c2f4d3dae
    Content-type: application/sdp;call-type=im

    v=0
    o=- 0 0 IN IP4 192.168.43.64
    s=session
    c=IN IP4 192.168.43.64
    t=0 0
    m=message 5060 sip null
    a=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/x-ms-ink application/ms-imdn+xml text/x-msmsgsinvite


    Response Data:

    101  Progress Report
    ms-diagnostics:  13004;reason="Request was proxied to one or more registered endpoints";source="LYNC-FE01.AA.COM.CN";Count="1";appName="InboundRouting"


    0  (null)
    (null):  52112;reason="Callee did not receive an ACK for the 200 OK";OriginalPresenceState="15000";CurrentPresenceState="15000";MeInsideUser="No";ConversationInitiatedBy="6";SourceNetwork="2";RemotePartyCanDoIM="Yes"

     
     解决方法:
     如果继续发生此错误,请与网络管理员联系。网络管理员可以使用诸如 Windows Resource Kit 中的 winerror.exe 或 Office Communications Server Resource Kit 中的 lcserror.exe 等工具来解释上面所列的任何错误代码。

    2.您的边在边缘服务器上没有看到缘服务器是如何配置的,是为不同的服务(accesswebconferenceA/V)使用相同的FQDN配置不同的端口,还是配置不同的  FQDN

    使用的同一IP的不同端口,FQDN名称不同

    如果使用单FQDN不同端口,请提供下配置的端口信息,另外请检查防火墙上对这些端口都开放。

    如果使用不同FQDN,请检查下各个FQDN名称配置正确以及对应端口在防火墙上都开放。

    端口主要有TCP/UDP 3478, 443.

    防火墙是开放的,使用telnet 可以访问相应的端口

    另外,根据您提供的Log信息,据我们分析这些内容只包含用户Logon时的一些信息,并没有记录到问题出现时的情况。我们建议您可以先退出客户端,删除Trace下文件,登陆Lync客户端复现问题,获取Log文件。您也可以使用Notepad打开分析log文件查看错误信息。

    2017年12月8日 9:16
  • UCCLOG日志超过了6000字符,上传不上来,有其他方式可以传输吗?
    2017年12月8日 9:20
  • Hi patriotabc,

    感谢您提供的信息。

    对于这个报错,我们做了一些调查,给予您以下建议:

    1.请检查下边缘服务器上的内网卡证书SN,请使用仅包含边缘服务器FQDNSN的证书(SN=edge.domain.com),而不要使用将边缘服务器FQDN包含于SAN的证书 (SN=pool.domain.com, SAN=edge.domain.com).

    2. 请检查边缘服务器路由及DNS解析信息,在边缘服务器端可以正常解析每台前端服务器FQDN及前端池FQDN,对于边缘服务器内网卡有添加静态路由至内网相关网段(内网服务器和客户端网段)。


    Regards,

    Leon Lu


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    2017年12月12日 2:27
    版主