Has anyone ever seen this error before while provisioning?

NT_STATUS_RESOURCE_NAME_NOT_FOUND



0 Comments   [ + ] Show Comments

Comments

Please log in to comment

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

Answers

0
Answered 09/09/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
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.



Answered 09/09/2011 by: brucegoose03
Second Degree Black Belt

Please log in to comment
0
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.
Answered 09/09/2011 by: brucegoose03
Second Degree Black Belt

Please log in to comment
-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.

Answered 05/02/2013 by: j.hough_FNP
Orange Senior Belt

Please log in to comment
1

Yes i did!

Cause - KBRemoteService was still running. 

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

Answered 05/02/2013 by: brucegoose03
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity