diff --git a/docs/3-Create/Deploy/ier.mdx b/docs/3-Create/Deploy/ier.mdx
index a8346775..c157cf0d 100644
--- a/docs/3-Create/Deploy/ier.mdx
+++ b/docs/3-Create/Deploy/ier.mdx
@@ -439,4 +439,105 @@ Scale the navigator deployment down and up. If your replicas are more that 1, sc
```tsx
kubectl scale deploy fncmdeploy-navigator-deploy --replicas=0
kubectl scale deploy fncmdeploy-navigator-deploy --replicas=1
-```
\ No newline at end of file
+```
+
+## Troubleshoot
+
+### On Configuration Manager
+
+If you see this error when running the Configure File Plan Object Store task:
+```
+Starting to run Configure File Plan Object Store
+
+Configure File Plan Object Store *************************
+Finished running Configure File Plan Object Store
+An error occurred while running Configure File Plan Object Store
+Running the task failed with the following message: A network error occurred when processing a Web service request or response. See the nested exception for specific details. See full stack trace for details. Message: Unexpected end of file from server Duration 50,063 milliseconds.
+```
+
+Workaround:
+Update config of `server.xml` in the CPE pod, add a timeout for 10m:
+```
+cat server.xml
+```
+
+```
+
+
+
+
+
+```
+
+### On deploying IER (IER pod doesn't start properly or it starts but getting ssl related error)
+
+If your IER pod doesn't start:
+```
+Unable to attach or mount volumes: unmounted volumes=[custom-config-volume ier-custom-keystore-volume], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition
+```
+
+OR IER pod running ok but you see some SSL related error prevent IER engine to start:
+```
+[ERROR ] CWWKS9582E: The [cssSSLSettings] sslRef attributes required by the orb element with the defaultOrb id have not been resolved within 10 seconds. As a result, the applications will not start. Ensure that you have included a keyStore element and that Secure Sockets Layer (SSL) is configured correctly. If the sslRef is defaultSSLConfig, then add a keyStore element with the id defaultKeyStore and a password.
+```
+
+There is a workaround by manually uploading the plugin.jar to pod:
+
+1. Copy `IERApplicationPlugin.jar` from the latest IER fixpack.
+
+2. log onto Openshift and retrieve navigator pod:
+```
+oc get pods | grep fncmdeploy-navigator
+
+fncmdeploy-navigator-deploy-f64db4b8f-jj44k 1/1 Running 1 (18d ago) 18d
+```
+
+3. Upload IER plugin jar to plug-in store:
+```
+oc cp IERApplicationPlugin.jar fncmdeploy-navigator-deploy-f64db4b8f-jj44k:/opt/ibm/plugins
+```
+
+4. upload IER plugin jar to Task Manager pod: configdropin/overrrides & :/opt/ibm/extTM:
+```
+oc get pod | grep navigator
+```
+
+```
+oc cp IERApplicationPlugin.jar fncmdeploy-tm-deploy-854595dfcd-ptwm6:configDropins/overrides
+oc cp IERApplicationPlugin.jar fncmdeploy-tm-deploy-854595dfcd-ptwm6:/opt/ibm/extTM
+```
+
+### On Content Navigator (when declaring FPOS as File Plan repository)
+
+If you see error when declaring FPOS as File Plan repository:
+
+1. Create a file named ier-library.xml containing:
+
+```
+
+
+
+
+
+```
+
+2. Copy `xercesImpl-2.12.2.jar` from `/API/JARM`
+
+3. Navigate to your navigator pod, cd to `/opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides` and create a folder:
+```
+mkdir ier-jars
+```
+
+4. Then upload the files from local machine to pod:
+```
+oc cp ier-library.xml fncmdeploy-navigator-deploy-f64db4b8f-25xz5:/opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides
+
+oc cp xercesImpl-2.12.2.jar fncmdeploy-navigator-deploy-f64db4b8f-25xz5::/opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides/ier-jars/
+```
+
+###
diff --git a/docs/4-Uses/IER.mdx b/docs/4-Uses/IER.mdx
index f0a84b2b..56dbd963 100644
--- a/docs/4-Uses/IER.mdx
+++ b/docs/4-Uses/IER.mdx
@@ -180,3 +180,35 @@ These are some of the most common reports requested by Records Administrators an
3. Fillin details on report popup and click _Generate Report_

+
+
+## Troubleshoot
+
+### On IER Desktop (The object store FPOS is not configured to allow users to declare records)
+
+```
+[INFO ] FNRRD1149I: ---- Start workflow launch ----
+[ERROR ] FNRRD1035E: The object store FPOS is not configured to allow users to declare records.
+[err] Apr 22, 2024 3:22:09 PM com.ibm.ier.plugin.tasks.BaseIERTask handleErrors
+SEVERE: FNRRD1035E: The object store FPOS is not configured to allow users to declare records.
+com.ibm.ier.ddcp.exception.DDCPRuntimeException: FNRRD1035E: The object store FPOS is not configured to allow users to declare records.
+at com.ibm.ier.ddcp.exception.DDCPRuntimeException.createDDCPRuntimeException(DDCPRuntimeException.java:87)
+at com.ibm.ier.ddcp.ReportGeneration.validateInitWorkflowConfigMap(ReportGeneration.java:1085)
+at com.ibm.ier.ddcp.ReportGeneration.validatePEParams(ReportGeneration.java:1038)
+at com.ibm.ier.ddcp.ReportGeneration.launchDDWorkflows(ReportGeneration.java:747)
+at com.ibm.ier.plugin.tasks.RunDefensibleDisposalReportSweepTask.performBaseTask(RunDefensibleDisposalReportSweepTask.java:212)
+at com.ibm.ier.plugin.tasks.BaseIERTask.performTask(BaseIERTask.java:127)
+at com.ibm.ecm.task.commonj.work.BaseTask.call(BaseTask.java:75)
+at com.ibm.ecm.task.commonj.work.BaseTask.call(BaseTask.java:42)
+at javax.enterprise.concurrent.ManagedExecutors$CallableAdapter.call(ManagedExecutors.java:231)
+at com.ibm.ws.concurrent.internal.ScheduledTask.call(ScheduledTask.java:420)
+```
+
+Workaround:
+Disabling `Declare result files as a record` to prevent this error:
+
+1. Log onto IER Desktop and go to `Administration`.
+
+2. From Repositories, select `FPOS`.
+
+3. In `Basic Schedule Sweep`, change `Declare result files as a record` from Yes to No.
\ No newline at end of file