Windows Legacy OS forum

General discussion

Windows Installer Problem

by DUKEMON / March 4, 2007 5:46 PM PST

I try to install some software but i kept on getting the error message which it said:

"The Windows Installer Service could not be accessed.This can occur if you are running in safe mode, or if the windows installer is not correctly installed. Contact your support personnel for assistance"


I'm using Windows XP Professional SP2 with all the latest update applied.

I'm running in Normal mode and the user account has administrator privilege.

Windows Installer version: 3.1.4000.1823

I had tried downloading Windows Installer 3.1v2 package and installed it but that did not fix the problem.

Screenshot of the error message can be view at the following URL:
http://img258.imageshack.us/img258/5964/windowsinstallerhn6.png

I had tried the solution of microsoft KB315346 but that also fail to correct the problem.

Discussion is locked
You are posting a reply to: Windows Installer Problem
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: Windows Installer Problem
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
Is the Windows Installer service disabled?
by Gertnoob / March 4, 2007 11:16 PM PST

Tjeck out if the service is disabled. Start >> run >> services.msc
Look for Windows Installer. Rightclick >> properties. The start up type for this service should be manual, meaning it will run if its called upon.

Maybe this tool can help to remove any flawed install info, and then after you can do reinstall of the desired software. :
http://support.microsoft.com/kb/290301

I once had a weird install problem, then I realised that I had removed VBS script reference, for security reasons years ago, lol. But with that error message your having, I would guess its the service being disabled.

-cheers-

Collapse -
Non of the solution work
by DUKEMON / March 5, 2007 2:59 PM PST

I checked the starup type for windows installer service and it is indeed in manual mode.Unfortunately, the solution(KB290301)you had provided does not work for me and i try to run the Windows Installer CleanUp Utility but it failed with the same error message.

Collapse -
Re-register the Windows Installer
by Gertnoob / March 5, 2007 7:18 PM PST
Collapse -
edit
by Gertnoob / March 5, 2007 7:33 PM PST

Just realised, that you have done that allready.

