Upgrade BO X1 R2 SP1 to SP5/SP6

Hi,
We are working on a migration project where we are upgrading the Oracle Database version from Oracle 10.2.0.4 to Oracle 11g.
BO is used as a reporting tool in teh application and we need to upgrade teh service pack from BO X1 R2 SP1 to SP5/SP6.
Can anybody please help with the steps to carry out the upgradation

Hello,
you are using a BO Version which is out of Support. Maybe you should consider a Migration to the latest Version which is SAP BI 4.1.
The BO XI Rel.2 Downloads have already been moved to the archieve and you should check if you have access to it.
If you are on BO XI Rel.2 SP1 you first have to move to BO XI Rel.2 SP4. Afterwards to BO XI Rel.2 SP6 and at last a would recommend you move to BO XI Rel.2 SP6 Fix Pack 4 which is the very "latest" release.
Try to find the Installation packages. These are (For Windows):
ENTERPRISEA04P_0-20008636.EXE
ENTERPRISEA06P_0-20008636.EXE
ENTERPRISEA06P_4-20008636.EXE
But i would highly recommend you contact your SAP Sales Rep. and talk about a Migration to SAP BI 4.1.
Regards
-Seb.

Similar Messages

Upgrading from WL Server 7 SP1 to SP5

I don't see this discussed anywhere in the documentation, but I need to upgrade from Server 7 SP1 to SP5, and wondered what is the best way to do this? Uninstall SP1 first, or can I just install SP5?
Thx!

UPDATE:
In the WebLogic Server 7.0 Installation Guide, Chapter 6, I found the following:
It says I can "...download the service pack installer where" ... "the name of the upgrade installation program ... is ...for example, serverXXX_upgrade_solaris.bin”.
However, on the download site, the only thing available for my server is "server705_win32.exe" (which is an INSTALL file, NOT an upgrade file!).
For the heck of it, I tried running that install executable, but was told "The version of this installer (7.0.5.0) is not compatible with the version of the software installed on your system (7.0.1.0). Please upgrade using SmartUpdate or an upgrade installer".
Where do I find the "upgrade installer"?
How do I get help from BEA? I can't find an e-mail address or phone# for support? DO I have to pay to talk to a real person there?

Proxy upgrade from SP1 to SP5 doesn't work anymore for virus scanning.

Upgraded from SP1 to SP5 and the virus scanning updates no longer work. No changes have been made it is a complete carbon copy using the migrate button. No ip addresses have been altered nor has the ports been changed. I've tried SP2, 3 & 4 and they too fail with a 504 error log. I turned SP1 back on and it works first time.
If you can solve this I'll be so impressed because its driving me crazy. I've checked all config files and everything is as it should be.

Hi
This thread was interesting as I have many customer sites using virus scanning without any problems together with this proxy.. Some sites are really huge as well.
Can the author of this thread explain how the scanning that now refuse to work is done with the proxyserver... Through an API or as forwarded requests to another scanning proxy (trend micro etc.) or what ? Maybe this is done in some way I am not aware of. Then I am really interested in your problem.
We mostly use it "user->proxy->vscanner->site" where the proxy and the scanner often run at the same host. This in huge installations together with load balancers infront and behind.
/Per-Olov

Upgrading the current EP 5.0 SP5 version to EP 6.0

Hi,
We currently have our production portal running with the following configuration.
1) SAP Enterprise Portal 5.0 SP 5
2) Oracle DB 8.1.7
3) SAP J2EE engine 6.20.
we are using 2 servers: one is the EP 5.0 Portal server with SAP J2EE 6.20, and the other is Oracle DB with LDAP server
We want to upgrade the current EP 5.0 SP5 version to EP 6.0. Could you furnish the details for the upgrade and migration with regards to which version to use in EP, the DB version and other softwares required. Also the Hardware required and configuration setup information issues.
Awaiting a response
Regards
Rohan

Hi john,
Well could u tell me the approx time estimate(in weeks or months would be helpful)that is required to do the following:
1)Upgrade EP5.0 sp5 to EP5.0 SP6
2)Apply the Hotfix and patch 1 to make it ready for upgrade to Netweaver '04 Stack 14
4)Install and configure Netweaver '04 Stack 14
3)Complete the migration from EP5.0 SP6 to the new portal using SAP migration tools
The above, is the procedure given in the upgrade guide.
And it tells it is a lengthy time consuming task.
I need to estimate the -TIME FACTOR-(in weeks or months) taken to accomplish the task using 2 consultants, as it is to be used for proposing the upgrade project to my client.
Awaiting a response
thanks and regards
Rohan

Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
I have to remove the management installation first. And that's not gonna happen.
I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
Control Panel. And this can NOT be the most healthy way of getting through the setup.
I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
Any of you have tips as to how I can get rid of the agents more gracefully?

Hi
Thanks for the replay guys!
None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
days.
Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

Upgrade From Exchange 2010 SP1 to SP3 - Schema Upgrade Question

Hello,
We're currently running Exchange 2010 SP1 in our environment and want to upgrade to SP3. I just had a couple of questions related to preparing AD for this new SP that I was hoping that someone could answer.
Setup
We have a single forest with two domains within it (A and B for example). The schema master is in Domain A but this domain doesn't contain any Exchange 2010 servers. Domain B contains our 2010 CAS and Mailbox servers.
Both domains have Windows 2003 SP2 domain controllers.
I understand that before I proceed with the upgrade to SP3, I first need to update the AD schema on our schema master. I was planning on doing the following :
Log onto an existing Windows 2008 R2 64 bit "member" server in domain A (containing the schema master) with an account which is a member of the Schema Admins and Enterprise Admins groups.
Run SETUP.EXE /PrepareAD.
Do I need to also run SETUP.EXE /PrepareDomain on domain A as well or does the /PrepareAD sort this out ?
I was then going to turn my attention to domain B (which contains the 2010 CAS and Mailbox servers) and do the following :
Log onto an existing Windows 2008 R2 64 bit 2010 Mailbox server with an account which is a member of the Domain Admins and Enterprise Admins groups.
Run SETUP.EXE /PrepareDomain
Is this the correct procedure to follow ? I assume that I can then go ahead and start to upgrade the Exchange 2010 SP1 servers in the following sequence :
CAS\HUB Server(s)
Mailbox Server(s).
Clarification on the AD upgrade steps would be appreciated.
Thanks
Mark

This has all the info you need:
http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx
Prepare Active Directory and Domains
and
http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx
Upgrade Exchange 2010 to Exchange 2010 SP1, Exchange 2010 SP2, or Exchange 2010 SP3
Note: There is no harm in simply running setup/PrepareAllDomains.
You should break out each Prep step since you have multiple domains:
setup/PrepareSchema
setup /PrepareAD
setup /PrepareAllDomains
you can run all of these from the same DC you run the setup/PrepareSchema step!
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

WLS 6.1 SP4- SP5/SP6

Good morning,
I tried re-running weblogic.ejbc on my ejb-jar files and it failed with the same
error. I am using Javlin for a transactional cache with WebLogic and I don't think
it knows anything about the getLoadUser and setLoadUser methods. I had the same
problem when I went to WS 6.1 SP4 with the methods __WL_needsRemove and __WL_setNeedsRemove
but I was able to implement those inside my bean code and everything worked. I
figured I could just implement the __WL_getLoadUser and __WL_setLoadUser and I
would be okay. I implemented them with an empty setLoadUser and tried various
returns for getLoadUser. After implementing them, I am able to access from the
database with no problem, but when I try to create beans, the program throws a
NullPointerException. I have not seen any information on what these two methods
are supposed to do but it seems they first show up in SP5.
Thanks,
Dan
Rob Woollen <[email protected]> wrote:
Does re-running weblogic.ejbc on your ejb-jar fix the problem?
-- Rob
Dan Shelton wrote:
Hello All,
I am trying to deploy some EJBs from a system with WS 6.1 SP4 ontoa system with
SP5/SP6 and get an error stating that the bean has to be declared abstractbecause
the methods __WL_getLoadUser() and __WL_setLoadUser(..) are not implemented.These
two methods are listed in the WLEnterpriseBean interface in weblogic.ejb20.interfaces
for SP5/SP6 but not in SP4. Anybody know what these methods are supposedto do?
I have found no information at all on these. I have a case in but figuredsomeone
might already know.
Have a good one,
Dan

