on 11-11-2017 4:13 PM
I have downloaded & installed the latest SAP Gui 7.50. Previously there was no gui installed on Windows 10 64 bit laptop.
When I try to launch the app, I get a lot of errors regarding missing .dll files. I have updated the C++ environment & checked that all of the missing .dll files are now present. Yet this problem persists.
Are you on windows 10 patch 1709? Looks like patch 1709 has some weird security features which is preventing from writing certain files to the Windows folder.
Please follow SAP note 2578664 to fix the issue.
- Open a PowerShell and navigate to the folder that contains the installation source files.
- Run the following command: Get-ChildItem -Recurse | Unblock-File
Regards
Shibin Yohannan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The dos command - dir /R can be used to display the "alternate date streams" (this is a feature of NTFS) that can be removed by the powershell Unblock-File command.
The /R
switch displays any alternate data streams (ADS) that files might contain. ADS are a feature of the NTFS file system that let files contain additional metadata for locating files by author and title.
dir /R
Regards,
Darryl Rees
Hi, I'm running into the same issue, however, installing via a USB drive or local device isn't an option based on the fact that we are using MDT to image these systems, and installing the application via the MDT applications feature. This means it will install on a target machine using the network. One of the responses indicated you can run a Powershell command to essentially unblock files. However, I tested this and it did not work running from the network share that houses the installation source files.
The unblock-file feature does allow you to run files that would otherwise not be trusted based on the zone identifier. With that said, I was able to copy the source files to the local OS drive, run the unblock-file on those, and successfully install the product. I'm guessing that MS has introduced additional security features with 1709. I'm going to play with this more and see if I can focus on what the unblock feature is actually doing to allow for the installation over a network share. Otherwise I will have to copy the source files to my image, then run the unblock and then the install.
Update: I worked on this more after posting and discovered that it appears quite a few files in our SAP setup source had zone.identifiers (streams) attached to them. If you do a dir /r on the folder containing source files, you would see a filename, then another identical filename with :Zone.Identifier:$DATA. You can then check the zone identifier by typing notepad.exe <filename:Zone.Identifier> in the cmd prompt. If you see Zone 3 or 4, then it will most likely cause problems (I haven't tested other zones yet). I ran the powershell command recommended in this thread on the local system hosting those source SAP files. I was then able to install SAP from the network source successfully and there were no DLL errors when running.
We have many source applications on our imaging system so I'm not sure why the ones for SAP 7.5 happen to have these streams attached to them. Either way, removing those solved the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It works perfect if you install from a USB stick.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Folks,
I found a work-around.
I copied the installation folder to a slow thumb drive and I installed SAP GUI from there.
Try it,
Jim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.