TIBCO iProcess® Engine (iPE) upgrade on Windows fails with SE_DEBUG_NAME issue
Article ID: KB0076441
Updated On:
| Products | Versions |
|---|---|
| TIBCO iProcess Engine (Oracle) | 11.6.1 |
Description
iProcess® Engine upgrade fails on the “Setup Type” screen with the error:
Failed to set SE_DEBUG_NAME, cannot determine whether installation at ‘c:\swserver\staffw_nod1’ is running: (5) access is denied
Failed to set SE_DEBUG_NAME, cannot determine whether installation at ‘c:\swserver\staffw_nod1’ is running: (5) access is denied
Issue/Introduction
iProcess® Engine (iPE) upgrade (Windows) fails on the “Setup Type” screen with the error:
Failed to set SE_DEBUG_NAME, cannot determine whether installation at ‘c:\swserver\staffw_nod1’ is running: (5) access is denied
Environment
TIBCO iProcess® Engine on Windows - all database types and versions
Resolution
There is a permission / rights issue for the Windows user running the iProcess® Engine installer.
The IPE installer needs the Windows right SE_DEBUG_NAME to get the list of all processes on the system. The installer can then determine the node(s) for upgrade and if the node(s) is running or not.
The error is generated as the Windows user does not have permission / access to get a list of all processes running on the server.
The resolution is to grant the SE_DEBUG_NAME right to the user running the iProcess installer – this is part of Windows server administration.
The SE_DEBUG_NAME right can be set on the Windows server using the “Local Security Policy”
The right is configured under:
Local Policies\User Rights Assignment\Debug Programs
The Windows user running the iProcess installer must be added to “Debug Programs”
Alternately the SE_DEBUG_NAME right can be set in a Group Policy if these are implemented across the Windows servers / Active Directory.
The IPE installer needs the Windows right SE_DEBUG_NAME to get the list of all processes on the system. The installer can then determine the node(s) for upgrade and if the node(s) is running or not.
The error is generated as the Windows user does not have permission / access to get a list of all processes running on the server.
The resolution is to grant the SE_DEBUG_NAME right to the user running the iProcess installer – this is part of Windows server administration.
The SE_DEBUG_NAME right can be set on the Windows server using the “Local Security Policy”
The right is configured under:
Local Policies\User Rights Assignment\Debug Programs
The Windows user running the iProcess installer must be added to “Debug Programs”
Alternately the SE_DEBUG_NAME right can be set in a Group Policy if these are implemented across the Windows servers / Active Directory.
Feedback
Yes
No
Powered by