Keith,
This message gives you exact reason. Double-check classpaths
used the start weblogic and to run ejbc. There may be something
left from previous installations.
Regards,
Slava Imeshev
"Keith" <[email protected]> wrote in message news:3fb0337c$[email protected]..
>
Hi,
We run version WLS 6.1 SP4 (I never noticed this when we were using
WLS 6.1) on each of development, system test, and production machines.
When I compile and deploy my web app to our devlopment machine
everything is fine. It is always compiled on our devlopment machine.
However when I deploy the same web app to our system test machine it
gives the following error:
####<Nov 7, 2003 9:49:05 AM EST> <Warning> <EJB> <blah.com.au>
<myserver> <main> <system> <> <010004
<The EJB deployment named: blah_blah was compiled by a different version ofthe WebLogic Server.>
This has always happened on our development machine but not on our
production machine, so it has never really been a problem because it
just recompiles it and everything is fine.
But now I have added some EJBs to the web app and now when I
recompiles it at startup it never compiles the new EJBs, and thus
never deployes them.
I have check the following on each machine to compare WLS versions.
wlgenerated file in the app jar file
java weblogic.ejbc -version
java weblogic.version
and java -version
They all report to be the exactly the same version.
Are there any suggestions to stop the WLS recompiling my app or to
make it compile my new EJBs when the server starts up.
Any suggestions would be very much appricited.
Cheers
Keith

Upgrading WLS 8.1 SP2 to SP5: does SSL setup need to be re-done?

All,
Our production application has been built using Workshop 8.1 SP2, and is deployed on a WLS 8.1 SP2. We are now wanting to upgrade to SP5, and so I used the "Smart Update" utility to upgrade my local instance to SP5. Our application is accessed over SSL, so I was wondering if the whole SSL-setup that was done when we setup our production SP2 environment a year ago needs to be re-done? Our application has a web module, two java projects, uses SSL-based web-services and has a custom Oracle JAAS login module. I already found out that there is a particular setting on the domain that has changed between SP2 and SP5 that allows anonymous lookup of MBeans(Anonymous Admin Lookup Enabled). Are there any other such settings/considerations i need to be aware of in moving from SP2 to SP5?
All help is appreciated..it will help me decide on moving to SP5.
Thanks in advance!
Vik.

Hi Vik
When you use smartupdate to upgrade from sp2 to sp5, it will upgrade only the weblogic workshop instance and not the domains.
Either you will have to upgrade the existing sp2 domain to sp5 or create a new sp5 domain and configure it just like sp2.
After the upgrade open the config.xml under the new domain and check the SSL config under the server just to make sure.As far as the SSL config is concerned it did not change from sp2 to sp5.
More information on this is available at
http://e-docs.bea.com/platform/docs81/upgrade/faq.html
Thanks
Vimala

Upgrading to Exchange 2010 SP1

When I'm upgrading Exchange 2010 to SP1, I get to tthe Hub Transport Role and it errors out with the following messsage:
Summary: 8 item(s). 3 succeeded, 1 failed.
Elapsed time: 00:08:15
Language Files
Completed
Elapsed Time: 00:04:40
Restoring services
Completed
Elapsed Time: 00:00:01
Languages
Completed
Elapsed Time: 00:02:59
Hub Transport Role
Failed
Error:
The following error was generated when "$error.Clear();
          if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
            Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
        " was run: "There should only be a single RMS Shared Identity user. Found CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,CN=Users,DC=corporate,DC=internal and CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,OU=migrate,DC=corporate,DC=internal.".
There should only be a single RMS Shared Identity user. Found CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,CN=Users,DC=corporate,DC=internal and CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,OU=migrate,DC=corporate,DC=internal.
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.Ex88D115&l=0&cl=cp
Elapsed Time: 00:00:34
Client Access Role
Cancelled
Mailbox Role
Cancelled
Management Tools
Cancelled
Finalizing Setup
Cancelled
I haven't been able to find anything on the web regarding this error, so any help would be appreciated. We used to ADMT to migrate users into a new domain, but what it looks like to me (and I'm sure I'm wrong) is that the same user is set up in migrate
OUT as the regular Users Container.
What am I missing???
Thanks in advance.
Jeff

Hi,
Please try to use ADSIedit to check if you have two federated email account. You may need to delete the double one.
Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:
Click Start, click Run, type adsiedit.msc, and then click
OK.
Locate the Default Naming Context node, and then locate to the
CN=Users container.
Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click
Delete.
If that is not help, then I recommend y ou to remove all those two federatedemail account and then create a new one.
Rerun the Exchange Server 2010 Mailbox role setup application.
Create a new federated e-mail account by using the following command:
New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
Regards,
Xiu

Upgrading from SCOM 2012 SP1 to SCOM 2012 R2 what CU do i install? CU5?

