Providing system configuration info in an automated installer manifest.

In Solaris 11 Express it was possible to embed a system configuration xml file within the automated installer file. The documentation for this is here: http://docs.oracle.com/cd/E19963-01/html/820-6566/customsc.html
However this functionality seems to be missing from 11.1 at the moment. I get xml validation errors if I try to use embedded system configuration xml. Does anyone know of a way to do this? We would like to automate Solaris 11.1 installs without having to run an auto install server.

Please see the 11.1 documentation:
http://docs.oracle.com/cd/E26502_01/html/E28980/useaipart.html
System configuration profiles are no longer embedded in the AI manifest but are provided in one or more separate files.
Providing System Configuration Instructions
http://docs.oracle.com/cd/E26502_01/html/E28980/glgeh.html#ai3sc
Associating Client-Specific Configuration Instructions With Install Services
http://docs.oracle.com/cd/E26502_01/html/E28980/administer.html#gliea
Configuring the Client System
http://docs.oracle.com/cd/E26502_01/html/E28980/syscfg-1.html

Similar Messages

Bridge quit working, won't start, problem details and System Configuration info given..is this adobe or apple?

This is the info in the window that opened when I try to start Bridge. It has never done this, nothing has changed...is this a problem with Bridge, or mac?
Process:         Adobe Bridge CC [1968]
Path:            /Applications/Adobe Bridge CC/Adobe Bridge CC.app/Contents/MacOS/Adobe Bridge CC
Identifier:      com.adobe.bridge6
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process: launchd [154]
Date/Time:       2014-08-26 20:43:55.927 -0500
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report:          21183 sec
Crashes Since Last Report:           26
Per-App Crashes Since Last Report:   25
Anonymous UUID:                      2B9B30CC-BA8E-4CCC-B033-C5EF8A79E632
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /Applications/Adobe Bridge CC/Adobe Bridge CC.app/Contents/MacOS/../Frameworks/dvanet.framework/Versions/A/dvanet
Reason: Incompatible library version: dvanet requires version 7.0.0 or later, but libcurl.4.dylib provides version 6.0.0
Binary Images:
    0x7fff5fc00000 -     0x7fff5fc3be0f dyld 132.1 (???) <29DECB19-0193-2575-D838-CF743F0400B2> /usr/lib/dyld
Model: iMac11,3, BootROM IM112.0057.B00, 4 processors, Intel Core i7, 2.93 GHz, 4 GB, SMC 1.59f2
Graphics: ATI Radeon HD 5750, ATI Radeon HD 5750, PCIe, 1024 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 2.1.14.6
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: SAMSUNG HD103SJ, 931.51 GB
Serial ATA Device: HL-DT-STDVDRW GA32N
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: My Book 1110, 0x1058 (Western Digital Technologies, Inc.), 0x1110, 0xfa130000 / 5
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8215, 0xfa111000 / 6
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0xfa120000 / 3
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: USB Receiver, 0x046d (Logitech Inc.), 0xc52b, 0xfd140000 / 6
USB Device: My Passport 0748, 0x1058 (Western Digital Technologies, Inc.), 0x0748, 0xfd130000 / 5
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8502, 0xfd110000 / 4
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0xfd120000 / 3

Did you do the virus scan yourselt for have it done in a shop?
The problem according to your report is
Fault Module Name: StackHash_125c
It looks like this may be a virus. But check online and see what others say.
Sorry I do not have better news.

Bad system configuration info

I opened my PC this morning and it said that windows did not load properly... It tries to auto correct and then does a diagnostic and I get the message above to research ... I press the ok for it to restore to an earlier time when windows was running . And then the HP comes up and just sits there ,,,, any help would be greatly appreciated

Windows 7 Recovery:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01867418&cc=us&dlc=en&lc=en&jumpid=reg_r1002_us...
Windows 8 Recovery:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c03489643&tmp_task=solveCategory&cc=us&dlc=en&lc...
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

I can not make a "Automated Installation of the Introscope Agent" (Managed System Configuration, p.7)

I can not make a "Byte Code Adapter Installation"
When I open meets both paragraphs in step Managed System Configuration is somewhat obscure situations that do not allow the automatic configuration Introscope agent and Introscope Manager
Please help to resolve a number of questions that might help me complete the setup :
1. Why has the status of Enterprise Manager : <No Enterprise Manager configured> ( see picture)
I set up Enterprise Manager in accordance with the installation instructions and complied with all the setting items . Since without any configuration can be associated with the appearance of this status ?
2 . Why Server Node is empty detail settings ?
JDK Location:
Enterprise Manager Host:
Enterprise Manager Port:
Introscope Agent Name:
Introscope Agent Profile:
Autoprobe Directives:
Wily Version:
Introscope Agent Version:
Introscope Agent Log Location:
3 . What a mistake ($ MC: DIAG_WILY_MSG: 032 : L), which appears when I click configuration "Configure Introscope Agent Setup ...", and what it can be linked ? ( see picture )
And the last question , which is also linked to the process of automatic configuration and refers to a phrase from the instruction (Introscope Version 9
Installation Guide For SAP July 2012) points out "Automated Installation of the Introscope Agent via SMD"
there is such an item:
2 . Deploy ISAGENTJ5 *. SCA which is the Introscope Java Agent 9 with SDM to Solution Manager. You may need to deploy also ISAGENT *. SCA which is Introscope Java Agent 8.
However, nowhere does it say where exactly ( on what the absolute path ) I must perform unloading and then what to do with this discharge

The problem was resolved a small manipulation - on stage Basic Configuration,
point 3 "Configure CA Introscope"
I forgot to add to the list of CA Introscope Enterprise Managers link to my manager.
Thus it is necessary to take into account that the path should be correct (usually for linux - /usr/sap/ccms/apmintroscope) and the directory should be applied appropriate privileges.
Then in paragraph "Byte Code Adapter Installation" - there are all the necessary data, and it starts to work correctly

Which LabVIEW 2012 Installer disc has System Configuration 5.3.3 on it?

I am trying to build an installer here and under additional installers I selected to install MAX 5.3.3 - the installer builder is asking me to locate the installer for System Configuration 5.3.3 but I can not locate the source installer.
Ryan Vallieu
Automation System Architect
Solved!
Go to Solution.

I had to download it from the website and run the self extracting EXE
This then put the installer on my HD - of course the installer didn't install any software, since I had it already, but the installer folder was then what the Additional Installers was looking for when doing my build.
Gah - very annoying.
Ryan Vallieu
Automation System Architect

Oracle R12 Installation Error - Validate System Configuration

