|
What file access and user rights does a VShell® user need to access VShell?
Your access rights need to be reconfigured if you have problems accessing VShell or if you receive the following error message:
00093: Could not start shell program
(Scraper.exe /X 132 /Y 52 C:\!4U2C\System32\CMD.EXE /k c:\tools\prompt\setprompt.bat):
The type of the token is inappropriate for its attempted use.
To correct this, ensure that the account that you are trying
to connect to VShell with has its settings configured as follows:
- In the VShell Control Panel, select the "Access Control"
category. Ensure that the "Logon" access right is checked.
- In Windows, ensure that the "Log on locally" option is
selected.
Instructions for Windows 2000:
- Open the "Start" menu and click on "Settings / Control
Panel / Administrative Tools / Local Security Policy"
- In the folder tree, select "Local Policies / User Rights
Assignments".
- Make sure that the account in question is not listed
or a member of a group listed in the "Deny logon locally"
policy.
Instructions for Windows NT:
- Open the "Start" menu and click on "Programs / Administrative
Tools / User Manager".
- In the "User Manager" window, open the "Policies" menu
and select the "Log on locally" policy.
- Make sure that the account in question is listed in
this group.
Instructions for Windows XP:
For Windows XP Classic View, use the instructions for Windows 2000. For Windows XP Category View, follow these steps:
- Open the "Start" menu and click on "Control Panel".
- Open "Performance and Maintenance".
- Open "Administrative Tools" and select "Local Security
Policy".
- Make sure that the account in question is not listed
or a member of a group listed in the "Deny logon locally"
policy.
Was this information helpful?
|
| Three Fast Ways
to Learn More About VShell for Windows and UNIX |
|
|
|
Tell
me more. E-mail us your questions about putting VShell to work for your organization.
|
Try
it today! Download a free 30-day evaluation copy of VShell
for Windows or UNIX.
|
Talk
to us. Let us help define the right VShell server solution
for your company.
|
|