Status: Resolved (View Workflow)
Environment:Jenkins on Windows Server 2003 (x86), on a non-AD server
One slave on Windows Server 2008 x64, also non-AD.
VisualSVN Server with AD authentication, also a local user account set up with permissions for the Jenkins instance.
Our dev team manage our Jenkins instance, and our corporate IT manage our VisualSVN server.
The corporate guys are complaining that Jenkins is causing VisualSVN to dump thousands of Windows event log messages as follows:
"user builduser: (OS 1326) Logon failure: unknown user name or bad password. [client 10.2.2.2]"
10.2.2.2 is indeed our Jenkins instance. It accesses SVN over https.
Jenkins is working perfectly - credentials were requested, entered, and saved, and SVN checkouts work completely as expected.
Sometimes they're seeing 20+ event log entries every SECOND - sometimes none at all for hours on end. The pattern does not tie up in any obvious way to any build schedules.
I cannot find a reasonable explanation for this, nor can I find corresponding entries in the Jenkins logs.
Is there any way to turn on some logging in SVNKit to try to track down why this failure is occurring?
Any help appreciated.