Error Setting up Local Security Handlind (LSH)

[Former Member]

I'm trying to set up the SAPSetup installation server 7.10 following the documentation on the pdf available on MarketPlace... but having problems. I've configured the distribution service with accounts with all permisions. I know they should work, but on the LSH configuration wizard, fails showing:

<b>Failed to configure LSH.

Can not found the language resource on the image file:</b>

And of course, the installations on workstations fail as follows:

<b>

12:39:12 NwSapSetup 1E EventName: Global\IS_NW_SAPSETUP_Sync_Event69751968

12:39:43 NwSapSetup 1E LOCAL SECURITY HANDLING FAILED</b>

I've patched the Installation server with gui710_4 patch.

I've implemented OSS Note 1101397 & 1045238

I've cheked and triple checked OSS Note 593486.

Your help will be very apreciated.

Thanks in advance

[Former Member]

It's all over.

My problem was, the windows service created with the SAP installation Server, has a unknow problem on the first attempt to set the LSH. After this was for me, set the LSH.

If I delete this SAP windows service and try to set again the LSH, results succesfully, a new SAP windows service is generated and the installation on remote computers works fine.

I miss a SAP Uninstall process for the new installation server exists (like in older version).

Thanks!

[Former Member]

Thanks for you reply.

I've patched the SAP Installation Server with recently guipatch level 5, but LSH wizard ends with the same error:

<b>LSH failure.

Can not found the language resource on the image file</b>

Any suggestion to help me, please???

Thanks

[Former Member]

Sorry, the full description of the error on a workstation is:

<b>12:42:17 NwSapFeiUt 1E CallNamedPipe failed; maybe DS is not running or networking problem occurred: Pipe is ending .## Error code 0x6d (109)

12:42:18 NwSapSetup 1E * LSH failed *

12:42:18 NwSapSetup 1E LOCAL SECURITY HANDLING FAILED

12:42:18 NwSapFeiUt 3 Utilities Library shutdown</b>

Thanks for your help!

Kind regards

[former_member204746]

try with patch 5 which was released yesterday.