Upgrading to 2010 to SP3 Failed
Looking for some help quickly if possible.
Error: The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
if
(test-ExchangeServersWriteAccess -DomainController $RoleDomainController
-ErrorAction SilentlyContinue)
# upgrade the
discovery mailboxes to R5 version, this will fix the
RecipientDisplayType property of the discovery mailbox which was wrong
in R4.
get-mailbox -RecipientTypeDetails DiscoveryMailbox
-DomainController $RoleDomainController | where {$_.IsValid -eq $false}
| set-mailbox -DomainController $RoleDomainController
$name =
[Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::
DiscoveryMailboxUniqueName;
$dispname =
[Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::
DiscoveryMailboxDisplayName;
$mbxs = @( get-mailbox
-Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
if ( $mbxs.length -eq 0)
$dbs =
@(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController
$RoleDomainController);
if($dbs.Length -ne 0)
$mbxUser = @(get-user -Filter {name -eq $name}
-IgnoreDefaultScope -ResultSize 1);
if
($mbxUser.Length -ne 0)
enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname
-database $dbs[0].Identity;
else
write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox
because of insufficient permission."
" was run: "The user's Active Directory account must be logon-disabled
for linked, shared, or resource mailbox.".
The user's Active Directory account must be logon-disabled for linked,
shared, or resource mailbox. Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141
).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
I have rerun setup.com /prepairead & /prepareschema.
Thanks, Grady Vogt
I believe I resolved it recreating system & discovery mailboxes
http://vmehran.com/2013/07/re-create-discovery-and-other-system-mailboxes-in-exchange-2010.html
Thanks, Grady Vogt
Similar Messages
-
Cannot install KB982867 while trying to Upgrade exchange 2010 to SP3
I just had to reinstall Server 2008 standard with Exchange 2010. I am now trying to install SP3 on Exchange and got all the hotfixs but the KB982867. I go to the link on the install screen and it take me to a Archive page. I did find on the web a download
for the hotfix but it will not install. It turns out to be net frame works 4.0. This is the message I get. KB2532942 does not apply, or is blocked by another condition on your computer. I currently have installed net frameworks 3.5 SP1 and 4.5.1 . This
is the message I am getting during the install. Client Access Role Prerequisites
Failed
Error:
Install hotfix Microsoft Knowledge Base article 982867 from http://code.msdn.microsoft.com/KB982867.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex28883C&l=0&cl=cp
Elapsed Time: 00:00:14
Thanks
ZmanHi Zman,
Before you install KB2532942, you must have the .NET Framework 4 installed to apply this hotfix rollup.
The related KB for your reference:
Hotfix rollup package 2532942 is available for Windows Communication Foundation for the .NET Framework 4
http://support.microsoft.com/kb/2532942
If you have any further questions, please do not hesitate to post back.
Best regards,
Eric -
Exchange 2007 SP3 failed and cannot comeback to upgrade Menu
Hi team,
I plan to migrate from Exchange 2007 to 2013. so I wan to upgrade exchange 2007 from SP1 to SP3
I have two exchange 2007 SP1 Server, Server 1 CAS+HT. Server 2 CAS+HT+MBX.
I already upgrade Server1 (CAS+HT). upgrade success without issue. but when I upgrade Server2 (CAS+MBX+HT)
I found error at HT upgrade step.
this is the error
Error:
This role cannot be installed because the following roles are not current: ClientAccessRole MailboxRole AdminToolsRole
after this error I change registry HKLM\Software\Microsoft\Exchange\v8.0\
and config same version between Unpacked Version and configured Version. I change from 8.1.240.6 to 8.3.83.6. so all unpacked and configure version become 8.3.83.6
. this is the link
http://blogs.technet.com/b/exchange/archive/2007/05/21/3402900.aspx
But, after I restart the Server, Exchange installation not continue to upgrade from SP1 to SP3.
the Menu seems to appear like new Exchange installation menu. like attached picture bellow
its weird, if I click next, the menu appear like exchange 2007 new installation.
can I back to Exchange 2007 upgrade menu GUI?.
I suggest to use setup.com /m:upgrade. but is this a suitable method?
please help team :)
Thanks
RegardsHi,
According to your description, I understand that cannot upgrade to Exchange 2007 SP3 with error “This role cannot be installed because the following roles are not current: ClientAccessRole MailboxRole AdminToolsRole”.
If I misunderstand your concern, please do not hesitate to let me know.
If the upgrade isn’t complete, the version of current Exchange server (SP1) is 8.1.240.6. The version of 8.3.83.6 is related to Exchange 2007 SP3.
Therefore, please change the setting back and try again.
Besides, I find a similar thread about this error message when upgrade to Exchange 2007 SP3, for your reference:
https://social.technet.microsoft.com/Forums/en-US/fba6fd70-a406-4d79-8a07-0385ac04c600/exchange-service-pack-2-install-fails
“In the end I solved my issue here by re-running the /prepareAD and /preparedomain. I then deleted the watermark keys in the regestry as described above and happy days.”
Best Regards,
Allen Wang -
Why does downloaded upgrade to Acrobat 9.5.2 Pro Extended under Win XP HE SP3 fail
Why does downloaded upgrade to Acrobat 9.5.2 under Win XP HE SP3 fail ?
Also, do you mean the upgrade from AA9 to AA XI? Where did you download the upgrade? The only upgrade available from Adobe is to AA XI.
-
Best Path to upgrade Exch 2010 SP1/W2K8 R2 to Exch2010 SP3/W2K8 R2 SP1
What would be the best path forward to upgrade an existing Exchange 2010 SP1 server (no rollups) on Windows Server 2008 R2 to Exchange 2010 SP3 on Windows Server 2008 R2 SP1? Exchange is on a DAG with a secondary server.
Hi,
In addition to Ed Crowley's suggestion, I would like to clarify the following thing about upgrading Exchange server and Windows server:
In-place upgrade is not supported, it will break Exchange.
Here is a thread for your reference.
In-place upgrade exchange 2010-SP3 to Windows Server 2012
http://social.technet.microsoft.com/Forums/en-US/be9e10c3-c090-449b-bff3-693f52490d8d/inplace-upgrade-exchange-2010sp3-to-windows-server-2012?forum=exchange2010
In your case, you need to set up a new server, move mailboxes to it at first.
Secondly, upgrade Windows server.
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support -
7310 - Problem with CIFS and Roaming Profiles since upgrade to 2010.Q1.0.2
We have developed a strange problem with our environment which I'm pretty sure is down to the upgrade to 2010.Q1.0.2 from 2009.Q3.4.1 on our 7310 (all the previous 2009 releases had been fine) since nothing else has changed in our environment. I suspect some changes to the underlying CIFS server causing this?
We have virtual Windows servers hosted on a VMWare VSphere cluster which are stored on the 7310 via iSCSI LUNs and also CIFS shares on the 7310 for home directories and separate CIFS shares for roaming profiles - all paths are correct in AD for each user - we also use folder redirection for XP Pro clients to force things like "Application Data", "My Documents" etc. onto the Homedir share.
What we've been seeing recently (which only started happening after the upgrade) is a lot of failed logons to the domain for users. It looks like the usual corrupted profile problem that has plagued Windows forever ...the usual messages that it cannot log the user on with a copy of their roaming profile, and that it will use a temporary one. Some folder redirections (that are initiated via Group Policy) also don't get applied. Users don't see errors when logging off from a "good" profile, and NTUSER.DAT etc. seemingly gets written correctly - the next time they log on, around half the time the users will get these errors as described below:
Event viewer logs show "cannot find the file specified" errors for NTUSER.DAT, along with "directory name is invalid" errors for some of the folder redirections.
More worrying (and what I think might be the real reason for these failures) are the "offline caching is enabled on the roaming profile share" errors. I think that the client-side caching might not be working - possibly the profiles aren't getting flushed and written correctly upon logout?
Now, unfortunately the MMC snap-in for managing shares doesn't seem to support changing the behaviour for client-side caching on the CIFS shares (as confirmed in the latest 7000-series Admin Guide on page 198).
I've been thinking about unchecking the "Enable Oplocks" box which from the CIFS side would completely stop all client-side caching I presume?
Is this likely to be the culprit here, or is there any other known behaviour that could be causing these errors? Is it also worth disabling "Cache device usage" altogether for the Profiles share itself?
Can anyone help? It's a bit of a strange problem, and something I don't want to raise with Sun on our support contract just yet, since at first glance it looks like a Windows problem, but I suspect the storage could well be to blame...Unfortunately, this is still not working correctly...
So, it looks like it's not related to the offline caching seeing as it all works on the Q2009 despite the warnings...
Some more errors coming out of userenv.log on the affected Windows machines:
USERENV(280.284) 10:07:33:230 ReconcileFile: GetFileAttributes on the source failed with error = 2
USERENV(280.284) 10:07:33:230 CopyProfileDirectoryEx: ReconcileFile failed with error = 2
and later:
USERENV(280.284) 10:07:33:245 GetShareName: WNetGetConnection initially returned error 2250
USERENV(280.284) 10:07:33:245 CopyProfileDirectoryEx: Leaving with a return value of 0
USERENV(280.284) 10:07:33:245 RestoreUserProfile: CopyProfileDirectory failed. Issuing default profile
...which then forces the TEMP profiles.
All other errors linked to this look like "file not found", "invalid path" etc. when the files are present and the paths are correct.
Manually mapping drives using CIFS with UNC paths sporadically fails too now. We have a bunch of GPOs that map shares to users depending on their group memberships - these too are sporadically failing.
It certainly looks to me like it could be a CIFS problem introduced in the Q2010 release.
I'm going to raise a ticket with Sun... -
Exchange Server 2010 with SP3 Management Tools
Recently I have installed brand new Exchange Server 2010 with SP1 in my test domain. Afterwards I upgraded it to Exchange Server 2010 with SP3. On client machine (Windows 7 Pro with SP1 x64) I run setup.exe for Exchange Server 2010 with SP1 installation
DVD to install Management Tools. All checks passed successfully but after installation was completed there was an error in EMC:
The World Wide Web Publishing Service (W3SVC) isn't running on any Exchange servers in the site. If you want to connect to Remote Powershell, this service must be running. Make sure that the W3SVC is running on at least one Exchange server.
Of course service is running. I read this has something to do with different versions of Exchange Server itself and Management Tools. Since there is no installation of Exchange Server 2010 with SP3 how to solve this? I assume if I have installation of Exchange
Server 2010 with slipstreamed Service Pack 3, management tools installed from this installation would work.
Also does this mean that, if I have working tools for Exchange Server and SP for it is installed later, tools will stop functioning?I would install SP3 on all servers and workstation as SP1 and SP2 aren't supported anymore and see how it is behaving...
http://blogs.technet.com/b/rmilne/archive/2013/01/04/end-of-exchange-2010-sp1-support.aspx -
Change to Exchange 2010 after SP3, Update 5 installed
After updating Exchange 2010 from SP3 Update 2 to Update 5, a change has occurred for users with SendAs and Full Access to other mailboxes. Version 14.3 (build 123.4).
Before the Update, after giving a user these permissions to another user's mailbox, the mailbox would show in their Outlook 2010 client, and everything worked as expected.
After Update 5 was installed, when users select the other user's mailbox, they get a message "the folders are not available," or the connection to the Exchange server is not working." They can access their own mailbox with no issues.
The other mailbox has to be added to the Outlook client via Account Settings, Account Settings, Change, More Settings, Advanced tab, Add the other mailbox. The mailbox then shows up twice on the client, but only the one that has been added works,
the original still gives the same error.
Lou H.Hi,
I have seen some people have the same issue with you. After upgrading to Rollup 5, they need to add others' mailboxes that they have full access permission and send as permission manually on Outlook. But when they upgrade Outlook to 2010 SP2, this issue
is solved. I recommend you upgrade your Outlook to 2010 SP2 and check the result.
Besides, I'm not sure what changes after Rollup 5 lead to this issue, there is no official article explain it, thanks for your understanding.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support -
After upgrade the MDM 71 Sp3 to SP4 the MDS dos not startet
Hello,
I have an problme after a update from MDM 7.1 SP3 to SP4. The update was finished successful but my MDM Server (MDS) stopped after the starting wiht follow message
Starting: /usr/sap/TBD/MDS10/exe/mds-r - Wed Mar 3 10:16:31 CET 2010
SunOS Q4DE8NSYM07 5.10 Generic_141415-04 i86pc i386 i86pc
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 10240
coredump(blocks) unlimited
nofiles(descriptors) 4096
memory(kbytes) unlimited
-rwxr-xr-x 1 tbdadm sapsys 179664288 Feb 13 20:52 /usr/sap/TBD/MDS10/exe/mds-r
Application Started.
mds Version 7.1.04.120
Built on 2010-Feb-13
Client Interface Version 7.1.04.07
- Interface CRC=0x9229b868
MDS Admin Interface Version 7.1.04.07
- Interface CRC=0xb7b7fe03
MDS Public Interface Version 7.1.04.03
- Interface CRC=0xd7594919
Web Interface Version 7.1.04.11
- Interface CRC=0xb8de6193
Application Stopped.
Application Started.
[INFO] <MDM/Servers/MDS/MDSCommon/XCSGlobalFunctions.cpp:415> "User authentication method: Repository"
increasing thread stack from 0 kB to 1024 kB...
Loading shared library: ncs.so ...
ncs.so loaded.
increasing thread stack from 0 kB to 1024 kB...
increasing thread stack from 0 kB to 1024 kB...
increasing thread stack from 0 kB to 1024 kB...
Ending: /usr/sap/TBD/MDS10/exe/mds-r (rc=134) - Wed Mar 3 10:16:57 CET 2010
When I start it again it dosn't work. With th update with my development System I had no problem.
Have anybody an idea?
Thanks
ThomasHi,
I would suggest you to re-install MDM server again.
Also refer, SAP Note 1432315 for upgrading MDM 7.1 SP3 to MDM 7.1 SP4.
Go through section, B4. Update MDM Servers.
Again, I would suggest you to go through this SAP Note 1432315
Also refer SAP Note, Note 1359600 - MDM stopped communicating after upgrading to 7.1.03 or Higher.
It tells that it is something related to TCP Port/firewall restriction Change. Please check this SAP Note for more details.
Kindly mark the thread as Answered as your Problem solved so that others can benefit if they have similar issue.
Thanks and Regards,
Mandeep Saini
Edited by: Mandeep Singh Saini on Mar 3, 2010 12:55 PM
Edited by: Mandeep Singh Saini on Mar 3, 2010 4:57 PM -
The Connection Server does not start after an upgrade to BO4.1 SP3
Hello guys,
The Connection Server does not start after an upgrade to BO4.1 SP3
We are in process to upgrade our Business Objects environments to BO4.1 SP3
The first 2 environments , the upgrade went fine. But the third environment de connection server won’t start.
When I always try to start it returns me a failed status and shows me that the server is considered failed because it has stopped 5 time(s) in 60 minute(s).
Our OS is AIX
Uncaught Exception in SilentScope: [CS] Ser
verInitialization::InitManager::Initialize: 0.007^^
The CS initialization failed within the CS server. Aborting
trc file: "connectionserver_BIO.ConnectionServer_ncs.trc", trc level: 1, release: "720"
GerdHi Amine
The File seems ok
File from the failing connection server
-rw-rw---- 1 bioadm bosys 43993 Apr 11 11:29 boconfig.cfg
File from our test system
-rw-rw---- 1 bitadm bosys 43892 Apr 14 10:56 boconfig.cfg
I created a new connectieserver(by the copy function), but the new server won't start.
Regards
Gerd
Log
|89d4a6e0-2a89-7a05-3020-a51d517ab872|2014 04 14 11:54:30:113|+0200|Error| |>>|E| |connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||[CS] Unhandled exception raised during CS initialization.
init_srv.cpp:95:-: TraceLog message 3
|4dcf04b1-1e1d-df13-48ad-a67f06e29864|2014 04 14 11:54:30:113|+0200|Error| |<<|E|X|connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||Uncaught Exception in SilentScope: [CS] ServerInitialization::InitManager::Initialize: 0.003
|77ad78f4-37f7-3013-3b50-85cce9fbe7b8|2014 04 14 11:54:30:113|+0200|Error| |>>|E| |connectionserver_BIO.ConnectionServer|28246236|3097|| |0|0|0|0|-|-|-|-|-|-||||||||||||[CS] The CS initialization failed within the CS server. Aborting. -
SCCM 2012 - Project 2010 Standard deployment failed with error 1603
Hi everyone,
I’m in the progress to roll out a software deployment via SCCM 2012, it’s to remove the current Project 2010 Professional we installed and reinstall the Standard version. We got a task sequence for the job, which is Reboot>Un-install Project 2010 Pro>Reboot>Install
Project 2010 Std.
The Un-installation process uses this command: setup.exe /uninstall PrjPro /config "PrjPro.WW\uninstall.xml"
The Installation process uses this command: setup.exe /adminfile project_silent_install.MSP
But the deployment result is quite random, some of the PCs would succeed without any issue, some of them with fail at the installation process with 1708/1603 error. As far as I know we use standard Win 7 64bits SOE across the environment, so everyone should
have same system baseline.
I reviewed some of the failed Project 2010 Standard installation logs as it shows the following:
Executing chained package: PrjStdWW
05/09/2014 20:16:14 Installing chained package: PrjStdWW
PERF: TickCount=530512 Name=Verify MSI local install source Description=Begin function
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
LIS: wait for package "{90140000-003A-0000-0000-0000000FF1CE}" to complete caching
LIS: package "{90140000-003A-0000-0000-0000000FF1CE}" caching completed
PERF: TickCount=530528 Name=Completed verify local install source Description=End function
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Use Shell UI transform : LIS\{90140000-0115-0409-0000-0000000FF1CE}\ShellUI.MST
Current transform is at path: LIS\{90140000-0115-0409-0000-0000000FF1CE}\ShellUI.MST
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
Using transform at path: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\ShellUI.MST
Catalyst Package Install...
Package: PrjStdWW
File: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi
Command Line: PATCH="\\SCCM2012\SMSPKGE$\PC100139\project_silent_install.MSP" ADDLOCAL=C.35347883.0E64.45B4.88A0.1881DE05E259,OSpp_Core,Project_PIA,SetupExeArpEntry,Office10Fix1,ProductFiles,InternationalSupportFiles_JPN,AceFiles,IMNFiles,OfficeIntlRDC,AceOdbc,OArt_DocTheme,OSetupController,WISPFiles,TCDRegistration,SetLanguageFiles,TCWorks7Files,ClviewFiles,VBAFiles,OfficeAppSupport,TextConverters,ProductNonBootFiles,dummy_Office_PIA,CAGOffice10,VSCommonPIAHidden,WebDiscussFiles,CAGCat10,CAGCat10Clips,MsoInstalledPackagesScoped,WxpFiles,SetupControllerFiles,Forms_PIA,dummy_MSCOMCTL_PIA,AlwaysInstalled,Gimme_OnDemandData,AceRepl,OISFiles,OfficeOLESupport,OfficeMSProof6,CAGFiles,InternationalSupportFiles_ArialUni,OSpp,Ace_PIA,GraphicsFiltersFile,WebDriveFiles,PROJECTFiles,ProductFiles_B2TR,SetupXmlFiles,OfficePostBoot,DocumentImagingUtils,VSTOCLR35,CAGCategoryFiles,ProjectCommon,VSTO,ProofingParent,MsoCommonShellHandler,OfficeDigitalSFiles,CARegistryFeature,OfficeCoreRDC,SetupExeAddRegistry,NonC2R_ProductFiles,MSSOAP3,TranslationCore,CAGOffice10Clips REMOVE=WISPHidden ARPENTRY_NOMODIFY="#0" ARPENTRY_MODIFYPATH="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe"" /modify PRJSTD /dll OSETUP.DLL" INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SLD_OEMPIDKEY="0" ARPENTRY_NOELEVATEONMODIFY="#0" SETUP_REBOOT="never" COMPANYNAME=" " ARPENTRY_SKUCOMPONENTS="[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Proofing.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Project.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office64.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\PRJSTD\setup.xml[~]" ARPENTRY_HELPLINK="" ARPENTRY_DISPLAYICON="C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\OSETUP.DLL,1" ARPENTRY_DISPLAYNAME="Microsoft Project Standard 2010" ACCEPTEDEULA="1" ARPENTRY_DISPLAYVERSION="14.0.4763.1000" BRANDING_XML="C:\Windows\TEMP\Setup00001048\BRANDING.XML" SLD_SUPPORTSBYPASS="0" SLD_ACID="5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE" SLD_TRIALTYPE="0" ARPENTRY_PACKAGEREFS="[~]OfficeMUISet.en-us[~]OfficeMUI.en-us[~]Proofing.en-us[~]Proof.en-us[~]Proof.es-es[~]Office64MUISet.en-us[~]PrjStdWW[~]Office64WW[~]Office64MUI.en-us[~]ProjectMUI.en-us[~]Proof.fr-fr[~]" SLD_DPID="#xF804000004000000380032003500300033002D00300030003000390038002D003000300031002D003000300030003000310030002D00300033002D0031003000330033002D0037003600300031002E0030003000300030002D0031003200390032003000310034000000000000000000000000000000000000000000000000000000000000000000350064006300370062006600360031002D0035006500630039002D0034003900390036002D0039006300630062002D00640066003800300036006100320064003000650066006500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500072006F006A0065006300740053007400640056004C00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000A09E4657B64703B2F32E339838F004006FE4EEC0394DE6AB2D77DCABCBC8F1C3B8B617EF54ACB52805F38EE560D0B738230977F4AB92430B37CBF02B49DB7636DCF15CE7E175CCF354E009C7A02432315800310036002D0030003800300035003100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000056006F006C0075006D0065003A00470056004C004B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006C0074004B004D00530000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" REMOVESAMEVERSION="" SLD_LICENSETYPE="6" SETUPEXEINSTALLUICULTURE="en-US" ARPENTRY_SHELLUITRANSFORMLANGUAGE="en-US" USERNAME=" " ARPENTRY_CONTACT="" ARPENTRY_HELPTELEPHONE="" ARPENTRY_PRODUCTCODES="[~]{90140000-00B4-0409-0000-0000000FF1CE}[~]{90140000-002C-0409-0000-0000000FF1CE}[~]{90140000-003A-0000-0000-0000000FF1CE}[~]{90140000-002A-0000-1000-0000000FF1CE}[~]{90140000-001F-0C0A-0000-0000000FF1CE}[~]{90140000-001F-0409-0000-0000000FF1CE}[~]{90140000-001F-040C-0000-0000000FF1CE}[~]{90140000-0115-0409-0000-0000000FF1CE}[~]{90140000-006E-0409-0000-0000000FF1CE}[~]{90140000-002A-0409-1000-0000000FF1CE}[~]{90140000-0116-0409-1000-0000000FF1CE}[~]" ARPENTRY_INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SETUPEXE_DOARPWRITE="1" ACIDS="11B39439-6B93-4642-9570-F2EB81BE2238;5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE;B6E9FAE1-1A0E-4C61-99D0-4AF068915378" ARPENTRY_SPPSKUID="[~]5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE[~]" ARPENTRY_NOREMOVE="#0" SLD_PKU="0" SLD_PID="82503-001-0000106-49615" LICTYPE="ltKMS" ARPENTRY_UNINSTALLSTRING="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe"" /uninstall PRJSTD /dll OSETUP.DLL" ARPENTRY_NOREPAIR="#1" ARPENTRY_URLUPDATEINFO="" ARPENTRY_URLINFOABOUT="" REMOVEPREVIOUS="" ARPENTRY_CACHELOCATION="C:\MSOCache\All Users" REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\" ARPSYSTEMCOMPONENT=1 TRANSFORMS="C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\ShellUI.MST" ALLUSERS="1"
PERF: TickCount=530543 Name=MsiPackage::Install Description=Calling OMsiInstaller::InstallProduct for package file "C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Error: Failed to install product: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi ErrorCode: 1603(0x643).
Log level changed from: Standard to: Verbose
Rolling back chain
05/09/2014 20:18:47 Rolling back package: PrjStdWW
There appears to be no rollback work to do for package: PrjStdWW path: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi
05/09/2014 20:18:47 Rolling back package: Office64WW
Package Office64WW was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64WW
File: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\Office64WW.msi
Command Line: ADDLOCAL=AcePiaReg64,VSTO64,WordXmlEditVerb64,ExcelXmlEditVerb64,GrooveShellIntegration64,Project64Files,OSpp64_Core,ExcelPiaReg64,GraphPiaReg64,FormsPiaReg64,SmartTagPiaReg64,PPTXmlEditVerb64,MsoInstalledPackagesScoped,OfficeExample64bitFilesA,WAC_XmlEditVerb64SPD,SetupXmlFiles,WordPiaReg64,Outlook64Files,AlwaysInstalled64,VBEPiaReg64,VisioPiaReg64,Outlook64SearchShellReg,OneNote64Files,SetupControllerFiles,ProjectPiaReg64,SearchFilters64Files,OutlookPiaReg64,Gimme_OnDemandData,Visio64ShapeSearch,WAC_PIARegSPD64,ProductNonBootFiles64,XDocsPiaReg64,PublisherPiaReg64,OneNotePIAReg64,ProductFiles64,OfficeExample64bitFilesB,OfficePiaReg64,Visio64Files,TCDRegistration64,OSpp64,XDOCSFiles64,XDocsXmlEditVerb64,MsoCommonShellHandler64bit,AccessPiaReg64,PowerPointPiaReg64 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64WW ProductCode:{90140000-002A-0000-1000-0000000FF1CE}
05/09/2014 20:18:56 Rolling back package: ProjectMUI.en-us
Package ProjectMUI.en-us was installed in the chain... uninstalling as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Install Rollback (uninstall)...
Package: ProjectMUI.en-us
Product Code: {90140000-00B4-0409-0000-0000000FF1CE}
Command Line: REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back install of package: ProjectMUI.en-us path:C:\MSOCache\All Users\{90140000-00B4-0409-0000-0000000FF1CE}-C\ProjectMUI.msi
05/09/2014 20:19:00 Rolling back package: Proofing.en-us
Package Proofing.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proofing.en-us
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proofing.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proofing.en-us ProductCode:{90140000-002C-0409-0000-0000000FF1CE}
05/09/2014 20:19:04 Rolling back package: Proof.en-us
Package Proof.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.en-us
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.en\Proof.msi
Command Line: ADDLOCAL=FindAllWordFormsFiles_1033,Gimme_OnDemandData,SpellingAndGrammarFiles_1033,ThesaurusFiles_1033,MsoInstalledPackagesScopedIntl_1033,HyphenationFiles_1033,OCR_1033,SetupControllerFiles,SetupXmlFiles REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.en-us ProductCode:{90140000-001F-0409-0000-0000000FF1CE}
05/09/2014 20:19:05 Rolling back package: Proof.fr-fr
Package Proof.fr-fr was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.fr-fr
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.fr\Proof.msi
Command Line: ADDLOCAL=MsoInstalledPackagesScopedIntl_1036,Gimme_OnDemandData,SpellingAndGrammarFiles_1036,SetupControllerFiles,FindAllWordFormsFiles_1036,TranslationFiles_1036,ThesaurusFiles_1036,HyphenationFiles_1036,SetupXmlFiles,OCR_1036 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.fr-fr ProductCode:{90140000-001F-040C-0000-0000000FF1CE}
05/09/2014 20:19:11 Rolling back package: Proof.es-es
Package Proof.es-es was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.es-es
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.es\Proof.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SpellingAndGrammarFiles_3082,OCR_3082,FindAllWordFormsFiles_3082,HyphenationFiles_3082,ThesaurusFiles_3082,MsoInstalledPackagesScopedIntl_3082,SetupControllerFiles,SetupXmlFiles,TranslationFiles_3082 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.es-es ProductCode:{90140000-001F-0C0A-0000-0000000FF1CE}
05/09/2014 20:19:12 Rolling back package: Office64MUISet.en-us
Package Office64MUISet.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64MUISet.en-us
File: C:\MSOCache\All Users\{90140000-0116-0409-1000-0000000FF1CE}-C\Office64MUISet.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64MUISet.en-us ProductCode:{90140000-0116-0409-1000-0000000FF1CE}
05/09/2014 20:19:19 Rolling back package: Office64MUI.en-us
Package Office64MUI.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64MUI.en-us
File: C:\MSOCache\All Users\{90140000-0116-0409-1000-0000000FF1CE}-C\Office64MUI.msi
Command Line: ADDLOCAL=OfficeExample64bitFilesBIntl_1033,OfficeExample64bitFilesAIntl_1033,Gimme_OnDemandData,Outlook64SearchShellRegIntl_1033,ProductFilesIntl64_1033,MsoInstalledPackagesScopedIntl_1033,OneNoteToLinkedNotesIEAddin64Intl_1033,GrooveFiles64Intl_1033,SetupControllerFiles,SetupXmlFiles REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64MUI.en-us ProductCode:{90140000-002A-0409-1000-0000000FF1CE}
05/09/2014 20:19:20 Rolling back package: OfficeMUISet.en-us
Package OfficeMUISet.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: OfficeMUISet.en-us
File: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\OfficeMUISet.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: OfficeMUISet.en-us ProductCode:{90140000-0115-0409-0000-0000000FF1CE}
05/09/2014 20:19:20 Rolling back package: OfficeMUI.en-us
Package OfficeMUI.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: OfficeMUI.en-us
File: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\OfficeMUI.msi
Command Line: ADDLOCAL=MetricConverterIntl_1033,AlwaysInstalledIntl_1033,MSTagPluginStockFilesIntl_1033,WebDiscussFilesIntl_1033,GraphicsFiltersPNGFilesIntl_1033,EquationEditorFilesIntl_1033,GraphicsFiltersEPSFilesIntl_1033,MSTagPluginNamesFilesIntl_1033,TCWP5FilesIntl_1033,CAGOffice10Intl_1033,OISFilesIntl_1033,WxpFilesIntl_1033,XDOCSEditorFilesIntl_1033,CAGFilesIntl_1033,WISPHiddenIntl_1033,CAGCat10Intl_1033,SetLanguageFilesIntl_1033,OSetupControllerIntl_1033,MsoInstalledPackagesScopedIntl_1033,TCRecoverFilesIntl_1033,SetupControllerFiles,ClviewFilesIntl_1033,GraphHelpFilesIntl_1033,ProductNonBootFilesIntl_1033,MSTagPluginPlacesFiles_1033,VisioPreviewerIntl_1033,ProductFilesIntl_1033,AceReplIntl_1033,GraphicsFiltersCGMFilesIntl_1033,GraphicsFiltersWPGFilesIntl_1033,Gimme_OnDemandData,TCWP6FilesIntl_1033,GraphicsFiltersGIFFilesIntl_1033,GRAPHFilesIntl_1033,MSTagPluginDateFilesIntl_1033,WebDriveFilesIntl_1033,LOBiFilesIntl_1033,LISTFilesIntl_1033,UICaptionsCompanionIntl_1033,SetupXmlFiles,AceFilesIntl_1033,TOOLSFilesIntl_1033,MSSOAP3Intl_1033,VBAHelpFilesIntl_1033,GraphicsFiltersPICTFilesIntl_1033,OfficeDigitalSFilesIntl_1033,VBAFilesIntl_1033,GraphicsFiltersJPEGFilesIntl_1033,QueryFilesIntl_1033,SetLanguageHelpFilesIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: OfficeMUI.en-us ProductCode:{90140000-006E-0409-0000-0000000FF1CE}
Error attaching to OSE, error 0x00000000
Stopping running ose
LIS: start uncaching for download "{90140000-002C-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-002C-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-003A-0000-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-003A-0000-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-00B4-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-00B4-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-0115-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-0115-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-0116-0409-1000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-0116-0409-1000-0000000FF1CE}-C"
Error attaching to OSE, error 0x00000000
Stopping running ose
SystemRestore : Attempting to cancelling System-Restore-Point for Product [Microsoft Project Standard 2010] (with RestorePointType [0, Installed]).
SystemRestore : Successfully cancelled System-Restore-Point for Product [Microsoft Project Standard 2010] (with RestorePointType [0, Installed]).
Not showing completion dialog because it was not requested.
Catalyst execution finished: 05/09/2014 20:19:25. Return code: 1603.
PERF: TickCount=722128 Name=RunSetup Description=End function
Can onyone enlighten me what's went wrong, and why did I get this inconsitent installation behaviour?
Thank you very much!!!1603 means there is a fatal error during installation process.
Take a look at the article below. It may help on finding cause.
Hi Juke,
I did do fair a bit of Googling before I started the post. I have increased the logging level on one of the machines failed on the installation. Apparently Project installation log doesn't throw the "return value 3", I think it's pointing to a particular
updating item, anyone knows what is it?
Microsoft Office Project Standard 2010 - Update '{35347883-0E64-45B4-88A0-1881DE05E259}' could not be installed.
The following is the detailed installation log.
MSI (s) (8C:B4) [20:31:33:122]: Executing op: SetTargetFolder()
MSI (s) (8C:B4) [20:31:33:122]: Executing op: FontRegister(Title=Arial Unicode MS (TrueType),File=ARIALUNI.TTF)
MSI (s) (8C:B4) [20:31:33:122]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\Fonts
MSI (s) (8C:B4) [20:31:33:122]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (8C:B4) [20:31:33:122]: Error in rollback skipped. Return: 5
MSI (s) (8C:B4) [20:31:33:746]: Entering MsiProvideAssembly. AssemblyName: Policy.12.0.Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:746]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:777]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:777]: Entering MsiProvideAssembly. AssemblyName: Policy.11.0.Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:777]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:808]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:808]: Entering MsiProvideAssembly. AssemblyName: Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:808]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:840]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:840]: Note: 1: 2318 2:
MSI (s) (8C:B4) [20:31:33:840]: No System Restore sequence number for this installation.
MSI (s) (8C:B4) [20:31:33:840]: Unlocking Server
MSI (s) (8C:B4) [20:31:33:980]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (8C:B4) [20:31:34:011]: Product: Microsoft Office Project Standard 2010 - Update '{35347883-0E64-45B4-88A0-1881DE05E259}' could not be installed. Error code 1603. Additional information is available in the log file C:\WINDOWS\TEMP\MSI1f79e.LOG.
MSI (s) (8C:B4) [20:31:34:011]: Windows Installer installed an update. Product Name: Microsoft Office Project Standard 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Update Name: {35347883-0E64-45B4-88A0-1881DE05E259}. Installation success or error status: 1603.
MSI (s) (8C:B4) [20:31:34:011]: Note: 1: 1708
MSI (s) (8C:B4) [20:31:34:011]: Product: Microsoft Office Project Standard 2010 -- Installation operation failed.
MSI (s) (8C:B4) [20:31:34:011]: Windows Installer installed the product. Product Name: Microsoft Office Project Standard 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202cf.msp
MSI (s) (8C:B4) [20:31:34:011]: Unable to delete the file. LastError = 32
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202d0.mst
MSI (s) (8C:B4) [20:31:34:011]: Unable to delete the file. LastError = 32
MSI (s) (8C:B4) [20:31:34:011]: Deferring clean up of packages/files, if any exist
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202cf.msp
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202d0.mst
MSI (s) (8C:B4) [20:31:34:011]: MainEngineThread is returning 1603
MSI (s) (8C:24) [20:31:34:011]: No System Restore sequence number for this installation.
MSI (s) (8C:24) [20:31:34:011]: User policy value 'DisableRollback' is 0
MSI (s) (8C:24) [20:31:34:011]: Machine policy value 'DisableRollback' is 0
MSI (s) (8C:24) [20:31:34:011]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (8C:24) [20:31:34:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:24) [20:31:34:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:24) [20:31:34:027]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (8C:24) [20:31:34:027]: Restoring environment variables
MSI (s) (8C:24) [20:31:34:027]: Destroying RemoteAPI object.
MSI (s) (8C:48) [20:31:34:027]: Custom Action Manager thread ending.
MSI (c) (F4:1C) [20:31:34:027]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F4:1C) [20:31:34:027]: MainEngineThread is returning 1603
=== Verbose logging stopped: 7/05/2014 20:31:34 === -
Excel file error after upgrade from 2010 to 2013
Hi there,
I did the upgrade from 2010 (Enterprise) to 2013. The excel files are not opening giving error.
ULS Log: "Unexpected error when trying to access service settings in the configuration database. Make sure the proxy for this service application is a member of the default proxy group for the active web application. Error = ExcelServerWebServiceApplication.Local:
Could not get the web application associated with this context. This indicates that the Excel Server service is not properly registered or provisioned.."
Question : Do I need to create New Excel Service Application separately on SharePoint 2013 Server?
I followed this link for upgrade
http://technet.microsoft.com/en-us/library/jj839719.aspx but it doesn't say anything for Excel SA.
Note: I have plan to configure separate Office APP Server to give user access the documents on iPad/iPhone. Should I need to do any configuration related to this error on Office App Server?
Please advice.
Thanks,
KhushiHi Khushi ,
Yes, you need to create New Excel Service Application separately on SharePoint 2013 Server. Due to only the following service applications have databases that can be upgraded when you upgrade from SharePoint
Server 2010 to SharePoint Server 2013:
Business Data Connectivity service application
Managed Metadata service application
PerformancePoint Services service application
Search service application
Secure Store Service application
User Profile service application
Attaching and upgrading these databases configures these service applications. Settings for other services will have to be reconfigured when you upgrade.
Reference:
Services upgrade overview for SharePoint Server 2013
For configuring Office Web Apps Server , you can refer to the blog:
http://stevegoodyear.wordpress.com/sharepoint-2013-build-guide/office-web-apps-2013-server-install-and-configuration/
Best Regards,
Eric
Eric Tao
TechNet Community Support -
Help! I started to upgrade to ios7 and it failed. Now I have nothing on my iphone 5. It wont even restore.
Same thing happened to me this evening!!! Now i have no phone and cannot figure out how to fix it
-
Mac Pro 2008 - upgrade to 2010 model or not?
I have a Mac Pro 2008 2.8 gHz with 12GB RAM. I'm not running Premiere Pro CS5 which is great and seems to love RAM and processor speed. I also recently got a CUDA card to take advantage of it's GPU acceleration.
My question is: Should I get a new Mac Pro 2010, 6, 8, 12 core or just upgrade my RAM to say, 24GB and perhaps get some SSDs (maybe even in a RAID 0) as my boot drive.
The RAM upgrade will be in the $650 range, SSDs could be at least that. I'll need RAM anyway for a new model as my old RAM isn't compatible.
Getting a new model could set me back $5000 (or more) when it's all loaded.
I'm also a little disappointed in the 2010 Mac Pros, for example my 2008 Mac pro was a no-brainer, but now I'm ambivalent about this upgrade to 2010, thinking there may be new models out this year that fill in all the holes. I kind of feel like the 2010 Mac Pro upgrade was a little like the Final Cut Pro 7 upgrade, it was a stop gap because Apple needed to do something. I could be wrong about this though.
I know this is kind of a difficult question to answer, but if you have any opinions, please feel free to lend any advice.PCIe 3.0
USB3
Intel SATA3 6G
Socket LGA1356
Socket LGA2011
3G SSD (by the time 4th Gen SSDs are out, one unit would make out our current SATA channel bandwidth)
Mid-range Xeon roadmap:
Socket LGA1356, a direct replacement for the current Socket LGA1366. The parts here are 6-core and 8-core Sandy Bridge single-socket and dual-socket capable but mid-range positioned Sandy Bridge Xeon - and, ultimately, Core i7 - parts with up to 20MB of L3 cache, three DDR3-1600 memory channels just like the existing LGA1366 Westmeres with one memory speed grade higher, and 24 PCIe v3 lanes on-chip.
The single external QPI v2 link runs at up to 8 gigatransfers/sec, or 32GB/sec bidirectional bandwidth, a 25 per cent speed up over the current generation, but also feeding a third more cores on each socket.
http://www.theinquirer.net/inquirer/feature/1811091/2011-intel-xeon-update-holy- socket-trinity
Intel is set to replace its current high-end socket, LGA1366, when it releases its new 8-cores processors in the Late 2011. This socket is expected to be released alongside Sandy Bridge-EX in Q3 2011, and will support 4 memory channels as well as 40× PCIe 3.0 lanes.
http://en.wikipedia.org/wiki/LGA_2011 -
Hi,
I have been working with Labwindows CVI 2009 with no problem but after upgrading to 2010 version I have the following problem:
When i´m going to execute the unistaller, either from Windows Control Panel or directly from the uninst.exe icon, it doesn´t work. The PC thinks a few seconds and does nothing, and it happens with all the applications I build with Labwindows CVi 2010.
Thanks,
Asier
Solved!
Go to Solution.Hello -
Are you installing these distributions on a non-English operating system? If so, the first thing to try would be the workaround listed on this known issue.
The known issue only lists Italian OSs as the troublesome OS, but it could actually happen on many different non-English OSs. I will update the text accordingly the next time I update the known issues list.
NickB
National Instruments
Maybe you are looking for
-
New mac pro with ATI video card & 2x 24" displays??
is it possible to connect two 24" apple displays to the new mac pro using the ATI video card?
-
My external hard drive suddenly not recognized (retina macbook pro)
Windows 8 has a great feature which is "windows to go", so I have installed windows 8 in my external hard drive. The problem just happened. I was using windows via my hard drive. I shut down the computer and turned on mac system. Then the hard drive
-
Connection MACBOOK PRO to Philips LCD: NO VIDEO SIGNAL
Hello all, I recently both a Philips LED TV, type: 40PFL8605H/12. I have a MACBOOK PRO from 2007. I would like to use this MACBOOK PRO as a media server on the TV. I have connected the MACBOOKPRO via DVI-VGA connector to the VGA input of the Philips
-
Using f:facet name="header" in h:panelGrid
I'm battling with it for a week now... I'm trying to create a table with 3 columns and to have header for each column. This, don't display headers at all : <h:panelGrid styleClass="Context" columns="3"> <h:panelGroup>
-
ITunes Screensaver Broken after iTunes 11 update
After upgrading, the iTunes screensaver now only displays the most recently downloaded artwork (currently 1 album, 3 podcast backgrounds). Anyone else experiencing this, or has in the past as it may just be coincidental with the update? And of course