BO XI 3.1 SP2 upgrade to SP3 Problem

Hi All,
I'm trying to upgrade our current BO XI 3.1 SP2 installation towards SP3.
The server it is running on has the following OS: Windows 2003 SP2 (32bit)
When performing the update, all goes well untill the point in the installation where it says "updating component registration"
immediatly when the installer enters this phase, I receive the following error:
Error 2908: Could not register component {73DDBFD1-3CEC-4DE2-AD1F-5D9354AE44D6}
Cancel - retry - ignore
When chosing ignore I receive a new error:
Error 1935: An error occured during the installation of assembly component {73DDBFD1-3CEC-4DE2-AD1F-5D9354AE44D6}
OK
When clicking OK, the installer rolls back and the update isn't performed.
note that when the installation is performed with the BO Admin user, I receive both error messages, when running the update with any other local admin user, only the second error (assembly component..) comes up.
Would anyone have an idea on how to solve this ?
Best Regards,
Tim Van Caeyzeele

Thanks for the info Jonathan, good to know where the log files are
I restarted the installation (with the same end result) and noticed that the log file is created once I click cancel to abort the installation.
The log file is 65MB big
After a huge search in the log file I found the latest entries before the rollback, actually the point where it fails:
MSI (s) (C0:30) [11:23:24:044]: Executing op: ComponentRegister(ComponentId={73DDBFD1-3CEC-4DE2-AD1F-5D9354AE44D6},KeyPath=<\CrystalDecisions.Enterprise.Shared,FileVersion="12.3.0.601",version="12.0.1100.0",culture="neutral",publicKeyToken="692FBEA5521E1304",State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
1: {EEC13875-F4CB-416F-ADC0-1EDA01A85632} 2: {73DDBFD1-3CEC-4DE2-AD1F-5D9354AE44D6} 3: <\CrystalDecisions.Enterprise.Shared,FileVersion="12.3.0.601",version="12.0.1100.0",culture="neutral",publicKeyToken="692FBEA5521E1304"
MSI (s) (C0:30) [11:23:24:044]: MSCOREE not loaded loading copy from system32
MSI (s) (C0:30) [11:23:24:262]: Note: 1: 1935 2: 3: 0x80131700 4: 5: CreateAssemblyNameObject 6: CrystalDecisions.Enterprise.Shared,FileVersion="12.3.0.601",version="12.0.1100.0",culture="neutral",publicKeyToken="692FBEA5521E1304"
MSI (s) (C0:30) [11:23:24:278]: Transforming table Error.
MSI (c) (DC:84) [11:23:24:278]: Transforming table Error.
Info 2867. The error dialog property is not set
MSI (c) (DC:84) [11:23:24:278]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Error 2908. Could not register component {73DDBFD1-3CEC-4DE2-AD1F-5D9354AE44D6}.
MSI (s) (C0:30) [11:37:59:019]: Transforming table Error.
MSI (s) (C0:30) [11:37:59:019]: Product: SAP BusinessObjects Enterprise XI 3.1 SP3 Update -- Error 2908. Could not register component {73DDBFD1-3CEC-4DE2-AD1F-5D9354AE44D6}.
MSI (s) (C0:30) [11:37:59:019]: Note: 1: 1935 2: 3: 0x80131700 4: 5: CreateAssemblyNameObject 6: CrystalDecisions.Enterprise.Shared,FileVersion="12.3.0.601",version="12.0.1100.0",culture="neutral",publicKeyToken="692FBEA5521E1304"
MSI (s) (C0:30) [11:37:59:035]: Transforming table Error.
MSI (c) (DC:84) [11:37:59:035]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Error 2908. Could not register component {73DDBFD1-3CEC-4DE2-AD1F-5D9354AE44D6}.
MSI (s) (C0:30) [11:37:59:597]: Transforming table Error.
MSI (s) (C0:30) [11:37:59:597]: Product: SAP BusinessObjects Enterprise XI 3.1 SP3 Update -- Error 2908. Could not register component {73DDBFD1-3CEC-4DE2-AD1F-5D9354AE44D6}.
MSI (s) (C0:30) [11:37:59:597]: Note: 1: 1935 2: 3: 0x80131700 4: 5: CreateAssemblyNameObject 6: CrystalDecisions.Enterprise.Shared,FileVersion="12.3.0.601",version="12.0.1100.0",culture="neutral",publicKeyToken="692FBEA5521E1304"
MSI (s) (C0:30) [11:37:59:597]: Transforming table Error.
MSI (c) (DC:84) [11:37:59:597]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Error 2908. Could not register component {73DDBFD1-3CEC-4DE2-AD1F-5D9354AE44D6}.
MSI (s) (C0:30) [11:38:00:175]: Transforming table Error.
MSI (s) (C0:30) [11:38:00:175]: Product: SAP BusinessObjects Enterprise XI 3.1 SP3 Update -- Error 2908. Could not register component {73DDBFD1-3CEC-4DE2-AD1F-5D9354AE44D6}.
MSI (s) (C0:30) [11:38:00:175]: Transforming table Error.
MSI (c) (DC:84) [11:38:00:175]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
Are you sure you want to cancel?
I notice that the keypath doesn't point to a location on the server, contrary to all other omponents that hold a keypath like:
MSI (s) (C0:30) [11:23:24:044]: Executing op: ComponentRegister(ComponentId={FD575BFC-FBD5-46A6-A54F-413053DBB91D},KeyPath=G:\BOXI31\common\4.0\managed\,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
1: {EEC13875-F4CB-416F-ADC0-1EDA01A85632} 2: {FD575BFC-FBD5-46A6-A54F-413053DBB91D} 3: G:\BOXI31\common\4.0\managed\
Edited by: Tim Van Caeyzeele on Jul 16, 2010 11:57 AM

Similar Messages

Before I upgrade to SP3 for Exchange 2010...

Hi All!
My company’s Exchange environment consists of the following:
AD Domain forest with one PDC in the main office, and 4 additional domain controllers at 4 remote offices
The forest and domain functional level is 2003
The PDC at the main office is running Server 2012 R2.
The domain controllers at the remote offices are running Server 2003 SP2 (upgrade to 2012 R2 is in the works)
Our Exchange server is in the main office. It is a simple Mailbox, Client, Hub, UM setup.
The Exchange version is 14.00.0722.000
Questions:
Version 14.00.0722.000 would be Exchange RTM, and as a result hasn’t been SP’d or RU’d since it was installed on our email server correct?
I would like to upgrade this Exchange server to the latest SP and RU. I understand that the updates are cumulative and that I should be able to install SP3 and RU8 without having
to install all of the previous versions. Is this a safe assumption?
What steps should I take before/after installing the SP and RU to ensure a "pleasant" and smooth experience for myself, my boss and my users?
Any and all comments are appreciated, thank you!

Hi ,
Please check this link.
http://pipe2text.com/?page_id=1761
Throughout up gradation process , you have to play with the below mentioned commands.
StartDagServerMaintenance.ps1
StopDagServerMaintenance.ps1
RedistributeActiveDatabases.ps1
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham

XP SP2 or XP SP3

I'm looking to buy a Nano 5th (current) generation, and saw on the Apple website that SP3 is required. I'm sure it used to read SP2..if I'm correct, maybe they changed it when MS announced no further support to SP2?
Anyway, my question is...will this 5th gen Nano work with XP Pro SP2 and the latest iTunes 9.2.1 version?
I ask because I don't want to 'upgrade' to SP3.
It's for my wife's PC laptop, not my 's

Go with SP3. Microsoft no longer supports SP2: http://support.microsoft.com/gp/windowsxpsp2
ThinkPad: T530 / X1 Gen 2 / Helix - Yoga: Tablet 2 Pro (Win) / Yoga 3 Pro
If you find a post helpful and it answers your question, please click the "Accept As Solution" button.
Lenovo Advocate ~ I am not employed by Lenovo or Microsoft. I am a volunteer.
Microsoft MVP - Consumer Security
SpywareHammer

Error while upgrading to SP3 from SP1 Exchange 2010

Here is the error I get when trying to upgrade to SP3, it fails when it gets to the mailbox role.
Summary: 8 item(s). 5 succeeded, 1 failed.
Elapsed time: 00:34:21
Language Files
Completed
Elapsed Time: 00:11:05
Restoring services
Completed
Elapsed Time: 00:00:02
Languages
Completed
Elapsed Time: 00:05:08
Hub Transport Role
Completed
Elapsed Time: 00:07:35
Client Access Role
Completed
Elapsed Time: 00:04:56
Mailbox Role
Failed
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: "Database is mandatory on UserMailbox. Property Name: Database".
Database is mandatory on UserMailbox. Property Name: Database
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
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: "Database is mandatory on UserMailbox. Property Name: Database".
Database is mandatory on UserMailbox. Property Name: Database
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
Elapsed Time: 00:05:32
Management Tools
Cancelled
Finalizing Setup
Cancelled

Hi,
Glad to know that we have solved the problem.
Thanks for your sharing.
Have a nice day : )
Thanks
Mavis
Mavis Huang
TechNet Community Support

PWA issues after Office 2010 SP2 upgrade

We recently upgraded some client machines that have Project 2010 Professional installed to Project SP2. Several of these users also use PWA.
After the upgrade, I heard from a few of these users that in PWA, the Workflow Approval buttons were unavailable, and that they were unable to export to Excel. I checked with another user who uses the same Project Server and did
not receive the update, and he had the same issue.
I did find kb2817580 that describes these exact issues, but the timing is suspicious with the client SP2 upgrade. Is there something in the Project 2010 SP2 update that would cause this problem on Project Server, or does Server need to be upgraded
concurrently with the client update? I was not under the impression that the local Project update would affect Project Server. Is that incorrect?

Cwoodin, in my experience, the client doesn't make any modifications at the server.
About the updates, i would recommend you to apply SP2 at the server as well. Besides that, take a look at the ULS logs to see if it spits any errors.
Regards

ES SP2 Upgrade Breaks XML in Submitted Forms

Hi
I've just installed the SP2 upgrade for LC ES - after 5 tries over 2 days...
Now it all *seems* to be working OK - checked version numbers etc - and I can access my processes and forms via Workspace.
However when I try to Submit any Form the server throws a - "com.adobe.idp.taskmanager.dsc.client.task.ActivePrincipalNotFoundException: Assignment to XPath was specified with the following expression: /process_data/formVariable/object/data/xdp/datasets/data/form1/workflowDetails/nextRecipi ent, but this expression did not evaluate to anything.
Looking further into this the Form's XML data is there when the form is initially rendered (the PrePopRender 'User Details' are showing correctly), but after the Form is submitted the XML data is not there - hence why my XPath Next User Selection fails.
I've tried setting the Next User Selection to a fixed User ID, but then the WorkFlowState variable setting fails in the Workflow - so the Form XML is definitely totally stuffed :-(
I've tried re-importing the formTemplate and re-setting the Form Data Schema etc - but nothing works.
Has anyone else had a similar issue with ES SP2 and if so got any suggestions for a fix ?
Thanks - Stuart

In the course of building a simplified process to send to otsupport I have discovered why SP2 breaks our process xml data mapping in our processes.
Most of our processes use 2 form variables (one to start the process then one, or more, dependent on the initial forms content) that run through the rest of the process - e.g. we use different templates in the process for different originator/request types etc, but capture the initial data from a number of single templates to simplify the 'user experience' and reduce number of front end form versions.
In this type of workflow the SP2 xml error issue is caused by the following -
In 8.0.1 (our current version) to copy the initial form variable data to the process form variable we have to copy across the 'form1' variable values to the 'data' node using the following -
/process_data/formVariable/object/data/xdp/datasets/data = /process_data/formVariable/object/data/xdp/datasets/data/form1
Although this is strictly wrong - if you assigned the ...data/form1 = ...data/form1 mapping then you got a 2nd form1 element nested in the 1st one in the 2nd form template xml data - so this did not work.
In SP2 you now have to correctly assign the form variables data as follows -
/process_data/formVariable/object/data/xdp/datasets/data/form1 = /process_data/formVariable/object/data/xdp/datasets/data/form1
So I guess you can say that SP2 has fixed a deficiency in 8.0.1 - but having wasted 4 solid days tracking this down I think it would be nice to have noted this 'change' somewhere in the SP2 installation notes :-(
If it is included in any of the SP2 documentation then please let me know so I can pass it on.

SP3 problems

Hi,
i have upgraded to SP3 and deployed my Portal application, which was developed in SP2. I now get the exception below. Surely SP3 is backwards compatible to apps developed in older versions ?
I have reinstalled SP2 and my app is still not working !!
Any ideas on how to solve this ?
Thanks
Mark
java.lang.NullPointerException
     at jsp_servlet.__error._jspService(error.jsp:15)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:446)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:208)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6356)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Portal gurus -
