My Oracle Support Banner

E1: PKG: Troubleshooting Server Package Deployment UBE R98825D Internal Error Code 34 - Failed To Lock/Unlock Server (Doc ID 1134365.1)

Last updated on JULY 17, 2019

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Purpose

This document was created to assist customers on troubleshooting the different scenarios, causes and resolutions for Error in Package Deployment UBE R98825D PDF as:

" Internal Error Code 34 " - Failed to Lock / Unlock Server 

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Troubleshooting Steps
 Scenario 1 - Deploying an Update Package to Multiple Servers - PKGENG0042 and PKGSVRDPL018 Errors
 Scenario 2 - Package Deploy Fails with Internal Error 34- PKGENG0042 Errors
 Scenario 3 - Package Deploy Fails with Internal Error 34- JDB9900364 - Failed to lock IPC Resource - PKGSVR0119 and PKGSVR0100 Errors
 Scenario 4 - Deploying Package to Enterprise Server and Getting Internal Error 34 - PKGENG0037 ERROR: Failed to get lock on server SVRNAME
 Scenario 5 - Package will not deploy, Internal Error 34
 Scenario 6 - R98825D shows error code 34, Failed to lock/unlock server
 Other possible scenario for Error Code 34 - IASP Setup
 How to Identify the Locked Kernel When Package Deploy Fails with Internal Error Code 34
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.