I have a customer who is installing Visual Studio.NET 2002 and during the
main setup the installation fails with the error message:
Could not configure namespace for Application Center Test. The system tried
to delete the substitution of a drive that is not substituted. (0x00000089)
This install is coming from a network share. Since the error message deals
with drives I had the user attempt to unmap all network drives and attempt
the installation again with no success. The customer has Windows 2000 Pro
SP4. Here are the lines from the windows installer log where the error
occurs:
MSI (s) (CC:3C): Creating MSIHANDLE (7114) of type 790536 for thread 2364
0
Info 5002.HrVSAnalyzerCAH() : Info Message is Visual Studio Analyzer Setup:
Visual Studio Analyzer User Created: VUSR_PC316865
Info 5002.HrVSAnalyzerCAH() : Info Message is Visual Studio Analyzer Setup:
Visual Studio Analyzer User Privilege granted: SeBatchLogonRight.
Info 5002.HrVSAnalyzerCAH() : Info Message is Visual Studio Analyzer Setup:
Visual Studio Analyzer User Privilege granted: SeDebugPrivilege.
Info 5002.HrVSAnalyzerCAH() : Info Message is Visual Studio Analyzer Setup:
Enabled perf lib reading for user.
Info 5002.HrVSAnalyzerCAH() : Info Message is Visual Studio Analyzer Setup:
Enabled WMI access for user.
Info 5002.HrVSAnalyzerCAH() : Info Message is Visual Studio Analyzer Setup:
LEC (valec.exe) configured.
Info 5002.HrVSAnalyzerCAH() : Info Message is Visual Studio Analyzer Setup:
WMI Bridge (vawmiec.dll) configured.
-2147024894
MSI (s) (CC:3C): Executing op:
ActionStart(Name=ACTMofcompNamespace_Rollback.A5D8A560_0C3B_44C7_8C86_6F7A99
46C3BF,,)
MSI (s) (CC:3C): Executing op:
CustomActionSchedule(Action=ACTMofcompNamespace_Rollback.A5D8A560_0C3B_44C7_
8C86_6F7A9946C3BF,ActionType=1281,Source=BinaryData,Target=MofcompNamespace_
Rollback,CustomActionData="C:\Program Files\Microsoft ACT\ActRegMof.exe"
-delinstance root\cimv2\applications __NAMESPACE.Name=\"MicrosoftACT\")
MSI (s) (CC:3C): Executing op:
ActionStart(Name=ACTMofcompNamespace.A5D8A560_0C3B_44C7_8C86_6F7A9946C3BF,,)
MSI (s) (CC:3C): Executing op:
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 Fi
les\Microsoft ACT\actnamespace.mof")
MSI (s) (CC:3C): Creating MSIHANDLE (7124) of type 790536 for thread 2364
Could not configure namespace for Application Center Test. The system tried
to delete the substitution of a drive that is not substituted. (0x00000089)
Action ended 10:45:16: InstallFinalize. Return value 3.
MSI (s) (CC:3C): User policy value 'DisableRollback' is 0
MSI (s) (CC:3C): Machine policy value 'DisableRollback' is 0
MSI (s) (CC:3C): Executing op:
Header(Signature=1397708873,Version=200,Timestamp=844188954,LangId=1033,Plat
form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttribu
tes=1)
MSI (s) (CC:3C): Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (CC:3C): Executing op: DialogInfo(Type=1,Argument=Visual Studio .NET
Enterprise Architect - English)
MSI (s) (CC:3C): Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
action:,RollbackTemplate=,CleanupAction=RollbackCleanup,CleanupDescription=R
emoving backup files,CleanupTemplate=File: )
Any help with this would be greatly appreciated.
Jason Galbreath
Arizona Public Service
Rhett Gong [MSFT] - 18 Feb 2005 09:10 GMT
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.
Jason Galbreath - 18 Feb 2005 15:30 GMT
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.
> Additional error information can be found in the file
> %windir%\actsetup.log, which contains some log information for the
[quoted text clipped - 21 lines]
> 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")
[quoted text clipped - 8 lines]
>
> This posting is provided "AS IS" with no warranties and confers no rights.
Rhett Gong [MSFT] - 21 Feb 2005 06:51 GMT
From your log above, seems your installation process failed in
pCompiler->CompileFile, but it is hard to decide what may cause this
probelm. Could you tell what addition information you get when running the
command manually?
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.
Jason Galbreath - 22 Feb 2005 18:43 GMT
When running the command manually no additional information is displayed.
The command runs and exits silently. The actsetup.log file contains the
same information as it did when setup ran the command.
Jason Galbreath
Arizona Public Service
> From your log above, seems your installation process failed in
> pCompiler->CompileFile, but it is hard to decide what may cause this
[quoted text clipped - 7 lines]
>
> This posting is provided "AS IS" with no warranties and confers no rights.
Rhett Gong [MSFT] - 23 Feb 2005 06:58 GMT
Now, could you let your customer copy the installation files and logoff the
current domain user but logon with a local admin account to see if it still
exhibits the same problem?
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.