Windows script host login error

[Little John]

I am having a problem with a user account displaying the following message on login


windows script host loading your profile settings failed (Access denied)

I have also tried logging on to the terminal server and I get the same error with the same user account but if I use another account the error doesn't appear.

Does anyone have any suggestions?

[allanj]

Try Googling "Unlocker Assistant" it may help

[Mr.James]

sounds like the account that is logging in does not have access to:

HKLM\Software\Microsoft\Windows Script Host\Settings

and/or

HKCU\Software\Microsoft\Windows Script Host\Settings

if the problem is when you're creating a new profile it may be that you haven't got acces to the default settings for new users from:

HKU\.Default\Software\Microsoft\Windows Script Host\Settings

You need to make sure that you have read acces to these registry keys.

[Little John]

How do I go about giving permision? I have never had a problem like this before? The strange thing is it happens when logging on tot he terminal server also so where do the permisions need to be set the local PC or the user profile while loged on to terminal server or is there somthing in active directory?

2003 server btw

[ant3b]

are you using roaming profiles?

[liveseytowers]

I'd say try and reset the permissions on your profile on the server if you are using roaming profiles as Ant said. We often get weird profile issues at work. Are you an admin?

Do you know what groups your account is a member off in AD? Try comparing it with the one that works

[Little John]

Yep it is roaming profiles
I do have admin rights but the user doesnt.

permisions as far as I know havn't changed all the other users are in the same groups and they are working fine. just this one user.

[liveseytowers]

Yep it is roaming profiles
I do have admin rights but the user doesnt.

permisions as far as I know havn't changed all the other users are in the same groups and they are working fine. just this one user.

Its not really a fix but have you thought about just giving the user a new profile? Doesn't take long and sometimes is better than wasting hours on finding the route cause?

[Little John]

I was considering a new profile, but it is ages since I have done the transfer of everything from the old to the new I prefer to come up with a solution by finding the cause rather than just sticking a plaster over it.

[liveseytowers]

sounds like the account that is logging in does not have access to:

HKLMSoftwareMicrosoftWindows Script HostSettings

and/or

HKCUSoftwareMicrosoftWindows Script HostSettings

if the problem is when you're creating a new profile it may be that you haven't got acces to the default settings for new users from:

HKU.DefaultSoftwareMicrosoftWindows Script HostSettings

You need to make sure that you have read acces to these registry keys.

I've just googled the error and read this as well. It says you do it on the local machine in regedit, you just find the key and give the users group full control over it.

However you said that you'd tried it on a different workstation so you wouldn't want to be doing that everytime?

Guess it depends on your environment. Our users don't store anything meaningful in their profile so a new one is a quick fix.

[Little John]

The user with the problem is the general manager so has lots of private docs and huge amounts of email in exchange that she will need transfering over.

I have only used the terminal server to log on and I get the error not tried to use the account on another machine other than her workstation and the TS

[Mr.James]

Just give the user access rights to those folders in the registry and test the login. If it works then it's definately some problem with accessing that key. I'm pretty sure that this is a permissions issue.

Is your user a member of the local users group on the machine in question? They would need to be to have acces to the HKLM entry.

[Little John]

Thanks for all the sugestion but nothing worked, the permisions were correct for the user in the registry entries etc.

The solution for me was to rename the local and remote profile folders as the administrator and take ownership. I then logged on to recreate a new profile folder on both the server then the workstation as I logged off.

I then took ownership of the folder as the user again and transferd them in to the new profile.

The only thing I lost was her contacts which I am not sure why being an exchange server but she was OK with that.