#206170 - 2012-11-0907:28 AMEnvironment is Incorrect
BradGBradG
Fresh Scripter
Registered: 2009-02-13
Posts: 12
Loc: Australia
Dont know if this is the correct forum for this, but this issue is really driving me nuts. We are using the Universal Login Script successfully on around 130 machines, but on 2 machines it simply fails to map the required network drives. the error generated is as follows:
2012/11/09 17:17:31 : DriveMap Z: to \\sw.local\shares\sites\Camperdown\Users\op-cdn The environment is incorrect.
I have been looking for a resolution for this for several days, but cannot get the Kix script to work on these 2 machines. The machines themselves are running Windows XP with SP2 applied.
#206178 - 2012-11-0904:36 PMRe: Environment is Incorrect
[Re: BradG]
Glenn BarnasGlenn Barnas KiX Supporter
Registered: 2003-01-28
Posts: 4400
Loc: New Jersey
Please review the Login Script manual for support requests for the Universal Login Script. You can send the required files to me directly (gbarnas@...). This script is not supported in a public forum due to the potentially sensitive nature of the diagnostic information needed.
PM me here if you need further information. I will need the LoginDebug.log and the Login.INI file, along with the LoginError.Log if present.
I can verify that using version 2.0 or higher that the dash in the pathspec is not an issue.
If you have already sent these in the past week, I apologize and ask that you resend your email. We have been off the network due to Hurricane Sandy since 10/29, and came back online just yesterday.
Glenn
PS - moving this to the Lounge as it is not something that relates to public Kix code.
_________________________ Actually I am a Rocket Scientist!
#206221 - 2012-11-1403:55 PMRe: Environment is Incorrect
[Re: Glenn Barnas]
Glenn BarnasGlenn Barnas KiX Supporter
Registered: 2003-01-28
Posts: 4400
Loc: New Jersey
Just an update - after working with Brad for a few days and providing him with a customized version of ULS with enhanced debugging data, we found that these two computers indeed had an invalid environment.
When logging in, the NET USE command always returned "Error 10 - The environment is invalid". Adding a "SET > UserEnv.txt" command to the login script showed that there were no variables defined in the environment (the file was empty!) - neither System or User environment variables were present. It was almost as if the registry was unavailable to initialize the environment. It didn't matter if the workstation was recently rebooted or had been on for a while - it happened consistently at login.
After the login completed and a command prompt was opened, the SET command displayed the environment and NET USE commands ran successfully.
The problem presented with any user as well as a new user profile. We checked network settings, (LM)Host file entries, verified that the system was not in a strange return from hibernate state, and a few other things such as verifying that the related login script files were saved in ANSI format and removing the cached copy of the config file. Google searches turned up nothing useful beyond dozens of sites with tables of error messages.
Since this issue was confined to just two of 100+ workstations, they were replaced and the problematic systems are scheduled for reimaging.
With this additional insight, I'm just wondering if anyone has any ideas as to why the environment would be blank during logon, yet operational moments later?
Glenn
_________________________ Actually I am a Rocket Scientist!
Not exactly the same problem, but I have run into a similar problem using runas. On about 3 machines so far, runas will simply not work. I can't remember the return error right this second. The only fix besides rebuilding the pc was to blow away their desktop profile and start new. Interestingly, one of these three pcs had the profile rebuilt, and within a week it was broken again.
#206235 - 2012-11-1610:40 PMRe: Environment is Incorrect
[Re: Allen]
NTDOCNTDOC Administrator
Registered: 2000-07-28
Posts: 11625
Loc: CA
Well imaging the system is certainly the faster approach as most of us just don't have enough time in our days to do academic research into an issue like this but if you did have time you could probably run a debugger on it to see if you can trap an error or maybe even a perfmon - but after a couple hours of checking stuff I'd image the box myself and move on unless it was something hitting a lot of boxes.
