Sp4 Upgrade

All -
I just upgraded my app from SP2 to Sp4. Now I see the following error -
(all my portlets in sp2 used a patch from bea for the refreshAction).
<html><head><title>Page Flow Error - No Relevant Page</title></head>
<body>
<table border="1" cellspacing="0">
<tr><td><b>Page Flow:</b></td><td>/Controller.jpf</td></tr>
<tr><td><b>Action:</b></td><td>portalRefresh</td></tr>
</table>
<h1>Page Flow Error - No Relevant Page</h1>
<span style="color:red">You have tried to return to a recent page in the current page flow through return-to="currentPage", but there is no appropriate page.</span>
</body></html>

Here goes..
* This method represents the point of entry into the pageflow
* @jpf:action
* @jpf:forward name="begin" path="salesadmin.jsp"
* @jpf:forward name="searchDealnAlerts" path="getDealAlertResults.do"
* @jpf:forward name="searchOfferAlerts" path="getDealAlertResults.do"
protected Forward begin(final SalesAdminForm form) {
Note - this is working fine in SP2 with the refreshAction patch. Not working in SP3 or 4.
Thanks for your help....

Similar Messages

Order of steps in CRM Mobile Sales 7.0 SP4 Upgrade

Hi,
Since I read the upgrade guide I am not really sure anymore about the right order of step when performing the upgrade (form 4.0 SP6 to 7.0 SP4):
(OS and Office version are up to the prerequesites)
0. Back up all ARS databases (dev, test, production)
1. Run Baseline Comparison tool: Is that recommended to do?
2. Upgrade SQL Server form 2000 to 2005 SP1 or SP2 with attach, detach and run the SQL script provided by SAP
2a. Install .net 2.0, Java VM 1.5.0_16 and Java Dev Kit (MAR and WB are on the same machine)
2b. Install Visual Studio (VBasic) 2005 SP00
3. Run Code Migration (only on DEV, it will create a change list which can be transported to the other systems, correct?)
4. Run MAR Upgrade tool
5. Upgrade MRS tools and services
The points I am really unsure is, when to upgrade SQL Server from 2000 to 2005 and when to install Visual Studio.
Could someone please feedback if all the steps are in the right order?
Whity

Hi everybody confronted with 4.0 to 7.0 SP4 upgrade of MSA,
I have done sich upgrade and here is the list of steps and the order of them:
Pre-upgrade: (check the current system works fine):
1. Confirm the SAP services (MAR Central, TA) are working fine
2. Confirm the Transport Process among DEV, QA and PRD is also working fine
3. Full generation of all apps
Pre-upgrade:
4. Baseline comparison in order to ensure all repos are in synch
5. Backup ars_db and ides
Upgrade steps:
6. Check software versions
7. Install Visual Studio 2005 SP00
8. Stop TA but not MAR Central Service
9. Install and run CMT (it will display thousands of collisions, we had 11270 but most of them were solved by the system, finally we had 67 collisisons to resolve manually)
10. Start TA and release CMT changelist and transport to CRM Server
11. Backup ars_db
12. CMT deinstallation
13. SQL Server upgrade from 2000 to 2005
14. Stop and uninstall TA. If TA is not being uninstalled there will be problems to uninstall but it can still be done via DOS command
15. Upgrade the MAR
16: Unistall the MAR upgrade tool
17. Install Java VM and SDK
18. Upgrade MDW (run on upgrade CD)
19. Resolve collisions (document the work!)
20. After CRM Online was upgraded do a BDoc synch (until this step, MAR, MDW upgrade run independently)
21. Generate Metadata and table scripts on Ides in ClientConsole
22. Do a full non incremental generation
23. Run the application (MSA, MSC, etc.)
Possible issues:
1. I had many errors during compilation (not generation, that worked fine). Some of the errors were resolved by ensuring that all objects were generated. This did not happen at the first generation. Other errors came from collision resolution. This is a bit more tricky but keep in mind NO MAJOR CODE CHANGE was required to resolve them. Probably date conversion issues will pop up which can be resolved by "fromadate" / "toadate"...
2. I had issues with the backed up Ides. Finally I had to restore an empty 7.0 standard SAP Ides and ran the Metadata and table scripts on this Ides. Then I connected and did an extract. This worked fine.
This is it in a nutshell. I hope it will help anybody with an upgrade!
Regards
Whity

Business Objects XI 3.1 SP4 UPgrade

Hi
I have couple of questions regarding the XI 3.1 SP4 Upgrade. We are currently on XI 3.1SP3 and we also have Live Office XI 3.1 SP3. We inten to upgrade to SP4.
1) Is there any Live office xi 3.1 sp4 upgrade available?
a) if Yes then where can I find it?
b) If No will the Live Office SP3 work with BOXI R3.1 SP4?
2) Where can I find the documentation for the list of issues fixed in the release SP4 for Business Objects XI R3.1?
Or if anyone is able to provide me with the list of fixed issues in SP4 , I would really appreciate it!
Thanks!
Samir

Step By Step
Login SID: https://websmp201.sap-ag.de/swdc
1-) Software Downloads
2-) Support Packages and Patches
3-) A - Z Index ( E Click)
4-) SBOP BI platform (former SBOP Enterprise)
5-) BOBJ ENTERPRISE XI 3.1
6-) Comprised Software Component Versions
7-) BOBJ LIVE OFFICE XI 3.1
8-) Windows Server on IA32 32bit
9-) Download
10-) BOBJLIVEOFFICE04_0-10007620.EXE
But In more simple;
Login SID: https://websmp201.sap-ag.de/swdc
1-) Software Downloads
2-) Search for Software Downloads
3-) searc term is : "SAP BusinessObjects LiveOffice XI 3.1 ServicePack 4 " result is download.

MDM SP4 Upgrade

Hi
we have migrated our MDM 5.5 from SP3 to SP4. Aftert this upgrade we have checked the syndication mappings for a copy of vendor repository and we have found out that in our syndication mappings, those mappings against qualified tables have dissapeared. It seems that for example all values for mapping Company code qualified table as can be BUKRS are not there, only LIFNR remains. We don´know if some of you have had this issue or not but we´ll appreciate much if there is somebody that have solved this issue anyway ( not remapping again obviously...)
Cheers

Hi Antonio,
we noticed this as well. What you could do if you you have not enhanced the repository: download the latest Vendor repository package from SMP. Use the maps delivered with this repository. You can simply import them to syndicator.
Kind regards
Michael

SP4 Upgrade problem

Hi Guys,
I have upgraded from SP3 to SP4. I use documentum 5.3 as CMS. I get this error when I try to see my portal home page.
SEVERE 7/19/05 10:43:44 AM findIDs: Throwing exception: com.bea.content.RepositoryException: Error executing sear
ch: Search[max=-41,sort="toProperty('sort_order') ASC",expr="(toProperty('approved_sites') == 'Intranet' && toProperty('r_object_type') == 'cpi_bulletin' &&
toProperty('content_type') == 'Hot_Announcement' && ((toProperty('locations') == null || toProperty('locations') == 'Alpharetta') && (toProperty('category')
== null || toProperty('category') != 'Manager')))"]
com.bea.content.RepositoryException: Error executing search: Search[max=-41,sort="toProperty('sort_order') ASC",expr="(toProperty('approved_sites') == 'Intra
net' && toProperty('r_object_type') == 'cpi_bulletin' && toProperty('content_type') == 'Hot_Announcement' && ((toProperty('locations') == null || toProperty(
'locations') == 'Alpharetta') && (toProperty('category') == null || toProperty('category') != 'Manager')))"]
at com.bea.content.repo.internal.RepoSearchOpsBean.search(RepoSearchOpsBean.java:175)
at com.bea.content.repo.internal.RepoSearchOpsEJB_c3xlib_ELOImpl.search(RepoSearchOpsEJB_c3xlib_ELOImpl.java:46)
at com.bea.content.spi.internal.SearchOpsImpl.search(SearchOpsImpl.java:84)
at com.bea.content.manager.internal.SearchOpsImpl.search(SearchOpsImpl.java:100)

