[OO Tip] Error: "A device attached to the system is not functioning"
Receiving these errors when trying to create users in AD using a flow using the (/Base [1.0.142]/Library/Operations/Active Directory/.NET/Users/Create User) operation.
Error in the debugger.log
session;exception=System.DirectoryServices.DirectoryServicesCOMException (0x8007001F): A device attached to the system is not functioning.
at dotNETWebActions_LDAP.ADCreateUser.Execute(ActionRequest req, ISession s, IActionRegistry reg);isSessionOn=False;}
Error in the Studio.log:
Caused by: java.lang.RuntimeException: Unable to execute mojo: Execution null of goal com.hp.oo:oo-web-sphere-legacy-plugin:1.0.37:plugin-metadata failed: Plugin com.hp.oo:oo-web-sphere-legacy-plugin:1.0.37 or one of its dependencies could not be resolved: The repository system is offline but the artifact com.ibm.websphere:ws_runtime:jar:6.1.0 is not available in the local repository.
This issue was caused by the failure to deploy a OO third party Content Pack (CP) which was a dependency of the used operations. For more information please visit https://hpln.hp.com/node/44/contentfiles (in Downloads tab you will find a folder under the "/HP Operations Orchestration 10.00/Process Automation Libraries/Third Party/Third Party Content Pack 1.x/oo10-thirdparty-cp-1.0.x" CP with the relevant release notes)
A template content pack was added in order to be used for libraries that will not be delivered with the out-of-the-box content due to legal considerations. It is called OO Third Party CP (oo10-thirdparty-cp-1.0.x) and serves for the following integrations:
OO Midleware CP - Library\Operations\Application Servers\WebSphere
OO Midleware CP - Library\Accelerator Packs\Application Servers\WebSphere
OO Midleware CP - Library\Operations\Application Servers\BEA WebLogic
OO Midleware CP - Library\Accelerator Packs\Application Servers\BEA WebLogic
OO Business Applications CP - Library\Operations\Exchange
OO Business Applications CP - Library\Accelerator Packs\Exchange
Initially this content pack is empty and should be populated with the needed libraries (if any) using the procedure described in the above mentioned document. In order to get the Middleware operations to work, follow the steps and create a third party .jar file that needs to be imported in Central and Studio.
In the future assure that, when using third party Content Packs, that they are properly loaded and populated with the needed libraries.
Direct link to the document here:
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.