Send us a question or comment
   

I'm having trouble connecting to VShell® and am getting a "Could not load environment" error message. What's the problem?

This problem is specific to Windows NT and is a known behavior. The cause is an empty string in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Environment

When VShell makes a CreateEnvironmentBlock system call (to get a user's environment when the user logs on), NT is not able to handle empty strings in this key and the function fails. Uninstalling Oracle is known to leave empty strings within the environment block.

The solution to this problem is to open the registry and delete any empty string values that you find in the above registry key.

Was this information helpful?
Yes No
Thank you!
Send your comments and questions to VanDyke Software Support,
or join the discussion in the VanDyke Software Forums.
Can't find the answer you're looking for?
Ask VanDyke Software Support directly
and we will get back to you as soon as possible.
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.