Hi Guys,
I have upgraded from SP3 to SP4. I use documentum 5.3 as CMS. I get this error when I try to see my portal home page.
SEVERE 7/19/05 10:43:44 AM findIDs: Throwing exception: com.bea.content.RepositoryException: Error executing sear
ch: Search[max=-41,sort="toProperty('sort_order') ASC",expr="(toProperty('approved_sites') == 'Intranet' && toProperty('r_object_type') == 'cpi_bulletin' &&
toProperty('content_type') == 'Hot_Announcement' && ((toProperty('locations') == null || toProperty('locations') == 'Alpharetta') && (toProperty('category')
== null || toProperty('category') != 'Manager')))"]
com.bea.content.RepositoryException: Error executing search: Search[max=-41,sort="toProperty('sort_order') ASC",expr="(toProperty('approved_sites') == 'Intra
net' && toProperty('r_object_type') == 'cpi_bulletin' && toProperty('content_type') == 'Hot_Announcement' && ((toProperty('locations') == null || toProperty(
'locations') == 'Alpharetta') && (toProperty('category') == null || toProperty('category') != 'Manager')))"]
at com.bea.content.repo.internal.RepoSearchOpsBean.search(RepoSearchOpsBean.java:175)
at com.bea.content.repo.internal.RepoSearchOpsEJB_c3xlib_ELOImpl.search(RepoSearchOpsEJB_c3xlib_ELOImpl.java:46)
at com.bea.content.spi.internal.SearchOpsImpl.search(SearchOpsImpl.java:84)
at com.bea.content.manager.internal.SearchOpsImpl.search(SearchOpsImpl.java:100)

IWS v6.0 SP4 upgrade problem

Trying to upgrade from iPlanet Web Server v6.0 SP2 to v6.0 SP4 on a Windows 2000 Server and receive the following Application Event Log error message every time I reboot the
server. " Netsite startup: Incorrect Parameter config (1320):
Full Thread dump Classic VM (JDK-1.2.2_010, native threads):"
I get this message for each instance, the web server and
the admin server. I've even tried uninstalling the web server
completely and installing v6.0 SP4 as a new installation and
I get the same event error log messages. This did not occur with my v6.0 SP2 version. Any ideas or suggestions
are greatly appreciated.
Thanks,
JD

Clay,
Instructions to upgrade are referenced in the link below:
http://knowledgebase.iplanet.com/ikb/kb/articles/5114.html
This will also work for iWS6.x servers. As always...make sure you test on a non-production server and have a complete backup prior to upgrading in a production environment.

Collisisons in a MSA CRM 4 SP8 - CRM 7 SP4 upgrade

Hello everybody,
I have run the MAR Upgrade tool CRM 7.0 SP4 on a CRM MSA 4.0 SP8 landscape. In total 11 Change Lists have been imported. Each change list caused approximately 1000 collisions which is in total 11000 collisions. I am a bit surprised by that amount of collisions. Does anyone have the experience if so many collisions are normal and that it is worthwhile to proceed?
Some other questions:
- can it be that the CMT changelist is also a reason for collisions of the later imported SAP CLs?
- does each of the 11 CLs run into the same collision, e.g. if we have changed a SAP owned object that each of the 11 CL runs here into a collision, which would mean that we have actually only ca. 1000 collisions to resolve instead of 11000?
Thanks in advance,
Regards,
Raquel

Thanks for your help Shankar,
Finally we have realized that the result: 11917 collisions, was not the number of the non-resolved collisions.
If you perform the following SQL statement on ARS_DB, you can get an overview about the collisions:
select state,count(*) from collision group by state
state 0 means non-resolved collisions
state 2 means resolved collisions
In fact, we only have 67 in state 0.
Regards,
Raquel

XIR2 SP4 Upgrade

We are planning on upgrading our XIR2 server to SP4. Does anyone have any horror or success stories on SP4?
Also, any issues upgrading from SP2 -> SP4, rather than SP3->SP4?
Thanks

I've installed SP4 about a half dozen times all servers and clients working fine (some were SP2 some SP3). I'd suggest to follow the best practices and install in a DEV environment 1st. There always a possibility that there could be issues when patching any software. If any issues arise please log an incident with support.
Regards,
Tim

SQL SP4 Upgrade

We currently have our Zenworks Inventory database on a SQL 2000 SP3a
platform. We would like to upgrade this to SP4. Before doing this however,
does anyone know if Novell supports SP4 and if they have tested and
certified SP4. I can't seem to find any documentation on this anywhere.
Thanks!

Bhenning,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

Weblogic 6.1 sp2 to sp4 upgrade not working

