Not able to access a mapped drive path Follow

Avatar
Fernando Ramos Miracle

Symptom

 One of BarTender Suite's application is not able to access a resource located through a mapped drive path, such as:

G:\MyFolder\MyFile.btw

*This is not limited to BarTender documents, but also database files, folders being scanned for trigger files, external image files, etc.

Environment

 This will mostly happen when working on a service context. Some examples:

  • Integration Platform.
  • Print Station (BarTender does run in the background in such a context).
  • When automating BarTender through our .NET SDKs form a service type application.
  • Print Portal.

Fix/Answer

 The most important thing to understand when working with mapped network drives is that they are strictly "user defined"; which means that they only exist on that user's context, or that different user could have the same "letter" mapping different network resources.

Not only that, those mapped drives are only initialized when the user actually "logs into" the computer.

Considering the above, and as a general rule, all resources meant to work on a service or mutli-user context MUST be defined using their Universal Naming Convention (UNC) path: \\ComputerName\SharedResource.

For more detailed information on the above, please read the following article:

https://msdn.microsoft.com/en-us/library/windows/desktop/ms685143(v=vs.85).aspx

 



Was this article helpful?

0 out of 0 found this helpful


Please sign in to leave a comment.