Thanks for your help Rhett. Below is the entire contents of the actsetup.log
file. I will have the customer run the setup again and remote in then try to
run the command manually.
-------- (02/16/2005 15:12:32) --------
ACTREGMOF started: "C:\Program Files\Microsoft ACT\ActRegMof.exe" -i
"C:\Program Files\Microsoft ACT\actnamespace.mof"
ParseParams EXECUTE_TYPE: 0
--> INSTALL C:\Program Files\Microsoft ACT actnamespace.mof
SetCurrentDirectory (C:\Program Files\Microsoft ACT) returned 1 (00000000)
CoInitialize returned 00000000 CoCreateInstance returned 00000000
pCompiler->CompileFile returned 00000001
ACTREGMOF exited with code: 00000089 - The system tried to delete the
substitution of a drive that is not substituted.
-------- (02/16/2005 15:14:43) --------
ACTREGMOF started: "C:\Program Files\Microsoft
ACT\ActRegMof.exe" -delinstance root\cimv2\applications
__NAMESPACE.Name=\"MicrosoftACT\"
ParseParams EXECUTE_TYPE: 4
CoInitialize returned 00000000
CoCreateInstance returned 00000000
pIWbemLocator->ConnectServer(root\cimv2\applications) returned 00000000
pIWbemServices->DeleteInstance(__NAMESPACE.Name="MicrosoftACT") returned
pIWbemServices->80041002
ACTREGMOF exited with code: 00000000 - The operation completed successfully.
-------- (02/17/2005 10:34:21) --------
ACTREGMOF started: "C:\Program Files\Microsoft ACT\ActRegMof.exe" -i
"C:\Program Files\Microsoft ACT\actnamespace.mof"
ParseParams EXECUTE_TYPE: 0
--> INSTALL C:\Program Files\Microsoft ACT actnamespace.mof
SetCurrentDirectory (C:\Program Files\Microsoft ACT) returned 1 (00000000)
CoInitialize returned 00000000 CoCreateInstance returned 00000000
pCompiler->CompileFile returned 00000001
ACTREGMOF exited with code: 00000089 - The system tried to delete the
substitution of a drive that is not substituted.
-------- (02/17/2005 10:45:17) --------
ACTREGMOF started: "C:\Program Files\Microsoft
ACT\ActRegMof.exe" -delinstance root\cimv2\applications
__NAMESPACE.Name=\"MicrosoftACT\"
ParseParams EXECUTE_TYPE: 4
CoInitialize returned 00000000
CoCreateInstance returned 00000000
pIWbemLocator->ConnectServer(root\cimv2\applications) returned 00000000
pIWbemServices->DeleteInstance(__NAMESPACE.Name="MicrosoftACT") returned
pIWbemServices->80041002
ACTREGMOF exited with code: 00000000 - The operation completed successfully.
[quoted text, click to view] "Rhett Gong [MSFT]" <v-raygon@online.microsoft.com> wrote in message
news:Sx11ymZFFHA.932@TK2MSFTNGXA01.phx.gbl...
> Additional error information can be found in the file
> %windir%\actsetup.log, which contains some log information for the
> following custom actions:
>
> ACTCreateUser
> ACTDelNamespace
> ACTMofcompBroker
> ACTMofcompController
> ACTMofcompNamespace
> ACTRemoveUser
>
> Name
> ACTMofcompNamespace
> Runs when
> ACT is being installed.
>
> Description
> Creates the ACT WMI namespace (path \root\cimv2\applications\MicrosotACT)
> during the installation of ACT. The definition of this namespace is stored
> in the file actnamespace.mof, which is installed as part of ACT.
>
> Error handling
> The following error message is displayed to the user and also added to
the
> VS msi log "Could not configure namespace for Application Center Test.
> <text-reason> (hresult)¡±
>
>
CustomActionSchedule(Action=ACTMofcompNamespace.A5D8A560_0C3B_44C7_8C86_6F7A
>
9946C3BF,ActionType=1025,Source=BinaryData,Target=MofcompNamespace,CustomAct
> ionData="C:\Program Files\Microsoft ACT\ActRegMof.exe" -i "C:\Program
> Files\Microsoft ACT\actnamespace.mof")
>
> Could you run the command manually when the error occurs to see whether
> there is any additional info? (probably with FileMon and RegMon)
>
> Thanks,
> Rhett Gong [MSFT]
> Microsoft Online Partner Support
> Get Secure! -
www.microsoft.com/security >
> This posting is provided "AS IS" with no warranties and confers no rights.
>