VMware Horizon Community
rvb
Contributor
Contributor

View Composer agent initialization state error (2): Failed to redirect profiles directory (waited 0 seconds)

User Profiles on my linked clones desktop (XP SP2) are not redirected to data disk D.

See error above.

Profiles remain on drive C:\ and are lost if operating system disk is recomposed from master image

0 Kudos
40 Replies
tomski
Contributor
Contributor

i had the same problem, opened a support case, this problem is fixed with the latest 3.1 version.

0 Kudos
jbrazio
Enthusiast
Enthusiast

bump

I also have this error, and I'm running every component on the latest version.

So I assume theerror was not yet fixed on 3.1.. golden image is Windows XP (32bit) SP3.

The first time the golden image is created and the user logons into the VM, everything is created has it should:

- Datadisk created

- User's stuff copied to the userdisk

But when you refresh the client image, it reports the error: View Composer agent initialization state error (2): Failed to redirect profiles directory (waited 0 seconds)

EDIT Switched Agent log to be more verbose, any ideias ?

c:\windows\temp\vmware-viewcomposer-nga.log

06/05/09 01:05:50 Debug: (svmGaService:710) RunService - service started.

06/05/09 01:05:50 Status: Setting domain identity

06/05/09 01:05:50 Status: Set domain identity successfully

06/05/09 01:05:50 Info: (svmGaService:424) Local profiles features is enabled.

06/05/09 01:05:50 Info: (svmGaService:426) ExitWindows is disabled.

06/05/09 01:05:51 Status: Restored profile entries.

06/05/09 01:05:51 Error: (svmGaService:2135) Profiles registry dir doesn't match the expected persistent volume.

06/05/09 01:05:51 Error: (svmGaService:2237) Failed to verify profiles redirection.

06/05/09 01:05:51 Info: (svmGaService:2310) PolicyState set to 2

06/05/09 01:05:51 Info: (svmGaService:737) Immediate tasks have completed, policy state is 2

06/05/09 01:05:51 Status: (svmGaService:756) Service is running.

c:\windows\system32\vmware-viewcomposer-nga.log

-


svmNga run on 6/5/2009, 1:05

-


SvmFindPersistentDisks: Drive map is 0x0200000D.

Status: 0xC0000034 NtCreateFile(\??\C:\simvol.dat)

SvmMountPDisks: Creating a new mount \??\X: for volume \??\D:

SvmMountPDisks: No need to relocate disk with usage 0, index 1

SvmMountPDisks: No need to relocate disk with usage 0, index 2

NtQueryValueKey Failed: 0xC0000034

SvmRegQueryValueKeyA Failed 0xC0000034

NtQueryValueKey Failed: 0xC0000034

SvmRegQueryValueKeyA Failed 0xC0000034

SvmApplyProfilesPolicy: Relocating profiles folders to \??\X:

Status: 0xC0000034 NtCreateFile(\??\X:\Documents and Settings\All Users.bak)

SvmCopyFile: Failed to write file TCSCAN7.DAT. Status: 0xC000007F

SvmCopyDirectory: Could not copy file TCSCAN7.DAT. Status: 0xC000007F

SvmCopyDirectory: Could not copy dir vd2d4603.vdb with attrib: 16. Status: 0xC000007F.

SvmCopyDirectory: Could not copy dir I2_LDVP.VDB with attrib: 16. Status: 0xC000007F.

SvmCopyDirectory: Could not copy dir 7.5 with attrib: 16. Status: 0xC000007F.

SvmCopyDirectory: Could not copy dir Symantec AntiVirus Corporate Edition with attrib: 16. Status: 0xC000007F.

SvmCopyDirectory: Could not copy dir Symantec with attrib: 16. Status: 0xC000007F.

SvmCopyDirectory: Could not copy dir Application Data with attrib: 19. Status: 0xC000007F.

SvmRelocateProfilesFolder: Failed to copy All Users directory from \??\C:\Documents and Settings\All Users to \??\X:\Documents and Settings\All Users. Status: 0xC000007F

SvmApplyProfilesPolicy: Failed to relocate profiles folder to \??\X:. Status: 0xC000007F

SvmApplyPolicy: Done setting the clone's identity with error.

-


If you find this post helpful please don't forget to award points to it.

----- If you find this post helpful please don't forget to award points to it.
0 Kudos
jbrazio
Enthusiast
Enthusiast

OK, FOUND IT ! Smiley Happy

The issue happens when the Userdisk gets full..

This is indeed a bug that should be addressed by VMware on a future release.

-


If you find this post helpful please don't forget to award points to it.

----- If you find this post helpful please don't forget to award points to it.
0 Kudos
kcampbell
Contributor
Contributor

