Problems with logging off after upgrade to 2003 SP2

  • Thread starter Thread starter Tom
  • Start date Start date
T

Tom

Guest
Hello,

Does anybody alse have any sugestions regarding this problem?
This case is not solved yet.


Thanks for your replay TP.
I could not find any recent error logs from Userenv.
Also, I’m running UPHClean service.
Would you have some other suggestion?


"TP" wrote:

> Hi,
>
> Please check your Application event log for errors and
> warnings specifically from Source: Userenv and post
> them here (include the exact text including source,
> event id, type, and description) in sequence. Also if
> you see any other entries that may be relevant in the
> Application or System logs please post those as well.
>
> In the meantime, are you running UPHClean? If not I
> would suggest you give it a try. The download for it
> is here:
>
> User Profile Hive Cleanup Service
>
> https://www.microsoft.com/downloads/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582
>
> Thank you.
>
> -TP
>
> Tom wrote:
> > I’m experiencing problems after upgrade to Server 2003 SP2.
> > The issues seem to be related to each other but I’m not sure. The
> > users are unable to log off. Also, the TS profiles that are located
> > on a different server are getting an additional TS profile.
> > For example, user jsmith has two profiles now, jsmith and
> > jsmith.domain.com. Prior to SP2 upgrade the users only had on
> > profile, example jsmith.
> > Have anyone had similar problems after the upgrade
 
Re: Problems with logging off after upgrade to 2003 SP2

Hi,

You mention that users are unable to logoff. What exactly
happens when they attempt to logoff? Any error messages?

How do you/they end their session?

When they are unable to logoff what processes are running
in their session?

If you remove SP2 do the problems go away?

If you create a new user and logon to the TS does the
problem still occur?

Have you enabled verbose user environment logging in an
attempt to troubleshoot the problem? See these articles:

How to enable user environment debug logging in retail builds of Windows

http://support.microsoft.com/kb/221833

TechNet Support WebCast: Troubleshooting Group Policy and
profile issues in a domain environment by using Userenv logging

http://support.microsoft.com/kb/835302

Please enable verbose logon/logoff status messages so that you
users can see more information during logoff (for example, this
may allow you to see which step of the logoff hangs):

How to enable verbose startup, shutdown, logon, and logoff status
Messages in the Windows Server 2003 family

http://support.microsoft.com/kb/325376

What third-party applications have been installed on the server?
For example, antivirus/security/anti-malware software, any
software that hooks into the windows shell, printer drivers, etc.

Have you loaded any printer drivers that were not included on
the Windows 2003 cd?

Profile problems are often caused by networking issues,
permission problems, profile locked by another process, etc.

-TP

Tom wrote:
> Hello,
>
> Does anybody alse have any sugestions regarding this problem?
> This case is not solved yet.
>
>
> Thanks for your replay TP.
> I could not find any recent error logs from Userenv.
> Also, I’m running UPHClean service.
> Would you have some other suggestion?
 
Re: Problems with logging off after upgrade to 2003 SP2

TP,

Thanks for getting back to me.
1. There are no error messages while attempting to log off. Usually, users
click on log off and nothing happens, than at the second attempt users are
being prompted with “are you sure you want to log off?” and than when clicked
yes, nothing happens. Same third, fourth and so on.
2. I end TS sessions using Terminal Services Manager
3. Processes running: ccApp.exe – Symantec, stmon.exe, explorer.exe, only
bare bones. I did try suspending Symantec.
4. I enabled verbose logon/logoff last week with UserEnvDebugLevel to
0x00030002 – log everything. The files are massive. When successfully logging
off, it logs fine all of the events. However, during unsuccessful log offs,
it does not log any events to userenv.log, just like the system would not
event attempt to log off.
5. The list of applications and printers installed is pretty long. This is a
Terminal Server that was working fine in production environment for over two
years and started having problems right after the upgrade to SP2.

Regards,


"TP" wrote:

> Hi,
>
> You mention that users are unable to logoff. What exactly
> happens when they attempt to logoff? Any error messages?
>
> How do you/they end their session?
>
> When they are unable to logoff what processes are running
> in their session?
>
> If you remove SP2 do the problems go away?
>
> If you create a new user and logon to the TS does the
> problem still occur?
>
> Have you enabled verbose user environment logging in an
> attempt to troubleshoot the problem? See these articles:
>
> How to enable user environment debug logging in retail builds of Windows
>
> http://support.microsoft.com/kb/221833
>
> TechNet Support WebCast: Troubleshooting Group Policy and
> profile issues in a domain environment by using Userenv logging
>
> http://support.microsoft.com/kb/835302
>
> Please enable verbose logon/logoff status messages so that you
> users can see more information during logoff (for example, this
> may allow you to see which step of the logoff hangs):
>
> How to enable verbose startup, shutdown, logon, and logoff status
> Messages in the Windows Server 2003 family
>
> http://support.microsoft.com/kb/325376
>
> What third-party applications have been installed on the server?
> For example, antivirus/security/anti-malware software, any
> software that hooks into the windows shell, printer drivers, etc.
>
> Have you loaded any printer drivers that were not included on
> the Windows 2003 cd?
>
> Profile problems are often caused by networking issues,
> permission problems, profile locked by another process, etc.
>
> -TP
>
> Tom wrote:
> > Hello,
> >
> > Does anybody alse have any sugestions regarding this problem?
> > This case is not solved yet.
> >
> >
> > Thanks for your replay TP.
> > I could not find any recent error logs from Userenv.
> > Also, I’m running UPHClean service.
> > Would you have some other suggestion?
>
>
 
Re: Problems with logging off after upgrade to 2003 SP2

Hi,

Have you updated your Symantec to the very latest maintenance
release? This is different than just definition updates. SP2 is a
*major* OS update and since Antivirus hooks in at a low level
it should be updated as well (to a release certified for SP2).

Have you tried *completely* removing Symantec Antivirus for
a week or so to see if the problem goes away?

What is stmon.exe? Can you stop it from running automatically
for all users?

On a clean server if a user has closed all of their programs they
should only have csrss.exe, winlogon.exe, rdpclip.exe and explorer.exe
running in their session (and perhaps also userinit.exe if they have
only been logged on a minute or so).

For testing purposes create a shortcut to logoff.exe and place it
on their desktop. Do they have the same issues if they double-click
this shortcut to logoff?

Again for testing purposes have a problem user connect *without*
mapping any printers (uncheck on client side) and see if they
still have issues logging off.

Use autoruns.exe to help you examine your server for third party
software that runs automatically or is hooked into explorer.exe
and/or IE. One of these programs could be interfering with the
normal logoff process--note it does not necessarily have to be
some sort of malware, normal software can affect it just as easily.

It is helpful to use the Verify Code Signatures and Hide Signed
Microsoft Entries options (refresh after option change).

AutoRuns for Windows

http://www.microsoft.com/technet/sysinternals/Utilities/AutoRuns.mspx

-TP

Tom wrote:
> TP,
>
> Thanks for getting back to me.
> 1. There are no error messages while attempting to log off. Usually,
> users click on log off and nothing happens, than at the second
> attempt users are being prompted with “are you sure you want to log
> off?” and than when clicked yes, nothing happens. Same third, fourth
> and so on.
> 2. I end TS sessions using Terminal Services Manager
> 3. Processes running: ccApp.exe – Symantec, stmon.exe, explorer.exe,
> only bare bones. I did try suspending Symantec.
> 4. I enabled verbose logon/logoff last week with UserEnvDebugLevel to
> 0x00030002 – log everything. The files are massive. When successfully
> logging off, it logs fine all of the events. However, during
> unsuccessful log offs, it does not log any events to userenv.log,
> just like the system would not event attempt to log off.
> 5. The list of applications and printers installed is pretty long.
> This is a Terminal Server that was working fine in production
> environment for over two years and started having problems right
> after the upgrade to SP2.
>
> Regards,
 
Back
Top