Hello Guys,
while installing a plugin I am facing this problem
Need your help to overcome this problem.
A problem occurred while processing the request.
Logging ID=721ebbb0-29c4-47e7-b345-e8fa07d0442e
Does any one has the solution for this problem , please help me on this.
I will be thankful to you.
Thanks
Hi there,
“it doesn’t work” is always hard to remote debug. Try to always include these 3 things.
Otherwise, it’s hard for us to get into your context and you’ll have to have someone who is exactly knowledgeable come along.
In this case, others need more information than you’ve provided before they can offer much help.
Also check for that uuid in your logs
Hello sir,
Firstly I am a beginner learning devops through youtube
@halkeye sir uuid log
Log Name: Application
Source: jenkins
Date: 4/23/2023 8:12:18 PM
Event ID: 0
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Smarty
Description:
SIGINT to 3964 failed - Killing as fallback
Event Xml:
0
0
3
0
0
0x80000000000000
8290
Application
Smarty
SIGINT to 3964 failed - Killing as fallback
Log Name: Application
Source: Microsoft-Windows-Security-SPP
Date: 4/23/2023 1:14:19 PM
Event ID: 8228
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Smarty
Description:
The rules engine failed to evaluate the rules.
Reason:0x80070057
Stage:BUILD_FULL_MACHINE_STATE
Additional Data:
Event Xml:
8228
0
2
0
0
0x80000000000000
8247
Application
Smarty
0x80070057
BUILD_FULL_MACHINE_STATE
<none>
Hoping that my problem will get solved as soon as possible.
Thanks for your reply. Unfortunately, the information that you’ve provided doesn’t really allow others to help you. Enough details are usually needed so that others can duplicate the issue that you are reporting. You haven’t provided enough details so that someone else can duplicate the issue.
If others can’t duplicate the issue, then they may be able to offer guesses about what is causing the issue. Your report is missing key information that could help others offering those guesses.
For example, you noted that you were installing plugins and then listed a few of the plugins. To duplicate the issue, others need the exact list of plugins and their versions. Instructions for gathering that exact list of plugins and their versions is included in “How to report an issue”.
I made some guesses about the steps you were taking and tried to duplicate the issue that you’re reporting. I was unable to duplicate the issue. The steps that I took included:
java -jar jenkins.war
java -jar jenkins.war
I did not encounter the “Oops” page while taking those steps. The list of plugins that were installed is included in the details below:
Jenkins: 2.387.2 OS: Windows 11 - 10.0 Java: 17.0.7 - Eclipse Adoptium (OpenJDK 64-Bit Server VM) --- ant:487.vd79d090d4ea_e antisamy-markup-formatter:159.v25b_c67cd35fb_ apache-httpcomponents-client-4-api:4.5.14-150.v7a_b_9d17134a_5 bootstrap5-api:5.2.2-2 bouncycastle-api:2.27 branch-api:2.1071.v1a_188a_562481 build-timeout:1.30 caffeine-api:3.1.6-115.vb_8b_b_328e59d8 checks-api:2.0.0 cloudbees-folder:6.815.v0dd5a_cb_40e0e commons-lang3-api:3.12.0-36.vd97de6465d5b_ commons-text-api:1.10.0-36.vc008c8fcda_7b_ configuration-as-code:1625.v27444588cc3d credentials:1236.v31e44e6060c0 credentials-binding:604.vb_64480b_c56ca_ display-url-api:2.3.7 durable-task:504.vb10d1ae5ba2f echarts-api:5.4.0-3 email-ext:2.96 font-awesome-api:6.3.0-2 git:5.0.1 git-client:4.2.0 github:1.37.0 github-api:1.303-417.ve35d9dd78549 github-branch-source:1703.vd5a_2b_29c6cdc gradle:2.5.1 instance-identity:142.v04572ca_5b_265 ionicons-api:45.vf54fca_5d2154 jackson2-api:2.15.0-334.v317a_165f9b_7c jakarta-activation-api:2.0.1-3 jakarta-mail-api:2.0.1-3 javax-activation-api:1.2.0-6 javax-mail-api:1.6.2-9 jaxb:2.3.8-1 jjwt-api:0.11.5-77.v646c772fddb_0 jquery3-api:3.6.4-1 junit:1198.ve38db_d1b_c975 ldap:673.v034ec70ec2b_b_ mailer:448.v5b_97805e3767 matrix-auth:3.1.7 matrix-project:789.v57a_725b_63c79 mina-sshd-api-common:2.9.2-62.v199162f0a_2f8 mina-sshd-api-core:2.9.2-62.v199162f0a_2f8 okhttp-api:4.10.0-132.v7a_7b_91cef39c pam-auth:1.10 pipeline-build-step:491.v1fec530da_858 pipeline-github-lib:42.v0739460cda_c4 pipeline-graph-analysis:202.va_d268e64deb_3 pipeline-groovy-lib:656.va_a_ceeb_6ffb_f7 pipeline-input-step:468.va_5db_051498a_4 pipeline-milestone-step:111.v449306f708b_7 pipeline-model-api:2.2125.vddb_a_44a_d605e pipeline-model-definition:2.2125.vddb_a_44a_d605e pipeline-model-extensions:2.2125.vddb_a_44a_d605e pipeline-rest-api:2.32 pipeline-stage-step:305.ve96d0205c1c6 pipeline-stage-tags-metadata:2.2125.vddb_a_44a_d605e pipeline-stage-view:2.32 plain-credentials:143.v1b_df8b_d3b_e48 plugin-util-api:3.2.0 resource-disposer:0.22 scm-api:667.v8b_6e07cdc7f2 script-security:1244.ve463715a_f89c snakeyaml-api:1.33-95.va_b_a_e3e47b_fa_4 ssh-credentials:305.v8f4381501156 ssh-slaves:2.877.v365f5eb_a_b_eec sshd:3.275.v9e17c10f2571 structs:324.va_f5d6774f3a_d timestamper:1.24 token-macro:359.vb_cde11682e0c trilead-api:2.84.v72119de229b_7 variant:59.vf075fe829ccb workflow-aggregator:596.v8c21c963d92d workflow-api:1208.v0cc7c6e0da_9e workflow-basic-steps:1017.vb_45b_302f0cea_ workflow-cps:3659.v582dc37621d8 workflow-durable-task-step:1246.v5524618ea_097 workflow-job:1292.v27d8cc3e2602 workflow-multibranch:746.v05814d19c001 workflow-scm-step:408.v7d5b_135a_b_d49 workflow-step-api:639.v6eca_cd8c04a_a_ workflow-support:839.v35e2736cfd5c ws-cleanup:0.45
The message “A problem occurred while processing the request. Logging ID=721ebbb0-29c4-47e7-b345-e8fa07d0442e” is providing the identifier that you need to locate the detailed stack trace of that error in the Jenkins log on your computer. Unfortunately, you didn’t say how you installed Jenkins, so others are left to guess where you might find the Jenkins log on the computer.
The Windows installation instructions say that you can access Jenkins logs in the jenkins.err.log file in your Jenkins directory specified during the installation. You might check that directory.
There is one mention of “A problem occurred while processing the request” for the configuration as code plugin in the Jenkins issue tracker. JENKINS-64551 reports that issue when the Team Foundation Server plugin is installed. Distribution of the Team Foundation Server plugin was suspended over two years ago, so I doubt you are seeing that issue. You can check your list of installed plugins and confirm that the tfs plugin is not installed on your machine.
There are 97 other mentions of “A problem occurred while processing the request” in the Jenkins issue tracker. Without the stack trace details from your specific case, others are left to guess what might have happened. Those issues would be some of my first guesses.
Other guesses might include:
@MarkEWaite I am having the same issue with Jenkins. My jenkins version is Jenkins 2.440.1. However, I am trying to Integrate Jenkins with Bitbucket server. The process to reproduce the error is 
Manage Jenkins – System – I input all the Jenkins URL, Name, WebHook Token but once I hit save, I get the error:
Logging ID=666ea1e2-aa99-4cee-bb96-35c5dd850133
I have updated all plugins up to date, I have removed all deprecated plugins and Jenkins is clean.
Can you assist with a fix to this issue?
You’ll find that identifier in the Jenkins log on your system. The stack trace will be needed before anyone can provide more help with the issue. The Jenkins documentation can help you find that log file so that you cani read its contents.
[quote=“MarkEWaite, post:9, topic:7105”]
@MarkEWaite Thanks for your swift response. Below is the stack trace in the Jenkins log:
enkins: 2024-03-12 15:51:29.888+0000 [id=196]#011WARNING#011h.i.i.InstallUncaughtExceptionHandler#handleException: Caught unhandled exception with ID 66fe3b7a-1494-49d4-b841-eda0f3eae93a
Mar 12 15:51:29 ip-10-240-191-107 jenkins: java.lang.IllegalArgumentException: The frontend sent an unexpected list of classes ([“hudson.maven.local_repo.DefaultLocalRepositoryLocator”,“hudson.maven.local_repo.PerExecutorLocalRepositoryLocator”,“hudson.maven.local_repo.PerJobLocalRepositoryLocator”]) rather than an expected single class. See Table to div layout migration for more information.
Mar 12 15:51:29 ip-10-240-191-107 jenkins: at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:750)
Mar 12 15:51:29 ip-10-240-191-107 jenkins: Caused: java.lang.IllegalArgumentException: Failed to instantiate class hudson.maven.local_repo.LocalRepositoryLocator from {“stapler-class”:[“hudson.maven.local_repo.DefaultLocalRepositoryLocator”,“hudson.maven.local_repo.PerExecutorLocalRepositoryLocator”,“hudson.maven.local_repo.PerJobLocalRepositoryLocator”],“$class”:["hudson.maven.local_repo.Defaul
That is usually an indication that one or more of the plugins installed on your system has not been updated as part of the configuration forms modernization project (tables to div migration).
Details are available in an earlier community post. Follow the steps in that post.
I can confirm to you that all all deprecated plugins has been removed and all plugins are updated and Jenkins has been restarted. See attached snapshot
That screenshot shows that you have 80 plugins that are not running the most recent version of the plugin. Have you restarted Jenkins since installing the plugin updates?
Updating all the plugins resolved my issue. Thank you
