16 Bit Windows Subsystem error

[chrisukcov]

Hi all,

When connected on one of our Users machines, launching a application called Termite causes the following message:

16 Bot Windows Subsystem

C:\documents and settings etc etc\'user name'\temp\2

A temporary file needed for initialisation could not be created or could not be written to.

This only happens on one users account - on the same machine, testing another account worked fine - we have deleted the account and it recreated it but still the same message.

Any ideas??there are no special permissions on the folders - just windows defaults.

Thanks all :O)

 

[CitrixEngineer]

Try deleting the profile rather than the account

Hope this helps

 

[chrisukcov]

Sorry thats what we did - we deleted the whole users folder under c:\documents and settings and then on next logon it recreated.

Any more ideas.........please

chris

 

[CitrixEngineer]

If you're using roaming profiles, did you delete all locally cached copies of the profile (in %systemroot%\winnt\profiles)?

Is the user in question in the exact same groups, with the same policies applied?

What happens if you create a new user - do they get the correct settings?

All per-user information is stored in the profile, so it's either specific to the user, in which case completely re-creating the profile should work - if that fails, then it looks like a problem with the default profile.

Another thing you could try is to rename the old profile, then copy a profile from a user that is known to be working. The problem there, of course, is that you would have to amend the profile manually to avoid the user trying to access resources belonging to the original user!

 

[chrisukcov]

Tried different system aswell now - problem definetely down to profile on server i think. Weve scrapped the old profile settings and it recreates fine. Its on a App called Termite and its just not being able to create the path. Is there any permissions i should check? Ive made sure all Active Directory account settings /permissions are identical to a fully working user so I dont know what to do short of killing off her AD account and trying that !

Any advice over the weekend would be great for monday :O)

Cheers Guys

Chris