[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

x
?
Solved

Problems logging off and logging back on - due to UPH clean (it appears)

Posted on 2006-11-03
1
Medium Priority
?
468 Views
Last Modified: 2008-02-20
I need to know what is causing this event in app event viewer and how to correct the problem.  The following occurred yesterday - earliest (first) entry was at 3:38:41... entry every second until 3:41:23.  The day before it occurred on another user.... same info in each entry.

Event Type:      Information
Event Source:      UPHClean
Event Category:      None
Event ID:      1401
Date:            11/2/2006
Time:            3:41:23 PM
User:            HOWARDSHEPPARD\lisa
Computer:      HSIWIN
Description:
The following handles in user profile hive HOWARDSHEPPARD\lisa (S-1-5-21-1198605736-1630746206-1236467883-1162) have been remapped because they were preventing the profile from unloading successfully:
 
spoolsv.exe (1000)
  HKCU\Software\Lexmark\PCLPlugIn\Lexmark E240 XL\Watermark (0x983c)
      0x77fb6221 ADVAPI32!ElfFlushEventLog+0x1d9a
      0x77fb5c5b ADVAPI32!ElfFlushEventLog+0x17d4
      0x77f67ea9 ADVAPI32!RegCreateKeyExW+0xc0
      0x5000b1cc <no module>!<no symbol>
      0x5000b262 <no module>!<no symbol>
      0x50001f76 <no module>!<no symbol>
      0x767b7d27 UNIDRVUI!DrvUpgradePrinter+0x1693
      0x767adb1e UNIDRVUI!DrvSplDeviceCaps+0x2af5
      0x767b3234 UNIDRVUI!DrvConvertDevMode+0x5e
      0x7406df2e SPOOLSS!CallDrvDevModeConversion+0x103
      0x7403d5aa win32spl!InitializePrintProvidor+0xbc24
      0x7403728b win32spl!InitializePrintProvidor+0x5905
      0x7403f298 win32spl!InitializePrintProvidor+0xd912
      0x740407d0 win32spl!InitializePrintProvidor+0xee4a
      0x740413cb win32spl!InitializePrintProvidor+0xfa45
      0x74041e75 win32spl!InitializePrintProvidor+0x104ef
      0x74041fa6 win32spl!InitializePrintProvidor+0x10620
      0x74041ff0 win32spl!InitializePrintProvidor+0x1066a
      0x74071077 SPOOLSS!AddPrinterConnectionW+0x4d
      0x01007f7a spoolsv!YSetJob+0x314
      0x01006f44 spoolsv!YGetPrinterDriverDirectory+0x133d
      0x77c70f3b RPCRT4!NdrServerInitialize+0x462
      0x77ce23f7 RPCRT4!NdrStubCall2+0x217
      0x77ce26ed RPCRT4!NdrServerCall2+0x19
      0x77c709be RPCRT4!I_RpcGetBuffer+0x1d8
      0x77c7093f RPCRT4!I_RpcGetBuffer+0x159
      0x77c70865 RPCRT4!I_RpcGetBuffer+0x7f
      0x77c734b1 RPCRT4!NDRCContextMarshall+0x46f
      0x77c71bb3 RPCRT4!RpcRevertToSelfEx+0x6a6
      0x77c75458 RPCRT4!I_RpcBindingIsClientLocal+0x68b
      0x77c5778f RPCRT4!NdrOleFree+0x3c5
      0x77c5f7dd RPCRT4!I_RpcTransGetThreadEvent+0x188
      0x77c5de88 RPCRT4!I_RpcLogEvent+0xe92
      0x77e6608b kernel32!GetModuleFileNameA+0xeb
  HKCU\Software\Lexmark\PCLPlugIn\Lexmark E240 XL\Watermark (0x9854)
      0x77fb6221 ADVAPI32!ElfFlushEventLog+0x1d9a
      0x77fb5c5b ADVAPI32!ElfFlushEventLog+0x17d4
      0x77f67ea9 ADVAPI32!RegCreateKeyExW+0xc0
      0x5000b1cc <no module>!<no symbol>
      0x5000b262 <no module>!<no symbol>
      0x50001f76 <no module>!<no symbol>
      0x767b7d27 UNIDRVUI!DrvUpgradePrinter+0x1693
      0x767adb1e UNIDRVUI!DrvSplDeviceCaps+0x2af5
      0x767a7fdd UNIDRVUI!DrvDocumentPropertySheets+0x859
      0x767a7f45 UNIDRVUI!DrvDocumentPropertySheets+0x7c1
      0x767a9553 UNIDRVUI!DrvDeviceCapabilities+0x122c
      0x767a8342 UNIDRVUI!DrvDeviceCapabilities+0x1b
      0x761428f0 localspl!SplSetPrinterDataEx+0x3af
      0x761422c1 localspl!SplSetPrinter+0x19a3
      0x76140c5c localspl!SplSetPrinter+0x33e
      0x74069039 SPOOLSS!SetPrinterW+0x79
      0x01005681 spoolsv!YGetPrinter+0x710
      0x010055f3 spoolsv!YGetPrinter+0x682
      0x77c70f3b RPCRT4!NdrServerInitialize+0x462
      0x77ce23f7 RPCRT4!NdrStubCall2+0x217
      0x77ce26ed RPCRT4!NdrServerCall2+0x19
      0x77c709be RPCRT4!I_RpcGetBuffer+0x1d8
      0x77c7093f RPCRT4!I_RpcGetBuffer+0x159
      0x77c70865 RPCRT4!I_RpcGetBuffer+0x7f
      0x77c734b1 RPCRT4!NDRCContextMarshall+0x46f
      0x77c71bb3 RPCRT4!RpcRevertToSelfEx+0x6a6
      0x77c75458 RPCRT4!I_RpcBindingIsClientLocal+0x68b
      0x77c5778f RPCRT4!NdrOleFree+0x3c5
      0x77c5f7dd RPCRT4!I_RpcTransGetThreadEvent+0x188
      0x77c5de88 RPCRT4!I_RpcLogEvent+0xe92
      0x77e6608b kernel32!GetModuleFileNameA+0xeb
  HKCU\Software\Lexmark\PCLPlugIn\Lexmark E240 XL\Watermark (0x9874)
      0x77fb6221 ADVAPI32!ElfFlushEventLog+0x1d9a
      0x77fb5c5b ADVAPI32!ElfFlushEventLog+0x17d4
      0x77f67ea9 ADVAPI32!RegCreateKeyExW+0xc0
      0x5000b1cc <no module>!<no symbol>
      0x5000b262 <no module>!<no symbol>
      0x50001f76 <no module>!<no symbol>
      0x767b7d27 UNIDRVUI!DrvUpgradePrinter+0x1693
      0x767adb1e UNIDRVUI!DrvSplDeviceCaps+0x2af5
      0x767a7fdd UNIDRVUI!DrvDocumentPropertySheets+0x859
      0x767a7f45 UNIDRVUI!DrvDocumentPropertySheets+0x7c1
      0x767a9553 UNIDRVUI!DrvDeviceCapabilities+0x122c
      0x767a8342 UNIDRVUI!DrvDeviceCapabilities+0x1b
      0x76141afd localspl!SplSetPrinter+0x11df
      0x76140c5c localspl!SplSetPrinter+0x33e
      0x74069039 SPOOLSS!SetPrinterW+0x79
      0x01005681 spoolsv!YGetPrinter+0x710
      0x010055f3 spoolsv!YGetPrinter+0x682
      0x77c70f3b RPCRT4!NdrServerInitialize+0x462
      0x77ce23f7 RPCRT4!NdrStubCall2+0x217
      0x77ce26ed RPCRT4!NdrServerCall2+0x19
      0x77c709be RPCRT4!I_RpcGetBuffer+0x1d8
      0x77c7093f RPCRT4!I_RpcGetBuffer+0x159
      0x77c70865 RPCRT4!I_RpcGetBuffer+0x7f
      0x77c734b1 RPCRT4!NDRCContextMarshall+0x46f
      0x77c71bb3 RPCRT4!RpcRevertToSelfEx+0x6a6
      0x77c75458 RPCRT4!I_RpcBindingIsClientLocal+0x68b
      0x77c5778f RPCRT4!NdrOleFree+0x3c5
      0x77c5f7dd RPCRT4!I_RpcTransGetThreadEvent+0x188
      0x77c5de88 RPCRT4!I_RpcLogEvent+0xe92
      0x77e6608b kernel32!GetModuleFileNameA+0xeb
  HKCU\Software\Lexmark\PCLPlugIn\Lexmark E240 XL\Watermark (0x9884)
      0x77fb6221 ADVAPI32!ElfFlushEventLog+0x1d9a
      0x77fb5c5b ADVAPI32!ElfFlushEventLog+0x17d4
      0x77f67ea9 ADVAPI32!RegCreateKeyExW+0xc0
      0x5000b1cc <no module>!<no symbol>
      0x5000b262 <no module>!<no symbol>
      0x50001f76 <no module>!<no symbol>
      0x767b7d27 UNIDRVUI!DrvUpgradePrinter+0x1693
      0x767adb1e UNIDRVUI!DrvSplDeviceCaps+0x2af5
      0x767a7fdd UNIDRVUI!DrvDocumentPropertySheets+0x859
      0x767a7f45 UNIDRVUI!DrvDocumentPropertySheets+0x7c1
      0x767a9553 UNIDRVUI!DrvDeviceCapabilities+0x122c
      0x767a8342 UNIDRVUI!DrvDeviceCapabilities+0x1b
      0x76141bb4 localspl!SplSetPrinter+0x1296
      0x76140c5c localspl!SplSetPrinter+0x33e
      0x74069039 SPOOLSS!SetPrinterW+0x79
      0x01005681 spoolsv!YGetPrinter+0x710
      0x010055f3 spoolsv!YGetPrinter+0x682
      0x77c70f3b RPCRT4!NdrServerInitialize+0x462
      0x77ce23f7 RPCRT4!NdrStubCall2+0x217
      0x77ce26ed RPCRT4!NdrServerCall2+0x19
      0x77c709be RPCRT4!I_RpcGetBuffer+0x1d8
      0x77c7093f RPCRT4!I_RpcGetBuffer+0x159
      0x77c70865 RPCRT4!I_RpcGetBuffer+0x7f
      0x77c734b1 RPCRT4!NDRCContextMarshall+0x46f
      0x77c71bb3 RPCRT4!RpcRevertToSelfEx+0x6a6
      0x77c75458 RPCRT4!I_RpcBindingIsClientLocal+0x68b
      0x77c5778f RPCRT4!NdrOleFree+0x3c5
      0x77c5f7dd RPCRT4!I_RpcTransGetThreadEvent+0x188
      0x77c5de88 RPCRT4!I_RpcLogEvent+0xe92
      0x77e6608b kernel32!GetModuleFileNameA+0xeb


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
Comment
Question by:lisaj599
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 85

Accepted Solution

by:
oBdA earned 1500 total points
ID: 17869869
That's not a problem of UPHClean; UPHClean is just displaying the symptoms, it's not the cause.
UPHClean checks whether there are still handles to the registry open when a user logs off, as this will prevent the profile from unloading. If it finds open handles, it tries to remap them to the local system account (if I remember correctly).
The cause here seems to be the Lexmark 240 driver, that upon the user logoff doesn't close the registry handles it opened before.
First thing to check is if there's an updated driver available.
0

Featured Post

Learn Veeam advantages over legacy backup

Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn about cloud computing and its benefits for small business owners.
While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
Are you ready to place your question in front of subject-matter experts for more timely responses? With the release of Priority Question, Premium Members, Team Accounts and Qualified Experts can now identify the emergent level of their issue, signal…
Suggested Courses

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question