Hello,
I was doing the oracle apps R12 installation and got this error
=======================
Validate System Configuration
The post-install check inspects your system for a complete installation.
The list below shows the tests that were performed and the results.
Click on the test icon for details.
One or more of the post-install tests did not succeed for this:
Database Availability
HTTP
Virtual Directory
Login page
Configuration Upload
Help page
JSP
=======================
I’ve checked the details which are listed below.
Please help me in solving the issue :(
Configuration Upload
uploading config file at /u05/oracle/TEST/db/tech_st/11.1.0/appsutil/conf_TEST.txt
Failed upload of config file at /db/tech_st/11.1.0/appsutil/conf_TEST.txt
Database Availability
command: su dbuser -c "/tmp/RapidInstall/bin/riwTDBup.sh /u05/oracle/TEST/db/tech_st/11.1.0/TEST_erp.env APPS/APPS"
riwTDBup.sh started at Fri May 25 06:42:59 IST 2012
Parameters passed are : /u05/oracle/TEST/db/tech_st/11.1.0/TEST_erp.env APPS/APPS
The environment settings are as follows ...
ORACLE_HOME : /u05/oracle/TEST/db/tech_st/11.1.0
ORACLE_SID : TEST
TWO_TASK :
PATH : /u05/oracle/TEST/db/tech_st/11.1.0/perl/bin:/u05/oracle/TEST/db/tech_st/11.1.0/bin:/usr/bin:/usr/sbin:/u05/oracle/TEST/db/tech_st/11.1.0/appsutil/jre/bin:/usr/ccs/bin:/bin:/usr/bin/X11:/usr/local/bin:/usr/bin:/u05/Setup12.1.1/startCD/Disk1/rapidwiz/unzip/Linux:/usr/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin:/root/bin:.
LD_LIBRARY_PATH : /u05/oracle/TEST/db/tech_st/11.1.0/lib:/usr/X11R6/lib:/usr/openwin/lib:/u05/oracle/TEST/db/tech_st/11.1.0/lib:/usr/dt/lib:/u05/oracle/TEST/db/tech_st/11.1.0/ctx/lib
Executable : /u05/oracle/TEST/db/tech_st/11.1.0/bin/sqlplus
riwTDBup.sh exiting with status 3
RW-50011: Error: - Database ORACLE_HOME connection test has returned an error: 3 command: su appsuser -c "/tmp/RapidInstall/bin/riwTDBup.sh /u05/appl/TEST/inst/apps/TEST_erp/ora/10.1.2/TEST_erp.env APPS/APPS"
riwTDBup.sh started at Fri May 25 06:43:16 IST 2012
Parameters passed are : /u05/appl/TEST/inst/apps/TEST_erp/ora/10.1.2/TEST_erp.env APPS/APPS
The environment settings are as follows ...
ORACLE_HOME : /u05/appl/TEST/apps/tech_st/10.1.2
ORACLE_SID :
TWO_TASK : TEST
PATH : /u05/appl/TEST/apps/tech_st/10.1.2/bin:/usr/bin:/usr/sbin:/u05/appl/TEST/apps/tech_st/10.1.3/appsutil/jdk/jre/bin:/usr/bin:/u05/Setup12.1.1/startCD/Disk1/rapidwiz/unzip/Linux:/usr/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin:/root/bin
LD_LIBRARY_PATH : /u05/appl/TEST/apps/tech_st/10.1.2/lib32:/u05/appl/TEST/apps/tech_st/10.1.2/lib:/usr/X11R6/lib:/usr/openwin/lib:/u05/appl/TEST/apps/tech_st/10.1.2/jdk/jre/lib/i386:/u05/appl/TEST/apps/tech_st/10.1.2/jdk/jre/lib/i386/server:/u05/appl/TEST/apps/tech_st/10.1.2/jdk/jre/lib/i386/native_threads:/u05/appl/TEST/apps/apps_st/appl/sht/12.0.0/lib
Executable : /u05/appl/TEST/apps/tech_st/10.1.2/bin/sqlplus
riwTDBup.sh exiting with status 2
RW-50011: Error: - Apps ORACLE_HOME connection test has returned an error: 2
Help Page
checking URL = http://erp.tez.co.in:8009/OA_HTML/help
RW-50015: Error: - Help Page is not responding. The service might not have started on the port yet. Please check the service and use the retry button.
HTTP
checking URL = http://erp.tez.co.in:8009
RW-50015: Error: - HTTP Listener is not responding. The service might not have started on the port yet. Please check the service and use the retry button.
JSP
checking URL = http://erp.tez.co.in:8009/OA_HTML/jtfTestCookie.jsp
RW-50015: Error: - JSP is not responding. The service might not have started on the port yet. Please check the service and use the retry button.
Login Page
RW-50015: Error: - Login Page is not responding. The service might not have started on the port yet. Please check the service and use the retry button.

Hi,
I think my linux was corrupted :(
I've done fresh linux installation and after that the R12 installation is complete without any issues :D
Thanks for you help Hussein Sir

Managed system configuration step 8: No Admin User Id provided for TS SID

Hello experts,
I face the following problem in step 8 of managed system configuration (Configure automatically, SolMan 7.1 SPS 3):
All Activities fail (except Activate services) with the following Details message:
No Admin User Id provided for TS <SID> (ABAP)
Any hint?
Thanks and best regards, Basti

Hi Sunny,
I don't find anything where I can provide the user information. It just uses the actual user (SOLMAN_ADMIN). Can you tell me where to provide the user for this step?
Managed system configuration -> step 8 Configure automatically -> SSO Setup
Thank you, Basti

What do I do when I am trying to install my new version of itunes, and it says this: The installer encountered errors before iTunes could be configured. Errors occurred during installation. Your system has not been modified.

What do I do when I am trying to install my new version of itunes, and it says this: The installer encountered errors before iTunes could be configured. Errors occurred during installation. Your system has not been modified.

I had this, and after a large number of fruitless attempts, I had to reload Windows, which solved it. This was of course a real pain, but I had to do it since updating iTunes was necessary in order to get the new iOS version. But before doing such a drastic thing, you could try to restore Windows to a previous point in time by picking a restore point. This of course presumes that you really have some issues with your Windows (which I had) and that you can make a decent guess on when the system was ok (which I couldn't), i.e that you can decide a good date to restore to.

Managed system Configuration : The JMX metrics of this Host / Byte Code Adapter are missing

Hi Friends
While Configuring EP system with SOLMAN 7.1 SP12 it is giving below message in self Diagnosis Phase.
1. Solman system is already having ISAGENT version 8 and 9 installed (but Managed system is having 8)
2. I have followed the automatic Process as below
==========================================
Automated Installation of the Introscope Agent via SMD
The Solution Manager provides an application that performs the setup of the Introscope
byte code agent for Java automatically. This section explains the steps to run the setup.
Before you can run the Introscope agent setup, the setup wizard for the managed system
must have been executed.
1.
2.
3.
4. Launch the Introscope Setup application: SAP Solution Manager Configuration 
Managed Systems Configuration  Step 7 Configure Automatically  Automatic
Activity “Byte Code Adapter Installation”  “Open Java URL” (only available in edit
mode). Your screen will look similar to the image below:
5. Check the Enterprise Manager Settings at the top of the screen. These are the
connection parameters that will be used by the agent to connect to the Enterprise
Manager.
6. In the pane Introscope Agent Setttings, select the system that you want to instrument
with the agent. Check “select all” and click “Retrieve Current Settings”. This will display
the current status of the agent setup.
7. To initially setup or update the agents, click Setup Introscope Agent …. This will open
the setup dialog as shown below. Select the desired agent version (by default only one
available) and choose the profile. Next, check the desired instrumentation areas, and,
in the case of AIX, review the AIX settings to match your environment (J9 or classic
mode).
8. Finally, hit Apply to perform the necessary changes in the agent configuration. Agent
config files will be adapted and the Java VM parameters will be set as required for the
managed system.
================================================================
3. Restarted SAP but error still present.
Please help to resolve the issue.
Thanks

Found the solution :
1819577 - Workload Analysis data missing for Java systems when using ISAGENT 8.2.4.0
Cause
l This issue has been identified as product defect and documented in note 1273028
Resolution
l As mentioned in note 1273028, update to ISAGENT 8.2.4 Patch 1 timestamp: 2012-06-26, please proceed as described below)
1. Enable the Maintenance Mode in the Agent Administration UI (http://solmanserver:port/smd/AgentAdmin)
2. Deploy the file to the Solution Manager JAVA stack using the Software Deployment Manager (SDM)
3. Disable the Maintenance Mode in the Agent Administration
4. Execute again the activity 'Byte Code Adapter Installation' of the step 'Configure Automatically' in the 'Managed System Configuration' for the
affected systems. This activity will deploy the new version of the
Introscope JAVA agent in the managed system servers and reconfigure the JVM parameters to use the new version of Introscope JAVA
Agent;
5. Check from Introscope Agent Admin if "IS Agent State" contains value "Running but needs restart"
6. Restart the affected managed system(s)
Finally Solution is update your SOLMAN system patch ISAGENT 8.2.4.0 from patch 0 to 1 via SDM.
Thanks
Mukesh

Installing Solaris 11 on SunFIre T1000 With Automated Installer Server Fail

h4. Hi
h4. A few days i am try to intall solaris 11 11/11 on our server Sunfire T1000
h4. we first upgrade the firmware of the server to
sc> showhost
Sun-Fire-T1000 System Firmware 6.7.12 2011/07/06 20:03
Host flash versions:
OBP 4.30.4.d 2011/07/06 14:27
Hypervisor 1.7.3.c 2010/07/09 15:14
POST 4.30.4.b 2010/07/09 14:25
h4. And after we install Solaris 11 x86 on a laptop, in that we configure an AIS (Automated installer Server)
installadm list
Service Name Alias Of Status Arch Image Path
default-sparc s11-sparc on Sparc /install/images/s11-sparc
s11-sparc - on Sparc /install/images/s11-sparc
h4. We are using the default installations with a DHCP server in the Laptop
installadm list -m -p
Service Name Manifest Status
default-sparc orig_default Default
s11-sparc orig_default Default
h4. By the other side, in the sparc server (T1000) we use OBP for a WAN Boot Installation
boot net:dhcp - installl
2012-08-08 20:33:44,911 InstallationLogger DEBUG Starting Automated Installation
2012-08-08 20:33:44,913 InstallationLogger INFO Using XML Manifest: /system/volatile/ai.xml
2012-08-08 20:33:44,965 InstallationLogger INFO Using profile specification: /system/volatile/profile
2012-08-08 20:33:45,018 InstallationLogger INFO Using service list file: /var/run/service_list
2012-08-08 20:33:45,070 InstallationLogger INFO Starting installation.
2012-08-08 20:33:45,122 InstallationLogger DEBUG Registering Manifest Parser Checkpoint
2012-08-08 20:33:45,124 InstallationLogger DEBUG Engine registering:
2012-08-08 20:33:45,126 InstallationLogger DEBUG name: manifest-parser
2012-08-08 20:33:45,128 InstallationLogger DEBUG module_path: solaris_install.manifest.parser
2012-08-08 20:33:45,129 InstallationLogger DEBUG checkpoint_class_name: ManifestParser
2012-08-08 20:33:45,131 InstallationLogger DEBUG args: None
2012-08-08 20:33:45,133 InstallationLogger DEBUG kwargs: {'call_xinclude': True, 'manifest': '/system/volatile/ai.xml', 'validate_from_docinfo': True}
2012-08-08 20:33:45,135 InstallationLogger DEBUG insert_before: None
2012-08-08 20:33:45,136 InstallationLogger DEBUG log_level: None
2012-08-08 20:33:45,138 InstallationLogger DEBUG =============================
2012-08-08 20:33:45,142 InstallationLogger DEBUG Current checkpoint list:
2012-08-08 20:33:45,144 InstallationLogger DEBUG      manifest-parser
2012-08-08 20:33:45,146 InstallationLogger DEBUG Executing Manifest Parser Checkpoint
2012-08-08 20:33:45,148 InstallationLogger DEBUG Retrieving checkpoint list from manifest-parser to None+
2012-08-08 20:33:45,150 InstallationLogger DEBUG Executing Engine Checkpoints...+
2012-08-08 20:33:45,152 InstallationLogger DEBUG Retrieving checkpoint list from manifest-parser to None+
2012-08-08 20:33:45,154 InstallationLogger DEBUG Engine will be executing following checkpoints:+
2012-08-08 20:33:45,155 InstallationLogger DEBUG      manifest-parser
2012-08-08 20:33:45,157 InstallationLogger DEBUG Spawning InstallEngine execution thread
2012-08-08 20:33:45,160 InstallationLogger DEBUG Loading manifest-parser checkpoint
2012-08-08 20:33:45,213 InstallationLogger.manifest-parser DEBUG Initializing ManifestParser (manifest=/system/volatile/ai.xml, Validate_from_docinfo=True, dtd_file=None, load_defaults=True, call_xinclude=True)
2012-08-08 20:33:45,273 InstallationLogger DEBUG manifest-parser: prog est-1, prog ratio-0.95, total_ratio-1.00
2012-08-08 20:33:45,275 InstallationLogger DEBUG Last checkpoint, manifest-parser: prog ratio 0.95
2012-08-08 20:33:45,279 InstallationLogger DEBUG Snapshotting DOC to /var/run/install_engine/engine.MYk67H/.data_cache.manifest-parser
2012-08-08 20:33:45,286 InstallationLogger DEBUG Executing manifest-parser checkpoint
2012-08-08 20:33:45,288 InstallationLogger.manifest-parser DEBUG ManifestParser.execute(dry_run=False) called
2012-08-08 20:33:45,290 InstallationLogger.manifest-parser DEBUG ManifestParser.parse(doc=-> [DataObjectCache] (<solaris_install.data_object.cache.DataObjectCache object at 0xee1b90>)
     -> [persistent] (DataObjectCacheChild: persistent)
          -> [auto-install] (<solaris_install.ApplicationData object at 0xee1030>)
     -> [volatile] (DataObjectCacheChild: volatile)
          -> [apply_sysconfig_dict] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee1050>)) called
2012-08-08 20:33:45,292 InstallationLogger.manifest-parser DEBUG loading manifest (dtd_validation=True)
2012-08-08 20:33:45,872 InstallationLogger.manifest-parser DEBUG Parsed XML document:
<!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd.1">
<auto_install>
<ai_instance name="orig_default" auto_reboot="false">
<target>
<logical noswap="false" nodump="false">
<zpool name="rpool" is_root="true" action="create">
<filesystem name="export" mountpoint="/export" action="create" in_be="false"/>
<filesystem name="export/home" action="create" in_be="false"/>
<be name="solaris"/>
</zpool>
</logical>
</target>
<software type="IPS">
<destination>
<image action="create" index="false">

<facet set="false">facet.locale.*</facet>
<facet set="true">facet.locale.en</facet>
<facet set="true">facet.locale.en_US</facet>
<facet set="true">facet.locale.es</facet>
<facet set="true">facet.locale.es_ES</facet>
</image>
</destination>
<source>
<publisher name="solaris">
<origin name="http://pkg.oracle.com/solaris/release"/>
</publisher>
</source>
h4. When the installation precess is in this part
13% target-selection completed.
17% ai-configuration completed.
19% target-instantiation completed.
19% Beginning IPS transfer
Creating IPS image
Installing packages from:
solaris
origin: http://pkg.example.com/solaris/
h4. in the install_log file show us this errors:
2012-08-08 20:51:39,653 InstallationLogger.generated-transfer-1184-1 DEBUG Download: text/doctools ...
2012-08-08 20:51:43,156 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/core-os ...
2012-08-08 20:52:03,704 InstallationLogger.generated-transfer-1184-1 DEBUG Download: text/less ...
2012-08-08 20:52:03,788 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/management/rad/module/rad-smf ...
2012-08-08 20:52:03,835 InstallationLogger.generated-transfer-1184-1 DEBUG Download: system/library ...
2012-08-08 20:52:30,609 InstallationLogger.generated-transfer-1184-1 DEBUG Cleaning up
2012-08-08 20:52:30,611 InstallationLogger ERROR Error occurred during execution of 'generated-transfer-1184-1' checkpoint.
Traceback (most recent call last):
File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", line 811, in executecheckpoints
checkpoint.execute(dry_run)
File "/usr/lib/python2.6/vendor-packages/solaris_install/transfer/ips.py", line 359, in execute
self._transfer()
File "/usr/lib/python2.6/vendor-packages/solaris_install/transfer/ips.py", line 639, in _transfer
self.api_inst.prepare()
File "/usr/lib/python2.6/vendor-packages/pkg/client/api.py", line 2021, in prepare
self._img.imageplan.preexecute()
File "/usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py", line 2827, in preexecute
p.download()
File "/usr/lib/python2.6/vendor-packages/pkg/client/pkgplan.py", line 406, in download
mfile.wait_files()
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 2857, in wait_files
self._transport._get_files(self)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 432, in wrapper
return f(instance, fargs, *f_kwargs)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 1736, in getfiles
self._get_files_list(mfile, filelist)
File "/usr/lib/python2.6/vendor-packages/pkg/client/transport/transport.py", line 1685, in getfiles_list
raise tfailurex
TransportFailures: 1: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 7558caebcb4a599c08c6a1b1591672f2b3b3cb06.
2: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: c8edd4ff7e100c83ad74ba75a9baeda47348800c.
3: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 91350cb5e1dc88dbbcf2e94e0a05b075f03ba35b.
4: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 85bec186fd71c8a072cb3261aac5a2d26e0bed01.
5: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: feaf36a0752e78974e4cdbd757a2af9dd5f94236.
6: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 93adf874561a2c2e383fa55da1f23cc93f1b24b5.
7: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 5c261f9705a8c604bf3f473f1d76c7f646cedc60.
8: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 81fa4733fa459a553001f8fdf30f49e35067a5ea.
2012-08-08 20:52:30,731 InstallationLogger DEBUG Checkpoints Completed: DOC:+
-> [DataObjectCache] (<solaris_install.data_object.cache.DataObjectCache object at 0xee1b90>)+
     -> [persistent] (DataObjectCacheChild: persistent)+
          -> [auto-install] (<solaris_install.ApplicationData object at 0xee1030>)+
          -> [Engine-DOC-Root-Node] (<solaris_install.engine.EngineData object at 0xecc930>)+
               -> [manifest-parser] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee10d0>)+
               -> [target-discovery] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1230>)+
               -> [target-selection] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee12f0>)+
               -> [ai-configuration] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1410>)+
               -> [var-shared-dataset] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1c30>)+
               -> [target-instantiation] (<solaris_install.engine.checkpoint_data.CheckpointRegistrationData object at 0xee1750>)+
          -> [discovered] (<solaris_install.target.Target object at 0xee1330>)+
               -> [disk] (Disk: ctd=c2t0d0; volid=None; devpath=/pci@7c0/pci@0/pci@8/scsi@2/sd@0,0; devid=id1,sd@n5000cca334c724bf; prop:dev_type=scsi; prop:dev_vendor=HITACHI; prop:dev_size=148.99gb; keyword: key=boot_disk; is_cdrom=False; label=VTOC; whole_disk=False; write_cache=False)+
                    -> [0] (Slice: name=0; action=preserve, force=False, is_swap=False, tag=2, flag=0, in_use={'used_by': ['exported_zpool'], 'used_name': ['rpool']}; size=148.99gb; start_sector=4768)+
                    -> [2] (Slice: name=2; action=preserve, force=False, is_swap=False, tag=5, flag=1; size=148.99gb; start_sector=0)+
               -> [logical] (Logical: noswap=True; nodump=True)+
          -> [desired] (<solaris_install.target.Target object at 0xede3f0>)+
               -> [logical] (Logical: noswap=False; nodump=False)+
                    -> [rpool] (Zpool: name=rpool; action=create; is_root=True; vdev_list=['c2t0d0s0'])+
                         -> [export] (Filesystem: name=export; action=create; mountpoint=/export)+
                         -> [export/home] (Filesystem: name=export/home; action=create)+
                         -> [solaris] (BE: name=solaris; mountpoint=/a)+
                         -> [vdev] (Vdev: name=vdev; redundancy=none)+
                         -> [swap] (Zvol: name=swap; action=create; use=swap; size=1024m)+
                         -> [dump] (Zvol: name=dump; action=create; use=dump; size=512m)+
                         -> [var] (Filesystem: name=var; action=create; mountpoint=/var)+
               -> [disk] (Disk: ctd=c2t0d0; volid=None; devpath=/pci@7c0/pci@0/pci@8/scsi@2/sd@0,0; devid=id1,sd@n5000cca334c724bf; prop:dev_type=scsi; prop:dev_vendor=HITACHI; prop:dev_size=148.99gb; keyword: key=boot_disk; is_cdrom=False; label=VTOC; whole_disk=False; write_cache=True)+
                    -> [0] (Slice: name=0; action=create, force=True, is_swap=False, tag=2, flag=0; in_zpool=rpool; in_vdev=vdev; size=148.99gb; start_sector=4768)+
     -> [volatile] (DataObjectCacheChild: volatile)+
          -> [apply_sysconfig_dict] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee1050>)+
          -> [orig_default] (ai_instance: name='orig_default' auto_reboot=False; http_proxy='None')+
               -> [target] (<solaris_install.target.Target object at 0xee1d30>)+
                    -> [logical] (Logical: noswap=False; nodump=False)+
                         -> [rpool] (Zpool: name=rpool; action=create; is_root=True; vdev_list=[None])+
                              -> [export] (Filesystem: name=export; action=create; mountpoint=/export)+
                              -> [export/home] (Filesystem: name=export/home; action=create)+
                              -> [solaris] (BE: name=solaris)+
               -> [generated-transfer-1184-1] (<solaris_install.transfer.info.Software object at 0xee1f30>)+
                    -> [transfer] (<solaris_install.transfer.info.IPSSpec object at 0xecc050>)+
                    -> [destination] (<solaris_install.transfer.info.Destination object at 0xecc0b0>)+
                         -> [image] (<solaris_install.transfer.info.Image object at 0xecc130>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc150>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc1b0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc210>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc270>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc2d0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc330>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc390>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc3f0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc450>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc4b0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc510>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc570>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc5d0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc630>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc690>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc6f0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc750>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc7b0>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc810>)+
                              -> [facet] (<solaris_install.transfer.info.Facet object at 0xecc870>)+
                              -> [img_type] (<solaris_install.transfer.info.ImType object at 0xee1b70>)+
                    -> [source] (<solaris_install.transfer.info.Source object at 0xecc8b0>)+
                         -> [publisher] (<solaris_install.transfer.info.Publisher object at 0xecc8f0>)+
                              -> [origin] (<solaris_install.transfer.info.Origin object at 0xecc910>)+
          -> [transfer-zpool-cache] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee18f0>)+
          -> [transfer-ai-files] (<solaris_install.data_object.data_dict.DataObjectDict object at 0xee15b0>)+
