The BigFix Console has encountered an error and is unable to complete your request

[KVarekar]

BigFix Console has encountered an error and is unable to complete your
request.
If you choose to ignore this error, the application may be in an inconsistent state.
If you choose to quit, you will lose any unsaved changes.

The diagnostic message is:
File error “class DirectoryCreateFailed” on “C:\Users\Appadmin\AppData\Local
\Temp\2”: “Windows Error 0x10b%: The directory name is invalid.”

The Bigfix console is showing the above error.

[DanieleColi]

@KVarekar

DirectoryCreateFailed

It looks like the Console was unable to create a folder. What operations you were doing while it happened? Can you reproduce? What about using a Console on another machine, same problem?

[vk.khurava]

@KVarekar

File error “class DirectoryCreateFailed” on “C:\Users\Appadmin\AppData\Local

\Temp\2”: “Windows Error 0x10b%: The directory name is invalid.”

Try cleaning up your cache & restart console.

For manual cleanup delete following cache folder:
C:\Users\Appadmin\AppData\Local\BigFix OR %appdata%\loca\\BigFix

I have overserved similar behavior multiple times & deleting cache resolve the problem.

[KVarekar]

I already cleared the cache it worked, but came again after some time.
Is there any other suggestion?

[KVarekar]

What about using a console on another machine? Same problem.
I am working on it .

[vk.khurava]

Similar Old post:

Bes Console issue: File error "class DirectoryCreateFailed"

Hi community. Today I logged in my BigFix console and as soon as I click on any content i get an error: File error “class DirectoryCreateFailed” on “C:\Users\SA\AppData\Local\Temp\2” : “Windows Error 0x10b%: The directory name is invalid.” [BigFix_error] I don’t understand why it is referring to “AppData\Local\Temp” folder that is definitely is not a pert of the BigFix. Also clearing cashe of the console is not helping. Best regards, Anton

Another option is to try what @ageorgiev stated in the post above.

If the problem persists, you may need to verify if your endpoint controls have the appropriate exclusion for BESConsole.exe in place.

If everything is in place, I would advise opening a HCL case for additional investigation with console debug logs.

Logging

How to enable BES Console Logging?

By default logging is not enabled for the BigFix Console. How to enable logging for BigFix Console? Resolution Console logging is not enabled by default because the log can grow to be quite large. Best practice recommends you turn on the log file for debugging purposes only and then de-activate it afterwards (by removing the settings) to disable further logging. To activate console logging, create the following two REG_SZ values in the [HKEY_CURRENT_USER\Software\BigFix\Enterprise Console] re…

[JasonWalker]

That looks very likely like an antivirus or EDR product is preventing or delaying the Console in creating some temp directories that it needs to function. Check that you have your Antivirus and EDR exclusions in place.

[KVarekar]

error was because of a lot of load coming on the server most of the agents were directly connecting to the relay instead of the relay. and bandwidth was low.

[DerrickD]

This is extremely common issue in my experience. SUPER ANNOYING
I normally just have to go create the “2” folder inside of the Temp folder, then refresh the console and it works…

If I recall correctly, in the last year +/- there was a change log stating it was fixed in I think the v11 release. However, I had it happen since then to.

[quest]

@DerrickD

I normally just have to go create the “2” folder inside of the Temp folder, then refresh the console and it works…

I can confirm this worked for our BigFix installation.