I have successfully migrated my app to SP3, but not moved it to production yet. We are yet trying to figure out what do we really gain by migrating our production app to SP3. Anyone? I am not sure we are seeing the 10% performance increase, or the http session size reduction (that BEA claims) - at least with our app - that might warrant an upgrade. Yes, the 10 or so patches that we have on top of SP2, are part of Sp3, but since we already have the patches - i am not sure we need to upgrade just for that.
My reason for posting all this - is can bea recommend why an upgrade is really required - except to get vendor support?
Thanks
Kunal

[SOLVED] Upgrade from SLES10 SP3 & OES2 SP2 to SP4/SP3 breaks NCS

Hi folks,
(This post was originally meant to be a rant and a request for help, but
while writing the final paragraph i found the solution. It's still a
rant, but i figured i'd post my solution here in case someone else runs
into the same issue.)
I've just spent several hours banging my head against a broken cluster
node. My system is a 32-bit SLES 10 VM running on VMware ESX 3.5.x.
I upgraded from SLES10 SP3 and OES2 SP2 to the next service packs for
each (using the move-to-oes-sp3 script in yast2 online_update).
Everything went well for the first few update/reboot sequences, then
after the final reboot on SLES10 SP4 & OES2 SP3, cluster services would
not load or join the cluster on restart.
I checked dmesg and found errors about "Loading module compiled for
kernel version 2.6.16.60-0.54.5-vmi" into a previous kernel version, so
i tried downgrading to that kernel version, only to find that it was
older than the one i had just upgraded from (it's the original SLES10
SP3 kernel). So i tried upgrading back to the same kernel which is
running on the other cluster node (2.6.16.60-0.77.1-vmi), but that did
not work any better.
<preaching>
I have to say that i'm not impressed that OES2 SP3 isn't even compiled
against the appropriate kernel, and because of SUSE's kernel RPM
overwrite policy there's no way i can select to boot from a previous
kernel to see if that fixes things. Note to SUSE and other distro
builders: if you're not doing kernel package upgrades like Red Hat or
Ubuntu (so that we can select to boot from the previous kernel from the
boot menu), you're doing it *WRONG*.
</preaching>
I then upgraded again to the latest recommended kernel for SLES10 SP4,
and still no joy. Dmesg shows this error before the rot starts:
allocation failed: out of vmalloc space - use vmalloc=<size> to increase
size.
When searching for this error i stumbled across
http://ubuntuforums.org/showthread.php?t=1613132
which pointed me to
http://www.mythtv.org/wiki/Common_Pr...lloc_too_small
Adding vmalloc=192M to /boot/grub/menu.lst and rebooting solved the
problem for me.
Regards,
Paul

