Solved

View VDI "Error during provisioning...  Active Directory" error

Posted on 2014-12-17
15
210 Views
Last Modified: 2015-01-02
Hi.  I have an error from 6 weeks ago on this pool of non-persistent linked-clone virtual desktops.  Running View v5.x; see attached pic for details.

The pool is healthy, and has been used before and since this error.  It was a one time thing before I got here, so I don't think the AD settings are wrong.

The error COM code number specifically doesn't resolve on the web (not exactly the same number) and at this point I just want to clear this error so the system reports healthy.  Who can advise the best, safest way to do this?

Thx
VDI-1.PNG
0
Comment
Question by:Chach DalSanto
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 8
  • 7
15 Comments
 
LVL 11

Expert Comment

by:rharland2009
ID: 40507026
The 6 warnings I see there - did any of those occur at or around the time of the AD error? If so, can you show what they were?
0
 
LVL 2

Author Comment

by:Chach DalSanto
ID: 40507043
Thx for replying.  No; those events you are seeing have to do with end users letting sessions expire; a common occurrence around here.  They are from the last 2 days and are unrelated to this issue.
0
 
LVL 11

Accepted Solution

by:
rharland2009 earned 500 total points
ID: 40507083
Okay, cool. You're right - that particular error code is nowheresville on the web. Is it possible there was a momentary network disruption or some other anomalous thing that prevented communication to AD for that one moment of creation?
I'm not sure if this is what you want to hear, but if it was me, I'd look at this single event as an outlier, clear it, and move on - or I'd bite the bullet and involve Vmware support. It's a shame they don't have a full repository of error code root cause descriptors.
0
ScreenConnect 6.0 Free Trial

At ScreenConnect, partner feedback doesn't fall on deaf ears. We collected partner suggestions off of their virtual wish list and transformed them into one game-changing release: ScreenConnect 6.0. Explore all of the extras and enhancements for yourself!

 
LVL 2

Author Comment

by:Chach DalSanto
ID: 40507122
Actually, that was the exact conclusion I came to; a one-time network hiccup, a time-out of some kind due to network lag, etc. that prevented authentication from happening.  I could understand if it was a new pool and this problem was recurring, but it has worked and continues to work without issue.

Clearing the error is exactly what I'd like help with.  I've reset the hung desktop session that this happened to, and after several tries (and about 20 minutes) it cleared and all Problem Desktops are gone.  But the error still persists as shown.  I'm not sure how to clear it...

I'm not sure if a refresh/recompose will clear this, and what the consequences to users would be.  Or if I need to disable then re-enable this pool.  Or if I need to create a whole new pool and migrate workstations to it, but I'm really trying to avoid drastic measures like that.

Thx
0
 
LVL 11

Expert Comment

by:rharland2009
ID: 40507155
Looks like the recompose option might be a good bet. You can do it off-hours, force logoffs, or wait until users log off to start the recompose.

Recompose

Not positive if that'll clear that particular error, but most errors don't survive a recompose.
0
 
LVL 2

Author Comment

by:Chach DalSanto
ID: 40509058
I'm going to try to reboot a couple key servers to solve some other problems I'm having (I seem to be having glitchy behavior all around the last few days) including the vCenter (composer) server as well.  If that doesnt clear it I may bounce the whole infrastructure.  If that fails to clear it, I'll try recomposing the desktop pool as you suggest.

Now I just need to get an approved service window...

Thx.  Standby...
0
 
LVL 11

Expert Comment

by:rharland2009
ID: 40509063
Good luck, Chach! Keep us posted.
0
 
LVL 2

Author Comment

by:Chach DalSanto
ID: 40513907
Well I rebooted the vCenter server and the connection server in question.  The error still persists and cant be cleared.  Overall behavior is a bit better though, so it was a good first step.

I think I'll have to get permission to recompose this desktop pool sometime this week.  Im not sure if thats better or if I should make a new pool and just migrate everyone's vPC's to the new pool.  Thoughts on what direction would be better?  Have less administrative overhead?
0
 
LVL 2

Author Comment

by:Chach DalSanto
ID: 40513908
^ I meant security server not connection server.  Thx
0
 
LVL 11

Expert Comment

by:rharland2009
ID: 40513974
If you have space, I think migration might be a simpler task.
0
 
LVL 2

Author Comment

by:Chach DalSanto
ID: 40522011
I had a thought that maybe there was an event in the logs from when this happened, but I cant go back far enough; I get to early November and this happened mid October.  

Would a severe error like this need to be acknowledged and would that clear up that error being displayed, or do you not acknowledge errors in the event logs in VIEW that way?  If its possible that would clear it, I could override the 2000 event restriction and/or go right to the database server itself, but thats rather drastic.

Thx
0
 
LVL 11

Expert Comment

by:rharland2009
ID: 40522407
That's a good question - I haven't encountered that particular issue before. Has Vmware been of any assistance with this issue?
0
 
LVL 2

Author Comment

by:Chach DalSanto
ID: 40528339
No.  Im closing the question; it seems to be a random glitch that isnt going to clear out like its supposed to.  Thanks.
0
 
LVL 2

Author Closing Comment

by:Chach DalSanto
ID: 40528342
Helpful but ultimately root cause is undetermined.  Thanks for help!
0
 
LVL 11

Expert Comment

by:rharland2009
ID: 40528481
Wish I could have helped more - thanks.
0

Featured Post

ScreenConnect 6.0 Free Trial

Explore all the enhancements in one game-changing release, ScreenConnect 6.0, based on partner feedback. New features include a redesigned UI, app configurations and chat acknowledgement to improve customer engagement!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Learn how the use of a bunch of disparate tools requiring a lot of manual attention led to a series of unfortunate backup events for one company.
Advanced tutorial on how to run the esxtop command to capture a batch file in csv format in order to export the file and use it for performance analysis. He demonstrates how to download the file using a vSphere web client (or vSphere client) and exp…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question