Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

c:winnt\debug\usermode\userenv.log grows uncontollably

Status
Not open for further replies.

raygg

Technical User
Jun 14, 2000
397
0
0
US
Recently the c:winnt\debug\usermode\userenv.log started growing uncontrolably. This is on my home win2k pro machine. I am not using the machine much - basically email and some gaming currently, and this log will grow to 1.5gb in a couple of weeks. I cannot find anytthing on the internet that addresses this. I am also an Oracle dba and recently cleaned all oracle components off the box and this problem started after that. Perhaps a registry setting got changed somewhere. Other than this there is no unusual behavior or response time on the box. I first noticed it when I could not read my email. I would open emails and they would be blank. After I discovered by 4gb C: drive was completely full because this log was nearly 2gb in size and then I deleted it, I could then again read the email ok. I have virus checked the drive and found nothing. If I delete this log within 60 sec it is up to 200kb and seems to grow by 17k to 64k every time I ckick it..
 
Check to see if Auditing has been turned on for any files/folders on your PC.

Go into the Event Log (Control Panel, Administration tools, Event Logs). Click Security in the left plain and see if there is any entries in the right plain. If there isn't then Auditing is not turned on. New Zealand, a great place to live.
tokala@orcon.net.nz
 
eventlog auditing is off - this log filled the C drive by expanding to 12.4 GB just since I last posted here. It automatically restarted and these are the very first entries. Note that the last 3 entries keep repeating. I formerly had an Oracle db on this machine but wiped out all trace of oracle using the 'clean machine' procedure (I am an Oracle dba) approach, deleted all the registry and program files entries, and deleted oracle from the path. I am stumped.

USERENV(dc.d8) 10:01:24:375 UnloadUserProfile: received a NULL hProfile.
USERENV(c0.a8) 10:05:22:265 UpdateSystemEnvironment: Failed to set environment variable <JSERV> to <> with 1008.
USERENV(c0.a8) 10:05:22:265 UpdateSystemEnvironment: Failed to set environment variable <OLAP_HOME> to <> with 1008.
USERENV(c0.a8) 10:05:22:265 UpdateSystemEnvironment: Failed to set environment variable <WV_GATEWAY_CFG> to <> with 1008.
USERENV(c0.a8) 10:05:22:375 MyGetUserName: GetUserNameEx failed with 1355.
USERENV(c0.a8) 10:05:22:890 MyGetUserName: GetUserNameEx failed with 1355.
USERENV(c0.a8) 10:05:23:390 MyGetUserName: GetUserNameEx failed with 1355.
USERENV(c0.a8) 10:05:23:890 MyGetUserName: GetUserNameEx failed with 1355.
USERENV(c0.a8) 10:05:23:890 GetUserGuid: Failed to get user guid with 1355.
USERENV(c0.a8) 10:05:23:890 MyGetUserName: GetUserNameEx failed with 1355.
USERENV(c0.a8) 10:05:24:390 MyGetUserName: GetUserNameEx failed with 1355.
USERENV(c0.a8) 10:05:24:890 MyGetUserName: GetUserNameEx failed with 1355.
USERENV(c0.a8) 10:05:25:390 MyGetUserName: GetUserNameEx failed with 1355.
USERENV(c0.a8) 10:05:25:390 GetUserGuid: Failed to get user guid with 1355.
USERENV(c0.a8) 10:05:25:390 UpdateSystemEnvironment: Failed to set environment variable <JSERV> to <> with 0.
USERENV(c0.a8) 10:05:25:390 UpdateSystemEnvironment: Failed to set environment variable <OLAP_HOME> to <> with 0.
USERENV(c0.a8) 10:05:25:406 UpdateSystemEnvironment: Failed to set environment variable <WV_GATEWAY_CFG> to <> with 0.
USERENV(20c.2f4) 10:05:51:046 UpdateSystemEnvironment: Failed to set environment variable <JSERV> to <> with 183.
USERENV(20c.2f4) 10:05:51:109 UpdateSystemEnvironment: Failed to set environment variable <OLAP_HOME> to <> with 183.
USERENV(20c.2f4) 10:05:51:140 UpdateSystemEnvironment: Failed to set environment variable <WV_GATEWAY_CFG> to <> with 183.
USERENV(20c.2f4) 10:05:52:281 UpdateSystemEnvironment: Failed to set environment variable <JSERV> to <> with 2.
USERENV(20c.2f4) 10:05:52:281 UpdateSystemEnvironment: Failed to set environment variable <OLAP_HOME> to <> with 2.
USERENV(20c.2f4) 10:05:52:296 UpdateSystemEnvironment: Failed to set environment variable <WV_GATEWAY_CFG> to <> with 2.
USERENV(510.50c) 10:06:09:984 UpdateSystemEnvironment: Failed to set environment variable <JSERV> to <> with 183.
USERENV(510.50c) 10:06:09:984 UpdateSystemEnvironment: Failed to set environment variable <OLAP_HOME> to <> with 183.
USERENV(510.50c) 10:06:10:000 UpdateSystemEnvironment: Failed to set environment variable <WV_GATEWAY_CFG> to <> with 183.
USERENV(510.50c) 10:06:12:265 UpdateSystemEnvironment: Failed to set environment variable <JSERV> to <> with 1008.
USERENV(510.50c) 10:06:12:281 UpdateSystemEnvironment: Failed to set environment variable <OLAP_HOME> to <> with 1008.
USERENV(510.50c) 10:06:12:281 UpdateSystemEnvironment: Failed to set environment variable <WV_GATEWAY_CFG> to <> with 1008.
 
The problem is with your user profiles.

Try this..

Rename the USERENV.DLL file in the \WINNT\SYSTEM32 (or whatever your system folder is) folder to something different (eg USERENV.OLD).

Copy the USERENV.DLL off your Win2k CD into \WINNT\SYSTEM32 and see if the problem goes away.
New Zealand, a great place to live.
tokala@orcon.net.nz
 
error message - cannot rename userenv.dll - being used by windows - sorry so slow in answering - out of state for a week.

Now what?
 
Use the Recovery Console to rename the DLL.

I would copy the replacement USERENV.DLL from your CD onto the C drive in Win2k.

Then boot off the Win2k CD and take the R (Repair) option and go into the Recovery Console (Win2k version of DOS) and then rename and copy the DLL.
New Zealand, a great place to live.
tokala@orcon.net.nz
 
Go to actions in the event viewer
then properties
if the default of 512 is there and manual delete (or erase) is not checked and you are writing to 12gb you have a bigger problem than a missing folder.

setting the log size and telling it to overwrite when full will only cure the symptom but it should let you use yoyr PC while you look for a cure.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top