Clarity Service Management

Expand all | Collapse all

Attachment Failing

Jump to Best Answer
  • 1.  Attachment Failing

    Posted 09-27-2018 10:30 AM

    ServiceDesk attachment is not working and we are getting following error in stdlog :

     

    09/27 10:27:10.97 DC1PRCAUSB0000 rep_daemon           5196 ERROR        AttmntMng.c           2049 Failed to log off UNC logon handle. UNC library returned code: -1

     

    After service recyle it works for few seconds and then fails again.

     

    Need an urgent advise here. Using r14.1 with AA mode. Attachments are going to external file share.

     

    Thanks

    ArunavaS



  • 2.  Re: Attachment Failing

    Posted 09-27-2018 11:17 AM

    When the problem happens, from SDM server, are you able to manually go to the UNC using the same username/password and can you create a file there? The error points to UNC error.



  • 3.  Re: Attachment Failing

    Posted 09-27-2018 11:26 AM

    We don't have any UNC credential set. In attachment repository UNC credentials are blank and thats how its working for last couple of years. It seems Rep_daemon is running but failing to communicate with certain port .



  • 4.  Re: Attachment Failing

    Posted 09-27-2018 11:36 AM

    you seem to say your Upload Path is a UNC path and your UNC Credentials field is blank...if that is the case, your remote

    server maybe configured to trust this connection and there is some changes in the configuration?

    you could try this...

    from SDM server, open the windows explorer and then copy/paste the Upload Path here...do you see something? and if yes, can you open an existing file and can you write a file there?



  • 5.  Re: Attachment Failing
    Best Answer

    Posted 09-27-2018 12:55 PM

    Looks like a port issue which was failing to communicate with rep_daemon. we restarted the whole server which fixed the issue. Though the actual root cause is still not very clear. If anyone has insight please let me know or this thread can be consider closed as the actual issue fixed (somehow!)

     

    Thanks

    ArunavaS