2012-08-08 20:52:30,747 InstallationLogger DEBUG Checkpoints Completed: DOC (xml_format):
<root>
<target name="discovered">
<disk whole_disk="false">
<disk_name name="c2t0d0" name_type="ctd"/>
<disk_prop dev_type="scsi" dev_vendor="HITACHI" dev_size="312461344secs"/>
<disk_keyword key="boot_disk"/>
<slice name="0" action="preserve" force="false" is_swap="false">
<size val="312456576secs" start_sector="4768"/>
</slice>
<slice name="2" action="preserve" force="false" is_swap="false">
<size val="312461344secs" start_sector="0"/>
</slice>
</disk>
<logical noswap="true" nodump="true"/>+
</target>+
<target name="desired">+
<logical noswap="false" nodump="false">+
<zpool name="rpool" action="create" is_root="true">+
<filesystem name="export" action="create" mountpoint="/export" in_be="false"/>+
<filesystem name="export/home" action="create" in_be="false"/>+
<be name="solaris"/>+
<vdev name="vdev" redundancy="none"/>+
<zvol name="swap" action="create" use="swap">+
<size val="1024m"/>+
</zvol>+
<zvol name="dump" action="create" use="dump">+
<size val="512m"/>+
</zvol>+
<filesystem name="var" action="create" mountpoint="/var" in_be="true"/>+
</zpool>+
</logical>+
<disk whole_disk="false">+
<disk_name name="c2t0d0" name_type="ctd"/>+
<disk_prop dev_type="scsi" dev_vendor="HITACHI" dev_size="312461344secs"/>+
<disk_keyword key="boot_disk"/>+
<slice name="0" action="create" force="true" is_swap="false" in_zpool="rpool" in_vdev="vdev">+
<size val="312456576secs" start_sector="4768"/>+
</slice>+
</disk>+
</target>+
<ai_instance auto_reboot="false" name="orig_default">+
<target>+
<logical noswap="false" nodump="false">+
<zpool name="rpool" action="create" is_root="true">+
<filesystem name="export" action="create" mountpoint="/export" in_be="false"/>+
<filesystem name="export/home" action="create" in_be="false"/>+
<be name="solaris"/>+
</zpool>+
</logical>+
</target>+
<software name="generated-transfer-1184-1" type="IPS">+
<software_data>+
<name>pkg:/entire@latest</name>+
<name>pkg:/group/system/solaris-large-server</name>+
</software_data>
<destination>
<image img_root="/a" action="create" index="False">
<facet set="false">facet.locale.*</facet>
<facet set="true">facet.locale.en</facet>
<facet set="true">facet.locale.en_US</facet>
<facet set="true">facet.locale.es</facet>
<facet set="true">facet.locale.es_ES</facet>
</image>
</destination>
<source>
<publisher name="solaris">
<origin name="http://pkg.oracle.com/solaris/release"/>
</publisher>
</source>
</software>
</ai_instance>
</root>
2012-08-08 20:52:30,749 InstallationLogger CRITICAL Failed Checkpoints:
2012-08-08 20:52:30,803 InstallationLogger ERROR
2012-08-08 20:52:30,855 InstallationLogger ERROR generated-transfer-1184-1
2012-08-08 20:52:30,907 InstallationLogger ERROR
2012-08-08 20:52:30,960 InstallationLogger ERROR Checkpoint execution error:
2012-08-08 20:52:31,012 InstallationLogger ERROR
2012-08-08 20:52:31,064 InstallationLogger ERROR 1: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 7558caebcb4a599c08c6a1b1591672f2b3b3cb06.
2012-08-08 20:52:31,117 InstallationLogger ERROR 2: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: c8edd4ff7e100c83ad74ba75a9baeda47348800c.
2012-08-08 20:52:31,169 InstallationLogger ERROR 3: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 91350cb5e1dc88dbbcf2e94e0a05b075f03ba35b.
2012-08-08 20:52:31,222 InstallationLogger ERROR 4: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 85bec186fd71c8a072cb3261aac5a2d26e0bed01.
2012-08-08 20:52:31,274 InstallationLogger ERROR 5: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: feaf36a0752e78974e4cdbd757a2af9dd5f94236.
2012-08-08 20:52:31,326 InstallationLogger ERROR 6: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 93adf874561a2c2e383fa55da1f23cc93f1b24b5.
2012-08-08 20:52:31,379 InstallationLogger ERROR 7: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 5c261f9705a8c604bf3f473f1d76c7f646cedc60.
2012-08-08 20:52:31,431 InstallationLogger ERROR 8: Invalid contentpath usr/share/man/man3dlpi/dlpi_send.3dlpi: chash failure: expected: 74354376b4382a6ccdc566157c6ad82892aa0679 computed: 81fa4733fa459a553001f8fdf30f49e35067a5ea.
2012-08-08 20:52:31,484 InstallationLogger ERROR
2012-08-08 20:52:31,536 InstallationLogger INFO Automated Installation Failed. See install log at /system/volatile/install_log
2012-08-08 20:52:31,588 InstallationLogger DEBUG Shutting down Progress Handler
h4. Is something about:
2012-08-08 20:52:30,611 InstallationLogger ERROR Error occurred during execution of 'generated-transfer-1184-1' checkpoint.
Traceback (most recent call last):
File "/usr/lib/python2.6/vendor-packages/solaris_install/engine/__init__.py", line 811, in executecheckpoints
checkpoint.execute(dry_run)
2012-08-08 20:52:30,749 InstallationLogger CRITICAL Failed Checkpoints:
2012-08-08 20:52:30,803 InstallationLogger ERROR
2012-08-08 20:52:30,855 InstallationLogger ERROR generated-transfer-1184-1
2012-08-08 20:52:30,907 InstallationLogger ERROR
2012-08-08 20:52:30,960 InstallationLogger ERROR Checkpoint execution error:
h4. Somebody knows about this error?

