DNS + Dropbox in NAV issue

Milad Rahmani 21 Reputation points
2023-01-18T15:10:10.7366667+00:00

Hi all,

This is an error message when a user wants to drag a pdf or other word file and import it into Dynamics Business Central. There is a Dropbox feature in this application where a user can drag and drop files. When importing, the user gets an error message. This happens when the user works at home, i.e. connects to wifi at home. When users work at home they make vpn connection, otherwise there is no possibility to access company files.

Would like to know where to look in the DNS? I don't understand anything about it? would like to learn in which corner to look. Because this is a DNS issue on a Windows Server 2019. Or maybi is this a Dynamics Business Central issue? 
I have completely reinstalled the laptop and Dynamics Business Central and insert the laptop again on the domain with a new laptop name for in Active Directory and reinstalled windows as well, and still it is only with this user who gets this error message. What am I supposed to understand about this error message? 

I look forward to your response,

Regards,

Milad

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
2,201 questions
No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Milad Rahmani 21 Reputation points
    2023-01-18T15:11:00.4833333+00:00

    This is the screenshot of the error message.

    Screenshot 2023-01-18 141212

    No comments

  2. Marilee Turscak-MSFT 20,596 Reputation points Microsoft Employee
    2023-01-20T19:49:23.7766667+00:00

    That error indicates that there's nothing at the path you're supplying to the call. Normally this occurs if there is a typo or incorrect character in the path.

    [https://www.dropboxforum.com/t5/Dropbox-API-Support-Feedback/path-not-found-error/td-p/284453

    I would suggest posting this to the Dropbox or Dynamics forums though as this does not appear to be an Azure issue.

    No comments