Weblogic is not able to create connection pool after the upgrade. if we reinstall sp2 it works fine.
please help

madhekar wrote:
Weblogic is not able to create connection pool after the upgrade. if we reinstall sp2 it works fine.
please helpHello,
Can you post your config.xml file?
rgrds,
Bart

Mssql 2005 express SP4 upgrade fail with error code 1603

The patch install through windows update is fail, then I do it manually, SQL server Database Services setup failed.
Here is the setup log
Property(S): USERNAME = Windows User
Property(S): PackagecodeChanging = 1
Property(S): ProductToBeRegistered = 1
Property(S): ProductState = 5
Property(S): TRANSFORMS = :SqlRun01.mst;:InstID01.mst;:InstName01.mst
Property(S): PackageCode = {49616E1E-6C6B-4938-B811-352C355EFDCE}
Property(S): MsiLogFileLocation = C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_W2K8FS_SQL.log
Property(S): AdministratorsGroup = BUILTIN\Administrators
Property(S): UsersGroup = BUILTIN\Users
Property(S): ModuleID_SYSDB2 = 75D79626_87FB_4E9A_B07F_87DAE18D0F36
Property(S): TempFolder = C:\Users\admin\AppData\Local\Temp\
Property(S): WindowsFolder = C:\Windows\
Property(S): CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:\Program Files (x86)\Common Files\
MSI (s) (B0:F8) [11:55:54:332]: Note: 1: 1729
MSI (s) (B0:F8) [11:55:54:332]: Product: Microsoft SQL Server 2005 Express Edition -- Configuration failed.
MSI (s) (B0:F8) [11:55:54:333]: Windows Installer reconfigured the product. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.4.5000.00. Product Language: 1033. Reconfiguration success or error status: 1603.
MSI (s) (B0:F8) [11:55:54:355]: Deferring clean up of packages/files, if any exist
MSI (s) (B0:F8) [11:55:54:355]: MainEngineThread is returning 1603
MSI (s) (B0:40) [11:55:54:356]: RESTART MANAGER: Session closed.
MSI (s) (B0:40) [11:55:54:356]: No System Restore sequence number for this installation.
=== Logging stopped: 1/10/2012 11:55:54 ===
MSI (s) (B0:40) [11:55:54:358]: User policy value 'DisableRollback' is 0
MSI (s) (B0:40) [11:55:54:358]: Machine policy value 'DisableRollback' is 0
MSI (s) (B0:40) [11:55:54:358]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B0:40) [11:55:54:359]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B0:40) [11:55:54:359]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B0:40) [11:55:54:360]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (B0:40) [11:55:54:360]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (B0:40) [11:55:54:360]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (B0:40) [11:55:54:360]: Restoring environment variables
MSI (s) (B0:40) [11:55:54:361]: Destroying RemoteAPI object.
MSI (s) (B0:AC) [11:55:54:361]: Custom Action Manager thread ending.
MSI (c) (04:88) [11:55:54:364]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (04:88) [11:55:54:366]: MainEngineThread is returning 1603
Please help.... Thanks~~

Thanks your quick reply,
As I checked before, the version is 9.3.4035
Please check the summary.txt
Microsoft SQL Server 2005 9.00.5000.00
==============================
OS Version : Service Pack 2 (Build 6002)
Time : Tue Jan 10 11:52:15 2012
w2k8fs : 64-bit ASP.Net is Registered. Required 32-bit ASP.Net to install Microsoft Reporting Services 2005(32-bit).
Machine : w2k8fs
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_w2k8fs_SQLSupport_1.log
Machine : w2k8fs
Product : Microsoft SQL Server Native Client
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_w2k8fs_SQLNCLI_1.log
Machine : w2k8fs
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.5000.00
Install : Successful
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_w2k8fs_SqlWriter_1.log
Machine : w2k8fs
Product : SQL Server Database Services
Error : The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
Machine : w2k8fs
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.4.5000.00
Install : Failed
Log File : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_w2k8fs_SQL.log
Last Action : SetInstanceProperty
Error String : The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
Error Number : 29528
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

CallManager upgrade from 3.3(5)es23 to 4.2(3) fails

