|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Event id 3003 - LoadPerfI am getting this combination of errors in my event log... I am running windows 2003 Enterprise with terminal services. please let me know if you have any ideas of why this might be happening. the only thing i did on the server was run a detect and repair on office 2003. Thanks, Jen Source: LoadPerf Event ID: 3011 Description: Unloading the performance counter strings for service outlook (outlook) failed. The Error code is the first DWORD in Data section. Source: LoadPerf Event ID: 3003 Description: The SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib key could not be opened or accessed in order to install counter strings.The Win32 status returned by the call is the first DWORD in Data section. Source: LoadPerf Event ID: 3009 Description: Installing the performance counter strings for service Outlook (Outlook) failed. The Error code is the first DWORD in Data section. Hi,
Does anyone fix the problem? If so, can you tell me how? Regards Rainer H. Show quoteHide quote "Jennifer Mar" wrote: > Hi, > > I am getting this combination of errors in my event log... I am running windows 2003 Enterprise with terminal services. please let me know if you have any ideas of why this might be happening. the only thing i did on the server was run a detect and repair on office 2003. > > Thanks, > > Jen > > > Source: LoadPerf > Event ID: 3011 > Description: Unloading the performance counter strings for service outlook (outlook) failed. The Error code is the first DWORD in Data section. > > Source: LoadPerf > Event ID: 3003 > Description: The SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib key could not be opened or accessed in order to install counter strings.The Win32 status returned by the call is the first DWORD in Data section. > > Source: LoadPerf > Event ID: 3009 > Description: Installing the performance counter strings for service Outlook (Outlook) failed. The Error code is the first DWORD in Data section You need to go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services Look for the perf services (not sure which one) & set the timeout for something more than 5000 (5 secs). Close registry editor & restart. There is another article that references something completely different though: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q325727 Crouchie1998 BA (HONS) MCP MCSE As with previous editions of Office - Outlook 2003 requires the administrator
to launch Outlook to complete the configuration. If you build a terminal server and install office 2003, you must login as an admin and configure and launch Outlook to complete the configuration and load the Performance Counter Strings (you will get an event ID 1000 confirming this). After that, all users should be able to launch Outlook without any errors being written to the event log. Show quoteHide quote "Jennifer Mar" wrote: > Hi, > > I am getting this combination of errors in my event log... I am running windows 2003 Enterprise with terminal services. please let me know if you have any ideas of why this might be happening. the only thing i did on the server was run a detect and repair on office 2003. > > Thanks, > > Jen > > > Source: LoadPerf > Event ID: 3011 > Description: Unloading the performance counter strings for service outlook (outlook) failed. The Error code is the first DWORD in Data section. > > Source: LoadPerf > Event ID: 3003 > Description: The SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib key could not be opened or accessed in order to install counter strings.The Win32 status returned by the call is the first DWORD in Data section. > > Source: LoadPerf > Event ID: 3009 > Description: Installing the performance counter strings for service Outlook (Outlook) failed. The Error code is the first DWORD in Data section
Domain Controller?
unable to reinstall tcp/ip protocol Urgent - NT Remote Authentication API HELP -Need instructions on running Service Pack from cmd prmpt Trouble with adding existing user to SBS 2003 network available disk space Automatically rebooting win 2000 once a day at a specific time Using WMI to determine boot device priority connect to the shared printer when start-up virtual memory |
|||||||||||||||||||||||