|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
We recently ran into this "Access is denied" issue. Jenkins had been working fine, but we decided to clone our Jenkins VM, so we could build another Jenkins instance. After the clone, we received the "Access is denied" message on the original Jenkins instance. So, we tried to log into the Jenkins VM, and we received the error "The security database on the server does not have a computer account for this workstation trust relationship." Apparently, the cloning process had changed something about the DNS configuration. I don't know what exactly changed, but once the DNS conflict was resolved by our Sys Admin team, we were able to use Jenkins again. Not sure if your case is the same issue, but might be worth trying to login directly to the Jenkins server to see if any errors display.