paul

Has anyone seen this before? I briefly reviewed the WMI
config and extensively reviewed the security config
(action account, etc..).

I have agents on several SQL servers. This is the only
server that throws this error.

Thanks,
Paul

********************

The Microsoft SQL Server management pack failed to execute
the SQL Server 2000 Database Health script successfully.
The following error event was returned "Unable to create
automation object 'Scripting.FileSystemObject'". The
following additional error details were returned "".
Please refer to the events associated with this alert to
view the computers that have experienced this problem.

*********************

kevin beares [msft]

Hi Paul,

Did you try restarting WMI on this machine?

--
Thanks,

Kevin Beares
MOM Community PM

--
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"

paul

I tried all of the standard stuff like wmi, permissions,
etc...

However, the machine simply couldn't use anything that
called the 'Scripting.FileSystemObject' function. I used
a sample script that I downloaded from the Technet website
that simply enumerates drive letters on the target
machine. The script bombed out on the first line of code
because the first line called Scripting.FileSystemObject.

What's funny is that all other WMI related activities were
working without error, only this class had an issue.

I dug deap on this one for a few hours and basically
reversed engineered how all of the dlls talked to one
another using a MS developer utility called "depends.exe".

Bottom line was that I needed to reinstall the MS
Scripting engine. Somehow the registry settings were
removed from the System and some but not all of the files
for the engine were also missing.

Thanks for the reply,
Paul


confers no rights.

please add "Use of

specified at