The chash failures indicate that either the repository you're using has corrupt content for those files, or the files are being corrupted on download. The latter is more likely, usually a result of badly-behaved http proxies.

Creating FRCommon system failed - in 11g Forms & Report Installation

Dear all,
When installing 11g Forms and Reports "*Creating FRCommon system failed - in 11g Forms & Report Installation*".
I have successfully created the weblogic server 10.3.5 , and continued with 11g forms & reports. First Installed the forms & reports software, and i try to configure. after several steps of configuration i have failed when its place "*Creating FRCommon system failed - in 11g Forms & Report Installation*".
What it is this Error.
Kindly help me.
My OS Windows
Forms and reports 11gR2
More info
When i start the configuration i have chosen Forms & Reports server and Development tools in the configuration page along with OHS.
Regards
Hamid

Hi experts,
I have the same problem when I try to install oracle Fusion Middleware 11g, is it possible that I forget some steps before, or should I install required something before continue intallation?
Best Regards.
Karim.

Problems With System Configuration

System Configuration is altered and not repairable. Selective startup is persistent. Normal startup is selected, but the Apply button is greyed out, inaccessible, and system always remains in Selective startup. As a result, Current User profile is probably
corrupted. Windows Store will not install (services are corrupt, SFC and DISM did not work). Outlook profile was deleted, needed to be reinstalled, and can not receive mail. Excel math engine totals values higher than actual amounts. IE automatically signs
into all Microsoft accounts (reset to default settings worked for a log on, but automatic sign in resumed afterwards).
Are there any solutions?
Office diagnostics produced the following report.
Diagnostic Results
None of the Microsoft Office Diagnostics found any problems.
More resources
Setup Diagnostic — File corruption or altered file
The Setup Diagnostic repaired problems with your installation of Microsoft Office. Your Microsoft Office programs should now function correctly.
If your Microsoft Office programs continue to crash, the source of the problem may be a hardware failure or hardware configuration problem. Review the results of the Disk and Memory Diagnostics to determine if a hardware failure is affecting your installation
of the 2007 Office release.
More resources
Setup Diagnostic — Missing media
The Setup Diagnostic was not completed because a valid source was not found. Either the local installation source is missing, or the original source that was used to install Microsoft Office is not available to the repair process. You may need to provide
the original source to allow this diagnostic to run successfully. Valid sources for the 2007 Office release include the following:
Your 2007 Office release installation CD
An installation disk or repair CD provided by the vendor of your computer
A connection to a network installation of the 2007 Office release
After you obtain access to a valid source, run Office Diagnostics again.
More resources
Disk Diagnostic — Failure of hard disk predicted
The Self-Monitoring, Analysis, and Reporting Technology (SMART) feature of your hard disk has found errors that may indicate that the hard disk is likely to fail. SMART is a feature that some disk drive manufacturers provide to give users advance notice
of potential hard disk failure. Instability in your Microsoft Office programs may be the result of these hard disk drive errors.
Note This result can indicate a severe problem, but some hard disks may not accurately report their results.
We recommend that you do the following:
1.Back up your important data immediately.
2.Check the results of other diagnostics, and follow the instructions for resolving any issues that the other diagnostics have reported. After you resolve those issues, run Microsoft Office Diagnostics again to see if this Disk Diagnostic issue is resolved.
3.If you continue to get this result, contact someone, such as the vendor of your computer or hard disk.
More resources
Disk Diagnostic — Errors in system event log
The Disk Diagnostic found evidence of hardware errors. Instability in your Microsoft Office programs may be the result of these hardware errors.
This result occurs if one of the following has happened recently:
The Self-Monitoring, Analysis, and Reporting Technology (SMART) feature of your hard disk has found errors. SMART is a feature that some disk drive manufacturers provide to give users advance notice of potential hard disk failure.
Microsoft Office Diagnostics has found blocked-out (failed) sectors on your hard disk.
Microsoft Office has had trouble accessing files from the hard disk; it needs these files to function properly.
We recommend that you do the following:
1.Check the results of other diagnostics, and follow the instructions for resolving any issues that the diagnostics have reported. After you resolve those issues, run Microsoft Office Diagnostics again to see if this Disk Diagnostic issue is resolved.
2.If you continue to get this result, contact someone, such as the vendor of your computer or hard disk.
More resources
Memory Diagnostic — RAM failure
The Memory Diagnostic found evidence of failure in the random access memory (RAM).
We recommend that you do the following:
1.Check the results of other diagnostics, and follow the instructions for resolving any issues that the diagnostics have reported. After you resolve those issues, run Microsoft Office Diagnostics again to see if this Memory Diagnostic issue is resolved.
2.If you continue to get this result, do either of the following:
Run a Microsoft Windows memory diagnostic. For more information, see the following:
Windows Vista How do I know if my computer has a memory problem?
Microsoft Windows XP Windows Memory Diagnostic
Contact someone, such as the vendor of your computer or RAM.
More resources
Memory Diagnostic — User is not an administrator
The Memory Diagnostic was unable to run because you do not have administrative rights on this computer. To successfully run the Memory Diagnostic, someone with administrative rights must log on to this computer and run Microsoft Office Diagnostics.
More resources
Update Diagnostic — Installation is out of date
The Update Diagnostic determined that your installation of Microsoft Office does not have the latest service packs installed. Installing service packs improves stability. We recommend that you visit Downloads on Microsoft Office Online, and then, under Office
Update, click Check for Updates.
More resources
Compatibility Diagnostic — Conflicting versions of Outlook found
The Compatibility Diagnostic identified conflicting versions of Microsoft Office Outlook. To remove the version of Outlook from your computer that you do not want, do the following:
Microsoft Windows Vista
1.Click the Start button, and then click Control Panel.
2.Click Uninstall a program.
Note In Classic view, double-click Programs and Features.
3.Select the version of Outlook that you do not want, and then click Uninstall.
Microsoft Windows XP
1.Click Start, and then click Control Panel.
2.Double-click Add or Remove Programs.
3.Select the version of Outlook that you do not want, and then click Remove.
More resources

