Compliance Calibrator Upgrade path CC 5.1 to AC 5.3

Hello,
In the PAM for access control 5.3, Compliace Calibrator 5.1 to Access Control 5.3 is not listed in the "Upgrade to SAP GRC ACCESS CONTROL 5.3 from" section. We are on CC 5.1 NW04. Will the rule conversion utility that is shipped with Access Control 5.3 work on CC 5.1 NW04?
Thanks,
Paul

Hi Paul,
The conversion utility of Ac 5.3 works for CC 5.1 as well .
Check pages 21-23 of Ac5.3 upgrade guide for step by step instructions for the upgrade.
Thnks
Jasmine

Similar Messages

Why upgrade from Compliance Calibrator to GRC?

Hello Experts- My company has yet to implement GRC 5.3. We already utilize SAP Compliance Calibrator by Virsa Systems 4.0, which works fine, so what would be the benefit of upgrading to GRC? Is it really necessary? Is it just to stay current? Also, is it true that GRC will be moving from Java back to an ABAP stack? If so, when is the new ABAP version of GRC set to be available?
Thanks for your advice and opinions.

Regarding the upgrade from 4.0 to 5.3 I concur with Alpesh and Varun.
Regarding the upgrade to 10.0, current plans are for Ramp-up to be available in December 2010 with general release scheduled for mid 2011.
According to the latest material from SAP, they are only supporting a migration path as follows:
4.0 -->5.3 --> 10.0
There is no supported upgrade path from 4.0 directly to 10.0.
It should be noted that it is a significant change in architecture and therefore not a simple migration path. SAP are recommending an upgrade to 5.3 followed by a migration to 10.0 for the technical side of things.
5.3 does still have some significant advantages over 4.0 and therefore is still an option. owever, if you wish to register your interest, SAP are seeking ramp up customers so I would suggest you contact your Consultants or account management within SAP to discuss the options if you are considering it.
Simon

4.6C to ECC 6.0 upgrade - Issue with Virsa Compliance Calibrator

The issue is that phase IS_SELECT during the PREPARE is not detecting VIRSA as an add-on. This of course will result in VIRSA not being upgraded and the system will be unstable ( note 989368 ). Also, I can't choose to delete the add-on either.
We installed the compliance calibrator before SAP purchased VIRSA. So, the tool was installed through transports, not SAINT. I assume this is why phase IS_SELECT is not seeing the tool.
Any ideas?
-Scott

