OK. I have followed your instruction. My rights are the same from desktop
to drive and am being allowed to exicute the file. (I could send a screen
shot if that will help.) Here is a list of error codes I am getting:
Level Date and Time Source Event ID Task Category
Information 4/18/2007 12:08:17 PM MsiInstaller 1035 None Windows Installer
reconfigured the product. Product Name: Business Contact Manager for Outlook
2007. Product Version: 3.0.6402.0. Product Language: 1033. Reconfiguration
success or error status: 1603.
Information 4/18/2007 12:08:17 PM MsiInstaller 11729 None Product: Business
Contact Manager for Outlook 2007 -- Configuration failed.
Information 4/18/2007 12:08:17 PM MsiInstaller 1036 None Windows Installer
installed an update. Product Name: Business Contact Manager for Outlook 2007.
Product Version: 3.0.6402.0. Product Language: 1033. Update Name: Update for
BCM V3. Installation success or error status: 1603.
Error 4/18/2007 12:08:17 PM MsiInstaller 1023 None Product: Business Contact
Manager for Outlook 2007 - Update 'Update for BCM V3' could not be installed.
Error code 1603. Additional information is available in the log file
C:\Users\BLeonard\AppData\Local\Temp\OHotfix\OHotfix(00013)_Msi.log.
Error 4/18/2007 12:08:15 PM MsiInstaller 11913 None Product: Business
Contact Manager for Outlook 2007 -- Error 1913.Could not update the INI file
C:\Windows\system32\mapisvc.inf. Verify that the file exists and that you
can access it.
Error 4/18/2007 12:08:12 PM MsiInstaller 11913 None Product: Business
Contact Manager for Outlook 2007 -- Error 1913.Could not update the INI file
C:\Windows\system32\mapisvc.inf. Verify that the file exists and that you
can access it.
Error 4/18/2007 12:08:11 PM MsiInstaller 11913 None Product: Business
Contact Manager for Outlook 2007 -- Error 1913.Could not update the INI file
C:\Windows\system32\mapisvc.inf. Verify that the file exists and that you
can access it.
Error 4/18/2007 12:08:10 PM MsiInstaller 11913 None Product: Business
Contact Manager for Outlook 2007 -- Error 1913.Could not update the INI file
C:\Windows\system32\mapisvc.inf. Verify that the file exists and that you
can access it.
Error 4/18/2007 12:08:09 PM MsiInstaller 11913 None Product: Business
Contact Manager for Outlook 2007 -- Error 1913.Could not update the INI file
C:\Windows\system32\mapisvc.inf. Verify that the file exists and that you
can access it.
Information 4/18/2007 11:52:13 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
The next run has been scheduled to occur at approximately 12:56 PM.
Information 4/18/2007 11:52:13 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
Automatic LiveUpdate has terminated.
Information 4/18/2007 11:51:23 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
Scheduler launched Automatic LiveUpdate.
Information 4/18/2007 10:55:58 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
The next run has been scheduled to occur at approximately 11:51 AM.
Information 4/18/2007 10:55:58 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
Automatic LiveUpdate has terminated.
Information 4/18/2007 10:55:24 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
Scheduler launched Automatic LiveUpdate.
Information 4/18/2007 10:48:16 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
The next run has been scheduled to occur at approximately 10:55 AM.
Information 4/18/2007 10:48:16 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
Automatic LiveUpdate has terminated.
Information 4/18/2007 10:47:28 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
Scheduler launched Automatic LiveUpdate.
Information 4/18/2007 9:54:56 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
The next run has been scheduled to occur at approximately 10:47 AM.
Information 4/18/2007 9:54:56 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
Automatic LiveUpdate has terminated.
Information 4/18/2007 9:53:34 AM Automatic LiveUpdate
Scheduler 101 Scheduler Events Information Level: success
Scheduler launched Automatic LiveUpdate.
Information 4/18/2007 9:53:16
AM Microsoft-Windows-LoadPerf 1000 None Performance counters for the WmiApRpl
(WmiApRpl) service were loaded successfully. The Record Data in the data
section contains the new index values assigned to this service.
Information 4/18/2007 9:53:15
AM Microsoft-Windows-LoadPerf 1001 None Performance counters for the WmiApRpl
(WmiApRpl) service were removed successfully. The Record Data contains the
new values of the system Last Counter and Last Help registry entries.
Information 4/18/2007 9:52:38 AM MSSQL$MSSMLBIZ 17137 (2) Starting up
database 'MSSmallBusiness'.
Information 4/18/2007 9:52:38 AM MSSQL$MSSMLBIZ 17401 (2) Server resumed
execution after being idle 207 seconds: user activity awakened the server.
This is an informational message only. No user action is required.
Information 4/18/2007 9:50:53 AM SecurityCenter 1 None The Windows Security
Center Service has started.
Information 4/18/2007 9:50:31 AM WcesComm 1 None Windows Mobile legacy
device connectivity service started.
Information 4/18/2007 9:50:31 AM RapiMgr 1 None Windows Mobile legacy device
connectivity service started.
Information 4/18/2007 9:50:17 AM LiveUpdate Notice Service 0 None "The
description for Event ID 0 from source LiveUpdate Notice Service cannot be
found. Either the component that raises this event is not installed on your
local computer or the installation is corrupted. You can install or repair
the component on the local computer.
If the event originated on another computer, the display information had to
be saved with the event.
The following information was included with the event:
Service started
"
Information 4/18/2007 9:49:53
AM Microsoft-Windows-CertificateServicesClient 1 None Certificate Services
Client has been started successfully.
Information 4/18/2007 9:49:53 AM Microsoft-Windows-Winlogon 6000 None The
winlogon notification subscriber <UmRdpService> was unavailable to handle a
notification event.
Information 4/18/2007 9:49:53 AM Microsoft-Windows-Winlogon 6000 None The
winlogon notification subscriber <SessionEnv> was unavailable to handle a
notification event.
Information 4/18/2007 9:49:53
AM Microsoft-Windows-Winlogon 4101 None Windows license validated.
Information 4/18/2007 9:48:43
AM Microsoft-Windows-CertificateServicesClient 1 None Certificate Services
Client has been started successfully.
Information 4/18/2007 9:48:41 AM Microsoft-Windows-Search 1003 Search
service The Windows Search Service started.
Information 4/18/2007 9:48:38 AM MSSQL$MSSMLBIZ 9688 (2) Service Broker
manager has started.
Information 4/18/2007 9:48:38 AM MSSQL$MSSMLBIZ 9666 (2) The Database
Mirroring protocol transport is disabled or not configured.
Information 4/18/2007 9:48:38 AM MSSQL$MSSMLBIZ 9666 (2) The Service Broker
protocol transport is disabled or not configured.
Information 4/18/2007 9:48:38 AM MSSQL$MSSMLBIZ 3408 (2) Recovery is
complete. This is an informational message only. No user action is required.
Information 4/18/2007 9:48:38 AM MSSQL$MSSMLBIZ 17137 (2) Starting up
database 'tempdb'.
Information 4/18/2007 9:48:37 AM MSSQL$MSSMLBIZ 17136 (2) Clearing tempdb
database.
Information 4/18/2007 9:48:37 AM MSSQL$MSSMLBIZ 17126 (2) SQL Server is now
ready for client connections. This is an informational message; no user
action is required.
Information 4/18/2007 9:48:37 AM MSSQL$MSSMLBIZ 17199 (2) Dedicated
administrator connection support was not started because it is not available
on this edition of SQL Server. This is an informational message only. No user
action is required.
Information 4/18/2007 9:48:37 AM MSSQL$MSSMLBIZ 26048 (2) Server local
connection provider is ready to accept connection on [
\\.\pipe\MSSQL$MSSMLBIZ\sql\query ].
Information 4/18/2007 9:48:37 AM MSSQL$MSSMLBIZ 26048 (2) Server local
connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\MSSMLBIZ ].
Information 4/18/2007 9:48:37 AM MSSQL$MSSMLBIZ 26018 (2) A self-generated
certificate was successfully loaded for encryption.
Information 4/18/2007 9:48:36 AM MSSQL$MSSMLBIZ 17137 (2) Starting up
database 'msdb'.
Information 4/18/2007 9:48:36 AM MSSQL$MSSMLBIZ 17137 (2) Starting up
database 'model'.
Information 4/18/2007 9:48:36 AM MSSQL$MSSMLBIZ 17663 (2) Server name is
'COWBERT\MSSMLBIZ'. This is an informational message only. No user action is
required.
Information 4/18/2007 9:48:36 AM MSSQL$MSSMLBIZ 958 (2) The resource
database build version is 9.00.3042. This is an informational message only.
No user action is required.
Information 4/18/2007 9:48:36 AM MSSQL$MSSMLBIZ 17137 (2) Starting up
database 'mssqlsystemresource'.
Information 4/18/2007 9:48:36 AM MSSQL$MSSMLBIZ 19030 (2) "SQL Trace ID 1
was started by login ""sa""."
Information 4/18/2007 9:48:36 AM Microsoft-Windows-WMI 5617 None Windows
Management Instrumentation Service subsystems initialized successfully
Information 4/18/2007 9:48:35 AM MSSQL$MSSMLBIZ 3454 (2) Recovery is writing
a checkpoint in database 'master' (1). This is an informational message only.
No user action is required.
Information 4/18/2007 9:48:35 AM Microsoft-Windows-WMI 5615 None Windows
Management Instrumentation Service started sucessfully
Information 4/18/2007 9:48:35 AM TOSHIBA Bluetooth Service 0 None "The
description for Event ID 0 from source TOSHIBA Bluetooth Service cannot be
found. Either the component that raises this event is not installed on your
local computer or the installation is corrupted. You can install or repair
the component on the local computer.
Nanjuan(MSFT) said:
Hi,
Thanks for the detailed information. Could you please verify that when
installing the QFE, you get the Vista "User Account Control" dialog and
choose to continue?
And if this User Account Control dialog does not show up, could you
please try save the QFE down to your local disk, right click the QFE exe, and
choose to "run as administrator"? There is a possibility that the admin did
not really install at admin level on Vista machine due to specific UAC
settings. Thanks.