Check disk and memory diagnostics found no errors.
SFC and DISM listed errors when performed in diagnostic start up. Commands changed from previous attempts. Before SFC and DISM only had to be entered as SFC and DISM. Presently, additional commands are required.
Log Name:      Microsoft-Windows-MemoryDiagnostics-Results/Debug
Source:        Microsoft-Windows-MemoryDiagnostics-Results
Date:          8/21/2014 12:51:09 PM
Event ID:      2001
Task Category: None
Level:         Information
Keywords:
User:          SYSTEM
Computer:      TAS
Description:
Windows Memory Diagnostic results
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5F92BC59-248F-4111-86A9-E393E12C6139}" />
    <EventID>2001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-08-21T16:51:09.612555200Z" />
    <EventRecordID>1</EventRecordID>
    <Correlation />
    <Execution ProcessID="5296" ThreadID="5300" />
    <Channel>Microsoft-Windows-MemoryDiagnostics-Results/Debug</Channel>
    <Computer>TAS</Computer>
    <Security UserID="S-1-5-18" />
</System>
<UserData>
    <Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
      <MemDiagRawData>89170000000000000200000003000000050000000A000000D80300000C0000000200000000000000964017005B090000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C800000000000000707E748DCE00000001000000C800000000000000C8000000000000000C00000038000000DE07080015000C001E00200000000700964017005B09000001000020000001000C00010000000000020001001E00010000000000040001004200010000000000060001002E0001000000000001000100660001000000000003000100EC00010000000000000001000D00020000000000020001001D00020000000000040001004200020000000000060001002F0002000000000001000100650002000000000003000100EC00020000000000</MemDiagRawData>
    </Results>
