mmiltenberger Valued Contributor.
Valued Contributor.

.Net Remote Loader on Win2016 - Driver Object Password not generated

I found/reviewed dgersics post (https://community.microfocus.com/t5/Identity-Manager-User/RemoteLoaderSvc-exe-Net-Remote-Loader-loads-but-doesn-t-work/td-p/2349030/page/2) very similar to my issue.  Basically when setting up remote loader security, it is failing to generate the encrypted driver object password file; dpwd1f4b, and is instead generating dxicert.pem and dxipkey.pem in its place. 

I am using RemoteLoader 4.7.3 on Win2K16.

Here is what l am doing to generate:

Running from command line as administrator;  C:\Novell\RemoteLoader.NET\RemoteLOader.exe -config O365-Config.txt -sp P@ssw0rd P@ssw0rd 

Returns response of :

Using running lcache instance...

Loaded Novell Audit sslKey material from dxicert.pem

Loaded Novell Audit sslKey material from dxipkey.pem

DXMLRemote.CryptoEncryption: Exception has been thrown by the target of an invocation.

  at DXMLRemote.CryptString.encrypt(Char[] plainChars, Char[] key)

  at DXMLRemote.loader.RemoteLoader.setPasswords (Char [] [] passwords)

  at DXMLRemote.loader.RemoteLoader._main(String[] args, LoaderFactory factory)

The lpw1f4b filel is generated correctly, but the dpwd1f4b file is not.   


So when I start remote loader, all I get in trace is:

DirXML Log Event -------------------
Level = error
Message = Could not find file 'C:\Novell\remoteloader.NET\dpwd1f4b'.

I am guessing it has something to do with the crypto on the 2016 server?

Any insight would be appreciated.  Thanks!

Labels (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.