Originally Posted by Paul Gear
On 13/10/11 07:36, magic31 wrote:
> ...
> Not sure if it's related to the issue you've hit, but along the lines
> of what Kevin already mentioned, there are issues that can arries when
> using the VMI kernel (that I've seen) if having multiple flavors of the
> kernel installed along with it (as in having both kernel-vmi as also
> kernel-smp packages installed) ...
> Curious, is that also the case with your setup?
The system in question has kernel-bigsmp and kernel-vmi installed. We
only ever boot from kernel-vmi.
> I've moved to only using the smp kernel on VMware (along with the
> clock=pit boot option to avoid time drift issues, or pmtr I think in
> your case when also running NCS services in the vm).
When we installed the system (on OES2 SP1, i believe) it was a while
ago, and kernel-vmi with clocksource=acpi_pm on the kernel command line
was the only solution we could find to get reliable time. If there are
updated best-practice documents, i'd be happy to hear about them.
However, this is a production cluster and my boss is (rightly) rather
reticent to make major changes.
Paul
the official Vmware paper on time is that IF you're using SLES 10.x 32-bit you will use VMI and NO kernel params (ie, get rid of the clockpit and clocksource=blah).
But if 64-bit then you're okay.
The easiest, IMO (especially with vmware) is to use the miggui (migration utility). That's how I'm converting all my 32-bit servers in vmware to 64-bit. Works quite well.
--Kevin