</UserData>
</Event>
Windows Resource Protection could not start the repair service.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>DISM
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
DISM.exe [dism_options] {Imaging_command} [<Imaging_arguments>]
DISM.exe {/Image:<path_to_offline_image> | /Online} [dism_options]
         {servicing_command} [<servicing_arguments>]
DESCRIPTION:
DISM enumerates, installs, uninstalls, configures, and updates features
and packages in Windows images. The commands that are available depend
on the image being serviced and whether the image is offline or running.
GENERIC IMAGING COMMANDS:
/Get-MountedImageInfo   - Displays information about mounted WIM and VHD images.
/Get-ImageInfo          - Displays information about images in a WIM or VHD file.
/Commit-Image           - Saves changes to a mounted WIM or VHD image.
/Unmount-Image          - Unmounts a mounted WIM or VHD image.
/Mount-Image            - Mounts an image from a WIM or VHD file.
/Remount-Image          - Recovers an orphaned image mount directory.
/Cleanup-Mountpoints    - Deletes resources associated with corrupted mounted images.
WIM COMMANDS:
/Capture-CustomImage    - Captures customizations into a delta WIM file on a WIM Boot system. Captured directories include all subfolders and data.
/Get-WIMBootEntry       - Displays WIMBoot configuration entries for the specified disk volume.
/Update-WIMBootEntry    - Updates WIMBoot configuration entry for the specified disk volume.
/List-Image             - Displays a list of the files and folders in a
                            specified image.
