Dot Net Error when starting Utility
 

Hi, since a couple of days I got a dotNet error when I am starting the utility. Regardless which version of the utility I try to start. Tried with the last three.
dotNet 4.8 is installed. Using latest Win10.

Attached is the dotNet error log.

Maybe someone has an idea ;)

Thank you very much in advance.

Courgan

Close the utility, then in the \EverQuest II\UI\DarqUI_v3 folder find a file called accounts.xml. Delete it, then try reopening the utility. Does it open?


.

It worked! accounts.xml was full of sh**... NULNUL... and so on...

Thanks a lot mate!

Courgan

I am having the same problem (the error log looks slightly different, probably because I am using English Win11). I tried the solution posted above, but this made no difference.
I can force the utiliy to start, ignoring the error. Then the file updater works, but the utility does not load any characters, so most of the functionality is not working.
I tried to repair or re-install .Net 4.8.1, but Windows seems to think that everything is as it should be.
Any more suggestions for a solution?
Thanks,

Rhim

Close the utility, then in File Explorer go to the \EverQuest II\UI\DarqUI_v3\POI folder. Find darquiv3_shutdown.xml. Move this file (don't copy it) to the Desktop, then reopen the utility. What happens?

If you have no errors, and if you are willing, please zip and send the shutdown file to me here in a private message. Don't post the file in the forum.

If you still have errors, put the shutdown file back and instead find the \EverQuest II\logincache folder. It may be named logincache-us or something similar. Move that out to the Desktop and then reopen the utility. What happens?


.

You saved the day!
The first trick did not work, but moving the logincache did!
Awesomely quick support!
Do you want a log of the logincache for your reference (but maybe you already have a good idea what cased this)?
Thanks,

Rhim

The logincache folder won't be needed but thank you for offering to send it. Use the LaunchPad to log in to Character Select once on each of your accounts, which will repopulate the \logincache folder. Don't log in to a specific character, just go to Character Select. Then finally reopen the utility, and if you still have no errors we can consider the problem resolved.


.

Ah, I may have been a bit too enthousiastic.
Indeed the problem was solved, but only as long as the login-cache was empty. As soon as I repopulated the Quick Setup list of the utility after going to the character select screen, the problem was back.

Please check your private messages.