MWave6
2009-02-06 16:16:17 UTC
Hello,
We recently began encountering this error on our 2k3 Svr x64 Exchange
2007 server.
*** SNIP ***
The description for Event ID ( 600 ) in Source ( PowerShell ) cannot
be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve
this
description; see Help and Support for details.
*** SNIP ***
Do I understand correctly that you advise deletion of the following
registry key followed by restarting the machine as the solution to
this problem?
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\PowerShell
Please confirm that this is the key to which you are referring.
Thanks,
Tom W.
On Oct 10 2006, 4:22 pm, "Narayanan Lakshmanan [MSFT]"
We recently began encountering this error on our 2k3 Svr x64 Exchange
2007 server.
*** SNIP ***
The description for Event ID ( 600 ) in Source ( PowerShell ) cannot
be
found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE= flag to retrieve
this
description; see Help and Support for details.
*** SNIP ***
Do I understand correctly that you advise deletion of the following
registry key followed by restarting the machine as the solution to
this problem?
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Eventlog\PowerShell
Please confirm that this is the key to which you are referring.
Thanks,
Tom W.
On Oct 10 2006, 4:22 pm, "Narayanan Lakshmanan [MSFT]"
"Windows PowerShell" is the correct log. The way to get around this is to
Delete the "PowerShell" key under Eventlog and restart the system. Then you
will find that the events get logged properly.
--
Narayanan Lakshmanan [MSFT]
Windows PowerShell Development
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Delete the "PowerShell" key under Eventlog and restart the system. Then you
will find that the events get logged properly.
--
Narayanan Lakshmanan [MSFT]
Windows PowerShell Development
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.