/Delete-Image           - Deletes the specified volume image from a WIM file
                            that has multiple volume images.
/Split-Image            - Splits an existing .wim file into multiple
                            read-only split WIM (SWM) files.
/Export-Image           - Exports a copy of the specified image to another
                            file.
/Append-Image           - Adds another image to a WIM file.
/Capture-Image          - Captures an image of a drive into a new WIM file. Captured directories include all subfolders and data.
/Apply-Image            - Applies an image.
/Get-MountedWimInfo     - Displays information about mounted WIM images.
/Get-WimInfo            - Displays information about images in a WIM file.
/Commit-Wim             - Saves changes to a mounted WIM image.
/Unmount-Wim            - Unmounts a mounted WIM image.
/Mount-Wim              - Mounts an image from a WIM file.
/Remount-Wim            - Recovers an orphaned WIM mount directory.
/Cleanup-Wim            - Deletes resources associated with mounted WIM images that are corrupted.
IMAGE SPECIFICATIONS:
/Online                 - Targets the running operating system.
/Image                  - Specifies the path to the root directory of an offline Windows image.
DISM OPTIONS:
/English                - Displays command line output in English.
/Format                 - Specifies the report output format.
/WinDir                 - Specifies the path to the Windows directory.
/SysDriveDir            - Specifies the path to the system-loader file named BootMgr.
/LogPath                - Specifies the logfile path.
/LogLevel               - Specifies the output level shown in the log (1-4).
/NoRestart              - Suppresses automatic reboots and reboot prompts.
/Quiet                  - Suppresses all output except for error messages.
/ScratchDir             - Specifies the path to a scratch directory.
For more information about these DISM options and their arguments, specify an option immediately before /?.
Examples:
    DISM.exe /Mount-Wim /?
    DISM.exe /ScratchDir /?
    DISM.exe /Image:C:\test\offline /?
    DISM.exe /Online /?
C:\WINDOWS\system32>DISM.exe /English
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Error: 1639
No DISM options were specified on the command-line.
Run DISM with a command-line option specified, such as /Image or /Online. For more information, refer to the help by running DISM.exe /?.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

7.2 Trial: Assign Provider system to service group

