on 2013 Jun 20 3:38 PM
Hello,
We have been working on getting an installation server set up, but have run into an issue.
When we call the NwSapSetup.exe executable as an admin user the install completes successfully, as do the updates when necessary, however our LSH does not seem to work for non-admin users.
We've configured the LSH with a domain admin account, and it seemed to be accepted by the server, but whenever we try to do an install with a non-admin user we immediately get the following error:
NwSapSetup was not able to grant you administrator rights, either because
- the distribution service didn't respond,
- the installation service couldn't be started or
- the logon credentials for the installation service are incorrect.
Please contact your system administrator.
I'm pretty sure it's not the top two bullets - since this works fine when an admin user runs it, but we've validated the logon credentials for the installation server a couple times as well - and can't find any indication that there are any issues.
Additional info (in case it's helpful)
The install process isn't generating any logs in the SapSetup log directory for me to check, so the above message seems to be all that I have to go on.
I've allowed Remote Service Management through the firewall on the target machine as well - as per the SAPSetup Guide document.
We're running Installation Server Version 9.0.35.0
I'm afraid I'm not sure what I need to evaluate next. We know our installation server works ok - it seems to just be LSH that is failing. Is there a specific permission on the domain admin that I need to validate, or something additional to do on the target machine? Anything you know that would point us in the right direction would be much appreciated.
Thanks,
Jonathan
Help others by sharing your knowledge.
AnswerRequest clarification before answering.
SAP Support provided me a new version of NwSapSetupDs. It seems that even though I was applying the patches to upgrade this (on multiple servers), it was still remaining at the base level. Once I overwrote this file, everything seems to be working ok.
Frustrating that it didn't get updated automatically on a patch - but at least it's now resolved. Thanks so much for all your help/feedback on this one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
After several tries, we end up in finding this solution:
Restart the service(s) SAP Front-End LSH Service (NwSAPDistribSvc).
If you don't restart the service(s) LOCAL SECURITY HANDLING FAILED error appears as documented before.
If we restart the service(s) it works.
Best Regards.
Franco
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's awesome Franco - I'm glad you were able to get it resolved.
I've tried the same from our end, and even after restarting the service on the installation server installs on both Windows 7 and on XP still fail, with the same error messages as previously. It looks like we may have different errors.
I'm hoping SAP will be able to resolve this on my message, and I'll post the resolution here if so, but in the meantime I'm glad that at least one of us has it up and running now...
Thanks Franco,
I went and verified that it was up - but just to be safe I stopped and restarted the service, and then went and tested it against our windows 7 machine. Unfortunately I still had the same result with the error about LSH.
I should also mention, SAP referred me to note 1162270 which had some additional setup instructions on it for the installation server, and some tests for the client. I went through the note and did all suggested tests and changes. It didn't make a difference in my error - but I wanted to reference it here as well in case it helps anyone else having this issue.
Which OS are you using for your installation server? I just upgraded my patch to 9.0.36.0, but am still not able to get this to work - even after restarting the service. I'm wondering if there's a difference in the OS?
We're using windows server 2003. If you're using something different I'm going to try to set up a test system with that OS, and see if I can duplicate your success
Hi Jonathan,
Check for the logs at C:\Program Files\SAP\SapSetup\LOGs on your target system.
Please refer to this document for additional information and double check the LSH configuration.
http://scn.sap.com/docs/DOC-43075
Thanks
Thirumal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please read carefully the post.
Don't keep on asking what we can't provide:
Additional info (in case it's helpful)
The install process isn't generating any logs in the SapSetup log directory for me to check, so the above message seems to be all that I have to go on.
Same situation here.
No logs on client PC.
We tried 9.0.34 and 9.0.35, same results.
But.....when we create the installation server the first time, from compilation 2 and sap setup 9.0.32, it works very well.
The first attempt to patch the server ends up in the same results as Jonathan reported in his question.
Best Regards.
Franco
Thanks Thirumal,
It looks like this document is pretty similar to the SAPSetup Guide pdf document that comes with the installation server, but I've reviewed it, and haven't found any additional information for my setup that I hadn't already completed.
Do you happen to know if there is a way for me to increase the verbosity of the logs by using a flag, or switch when I call NwSapSetup.exe? Perhaps if I can put something in there it can give me an idea of what specifically it is failing on, rather than just telling me that it has a general problem.
Hi Jonathan,
I tried to reproduce the same error on Windows XP workstation and it's ended up with the Return Code - 5. (the same error what you are getting)
NwSapSetup was not able to grant you administrator rights, either because
- the distribution service didn't respond,
- the installation service couldn't be started or
- the logon credentials for the installation service are incorrect.
Please contact your system administrator.
Please create a message in BC-FES-INS and attach the log files
Here's my log from XP workstation
********************************************************************************
Logfile: C:\DOCUME~1\UserName\LOCALS~1\Temp\NwSapSetup.log
Started logging: Fri Jun 21 08:44:32 2013
Operating system: Windows XP Professional (Service Pack 3, Build 2600)
Executing user: user
Workstation name: SystemName
Windows directory: C:\WINDOWS
Temp directory: C:\DOCUME~1\UserName\LOCALS~1\Temp
Working directory: C:\DOCUME~1\UserName\LOCALS~1\Temp\Sap86.tmp
Commandline: 'C:\DOCUME~1\UserName\LOCALS~1\Temp\Sap86.tmp\Setup\NwSapSetup.exe /package:"c4f29757-d407-46bc-aad7-f59192338a1b" /nodlg'
Executable: 'C:\DOCUME~1\UserName\LOCALS~1\Temp\Sap86.tmp\Setup\NwSapSetup.exe'
Version: 9.0.35.0
ProcessId: 4088
ThreadId: 1652
Physical memory: 2602 MB of 3292 MB free
System Uptime: 0 day, 9:43:54 hours
System libraries information
----------------------------
atl.dll: 3.5.2284.2
comctl32.dll: 5.82.2900.6028
mfc42.dll: 6.2.8081.0
msvcrt.dll: 7.0.2600.5512
oleaut32.dll: 5.1.2600.6341
shell32.dll: 6.0.2900.6242
shlwapi.dll: 6.0.2900.5912
msi.dll: 3.1.4001.5512
SAP Setup libraries information
-------------------------------
NwSapSetupEngine.dll: 9.0.35.0
NwSapSetupATLCommon.dll: 9.0.35.0
NwSapSetupUi.dll: 9.0.35.0
NwSapFeiUt.dll: 9.0.35.0
********************************************************************************
08:44:32 NwSapFeiUt 1 Not running on a terminal server host.
08:44:33 NwSapSetup 1E Server C:\DOCUME~1\UserName\LOCALS~1\Temp\Sap86.tmp\Setup is on a local drive!
08:48:38 NwSapSetup 1E LOCAL SECURITY HANDLING FAILED
08:48:38 NwSapSetup 1 ------------------------------------------------------------
08:48:38 NwSapSetup 1 Return-Code: 5
08:48:38 NwSapSetup 1 ------------------------------------------------------------
Franco,
Please refer these links
Note 559578 - SAPSetup Exit Codes - Your problem indicates Return Code - 5
Thanks
Thirumal
Thanks Thirumal,
We tried this on XP and observed the same result. On XP we get a log file similar to what you see, but on windows 7 get the error in my initial post, without a log file. It's curious that one OS generates a log file and one doesn't - but for me the larger issue seems to be that they are both failing when trying to use LSH.
I will work on getting a message created in BC-FES-INS.
Thanks again for all your help Thirumal,
I tried the solution from the ittoolbox link. It seemed to suggest not using the fully qualified name (which I was already doing). As a second check I tried using just the IP address of the installation server, but still had the same result. Both of these tests were done in against a Windows 7 host machine, and neither resulted in any logs.
I've also opened up message 574504 for this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.