Error 1326

[flowbass]

I am getting an error 1326: Access denied. Try re-entering your credentials” when running a Windows Update | Check for available updates. Confirmed the local administrator password. The machine is in a WORKGROUP and is an cached-mode and offline-mode state from the BatchPatch server.

[flowbass]

Never mind. I figured out what the problem was. I was setting the local administrator password too strong. What are the limitations in BatchPatch for setting the local administrator password inside the “Specify alternate login credentials” setting?

[doug]

I’m not sure what you’re asking. I need you to please clarify. For that matter, I’m also not sure what you’re describing about setting the local admin password too strong.

Anyway, if you specify alternate credentials in BP for a given row, you just input into the BP Credentials form the username and password that you defined for the particular user account on the target computer. There isn’t anything else special to do there.

[flowbass]

If you set the local administrator with a “strong” complex password (upper, lower, numeric, special character, 20 characters) and do the same inside the “Specify alternate login credentials” setting then it doesn’t work. It is almost like BatchPatch does not accept “strong” passwords inside this setting/field.

[doug]

Hmmm… There is no such limitation that we are aware of or that has ever been reported or that we have ever encountered ourselves. I’m not sure what to make of this observation. My initial reaction is that maybe in your troubleshooting something seemed to indicate that it was a BP limitation/issue when in reality it actually turned out to be due to something else such as a setting or password policy or something like that on your computers? I think the only way that we could conceivably figure this out with certainty is if you could provide us with the exact password that you were using… or if you are able to reproduce it with a different password and then provide us with that different password. I wouldn’t want you to do this unless it’s not in use anymore, and also I would have you send it to us via email, not in the forum here. Then we could test that exact password to see if we can reproduce the failure. Maybe somehow a certain character or sequence of characters could possibly create a weird/unexpected interaction in BP? I honestly don’t know how this could occur, but weird/obscure bugs can/do occur, so it would be hard to rule it out with certainty until we can test a password that is known to cause the problem for you. Let me know if you want to try this. Or feel free to email us through the contact form on our main website, and we can go from there. Thanks.

[Author]

Posts