Upgrade to SP3 from sql server 2008 R2 SP2 and SharePoint server 2010 known issues

Hi Guys,
We are planning to upgrade SQL server to SP3 from 2008 R2 SP2 and would like to known if there are any known issues with SharePoint 2010 server and office web apps.
Though I was searching blogs and forums and could not find any noteworthy but wanted to look if any noted SharePoint issues after the upgrade.
VM

Hi Venu,
There should no issue for SharePoint 2010 with install SP3 for SQL2008R2 (also like comments mentioned in article below), I searched from internal and internet, there seems no document/article mentioned the known issue for SharePoint about this, you can
back up your environment and test the SP3 in a test environment before touching the production environment.
https://habaneroconsulting.com/insights/SharePoint-SQL-Server-Support-Matrix#.VSTY-nkfr4Y
http://blogs.msdn.com/b/glsmall/archive/2014/12/03/list-of-fixes-in-sql-server-2008-r2-sp3.aspx
Thanks
Daniel Yang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Exchange Server 2010 SP2-Upgrade

I am currently preparing my SBS 2011 for a migration to Server 2012 R2 with Exchange 2013 installed. On my SBS 2011 I ran the Best Practices Analyzer 1.3 and was informed to upgrade my Exchange 2010 to SP2.
When I run the update, it checks if all requirements are met. For both the Organisation and Mailboxrole it comes up with a "warning" that for my domain, the Recipient Update Service can't be found. It mentions that new and existent users might
not be properly Exchange activated. Nevertheless, I was able to upgrade Exchange without any errors.
Is this warning a problem?

