DCO desktop client error when login

[DCIM_Support]

This question was originally posted on DCIM Support by Yilai Min on 2019-12-23

---

As soon as user logs into DCO, error message pops out as attached screenshot. 

below pasted error logs from client log: 

2019-12-23 11:17:00,410 WARN [com.apc.config.impact.impl.cfg.ImpactConfigurationServiceImpl] (Model Thread 0) No such profile Default. Has com.apc.config.impact.cfg.ImpactConfigurationBootstrapper been called? Anyway, creating now.
2019-12-23 11:17:19,639 ERROR [com.apc.sma.client.Application$EclipseToLog4jLogListener] (main) Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".[org.eclipse.core.runtime]java.lang.NullPointerException

(CID:153092741)

[DCIM_Support]

This answer was originally posted on DCIM Support by Jef Faridi on 2019-12-24

---

Hi Yilai,

It might be related to client temp files, user might want to start the client with clean temp files. 

Client temp files are usually location in:

(Win) C:\Users\<user name>\.isxo\8.*

this folder can be deleted (or re-maned to something like 8.*_old)

after deleting or renaming the folder, user can then start the client. 

Kind regards

(CID:153093104)

[DCIM_Support]

This comment was originally posted on DCIM Support by Yilai Min on 2019-12-24

---

Hi Jef, 

Although the user hasn't tested your  proposed workaround, I'm sure it will fix the issue.

My question is that is it a known issue or something? What did it cause?

Thanks,

Yilai

(CID:153093106)

[DCIM_Support]

This comment was originally posted on DCIM Support by Jef Faridi on 2019-12-27

---

Hi Yilai,

When I was working on another/previously reported case (room opening issue), I did not experience this, and I could start the client without any problem. So I was guessing most likely this client local files (the so-called temp files) might not be updated and therefore null pointer exceptions occurring. 

Kind regards

(CID:153093108)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.