KB74647135: DeskPack - In the Server Connection Assistant when specifying SMB as protocol to mount DeskPack shares, the shares do not mount automatically

Summary

When specifying SMB as protocol to mount the DeskPack shares for example DeskPackContainer and bg_data_cms_v010, the shares do not mount automatically on startup of Adobe^® Illustrator^®. A window to fill in the username and password for the server pops up.

Symptoms

DeskPack shares (DeskPackContainer and bg_data_cms_v010) do not mount automatically on startup of Adobe^® Illustrator^®. The Diagnostics shows the following messages:

ShareMount (ERROR): Error -128 while mounting smb://cssuite12a3/bg_data_cms_v010 as admin/trap/digi...
BSCLIENT (ERROR): Failed to mount container.

However when mounting the shares manually, DeskPack works correctly.

Solution

When using SMB as protocol to mount the DeskPack shares, which is the preferred default as AFP has several limitation in the file name length and path length, it is advised to always use the following format when filling the DeskPack Server Connection Assistant:

• NODOMAIN\User, or
• SERVERNAME\User

By following the format you can ensure that the user to mount the shares is a local user on the server with appropriate access permissions. When “NODOMAIN” or “SERVERNAME” is not filled before the user name, then any domain user or network user with the same name could be used. This user may not have the correct permissions to write to the DeskPackContainer.

In case when starting up the Adobe^® Illustrator^® the following window pops up several times, correct the user login details in the Server Connection Assistant.

1. Cancel this pop up window 3 times, the following DeskPack message pops up:
   

   

2. Click the Check Settings button to open the Server Connection Assistant.
3. Type <SERVERNAME>\bgsystem username and the default bgsystem password to mount the containers. Replace <SERVERNAME> with your server name.

This will ensure that the user to mount the container is a local user on the server with the required permissions to mount and write to the containers.