OK - thanks for your reassurance.
I have re-run "Best Practices Analyzer 1.3" and it mentions that "the most recent Update Rollup is not installed". As a resolution is says run Windows update. When I do this, no further updates are found. In the Exchange Management Console
I see that I have Version 14.2 (Build 247.5) installed.
Any ideas?
P.S. I have just seen that there is an Exchange SP3 along with Update Rollup 9... should I update to this? How should I best do this - install 2010SP2RU8, then 2010SP3 and finally 2010SP3UR9?

Urgent: WLS 8.1 upgrade to SP3

Hi all,
I want to upgrate a productive WLS 8.1 (not SP2) cluster environment to SP 3. There is no chance to upgrade the system over a direct connection to the internet..
Where can I download the SP3 directly ? Any ideas, hints or links ?
Any help would be appreciated !
Thanks,
Mike

Please go to support.bea.com and download the appropriate upgrade installer for your OS. You need to be a registered user for this.
-Vishwas

App-V 4.5 SP1 - SP2 Upgrade Question

Hello,
I am taking over our App-V environment and trying to get us all up to date before beginning our 5.0 migrations (and trying to become familar with the products in general). All clients are currently on 4.6 SP3 (HF1 is out there but not sure it's needed
at this time) and sequencers on 4.6 SP2 (SP3 available but not sure if it's needed at this time) but our Management servers are still on 4.5 SP1. I want to update our Management servers to 4.5 SP2 (or SP2 HF2) ASAP but have a few questions. We
are load balanced behind an ACE (2 servers total) and we have a very large Citrix/VDI footprint. We are also heavily relying on Shared Cache.
1 - Do both servers need to have services stopped during the upgrade and can I upgrade 1 at a time while the second is still used for connections? Thinking of doing one server at a time and ensuring it works before upgrading the second, assuming they
can be different versions during the upgrade.
2 - Does traffic need to be stopped via the load balancer or stopping the services OK?
3 - What all on the DB needs to be updated? Any big issues with this part?
4 - Anything different need to be done since we are running with Shared Cache mostly?
I know we are on an older version so hoping I can get some assistance to get us on 5.0 ASAP. Just not sure with all of our moving parts (Load balanced behind an ACE, Citrix footprint, Shared Cache, etc) how tricky this will be so any suggestions
would be greatly appreciated.
Thank you!

Hi,
the challenging point could be the database. I don't know if 4.5 SP2 would introduce any modification to the database (and if so... how 'old' SP1 servers would deal with that), but in theory it could happen that you upgrade server 1 (that you removed from ACE
load balancing before), upgrade it and thus silently apply a change to the database.
If the still unpatched server2 connects to that DB there could be issues.
As in Shared Cache mode a connection to the App-V servers is essential you should test that process in a test lab. Create a backup of your database, and use that along with two App-V servers to practice the migration in the lab.
If you can't do that, find a maintenance window that is long enough run and roll back.
Falko
Twitter
@kirk_tn   |   Blog
kirxblog   |   Web
kirx.org   |   Fireside
appvbook.com

Exchange Server 2007 sp1 to sp2 upgrade error

