/build/static/layout/Breadcrumb_cap_w.png

Provisioning error NT_STATUS_RESOURCE_NAME_NOT_FOUND

Has anyone ever seen this error before while provisioning?

NT_STATUS_RESOURCE_NAME_NOT_FOUND




0 Comments   [ + ] Show comments

Answers (5)

Posted by: brucegoose03 8 years ago
5th Degree Black Belt
2

Yes i did!

Cause - KBRemoteService was still running. 

I used pskill to stop it and then I was able to provision again. 

Posted by: brucegoose03 10 years ago
5th Degree Black Belt
1
Yes, results attached below.
I tried searching google to find out what that error means, and found nothing. I've seen it happen in two different environments.



Posted by: brucegoose03 10 years ago
5th Degree Black Belt
1
I'm going to check the NTLM lan authentication and see what it's set to on the clients and on the KBOX security settings.
Posted by: GillySpy 10 years ago
Posted by: j.hough_FNP 8 years ago
Purple Belt
-1

Did you ever happen to figure out what the issue was?  We're having the same problem on some of our machines we're trying to deploy the agent too.

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