Execution of NWCreateInstserver fails on remote server

[Former Member]

Hello all,

environment:

- 2 servers (more to come)

- version is 2008 R2

- one holds configuration (let's call it 'central SAP distribution share')

- second is to become a new frontend distribution server on a remote site.

I tried to execute NWCreateInstServer with all of the following scenarios:

(created local installation directory, gave appropriate rights, shared it - even gave everyone full access on both share and filesystem...)

- pull from downlevel server

- push from uplevel server.

I did it via commandline (
server1\...\setup\NWCreateInstserver /dest
server2\distShare /NoDlg), which I ran from both sides.

I tried to execute it as a batch job, and so on (I think I tried every possible way - at least this is what my co-workers say).

UAC is on the lowest level possible.

But:

Only the frontend installer proxy application (sorry, write from home office, don't have the correct filename with me here, now) is being copied - as soon as it comes to creation of new directory (e.g. the directory 'setup' on the downlevel server), setup hangs.

Analysis with processExplorer or FileMonitor show security issues when trying to create \distShare\Setup\filename.xml.

This is also recorded in the logfile.

But:

- I did it as local admin

- I did it as domain admin

- I gave various privileges

--> no success.

Tried it on Win7 x64 and Win7 x86, too - no success.

Anyone had this before?

Thanks for any hints,

regards,

Uwe

[jude_bradley]

Hello Uwe,

Can you upload your error logs from the server please?

Just paste any errors in the logs that start with 1E or 2E into the post.

BR,

Jude

[Former Member]

I too ran into the same failure, same file. I noticed it had moved one file SetupAll.exe to the root of the share, definitely not a permssions issue. The failure was on the first file into a subfolder.

I created the sub-folder \Setup and on the retry it worked, for a while, until the next sub-folder \Setup\DS. Same thing. I created all folders manually on the next server and it ran straight thru.

YMMV

--Doug

[Former Member]

Make sure Remote Registry service is up and running in the servers services.

Bob