Hello,
I am trying to upgrade exchange server 2007 to exchange server 2010 but my exchange server 2007 is running sp1 which cannot be directly upgraded to exchange 2010. To do this I need to first upgrade my exchange server 2007 sp1 to sp2, i am stuck because I
keep getting the error below:
Error:
The well-known object entry with GUID 6c01d2a7-f083-4503-8132-789eeb127b84 on the otherWellKnownObjects attribute on the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=mw refers to a non-USG CN=Exchange Servers,OU=Microsoft
Exchange Security Groups,DC=domain,DC=mw. Please either delete the well-known object entry or promote the target object to a universal security group.
Does anyone know how to resolve this error?? please assist

My recommendation to you is to upgrade it to Exchange 2007 SP3 with latest Rollup Updates.
Note: Before you start installing the SP3 make sure you upgrade the AD Schema for Exchange 2007 SP3.
For the error you are getting
https://social.technet.microsoft.com/Forums/exchange/en-US/a9d56cc7-dbf8-401c-b4ea-1bfd3c1f13fa/problems-installing-exchange-2007-sp1-ghost-guid?forum=exchangesvradminlegacy
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

OES11 SP2 -- Use SLES SP3?

The question is simple.
Part1
Should I also be upgrading to SLES SP3 when I do the upgrade to OES 11 SP2?
Due to version confusion -- the answers given in this forum are not always Crystal Clear.
Part 2:
Is this spelled out somewhere in the (thousands of pages) of the documentation that I missed somewhere? (Perhaps I am having a "senior moment" and just can't see the words in one of the manuals.
Thanks for any help.
Cheers!

On 09/01/2014 11:16 AM, davewr50 wrote:
>
> The question is simple.
>
> _PART1_[/B]
> SHOULD I ALSO BE UPGRADING TO SLES SP3 WHEN I DO THE UPGRADE TO OES 11
> SP2?
>
> DUE TO VERSION CONFUSION -- THE ANSWERS GIVEN IN THIS FORUM ARE NOT
> ALWAYS CRYSTAL CLEAR.
Yes; OES versions are, by default (with very, very few exceptions) linked
directly to SLES versions, with OES versions being one SP behind SLES SPs.
Thus, OES 11 SP2 is linked to SLES 11 SP3.
> [B]_PART_2:_
> Is this spelled out somewhere in the (thousands of pages) of the
> documentation that I missed somewhere? (Perhaps I am having a "senior
> moment" and just can't see the words in one of the manuals.
https://www.novell.com/documentation...a/btmu44d.html
Top of the page under Meeting All Server Software and Hardware Requirements:
Code:
Server Software
As part of the OES 11 SP2 installation, you install SUSE Linux Enterprise
Server 11 SP3.
IMPORTANT:OES 11 SP2 services were developed and tested on a default and
fully-patched SLES 11 SP3 server base.
As you install OES 11 SP2, do not change any of the SLES 11 SP3 Base
Technologies package selections, such as Java support. Doing so can cause
various problems, such as the installation failing or one or more OES 11
SP2 services not working properly.
If you are installing on an existing SLES 11 SP3 server, be sure to verify
that all of the default SLES 11 SP3 components are installed before
attempting to install OES 11 SP2 services.
I would not define missing this as a senior moment; powerful products come
with lots of docs, and knowing exactly where to find one specific piece of
information is not always clear.
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

Won't upgrade XP SP3

I don't use windows that often. I had loaded XP SP2 and after a few months, went to use the Windows side and Windows launched into a system check. After quite a while, it loads normally, but won't let me do any upgrades on the windows side (like to SP3). It gets about 3 minutes into it, then bails, reboots into the Mac side.

Well I was able to run the profile creator one time (firefox.exe -p) and I created a profile with it but still not able to start firefox. So I tried to start it again after rebooting. It starts a process which I can see in Task Manager but now I don't get either the Profile Manager dialog box or FF.
I also tried to start the profile manager with this command: "C:\Program Files\Mozilla Firefox\firefox.exe" -p.
I terminated the firefox process and tried again but get the same results.
BTW, this command: %APPDATA%\MOZILLA\FIREFOX\PROFILES shows a profile called m6woxz30.default, which is not the name I choice for my profile the one time I got the Profile Manager to run.
BTW, thanks for your help and ideas.

BO XI 3.1 SP2 upgrade to SP3 Problem

Similar Messages

Maybe you are looking for