that's one issue that can cause that error to occur...HOWEVER, i see this error with nowhere NEAR a full user data disk (allocated 10gb and all aren't even at a gb yet). after a recompose i did a refresh with one pool by mistake instead of a reset -or the reverse- and got this error with the ENTIRE pool of machines, neither action shouldve caused this. was informed by vmware that this issue is "specifically addressed" in 3.1 - upgrading to that this wk. they also stated that somewhere here in communities and/or kb there are instructions on how to manually re-associate the machines to their original respective data disks. havent happened upon those yet, if they in fact exist - i'll definitely post...would be good to know if this winds up happening after 3.1 upgrade.

0 Kudos
jbrazio
Enthusiast
Enthusiast

Well.. I'm running 3.1 and the error is there, so I assume that part of it was addressed.. the other part not quite.

-


If you find this post helpful please don't forget to award points to it.

----- If you find this post helpful please don't forget to award points to it.
0 Kudos
kcampbell
Contributor
Contributor

did this occur after the update or was an existing error prior to the 3.1 update? curious

0 Kudos
jbrazio
Enthusiast
Enthusiast

The gold image and the linked clone pool were already there before the update to 3.1.

The pool is setup with 250Mb user disks and in a way to refresh the clone's image every two days.

One day I saw all the clones on the pool giving the "View Composer agent initialization state error (2): Failed to redirect profiles directory (waited 0 seconds)" and did some research to find out that the error should have been addressed on version 3.1.

I upgraded every component to the latest version and manually refreshed all the pool clones without any happy results, the same error was there on 3.1.

At that time I didn't know that Symantec AV was using 300Mb on "C:\Documents and Settings\All Users" with stuck virus definitions on the gold image.

So I created a new pool to see if something was "wrong" with the old pool but the error is still there after a refresh.

Later I found out that View composer tries to copy the "all users" section to the data disk thus filling the disk and giving the composer agent error.

View Composer should then be mature enough to allow refreshing the the clone's image without burping when the user data disk is full.

-


If you find this post helpful please don't forget to award points to it.

----- If you find this post helpful please don't forget to award points to it.
0 Kudos
kcampbell
Contributor
Contributor

interesting. im seeing it with 9gb free space on user data disk and ive taken off antivirus due to previous problems with performance on our images so that's no longer a factor in my environment. appears to happen when there's a reset or refresh done on an entire pool - individually i dont recall seeing it happen but when the entire group is done, that's when ive seen it pop up. this error is really problematic and im hoping soon it'll be sorted properly, apparently 3.1 does not take care of this issue as stated by their techs.

0 Kudos
jbrazio
Enthusiast
Enthusiast

Did you tried to turn the "verbose" output for the composer agent on the

gold image ?

----- If you find this post helpful please don't forget to award points to it.
0 Kudos
kcampbell
Contributor
Contributor

No, i didnt even check that - how does one go about that?

0 Kudos
jbrazio
Enthusiast
Enthusiast

On the gold image open regedit and change (you may need to create the

"LogLevel" dword)

HKLM\SYSTEM\CurrentControlSet\Services\vmware-viewcomposer-ga\LogLevel

to value 5

Then do to stuff you normally do to create a gold image (ipconfig

/relase; shutdown; snapshot) and deploy a pool from it.

On the clone8s) that burp, just open the VI client console and login as

local admin to check to log files at:

- C:\Windows\Temp\vmware-viewcomposer-*.log

- C:\Windows\system32\vmware-viewcomposer-*.log

----- If you find this post helpful please don't forget to award points to it.
0 Kudos
kcampbell
Contributor
Contributor

COOL thank you!!!

0 Kudos
jbrazio
Enthusiast
Enthusiast

Glad to help !

----- If you find this post helpful please don't forget to award points to it.
0 Kudos
rvb
Contributor
Contributor

after some testing I found the following:

If the master image has never been a member of our AD, every linked clone re-directs the user profiles to the data disk d:\

If the master image has joined our domain and the linked clones are recomposed with the master, then the profiles are no longer re-directed to the data disk but instead directed to the operating system disk c:\.

0 Kudos
kcampbell
Contributor
Contributor

VERY interesting

0 Kudos
tomski
Contributor
Contributor

Besten Dank für Ihre E-Mail. Ich bin bis am 17.08.09 abwesend.

In dringenden Fällen wenden Sie sich bitte an mailto:rene.meier@akb.ch / 062 835 78 74

Danke für Ihr Verständnis.

Freundliche Grüsse

Thomas Wehrli

0 Kudos
medbowtech
Contributor
Contributor

Just FYI, this does not appear to be fixed... has anyone had any further progress on this ?

View Composer agent initialization state error (2): Failed to redirect profiles directory (waited 0 seconds)

If I create a brand new pool things create fine but if I try to create an additional desktop in that pool it fails as well as does recomposing or refreshing.

Thanks!

0 Kudos
tomski
Contributor
Contributor

i stopped the vmware view project, because there are more problem than just this i have to solve. and no solution on the way. i'm waiting now to the new vsphere version, hopping that will bring me the success. if not i'll show the citrix way....

0 Kudos
kcampbell
Contributor
Contributor

actually im not seeing this issue in build 3.1.2, so far so good for me.

0 Kudos