Dynamics Community Forum Thread Details

Client installer not seeing mapped drive

Dynamics SL 2011 FP1

Windows 10 OS

My client is trying to install the client on a new workstation. He has mapped the drive using the NET USE command in an admin invoked command prompt, and the mapped drive is visible in the Windows File Explorer. However, when he tries to install the MDSL client from the mapped drive, the network share appears in the application location window. Changing that to the mapped drive manually fails with a message that the MSDynamicsSL.exe file cannot be found. Trying to browse to the location, the mapped drive isn't visible. However, there are some "mapped drives" showing there that do not appear in the File Explorer.

We have detached and remapped the drive. We have verified that Network Discovery is turned on.

Any suggestions?

Dear Stuart,

You can take a look at this

This is bug 35988. it's a Windows issue that causes the SL installer to not recognize the map drive so it updates the registry incorrectly—being that it is Windows related, the SL developers cannot fix it.

These steps address the issue if the registry keys were not written correctly (e.g. the steps above were not performed):

Edit the following registry keys:

HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\DynamicsSL--->

Update the INSTALLDIR and ParentDirectory entries to the mapped drive path to the SL program files

HKEY_LOCAL_MACHINE\Software\WOW6432Node\Solomon\SolomonIV Tools for Visual Basic -->

Update the Parent Directory entry to the mapped drive path to the SL program files

For example, if the SL directory is shared on the server and workstation has the S: drive mapped the path would be S:\Applications

Best Regards,

Jana MacDonald

Quick Links

Leaderboard