Hi,
I just upgraded from SCOM 2012 SP1 to SCOM 2012 R2. What CU version should I install? CU5?
Thanks
K

The most current CU version os SCOM 2012R2 is CU4
You can download it from
https://support.microsoft.com/kb/2906925?wa=wsignin1.0
For detail description of SCOM 2012 R2 CU4, you may refer to
http://support.microsoft.com/kb/2992020
and
http://syscentercldman.blogspot.hk/2014/12/update-of-scom-2012-r2-ur4.html
Roger

Upgrade for SBO 2005A SP1 PL 43 to SBO 2007A.

Hi All
I would like some assistance with the procedure to upgrade from SBO 2005A SP1 to SBO 2007A.
Which patch level must I use or I can just go straight to 2007A SP1 patch level 5 from SBO 2005 SP1 PL43?
Thanks
Bongani Dlamini

You may check this thread to get more info regarding the upgrade:
Upgrade to 2007A SP01 PL05 HF2
Actually this question belongs to System Administration forum. Please post the similar question there and close this one.
Thanks,
Gordon

Novell GINA removed after R2 upgrade to ConfigMgr 2012 SP1 client

I am working with a customer and we just noticed an issue when upgrading some of their SCCM 2012 SP1 clients to R2. After the upgrade, everything appears to work fine, but as soon as a restart happens, the Novell GINA is replaced by the Windows GINA.
These machines were running Windows XP SP3 with Novell Client 4.91 SP5. This did not occur when installing the ConfigMgr 2012 SP1 client originally, but appears to happen every time when the ConfigMgr client is upgraded to R2. I wouldn't have
thought the ConfigMgr 2012 R2 client upgrade would have anything to do with the GINA, but we can replicate the issue.
It's not due to Windows Updates getting installed in the background while the client is temporarily unmanaged, which was my initial thought. We ensured the policy to disable Windows Updates was correctly in place and that no updates were installed.
The only fix so far is to completely remove the Novell client and reinstall it.
Has anyone else run in to this?
Thanks!

Yes, I have seen this when we took over a group that had Novell. It was ConfigMgr 2007 at the time. We only had to keep Novell long enough to completely remove it later. So your process is correct.
http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path

Hi everybody,
I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
<04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
<04-25-2014 02:06:47> ********************************************
<04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
minimum supported installed build version is [7804].
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Unsupported upgrade path;    Error;
Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
<04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Active Replica MP;    Passed
<04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Parent site replication status;    Passed
<04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
=====
<04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;
SQL Server sysadmin rights;    Passed
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;    SQL Server sysadmin rights
for reference site;    Passed
<04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Site server computer account administrative rights;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server security mode;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
<04-25-2014 02:07:09> INFO: Target computer is a Windows server.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Unsupported site server operating system version for Setup;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Domain membership;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Pending system restart;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server version;    Passed
<04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Edition;    Passed
<04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
Instance:.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Tcp Port;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
<04-25-2014 02:07:09> INFO: SQL Server memory is limited.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Configuration for SQL Server memory usage;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
<04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
Server to reserve a minimum of 8 gigabytes (GB) of memory.
<04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;    SQL Server process memory allocation;
Warning;    Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
http://go.microsoft.com/fwlink/p/?LinkId=233759.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Case-insensitive collation on SQL Server;    Passed
<04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFO: getaddrinfo returned success.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Validate FQDN of SQL Server Computer;    Passed
<04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
<04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Primary FQDN;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
=====
<04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
<04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Failover Cluster;    Passed
<04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Deployment Tools installed;    Passed
<04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;    Windows Preinstallation Environment
installed;    Passed
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
SMS Provider machine has same domain as site server;    Passed
<04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:10> ***************************************************
<04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
<04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
Prerequisite checking result into the registry
<04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
<04-25-2014 02:07:10> INFO: Setting registry values
If you wonder whether it might be related to this error:
-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
I've already tried the
Preinst /DELSITE XXX command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
Finally, the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
the impression that it's being cached somehow.
Any help would be highly appreciated,
Thank you.
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Hello again everybody,
I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
primary sites.
If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
DELETE
FROMServerDataWHERESiteCode='XXX'
DELETE
FROMSC_SiteDefinitionWHERESiteCode='XXX'
And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
Thank you all anyways for your answers and comments,
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

SharePoint Server 2013 Upgrade failure after Updating SP1 + Nov10 CU " Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown"