Hi Experts,
I've created a BPM with an automated activity that shall call a web service provided by a CAF application (everything takes place on a CE 7.2 Trial server).
In WS navigator the CAF web service works.
In my BPM the process always gets stuck in the autmated activity (without any error message).
Now I've tried to setup some system configurations:
1. Creating provider system (in SOA Management/Technical Configuration/System connections)
The communication profile is SAP_DEFAULT_PROFILE, the service source is the service registry.
Pinging the system works, so I guess that it's ok.
2. Setting up the application communication (in SOA Management/Application and Scenario Communication/Application Communication):
There I have to Software components in the list: a) testblcafear and b)testpr~pm
For a) I've assigned SAP_DEFAULT_PROFILE as profile
For b) I tried to add the provider system to the service group, but after saving I always get a red light and the following log message:
Configuration of logical ports for [test_SG] Service Group failed with [
Service [TestService] not found in the registry publications for the assigned provider [CE1 on pcccsn103]. Check if the service is published in the Services Registry. Check if the system SLD ID for the service publication matches the System SLD ID for the assigned provider. Provider System SLD ID: [CE1.SystemHome.pcccsn103.Java]
Service Group:[test_SG]
Service Group application: [test.com/travelmanagementprpm]
Service Reference application: [test.com/travelmanagementprpm]
Configuration Scenarion: [COMPOSITE_APPLICATIONS_CONFIGURATION_SCENARIO]
] error. For more information refer to the trace with ID [001EC96B0BCF00070000005D00001670]. Details: [CE1.SystemHome.pcccsn103.Java] provider system, [test.com/testprpm] Service Group application
The service is in the SR, I can see it under SR/service definitions.
How can it be that the SLD ID is different for provider and and receiver? In both cases it's the same system!
I've checked our SLD and we don't have a system number (because it's a trial license). Could that be the reason?
Thanks in advance!

Hi Sowmya
Say me one think, do you use a trial version of CE?
I have the same problem with the trial version. However, today I've deployed my application in a official released version of CE, and this error don't occur. Maybe this is an error of trial version.
Regards
Marcos.

Smsy "Read System Number" customer number unknown for installation

Hi gurus,
I 'm configuring SMSY and following the steps outlined in the IMG in the basic settings and trying to configure RFC connections to/from satellite systems. In SMSY, I have 2 systems configured SMA and BIF.
tcode SMSY-> Systems -> SAP ERP -> SMA , Tab "System Data in SAP Support Portal".
Click "Read System Number" returns error SAP customer number unknown for installation number 0020179718. <-Why?
Click "Installation Data" shows data from SMP with correct installation number and correct customer number 706822.
      The S-user listed under "Contact Persons" is not mine, not the correct one. <- Why? How to fix?
      The system number from SMP matches value in System Number field.
Click "System Data" shows data from SMP also shows correct data.
Why unable to "Read System Number" when the correct system number is read via "Installation Data" and "System Data"?
tcode SMSY->Systems->SAP ECC->BIF, Tab "System Data in SAP Support Portal".
Click "Read System Number" returns error "SAP customer number unknown for installation number 0020472810". <- Why?
Click "Installation Data" shows data from SMP with correct installation number and correct customer number 706822.
      The S-user listed under "Contact Persons" is correct one.
      The system number from SMP matches value in System Number field.
Click "System Data" shows data from SMP also shows correct data.
Why unable to read system number?
When I login to SMP with same S-user, under System Data Maintenance, the same data is displayed as in "Installation Data" and "System Data" links.

I don't know what happened. I came into work today and tested the "Read System Number" and it worked. I read thru the 2 notes you mentioned, just read now. The first notes I had already followed before opening this thread. The 2nd notes also talked about turning off BAdI implementation AI_SDK_SP_RFC_RP, of which I did a couple of days ago before opening this thread. I had turned turned off BAdI and simplified the AISUSER table and removed the customer number field, in order to get back to the "single-user number" basic setup in the IMG.
I had found the problem with the wrong contact info on the SMA system. It was wrong in the SMP system maintenance under installation data.
Thanks for your help.
-Don.

SolMan 7.1 SP10: Managed Systems Configuration: client 000 OK, client 100 error

Hello,
after installing SolMan 7.1 SP10 successfully I also completed the steps "System Preparation" and "Basic Configuration".
Now I'm connecting the managed ABAP systems to the Solution Manager by performing step "Managed Systems Configuration".
After several other ABAP systems I'm now connecting our productive CRM 7.0 EHP1 system "CM3" (SAP_BASIS 702).
I also connected the CRM development and CRM quality assurance system without a problem.
For client 000 everything worked fine, the RFC destinations were created and a green light is shown.
Now the problem is to connect the productive client 100:
The log for Activity RFC Connection says:
The corresponding dev_rfc tracefile says:
**** Trace file opened at 20140326 164911 W. Europe Standard Time, by disp+work
**** Versions SAP-REL 720,0,523 RFC-VER U 3 1468763 MT-SL
======> Name oder Kennwort ist nicht korrekt (Wiederholen Sie die Anmeldung)
ABAP Programm: SAPLSM_SETUP_API (Transaction: )
Called function module: FUNCTION_EXISTS
User: SOLMAN_ADMIN (Client: 001)
Destination: 0050568713C71ED3AD9FC4F78AC9D9EB (Handle: 16, DtConId: 27FEB4E356BCF14F99EB0050568713C7, DtConCnt: 1, ConvId: 64734943,{27FEB4E3-56BC-F14F-99EB-0050568713C7})
EPP RootContextId: 0050568713C71ED3AD9FB7AD4C4859EB, ConnectionId: 0050568713C71ED3AD9FB784232C59EB, ConnectionCnt: 1
EPP TransactionId: BDFDB4E3626AF14899EB0050568713C7
But both users taken to execute this step (SAP Solution Manager Administrator "SOLMAN_ADMIN" and Managed System Configuration User "SM_ADMIN_SM3") exist and have the correct provided password.
Does anyone have a clue?
Kind regards
Rüdiger Höckel

Hello Ranjith,
thanks for your quick response.
The ST-A/PI software component is the same on all systems: 01Q_700 #2.
SolMan system: SM3
CRM systems: CM0 (ok), CM1 (ok), CM3 (problem with client 100, client 000 OK).
I also tried the recommendation found in the SAP Community Network
(http://scn.sap.com/thread/3483642) but this didn't help either:
1.Delete system from LMDB.
2.Delete system from SLD of solman.
3.Re- register the system to SLD of solman(rz70 for AS ABAP)
[the LMDB synchronizes with the SLD every 10 minutes, system CM3 is visible again in the LMDB]
4.Now follow the steps in managed system configuration.
The wizard worked fine for client 000 but throws this error for client 100.
I use all the latest installation and configuration guides.
For this step I'm using the guide "Managed System Configuration" that is available in the SOLMAN_SETUP wiki.
https://websmp206.sap-ag.de/~sapidb/011000358700001120342013E.pdf
Kind regards
Rüdiger
P.S. In total I have already connected eight systems (SAP_BASIS 700 to 731) but this is the first system that gives an error.

Providing system configuration info in an automated installer manifest.

Similar Messages

Maybe you are looking for