Well I dunno then, maybe you missed something? I can see the Installer they offer at Microsoft link is Windows Installer 3.1 v2 (3.1.4000.2435. Maybe try that??

Good luck..

Collapse -
Installed the latest version
by DUKEMON / March 5, 2007 10:33 PM PST
In reply to: edit

I downloaded the latest version of the windows installer 3.1V2 and installed it and seems that the windows installer setup had finished the update with no error message but i checked the Windows\System32 folder and it still contain the same old version(which mean it fail to update).

By the way, i saw the KB893803v2 Log(Windows installer log)and it seems that it might have some problem but i'm not sure what cause the problem so i post the content of the log over here:

[KB893803v2.log]
0.221: ================================================================================
0.221: 2007/03/06 22:25:49.060 (local)
0.221: c:\39d4808ed8113a07bf0e\UPDATE\update.exe (version 6.1.22.4)
0.241: Hotfix started with following command line:
3.055: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with error 0x2
3.055: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with error 0x2
3.055: DoInstallation: CleanPFR failed: 0x2
3.065: SetProductTypes: InfProductBuildType=BuildType.Sel
3.065: SetAltOsLoaderPath: No section uses DirId 65701; done.
3.145: DoInstallation: FetchSourceURL for c:\39d4808ed8113a07bf0e\update\update_wxp.inf failed
3.145: CreateUninstall = 0,Directory = C:\WINDOWS\$MSI31Uninstall_KB893803v2$
3.145: LoadFileQueues: UpdSpGetSourceFileLocation for halacpi.dll failed: 0xe0000102
3.145: BuildCabinetManifest: update.url absent
3.155: Starting AnalyzeComponents
3.155: AnalyzePhaseZero used 0 ticks
3.155: No c:\windows\INF\updtblk.inf file.
3.155: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
3.155: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
10.936: Third Party Provider = VIA Technologies, Inc. for PCI\VEN_1106&DEV_3116&SUBSYS_00000000&REV_00\3&61AAA01&0&00
11.257: Third Party Provider = VIA Technologies, Inc. for PCI\VEN_1106&DEV_3177&SUBSYS_00000000&REV_00\3&61AAA01&0&88
11.687: Failed to query DriverPath of ROOT\LEGACY_AFD\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_AVGIO\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_BEEP\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_BLACK\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_DCDISK\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_DMBOOT\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_DMLOAD\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_FIPS\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_GPC\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_HTTP\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_IPFILTERDRIVER\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_IPNAT\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_IPSEC\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_KSECDD\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_MNMDD\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_MOUNTMGR\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_NDIS\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_NDISTAPI\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_NDISUIO\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_NDPROXY\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_NETBT\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_NPKCRYPT\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_NULL\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_PARTMGR\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_PARVDM\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_RAPFILE\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_RAPNET\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_RASACD\0000 0x2
11.687: Failed to query DriverPath of ROOT\LEGACY_RDPCDD\0000 0x2
11.697: Failed to query DriverPath of ROOT\LEGACY_RITFSD\0000 0x2
11.697: Failed to query DriverPath of ROOT\LEGACY_SECDRV\0000 0x2
11.697: Failed to query DriverPath of ROOT\LEGACY_TCPIP\0000 0x2
11.697: Failed to query DriverPath of ROOT\LEGACY_VGASAVE\0000 0x2
11.697: Failed to query DriverPath of ROOT\LEGACY_VOLSNAP\0000 0x2
11.697: Failed to query DriverPath of ROOT\LEGACY_WANARP\0000 0x2
12.508: SetupVerifyInfFile failed with error 0x490 for exdisk.inf of device ROOT\RITEXDISK\0000
12.559: SetupVerifyInfFile failed with error 0x490 for c:\windows\inf\exdisk.inf of device ROOT\RITEXDISK\0000
13.830: OEM file scan used 10675 ticks
14.321: AnalyzePhaseOne: used 11166 ticks
14.321: AnalyzeComponents: Hotpatch analysis disabled; skipping.
14.321: AnalyzeComponents: Hotpatching is disabled.
14.321: AnalyzePhaseTwo used 0 ticks
14.321: AnalyzePhaseThree used 0 ticks
14.321: AnalyzePhaseFive used 0 ticks
14.321: AnalyzePhaseSix used 0 ticks
14.321: AnalyzeComponents used 11166 ticks
14.321: Downloading 0 files
14.321: bPatchMode = FALSE
14.321: Inventory complete: ReturnStatus=0, 11176 ticks
14.341: Num Ticks for invent : 11196
14.341: Allocation size of drive C: is 4096 bytes, free space = 24652771328 bytes
14.341: Drive C: free 23510MB req: 5MB w/uninstall 0MB
14.341: CabinetBuild complete
14.341: Num Ticks for Cabinet build : 0
14.341: DynamicStrings section not defined or empty.
14.341: FileInUse:: need to restart already, turn off
14.341: FileInUse:: Add to list - Service Name: msiserver
15.363: LoadFileQueues: UpdSpGetSourceFileLocation for halacpi.dll failed: 0xe0000102
16.574: PFE2: Not avoiding Per File Exceptions.
17.836: DoInstallation: Installing assemblies with source root path: c:\39d4808ed8113a07bf0e\
17.836: Num Ticks for Copying files : 3495
17.876: Num Ticks for Reg update and deleting 0 size files : 40
17.886: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is empty; nothing to do.
19.719: RebootNecessary = 0,WizardInput = 0 , DontReboot = 1, ForceRestart = 0

Collapse -
policy rules
by Gertnoob / March 5, 2007 7:50 PM PST

run >> gpedit.msc >> Adm. templates >> Windows Component >> Windows installer.

Any weird rules settings?

Collapse -
services again
by Gertnoob / March 5, 2007 8:11 PM PST
In reply to: policy rules

Where is the edit button on this site, lol.

I can see Windows Installer is dependent on Remote Procedure Call, is that one running good?

Collapse -
RPC is running
by DUKEMON / March 5, 2007 10:19 PM PST
In reply to: services again

I checked the RPC on the services.msc and it is running and the sratup type is set to automatic.

Collapse -
Checked Group Policy setting
by DUKEMON / March 5, 2007 10:21 PM PST
In reply to: policy rules

I had checked the policy setting for windows installer and it stated that it's not configured.

Collapse -
permissions
by Gertnoob / March 6, 2007 1:58 AM PST

How about advice 3&4 from :http://support.microsoft.com/?id=319624

Method 3: Give Full Control permission to the SYSTEM account
1. Start Windows Explorer, right-click the computer's root hard drive, and then click Properties.
2. Click the Security tab, and then click Add.
3. In the Select Users, Computers, or Groups dialog box, click the SYSTEM account, click Add, and then click OK.
4. Under Allow, click to select the Full Control check box, and then click OK.
5. Click the TEMP folder and then verify that the SYSTEM account has full control.

Back to the top

Method 4: Verify the registry permissions
1. Click Start, click Run, then type Regedt32.
2. For each of the registry hives, follow these steps:a. Select the hive.
b. For Windows XP, on the Edit menu, click Permissions.

For Windows 2000 and Windows NT 4, on the Security menu, click Permissions.

3. Verify that the SYSTEM account has been added and that it has Full control. If it does not, add the SYSTEM account with Full control.


Or maybe you can find something at microsoft newsgroup:
http://www.microsoft.com/windowsxp/expertzone/newsgroups/reader.mspx?query=windows+installer&dg=microsoft.public.windowsupdate&cat=en-us-ms-winxp&lang=en&cr=US&pt=&catlist=B0DE109D-10E1-4C3C-BCC9-8EB7A22FC6A0&dglist=&ptlist=&exp=&sloc=en-us

I could see there was alot of entries for Windows installer 3.1

Its obviously not a triviel problem, so good luck with it.

Collapse -
checked permissions
by DUKEMON / March 6, 2007 4:49 PM PST
In reply to: permissions

I had try all the solution listed at KB319624 unfortunately it does not work. So i'm currently looking at the microsoft newsgroup to find for a solution.

Collapse -
Just FYI.
by R. Proffitt Forum moderator / March 6, 2007 8:34 PM PST
In reply to: checked permissions

I watched someone else with this issue and in the end it was viral damage. The damage apparently ran too deep and they had to do the usual wipe and reinstall. Best of luck here.

Bob

Collapse -
windows installer
by rexlperrry / March 7, 2007 8:32 AM PST

ive tried everything and a microsoft tech is working on t6he problem

Popular Forums
icon
Computer Newbies 10,686 discussions
icon
Computer Help 54,365 discussions
icon
Laptops 21,181 discussions
icon
Networking & Wireless 16,313 discussions
icon
Phones 17,137 discussions
icon
Security 31,287 discussions
icon
TVs & Home Theaters 22,101 discussions
icon
Windows 7 8,164 discussions
icon
Windows 10 2,657 discussions

GIVEAWAY

Turn up the volume with our Apple Byte sweeps!

Two lucky winners will take home the coveted smart speaker that lets Siri help you around your connected house. This sweepstake ends Feb. 25, 2018.