After Successfully having SharePoint Server 2013 Farm Installation on 2 Servers AD + Central Admin Application server, OS: win server 2008 R2 Ent SP1.
I set up the configuration for SharePoint app and Workflow Manager to work properly on the Den environment, the time for SP1 running has come and after downloading the Service pack 1 of SharePoint server 2013 and completing the wizard, I run the SharePoint
2013 Configuration Wizard after installing SharePoint 2013 SP1, and the wizard failed on step 2 with the Error from the Log file as showing below,
"Task upgradebootstrap has failed with an unknown exception
01/04/2015 00:43:30 11 ERR Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown.
at Microsoft.SharePoint.Upgrade.SPManager.BootStrap(Guid sessionId, SPUpgradeOperationFlags flags)
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()"
Also I was not able to create websites like before, and the creating of new site is failed with error message :
"Failed to call GetTypes on assembly Microsoft.Office.TranslationServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Method not found: 'Microsoft.Office.Web.Common.ProcessImageInfo"
Is there any solution to my problem with SP1 of SharePoint Server 2013, I don't think that SP1 should generate such bugs in a stable environment.
Basel Badr ,SharePoint Specialist ,MCAD ,MCTS.

Hi Basel,
What edition of SharePoint do you have and what patch did you attempt to install?
If you are on SharePoint 2013 Enterprise, please make sure you are installing Service Pack 1 for SharePoint Server:
http://www.microsoft.com/en-us/download/details.aspx?id=42544
If you are on SharePoint 2013 Foundation, please make sure you are installing Service Pack 1 for SharePoint Foundation :
http://www.microsoft.com/en-us/download/details.aspx?id=42548
For more information, you can refer to the thread:
https://social.technet.microsoft.com/Forums/sqlserver/en-US/ba9656e9-837e-4261-b164-b5bdfe8adce3/why-does-machine-translation-fail-when-i-do-not-use-it?forum=sharepointgeneral
http://sharepoint.stackexchange.com/questions/84284/failed-to-call-gettypes-on-assembly-microsoft-office-translationservices
Best Regards,
Eric
Eric Tao
TechNet Community Support

Problems after upgrade from SCVMM 2012 Sp1 to SCVMM 2012 R2

I did a in-place (uninstall VMM2012 Sp1, retain the database, and install VMM2012 R2 point to old database) upgrade. All the steps work fine.
The only problem (so far) is that when I create a new VM using a custom template (for example, Windows 2008 R2), the deploy fail with the following error:
Error (2912)
An internal error has occurred trying to contact the vm-scvmm2012.domain.com server: NO_PARAM: NO_PARAM.
WinRM: URL: [http://vm-scvmm2012.domain.com:5985], Verb: [INVOKE], Method: [GetError], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/bits/BitsClientJob?JobId={56B8E488-5DB9-4CC1-BEFA-AFF76E1E4D2D}]
Unknown error (0x80072f0d)
Recommended Action
Check that WS-Management service is installed and running on server vm-scvmm2012.domain.com. For more information use the command "winrm helpmsg hresult". If vm-scvmm2012.domain.com is a host/library/update server or a PXE server role then ensure
that VMM agent is installed and running. Refer to http://support.microsoft.com/kb/2742275 for more details.
Information (26278)
VMM could not offload transfer the file \\vm-scvmm2012.domain.com\MSSCVMMLibrary\VHDs\Template_Windows_2008_R2_SP1.vhdx to C:\ClusterStorage\Volume1\VM-NEWVM\Template_Windows_2008_R2_SP1.vhdx.
Any ideas?

I have a similar problem when migrating VMs from Windows 2008 R2 (Non Clustered) Hyper-V to Windows 2012 Hyper Cluster. I had previously migrated about 100 VMs like this with no problem. It appears since upgrading from VMM SP1 Rollup 4 to Rollup 5 this problem
is happening. All Agents are up to date.
I can migrate VMs in the cluster no problem.
I removed the Windows 2008 R2 Hyper-V host and added it back which allowed the job to at least start but when it gets to the final steps of importing the VM it fails with the same error and references the VMM server.
Others suggest this is a VMM Certificate problem and you can remove the Cluster node and add it back again but I can't do that in a production Cluster with hundreds of VMs. That is not an acceptable solution.
How can we fix this?

Upgrade BO X1 R2 SP1 to SP5/SP6

Similar Messages

Maybe you are looking for