Announcements
We are trying to install Microsoft Dynamics Sl 2011 workstation client on Windows 2012 R2 server. We mapped drive to SL 2011 SL\Applications folder and try to launch the setup installer from the workstation folder as usual. When the process gets to the point of asking for the location of the application files it populates with the correct UNC path, but then it gives an error message saying that you can't install from a UNC path but only from a mapped drive. If we click on the browse button, the mapped drive does not show, but if I look on the workstation, I can see the mapped drives. If we copy and paste the path into the box, we get the error saying the selected path doesn't contain the exe file.
Does anyone know what we can do to get client installed?
*This post is locked for comments
It sounds to me like you are running into Windows 10 user account issues. When you launch a command prompt as an Admin that is a different account than the one as a user. Here is how we install it:
- Open command prompt as admin
- Map share
- Run install
- Close admin command prompt
- Open regular user command prompt
- Map share (or through Group Policy which is much better).
- Run dynamics.
Thank you everyone for your help. I finally put in a tech support incident with Microsoft and I am including for your future knowledge the response which seems to have worked. We now have the client workstation installed. Even though the directions are are Windows 8, it does work with Windows 10 as well.
Mapping drives need to be persistent and applied to both elevated privilege and standard access.
To install from client:
1. Open a command prompt ‘as administrator’.
From Windows 8 start menu type COMMAND.
Right mouse click on ‘Command Prompt’ and select ‘Run as administrator’
2. Map the drive share
NET USE S: \\computername\sharename /PERSISTENT:YES
3. Run setup from the workstation folder
CD APPLICATION\WRKSTN
SETUP
4. Follow the usual prompts
5. Close the command prompt when completed
6. Open the command prompt without administrator
From Windows 8 start menu type COMMAND.
Select the ‘Command Prompt’ Entry.
7. Map the drive share
NET USE S: \\computername\sharename /PERSISTENT:YES
To verify try running Dynamics SL from the icon places on the Windows 8 menu as well as the Database Maintenance icon placed in control panel/Administrative Tools
Note: to remove the network mapped drives will require removing both the Administrator privileged and the standard access mappings.
Thanks. We will try and let you know if we are successful.
Try what Rena suggested and let us know if that worked. I recall having to do that approach with one client some time back now that Rena reminded me. With Microsoft increasing security in its products with each new version, there are times where the installer ends up not passing the needed security requests to an updated server and this might be your case here. Just clicking run as administrator is not quite the same as opening the command prompt as the administrator, mapping the drive using net use and then running setup.exe from the command prompt.
Hi Rick,
Yes, you are correct. We are trying to install a windows 10 workstation running a windows 2012 R2 server. Yes, we did try to run as administrator. We are using the SL 2011 FP1.
you need to run the install as "run as administrator"
you also need to run the install from the mapped drive letter. (J:\applications\ ) for example.
THEN You have to edit the registry.
1. HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\DynamicsSL---> Update the INSTALLDIR and ParentDirectory entries to the mapped drive path to the SL program files (for example, if the workstation has the J drive mapped the path would be J:\Applications)
2. 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
3. You may also have to fix the shortcut path for Dynamics SL to be J:\Applications\MSDynamicsSL.exe.
This also applies to Windows10.
We had the same issue. We mapped the drive and then ran it from the command prompt:
net use drive: \\server\msdynamics
changed directory to the directory with the install program (cd \SL\Applications)
ran the executable from the command prompt (.\clientsetup.exe)
This worked for us.
Barbara, I want to make sure that I understand the exact problem. I am taking you to say that you are trying to install the SL 2011 client on a Windows 10 workstation where Dynamics SL is installed on a server running Windows 2012 R2. Is that correct? The text of your question makes it sound like you are trying to install the SL client on the Windows server.
Assuming my assumption of what you are trying to do is correct, when you launch the SL client setup file are you just double-clicking it or are you right-clicking and selecting run as administrator? Do you have the original SL 2011 or is it SL 2011 FP1?
I have clients using Windows 10 with Dynamics SL 2011 installed on Windows Server 2012 R2 so I know this combination works. We just have to narrow down why your situation is different.
Unfortunately, non of these suggestions have worked.
In addition to what Rick said, you can try disconnecting the mapped drive and and remapping it via the command prompt using the NET USE command.
It seems like this was a bug that occurs in Win 8 as well.
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156