Not having a lot of luck over on the Unified Communications Applications forum so thought I would post this here as well.
The CallManager upgrade from 3.3(5)es23 to 4.2(3) fails at installing SQL2000 SP4.
On the Publisher :
OS Image 2000.2.4
OS Service rel : 2000.4.3aSR9
OS Upgrade : 2000.4.3a
On the Subscriber :
OS Image 2000.2.4
OS Service rel : 2000.4.3aSR9
OS Upgrade : 2000.4.3a
SQL2K SP : SP3a(1.0.6)
The SQL version is too high to allow the Publisher to be patched to SQL2k
SP3a(1.0.6).
I have also donwloaded the SQL200 SP4 upgrade and tried installing that on the
Publisher but this fails also.
I did try upgrading the OS on both the Pub and Sub to 2000.4.4a with
2000.4.4aSR6 but the CallManager upgrade still failed at the SQL2000 SP4
upgrade phase of the installation.
Has anyone seen this happen before and know a solution? All suggestions very welcome.
Keith.

SQL SP4 should be installed AFTER CallManager4.2(3) upgrading finished.
( Please refer to SQL SP4 readme.file from cisco , not from Microsoft)
Here is the basic task order:
OS upgrade->CCM upgrade->SQL SP4 upgrade.
My suggestion:
Restore your system to CCM3.3(5) ( find your backup data)
Then upgrade again.
Hope this help.
Howard
Please rate if this helps.
( I attached part of SQL SP4 readme file as follows:
SQL Server 2000 Service Pack 4 - (SQL2K-ServicePack4.1-0-3.exe)
Note: If you install SQL2K SP4 on a Cisco CallManager 3.3(5), or 4.0(2a) server,
you will not be able to upgrade the server to Cisco CallManager 4.1(2) later. If such an upgrade is required, you must upgrade the server to Cisco CallManager 4.1(2) before you install SQL2K SP4

*ExceptionCondition ' Table Not Exists' raised.*

Dear Gurus,
We are facing a problem in lot of our queries after EHP1 SP4 upgrade.
ExceptionCondition ' Table Not Exists' raised.
If somebody has any vague idea on how to resovle this. Kindly help.
Regards,
Dennis

Hi Dennis,
We ran into the same error.
You need to run the program called SAP_DROP_TMPTABLES. Click on the parameters called Temporary Tables and Temporary Hierarchy.
If the query is still getting this message, then you need to regenerate the query in RSRT.
Good Luck! Bill

Installation Sequence for NW04

Hello,
I am installing WEB AS J2EE(Central Instane with Default parameter))
Please suggest ,is this a corect installation Sequence ?
1)Install WEB AS J2EE.
2)Upgrade it from SP3 to SP4
3)Install portal platform .
4)Upgrade WEB AS J2EE from SP4 to SP9
5)Upgrade portal to SP9 .
6)Install CM and KM .
If it is correct then what should be patch level for CM and KM ?
Thanks .
Gyan

Hello Gyan,
   There are many combinations in which you can do your installation sequence. Here is what I have followed successfully.
   Install J2EE 6.30 SP3 (Central system, Java
   Patch J2EE 6.30 to Stack 5 (SP8)
   Install EP6.0 SP3
   Upgrade KMC to Stack 4 (SP6)
   Install KMC SP6 Patch 2
   Upgrade to EP 6.0 to Stack 4 (SP6)
   Install KMC Stack 2 (SP4)
   Upgrade EP6.0 to Stack 5 (SP7)
   Upgrade KMC to Stack 5 (SP7)
   Patch both EP6.0 and KMC to SP7 Patch 2
hope this helps
Regards
Abdul

Soft Comp Error :VALUEMAP for property SAP_SoftwareComponent.Production

Hi All,
I am trying to create a software component on SLD. I have created a Product first. Then trying to create a software component for the product.
While trying to create a software component I am getting the following error
"Value not allowed by VALUEMAP for property SAP_SoftwareComponent.ProductionState: Released"
I have tried using different Production State : Planned, Started, Released etc.
But I am getting the same error everytime.
Pls help me on this.
Thanks and warm regards
Purnendu

i Maiti,
I think your SP on XI is SP4, upgrade it to <b>SP5</b>. This will be solved
for your reference
Re: unable to create new software component
regards
Ramesh P

Sp4 Upgrade

Similar Messages

Maybe you are looking for