LabVIEW Application Web Service Http request generates Windows Event ID 4625 : Logon attempt failure

[RandomUserXXX]

I have an application web service running on my computer witch runs perfectly fine. However, every time I make a HTTP-request to the server it seems like that the web-server tries to logon to (windows, NI Authentication)? using the ApplicationWebServer.exe. I'm using no security things like API keys or user permission, just a blank http get request. Anyone have any idea what can be causing Audit Failure Event ID 4625 task to occur?

Best regrds

[geokim98]

Good afternoon,

This behaviour has been reported with other people previously.  A possible work around to the situation is by changing the user rights to be given specific access to the windows share. 

I hope this helps as a starting point in troubleshooting your problem.

Best regards,

Geo

[RandomUserXXX]

Thank you for your reply! But can you be a bit more specific with what you men by "changing the user rights to be given specific access to the windows share." because I don't really follow.

Best regards

[Gryffin]

Hello, was a solution ever found for this? I am now experiencing the SystemWebServer.exe producing hundreds of Event 4625 per second.

My only choice was to disable the SystemWebServer.exe service, however, that renders the FPGA Compile Worker unusable.

How can I prevent these events? It is attempting a Kerberos login, but, it is not configured as such.

[Gryffin]

I resolved this by changing the "NI System Web Server" service in "services.msc" to use a specific account rather than the "Local System account". The 4625 errors in event viewer immediately disappeared and Web Server functionality was restored.

[ooth]

Hi Gryffin, 

I've looking to fix this for a long time. Unfortunately it didn't work for me. In addition to the "NI System Web Server" service do you also have to change the "NI Web Server" service to something other Log On?

Below is what mine is set to.

[Gryffin]

Hello ooth,

In my case, I am using a true "Local Account":

And I use this account for my service logon (rather than the "Local System account):

Also note that I did this for "NI System Web Server", whereas I see in your case you are doing it for the "NI Web Server". Perhaps you have a different case in which the 4625 event is being triggered by that process, but Event Viewer indicated (for me) that "NI System Web Server" was the problematic process.

To my understanding, this error results from the PC being a member of a domain (in my case it was attempting a Kerberos login) where running processes as "Local System" is restricted. I think if you use explicit credentials for an account associated with that PC, and run the service as that account, it may fix the 4625 error generation.

I hope that helps!