Received a reply from SAP. Since VIRSA was installed through STMS the IS_SELECT phase will not see the add-on. I had to do the ECC 6 upgrade as normal and then install VIRSA 4.0 for SAP 700 systems through SAINT.
I had to clear SPDD and SPAU as much as possible for /VIRSA/* objects. However, there were six objects I could not clear. This did not cause any issues.
Notes 1006083 and 985617 are needed for this procedure.
Thanks for all the suggestions.
-Scott

Convert from Compliance Calibrator 4.0 to Risk Analysis and Remediation 5.2

Hello Forum,
I'm looking for other opinions on converting Compliance Calibrator (CC) 4.0 to Risk Analysis and Remediation (RAR) 5.2 (formerly CC)
I have inherited responsibility for RAR and need to upgrade it to the 5.2 level; our current ECC level prevents us from going to 5.3
I found a process that will unload the data from CC 4.0 and be imported into RAR 5.2
I want to understand the definitions that comprise the RAR and was thinking about recreating the definitions in 5.2 based on what is already defined in the CC 4.0 system; I have time to do this since there is no definitive deadline that would make it impossible to meet
Currently, I have the following definitions:
Business Process 6 entries
Functions 47 entries
Risks 147 entries
Mitigating Controls 40 entries
Would others find this approach acceptable and reasonable even though I would be entering all the information? Basically, it would be like defining the data for the very first time if this was NEW software
I would expect to come away with a good understanding of how everything ties together; at this point, I am only looking to create the necessary data that would allow for producing SOD reports that show all users with "risks" have been mitigated with acceptable controls
Thanks for your responses in advance
Jerry
Ryerson, Inc
630-758-2021

Thanks for the reply
I have the migration guide and have reviewed it; I have actually played around a bit with obtaining the file from CC 4.0; I found that the data records may need some adjustments to be compatible with RAR 5.2; one of the reasons that may be leading me to do everything from scratch
The definitions currently defined were completed by an outside source and the mitigated controls were defined by the Internal Audit area
I'm not sure if they were mixed with the defaults
I'm not sure at this point what impact or changes I would experience if I use the "default" supplied rules set but I expect to find out
Thanks again for your reply
Jerry

SAP GRC Access Control - Compliance Calibrator - License Cost

Dear all,
I have some questions on Compliance Calibrator implementation.
1. Do we have to pay additional cost for the license to implement Compliance Calibrator?
2. Since SAP GRC 5.3 is just released, which one do you recommend? SAP GRC 5.2 or 5.3?
3. What would be the major difference between Compliance Calibrator in GRC 5.2 and 5.3?
Best regards,
Rolando

Hi Rolando-
1. Yes, there lies some license cost and the amount should not as much as taking SAP R/3 license. I am not sure of exact amount but its nominal as compared to other SAP products.
2. SAP always recommend for the latest version available and why not one would go for latest version if you are paying something for that.
Also, it depends on your existing R/3 version and its compatibility. In short run, you can choose per your existing versions but in long run everyone has to move to latest version. Say for example whoever is using SAP R/3 technology with whatever version, they all need to upgrade to ECC6.0 by 2011 with extension upto 2013. I am not sure of any such information about GRC AC though.
3. Some enhancement have been done with CC 5.3. Those features include-
1. Risk analysis for SAP Enterprise Portal and UME
2. BI integration for custom reporting
3. Reporting enhancement features include additional auditor, business manager and IT reports
4. SOD management by exception. Can be integrated with workflow.
5. Import/Export of configuration data
6. Migration scripts
7. Download and print capability on every report.
Some performance improvements-
1. Concurrent risk analysis.
2. batch mode risk analysis
3. Improved memory mgmnt etc.
Hope it gives you now some more visibility.
Cheers!
Ashok

WLSE to WCS upgrade path

Hi,
Could anybody tell me if they are aware of an upgrade path from WLSE to WCS using existing WLSE hardware? Can anybody point out the main benefits/features moving to WCS from WLSE?
Many thanks
SJ

Hi Scott,
Just the 1130-19 or 1133 are supported;
The new Cisco WCS SKU family, WCS-WLSE-UPG-K9, is now available for CiscoWorks WLSE customers that wish to migrate from CiscoWorks WLSE (Models 1130-19 or 1133) to Cisco WCS. These new SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
All CiscoWorks WLSE conversion SKUs ship with two special conversion CDs. These CDs check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
This SKU family supports only ***CiscoWorks WLSE hardware models 1130-19 and 1133. To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. ***Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
Note: CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Model 1105) are not supported with CiscoWorks WLSE conversion SKUs. Do not install the CiscoWorks WLSE CDs on the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and it will not work.
Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Autonomous access points are not supported by a converted CiscoWorks WLSE.
Customers migrating their CiscoWorks WLSE to Cisco WCS do not need to buy a copy of RedHat Linux ES v. 4.0 software. A copy of RedHat Linux ES v. 4.0 software is included with the CiscoWorks WLSE migration CDs. (RedHat Linux AS v. 4.0 is not supported by a converted CiscoWorks WLSE.)
From this good doc;
http://www.cisco.com/en/US/products/sw/cscowork/ps3915/prod_bulletin0900aecd804b4635.html
Hope this helps!
Rob

Issue with Compliance Calibrator 5.2 SP9 Background Jobs

Hello,
I'm having an issue with Compliance Calibrator 5.2 SP9 where If I run a role analysis as a background job that has the same parameters as a previously run role analysis background job, the second job that is run will display a failure message. It does not appear to matter if the similar background jobs were run by the same individual or separate individuals. As long as the job that was previously run is still in the background job history, than any job with the same parameters run by a user will fail.
Is this normal operation for CC?
Is there a configuration change that could allow a job to be rerun in the background multiple times?
Is there a fix for this issue in a later support pack or with upgrade to 5.3?
Thanks for the help it's much appreciated,

To better clarify what is occurring, the 1st job will run and complete successfully and return/display the appropriate results correctly. The 2nd job will than be subsequently kicked off and finish same as with the previous job except when you open the background results no data is displayed and the message at the bottom reads: Failed to display result. To make more sense of what Iu2019m doing, these are the logical steps Iu2019m following:
1. Select Role Level analysis
2. Enter parameters for analysis
3. Schedule background job to run immediately
4. View background job results (successful job and correct results)
5. Select Role Level analysis (with same or any other user)
6. Enter same parameters as step 2 for analysis
7. Schedule background job to run immediately
8. View background job results (successful job, but the error message: u2018Failed to display resultu2019, instead of seeing the CC reports)
I believe the error is somewhere in the running of a job with the same parameters (Same Role and same Report Type). If I delete the previous jobs from the background history that have the parameters Iu2019m using and try the analysis again, a third time, with the same parameters as before, it will run successfully and display the correct results.
Is this normal and acceptable operation for CC5.2 SP9?
Is there a configuration change that would allow a job to be run in the background multiple times with the correct CC results?
Is there a fix for this issue in a later support pack or with upgrade to 5.3?

Does Compliance Calibrator come installed with CRM 2007

We will be installing CRM 2007 in May and I need to know if Compliance Calibrator is installed as part of the application. Currently we are running CC 3.0 in R/3, HR and BW. If the new version is part of CRM 2007 then we need to upgrade to the newest version. I also need to know if the CC is not part of CRM 2007, will CC 3.0 technically work in CRM 2007.

Hi, thanks for your replies,
Our SP is uptodate,
Note 1120400 is obsolete we have CRM 6 SP2 and our patch level is 15.
Besides we have a delta between tables entries:
USOBX     => 103.391
USOBX_C     => 103.389
and
USOBT     => 43.785
USOBT_C     => 43.769
Do these tables have the same number of entries in your system? What could be the impact of this delta?
Thanks,
Aldo

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

Error Message: "This upgrade path is not supported"

Scenario
During the process of upgrade to Windows 10 Technical Preview, we may encounter the error “This upgrade path is not supported. Please close Setup and re-launch from the root of the media or go back and pick a different installation
choice.” in the Compatibility report.
Analysis
Step 1: Perform the scenario 1: the upgrade installation fails.
Reproduce this error following the steps below:
Download the Windows 10 Technical Preview ISO installation file.
Extract the ISO installation file to C:\New folder, and now the location of the installation file is
C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\.
Click setup.exe from the installation file, and then click
Install now.
Setup is starting, and then get two options Upgrade and
Custom which is the classic setup wizard which we can see during booting from DVD.
Click Upgrade to run upgrade installation, however, the error occurs.
It seems that it is impossible to perform upgrade installation to Windows 10 Technical Preview, although it is fine to click
Custom to perform clean installation which cannot keep the personal setting and applications.
However, what we want is upgrade installation, not clean installation.
Step 2: Perform the scenario 2: the upgrade installation works fine.
If extract the ISO installation to C:\New in the above step2, click the
setup.exe from the installation file C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\, the upgrade installation would work fine, which is as shown the following two figures:
Step 3: Check the setupact.log
file which contains information about setup actions during the installation of the two scenarios.
Scenario 1: Check the setupact.log file of the scenario 1. The detailed information is shown as below:
2014-10-14 19:03:40, Info UI Determining whether we should run ConX or legacy setup
2014-10-14 19:03:42, Info UI Will launch ConX setup experience
2014-10-14 19:03:42, Info UI Launching ConX setup experience
2014-10-14 19:03:42, Info UI Launching C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
2014-10-14 19:03:44, Info UI Unknown command line for ConX setup experience. Launching legacy setup experience.
2014-10-14 19:03:44, Info UI Determining if we are in WDS/Unattend mode
2014-10-14 19:03:44, Info UI No need to hide autorun
2014-10-14 19:03:44, Info [0x0a000a] UI Autorun:Autorun core successfully initialized!!!
2014-10-14 19:03:44, Info [0x0a000b] UI Autorun:Autorun UI successfully initialized!!!
2014-10-14 19:03:44, Info UI AppWindow has layout style 0
2014-10-14 19:03:45, Info UI NavWindow has layout style 0
2014-10-14 19:03:45, Info [0x0a011c] UI WizardDialogPost::SetActive
2014-10-14 19:04:57, Info [0x0a018e] UI Passing command line parameter ("C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\setup.exe /HideWelcome /uilanguage:en-US /targetlanguage:en-US") to IBS.
Scenario 2: Check the setupact.log file of the scenario 2. The detailed information is shown as below:
2014-10-14 19:08:04, Info UI Determining whether we should run ConX or legacy setup
2014-10-14 19:08:05, Info UI Will launch ConX setup experience
2014-10-14 19:08:05, Info UI Launching ConX setup experience
2014-10-14 19:08:05, Info UI Launching C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
According to the two logs, we can get the following points:
In scenario 1, it would invoke the SetupPrep.exe in the source folder directly to perform an installation preparation. However, it failed to recognize the path
C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe. Then it would launch legacy setup.
In the scenario 2, Windows setup would be redirected to the ConX setup to perform upgrade installation automatically.
So, what is the difference of the scenario 1 and 2 to bring the different results of upgrade installation?
Workaround
Based on lots of testing, we find that if there is no space in the extracting location of the ISO installation
file, the upgrade installation would work fine.
What’s more, we can get the meaning of the two setup models in the setupact.log:
Legacy setup: it is same with setup from DVD boot.
ConX setup: it would check the compatibility and language UI for upgrade preparation, then perform migration and upgrade directly.
Additional Resource
From the release of Windows 10 Technical Preview, many users have installed and tested Windows 10 Technical Preview, we still hope more and more users would download and install Windows 10 Technical Preview for test, and provide
us your feedback.
Download Windows Technical Preview
http://windows.microsoft.com/en-us/windows/preview-iso
Download Windows Technical Preview for Enterprise
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-technical-preview-for-enterprise
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hello,
I would guess that existence of a space in the folder name is what the issue is. Try removing the space from the folder name and see if works. New_Folder for example
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me kn

I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me know why it didnt do any conversion. Am i missing something?

yes, that app engine didnt inserted any rows. So now when i tried to drill down i found that there was no data in the "new demo" database on table UPG_DATACONV. That is the reason for all this.
When i applied required for upgrade patch in demo it said couple of patch already exists so those update i skipped. Now when i check upd877654 has a step which imports the data in this table. my change assistant told that the update is already available in my demo so i skipped. Now i am not sure what to do.
I tried reimporting the data and running the analyzer again. But worried that there can be any issues due to this.

Windows 8.1, Update 1 upgrade path

Hi, if there is anyone of any influence who might read this, please, please, for you own sakes make an upgrade path directly from Windows 8.0 --> Windows 8.1, Update 1
I cannot upgrade from W8.0 --> 8.1.
I cannot upgrade due the the following error. But I believe it is a silly error and can be overcome as some have managed:
https://answers.yahoo.com/question/index?qid=20131018074442AAswJqp
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_install/windows-81-install-unable-to-create-ramdisk/887b5adc-86ce-4c37-9c58-72eca5f712d4?page=8&tm=1396807793681
I even had a MS 3rd line Andswer Desk (ref:1233447567.) guy who was remote controlling my machine trying clean boot give up after saying that if my
MB manufacturer wont support drivers past Vista then there is nothing they "should" do... But Vista is EoS but not extended support as XP is, that ends 2017:
http://windows.microsoft.com/en-gb/windows/lifecycle
This is an issue I'm having with my personal PC but I also work in IT infrastructure and I think this needs to be sorted. This is going to become a BIG issue for many other people who have Vista/XP-grade systems with the requirements for 8.1.1 who will try
to upgrade.
Please can someone help?
System: Q6600, MB: XFX Nvidia Nforce 680i LT, 8GB RAM

Hi,
Windows 8.1 do have have higher requirements for hardware, If your computer hardeware device was too old, you may encounter some problem during install or using Windows 8.1.
Roger Lu
TechNet Community Support

Upgrade Path from 5.1.4

We are currently running version 5.1.4 and are looking to upgrade. What is the recommended upgrade path or version we should be planning to go to? Our pipeline isn't very complicated since I've read some articles about there not being a direct migration to version 3.0. We currently develop using the RAD toolkit and .NET if that is a factor when upgrading.
Also if someone could clarify which packages I'm looking at migrating to as before I installed Endeca IAP and Dev Studio and I was up and running. I don't see those packages in the newer versions of the software and I'm not 100% on what the packages were renamed to after the transition to Oracle.

It sounds like you are upgrading an Endeca Commerce / Guided Search implementation. This forum is for Oracle Endeca Information Discovery (EID) products. You will get better answers over on the other forum, https://forums.oracle.com/community/developer/english/endeca_experience_management/technical_questions .

Is Compliance Calibrator the same as GRC Access Control?

I have been asked to look at Compliance Calibrator and am getting confused about what functionality is offered. I have done the basic e-learning course for Compliance Calibrator (GRC200): this was all about separation of duties etc. Fair enough. But I also have a Document called "SAP GRC Access Control" which talks about the same S.O.D compliance functionality but also talks of "roles triggering workflows", "users creating roles", "automated approvals for roles" eg:
"SAP GRC Access Control streamlines access requests by filling each request automatically with user identity information from a lightweight directory access protocol (LDAP) directory or HR database, thereby eliminating the need for user intervention. Approvers receive an e-mail with a direct hyperlink to the request inside the application, where they can easily view and approve the request. The application then checks for security violations before updating accounts automatically."
None of this was covered on the Compliance Calibrator course, so what product offers this? I can see another product by Virsa called Access Enforcer but have no info on this... can anyone enlighten me?

SAP GRC Access Control is the SAP application that comprises the former Virsa products Compliance Calibrator, Access Enforcer, Risk Terminator, Firefighter and Role Expert.

Custom report on Compliance Calibrator Job scheduler

Currently in compliance calibrator it is not possible for a user to view the status, success or otherwise, of another users scheduled job or sync unless granting that user full administrator rights.
Please advise if it's possible to expose the underlying scheduled job table for a given system via a custom built static html web page. Can you advise of the table that results would need to be displayed from and whether there would be any drawbacks of this approach, or if others have somehow solved this problem with another solution, please share?!
What are SAP's timeframe's for finer grained security in CC?

below are the tables used for CC:
VIRSA_CC_ACTRULE               SAPSR3DB
VIRSA_CC_ACTRULHDR             SAPSR3DB
VIRSA_CC_ACTVL                 SAPSR3DB
VIRSA_CC_ADMIN                 SAPSR3DB
VIRSA_CC_ALLASTRUN             SAPSR3DB
VIRSA_CC_ALLISTDTL             SAPSR3DB
VIRSA_CC_ALLISTHDR             SAPSR3DB
VIRSA_CC_ALTCDLOG              SAPSR3DB
VIRSA_CC_AUTHHT                SAPSR3DB
VIRSA_CC_AUTHMAP               SAPSR3DB
VIRSA_CC_BKGINP                SAPSR3DB
VIRSA_CC_BUAPPVR               SAPSR3DB
VIRSA_CC_BUMONITOR             SAPSR3DB
VIRSA_CC_BUSPRC                SAPSR3DB
VIRSA_CC_BUSPRCT               SAPSR3DB
VIRSA_CC_BUSUNIT               SAPSR3DB
VIRSA_CC_BUSUNITT              SAPSR3DB
VIRSA_CC_CDHDR                 SAPSR3DB
VIRSA_CC_CDPOS                 SAPSR3DB
VIRSA_CC_CGROUP                SAPSR3DB
VIRSA_CC_CONFIG                SAPSR3DB
VIRSA_CC_CRACT                 SAPSR3DB
VIRSA_CC_CRACTT                SAPSR3DB
VIRSA_CC_CRACTVL               SAPSR3DB
VIRSA_CC_CRPRM                 SAPSR3DB
VIRSA_CC_CRPRMVL               SAPSR3DB
VIRSA_CC_CRPROF                SAPSR3DB
VIRSA_CC_CRPROFT               SAPSR3DB
VIRSA_CC_CRROLE                SAPSR3DB
VIRSA_CC_CRROLET               SAPSR3DB
VIRSA_CC_CRROLEVL              SAPSR3DB
VIRSA_CC_DATAEXD               SAPSR3DB
VIRSA_CC_DETDESC               SAPSR3DB
VIRSA_CC_FLDMAP                SAPSR3DB
VIRSA_CC_FUNC                  SAPSR3DB
VIRSA_CC_FUNCACT               SAPSR3DB
VIRSA_CC_FUNCBP                SAPSR3DB
VIRSA_CC_FUNCPRM               SAPSR3DB
VIRSA_CC_FUNCSYS               SAPSR3DB
VIRSA_CC_FUNCT                 SAPSR3DB
VIRSA_CC_GENACT                SAPSR3DB
VIRSA_CC_GENOBJ                SAPSR3DB
VIRSA_CC_GENOBJT               SAPSR3DB
VIRSA_CC_GENPRM                SAPSR3DB
VIRSA_CC_GENUSR                SAPSR3DB
VIRSA_CC_GPRMLIST              SAPSR3DB
VIRSA_CC_GSEQ                  SAPSR3DB
VIRSA_CC_JOBHST                SAPSR3DB
VIRSA_CC_LASTRUN               SAPSR3DB
VIRSA_CC_LOCKTABLE             SAPSR3DB
VIRSA_CC_LSYSGRP               SAPSR3DB
VIRSA_CC_MGALERTS              SAPSR3DB
VIRSA_CC_MGCRTR                SAPSR3DB
VIRSA_CC_MGMTBU                SAPSR3DB
VIRSA_CC_MGMTTOT               SAPSR3DB
VIRSA_CC_MGRISKD               SAPSR3DB
VIRSA_CC_MGRISKS               SAPSR3DB
VIRSA_CC_MICCTLDTL             SAPSR3DB
VIRSA_CC_MICCTLDTT             SAPSR3DB
VIRSA_CC_MICEXLOG              SAPSR3DB
VIRSA_CC_MICORGDTL             SAPSR3DB
VIRSA_CC_MICORGDTT             SAPSR3DB
VIRSA_CC_MICPRCDTL             SAPSR3DB
VIRSA_CC_MICPRCDTT             SAPSR3DB
VIRSA_CC_MICRMAP               SAPSR3DB
VIRSA_CC_MICUMAP               SAPSR3DB
VIRSA_CC_MITHROBJ              SAPSR3DB
VIRSA_CC_MITMON                SAPSR3DB
VIRSA_CC_MITPROF               SAPSR3DB
VIRSA_CC_MITREF                SAPSR3DB
VIRSA_CC_MITREFT               SAPSR3DB
VIRSA_CC_MITRISK               SAPSR3DB
VIRSA_CC_MITROLE               SAPSR3DB
VIRSA_CC_MITRPT                SAPSR3DB
VIRSA_CC_MITUSER               SAPSR3DB
VIRSA_CC_MITUSRORG             SAPSR3DB
VIRSA_CC_MONAPV                SAPSR3DB
VIRSA_CC_MSG                   SAPSR3DB
VIRSA_CC_MSGPRMS               SAPSR3DB
VIRSA_CC_MSGTYP                SAPSR3DB
VIRSA_CC_OBJTEXT               SAPSR3DB
VIRSA_CC_ORGRULE               SAPSR3DB
VIRSA_CC_ORGRULEM              SAPSR3DB
VIRSA_CC_ORGRULET              SAPSR3DB
VIRSA_CC_ORGUSERS              SAPSR3DB
VIRSA_CC_PRMRULE               SAPSR3DB
VIRSA_CC_PRMVL                 SAPSR3DB
VIRSA_CC_RISK                  SAPSR3DB
VIRSA_CC_RISKFUNC              SAPSR3DB
VIRSA_CC_RISKOWN               SAPSR3DB
VIRSA_CC_RISKRS                SAPSR3DB
VIRSA_CC_RISKT                 SAPSR3DB
VIRSA_CC_ROLEVL                SAPSR3DB
VIRSA_CC_RTMAP                 SAPSR3DB
VIRSA_CC_RULESET               SAPSR3DB
VIRSA_CC_RULESETT              SAPSR3DB
VIRSA_CC_SAPOBJ                SAPSR3DB
VIRSA_CC_SCHEDULER             SAPSR3DB
VIRSA_CC_SUPP_DET              SAPSR3DB
VIRSA_CC_SUPP_HDR              SAPSR3DB
VIRSA_CC_SUPP_TEXT             SAPSR3DB
VIRSA_CC_SYSCRACT              SAPSR3DB
VIRSA_CC_SYSHMAP               SAPSR3DB
VIRSA_CC_SYSRULE               SAPSR3DB
VIRSA_CC_SYSSAPOBJ             SAPSR3DB
VIRSA_CC_SYSTEM                SAPSR3DB
VIRSA_CC_SYSTEMC               SAPSR3DB
VIRSA_CC_SYSTEMT               SAPSR3DB
VIRSA_CC_SYSUSR                SAPSR3DB
VIRSA_CC_TEXTKEY               SAPSR3DB
VIRSA_CC_THREAD                SAPSR3DB
VIRSA_CC_USRMAP                SAPSR3DB
VIRSA_CC_VARIANT               SAPSR3DB
VIRSA_CC_VARVAL                SAPSR3DB
VIRSA_CC_WFOBJ                 SAPSR3DB
VIRSA_CC_XSRULEMAP             SAPSR3DB
VIRSA_CC_XSYSGRP               SAPSR3DB
You can go and check which one contains the scheduling info (VIRSA_CC_SCHEDULER ??)
Hope this helps

Compliance Calibrator Upgrade path CC 5.1 to AC 5.3

Similar Messages

Maybe you are looking for