System configuration for ITS and for BSP

Hi,
I´m looking for the parameters needed in a system to connect to an ITS and also to BSP.
I have created one system to be able to connect to ITS and another one to be able con connect to BSP, both of type SAP Load Balancing system.
The system I created to connect to ITS has the following configuration I entered:
Connector:
SAP Client = 350
Internet Transaction Server (ITS)
ITS Description = myDescription
ITS Host Name = myhostname:port
ITS Path = /sap/bc/gui/sap/its/webgui
ITS Protocol = http
Thats it that´s the only configuration I´ve made.
For the BSP system I entered:
Connector:
SAP Client = 800
Web Application Server (Web AS):
Web AS Description = myDescription
Web AS Host Name = myhostname:port
Web AS Path = /sap/bc/bsp/sap
Web AS Protocol = http
My question is this, is this configutation enough?,
It is working fine with this configuration but I´ve seen some other information where they fill more parameters in the  connector section, would this extra parameters in the connector section help in any way or they will just simply be ignored?, We will be using Web Dispatcher for both.
does somebody knows the answer? Is there some documentation on this?
Thanx in Advanced!!
Kind Regards,
Gerardo J

The connector properties are only required if you are planning on utilizing the SAP connector to connect to your backend system.
What you have configured so far should suffice for ITS and BSP applications. I hope you have configured the system aliases already.
Have a look at the following links for some additional inputs:
http://wiki.sdn.sap.com/wiki/display/EP/MinimumSettingsforaSystem
http://wiki.sdn.sap.com/wiki/display/EP/HowtoCreateSystemObjectinthePortalforConnectingtoSAPbackend+System
- Shanti

Similar Messages

  • Managed System configuration for SAP NW Java system in Solution Manager 7.1 SP10

    Hi All,
    I am doing Managed system configuration for my SAP NW 7.01 Java system and getting below error in step 6 create users SAPSUPPORT & SM_COLL_SID.
    "An unexpected error occured. An error occured while processing the UME command READ_USER from agent <hostname> : Server returned: 302 Found "
    I have checked my DAA as well as host agents are up and running fine. My Solution Manager is 7.1SP10.
    Please suggest.
    Regards,
    Manish

    Manish,
    Which UME you are using? portal/ABAP/LDAP
    Are you using the SOLMAN_ADMIN user while configuring.
    Also check the below forum.
    https://scn.sap.com/thread/1167282
    Regards,
    Raja. G

  • Online systems configured for newbies to experiment

    Why does SDN not have online systems configured for newbies to experiment online.
    Will this pose too much of an administrative task? with the skills available in this forum it should not be a problem.
    or is it a question of making profit through the training academies which are not affordable to individuals not backed by their companies to learn on the technology?

    An interesting thought, however with so many users we would need a server farm of test systems to handle it.  And with users wanting to try so many different things it would be rather difficult to maintain the servers and have some sort of schedule for maintenance, resets, etc.

  • "No CEN system configured for CCMS monitoring" message

    Hello,
    When I want to use the reports option on central mode I receive this message:
    "No CEN system configured for CCMS monitoring"
    Can someone please guide me through this configuration?
    Thank you in advance,
    Roy

    Hi Roy,
    Monitoring Setup Guide will tell you how to setup CEN
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/43f30e51-0a01-0010-f59a-fecea2b95b2c
    Regards
    Juan
    Please reward with points if helpful

  • How Do I Create Default System Configurations for On- and Off-Dock?

    I recently purchased a T510 laptop with WIndows 7 Professional 64-bit and a Series 3 minidock. I would like two create two default system configurations (namely specifying active montiors, screen resolutions, networking options, and power management). I'd also like the laptop to detect the presence or absence of the dock and automatically switch accordingly. How can I do this? Thank you.

        Dear DavidLeon65,
    Good afternoon. I am sorry to learn of the difficulties you are experiencing with the bluetooth connection in your car. I know this can be frustrating. It would be my pleasure to address your bluetooth concerns.
    When the bluetooth connection drops out, is the phone near you? Also, do you have Wi-Fi turned on? If so, please turn off Wi-Fi, then test. What software version do you have? For directions on how to check the software verison on your phone, click http://vz.to/SrMyDh
    Thank You,
    MichelleS_VZW
    VZW Support
    Follow us on Twitter @VZWSUPPORT

  • System configuration for ESS/MSS Implementation

    Hi,
    I am stuck while configuring the systems for XSS configuration. I have completed following:
    1) Installed Portal 7.00 (based on NW2004s) which uses the backend ERP2005 system as a User Master source.
    2) Implemented the business packages for ESS 1.0 (SP6), MSS 1.0 (SP6) and SAPPCUI_GP 600 (SP6).
    3) Configured the SLD ( we have SLD running on a separate XI system)
    4) Configured JCO destinations (tested ok).
    5) Configured Systems for Portal and the ERP systems with system aliases.
        For Portal System:   I have only configured the WAS properties (i.e. hostname, path and protocol).and User management (using UDIPW as the logon method)
    The system alias is SAP_WebDynpro_XSS
        For ERP System:  I have configured connection, user management and W.A.S. properties. The system aliase is SAP_ECC_HumanResources
    However, when I perform the connection tests for both systems, they both fail for "Connection Test for connectors" test.  It gives the message "Connection failed. Make sure the user mapping is set correctly and all connection properties are correct".
    Any help is greatly appreciated.
    Regards.

    Hi Kristoffer,
    I have tried as per your suggestion but it still gives an error.
    The connector properties for my ERP system are as below:
    Application Host  : C1BL1 (also included the domain)
    Gateway Host   : C1BL1
    Gateway Service  : sapgw00
    Logical System Name   : ER1CLNT210    
    Remote Host Type -  3
    SAP Client   : 210
    SAP System ID (SID)  : ER1
    SAP System Number  : 00
    Server Port  : 3200
    System Type - SAP_R3
    System aliases for ERP system are:
    SAP_ECC_HumanResources and SAP_R3_Financials.
    I have not maintained any W.A.S. properties for this system.
    For my Portal system: WAS properties are:
    Web AS Description  : EP_Portal
    Web AS Host Name  : C1BL3:50100
    Web AS Path   : /webdynpro/dispatcher/
    Web AS Protocol - http
    I had not maintained the connector properties for this system before, but I have now maintained as following:
    Application Host  : C1BL1 (also included the domain)
    Logical System Name   : ER1CLNT210    
    Remote Host Type -  3
    SAP Client   : 210
    SAP System ID (SID)  : ER1
    SAP System Number  : 00
    Server Port  : 3200
    System Type - SAP_R3
    The system alias for EP is: SAP_WebDynpro_XSS
    In the UME configuration --> User mappings, I am using SAP_ECC_HumanResources system as the reference system.
    Please let me know if you need more info.
    Regards,
    Nilesh

  • What is the best system configuration for a video editing telecast quality using Adobe PRemier pro

    We need an editing suite for telecast quality for our church.
    What is the best system configuration please?
    What are all the requirements to set it up ?

    Buy a Desktop Video Editing PC http://www.adkvideoediting.com/
    Build a Desktop Video Editing PC
    -http://ppbm7.com/index.php/tweakers-page
    -3 price level ideas in http://www.pacifier.com/~jtsmith/ADOBE.HTM
    -what PC to build http://forums.adobe.com/thread/947698
    -2 how to build videos http://forums.adobe.com/thread/1104182
    -another video http://forums.adobe.com/thread/1145366
    -another video http://forums.adobe.com/thread/1132363
    -planning & Building http://ppbm7.com/index.php/intro-part-1
    -memory for LGA2011 http://forums.adobe.com/thread/1098759
    -an Adobe FAQ http://forums.adobe.com/thread/878520
    -http://www.shawnlam.ca/2012/premiere-pro-cs6-video-editing-computer-build/
    -http://www.videoguys.com/Guide/E/Videoguys+DIY9+Its+Time+for+Sandy+Bridge
    +E/0xe9b142f408a2b03ab88144a434e88de7.aspx
    -several more links http://forums.adobe.com/thread/815798
    -build tuning http://ppbm7.com/index.php/final-results

  • Managed System Configuration - Software version and OS is not accepting

    Dear
    When i try to setup the PI system in solman 7.1 - Managed system configuration, below the error msg.
    Please help to sort it the problem
    Regards
    Jay

    Hi Pany,
    Steps to follow
    - Rename the J2EEFRMW01_5-20002637.zip file to J2EEFRMW01_5-20002637.SCA.
    -telnet localhost 5$$08
    -logon with the user administrator
    - deploy /software/j2eefrmwpatch/J2EEFRMW01_5-20002637.SCA version_rule=all
    - Once it is done , then trigger the data to the SLD
    - Checked the software component in SLD
    - Resync the LMDB with SLD
    - Then performed the activity of manage system Configuration.
    With Regards
    Ashutosh Chaturvedi

  • System Configuration for CRM Business Package 4.0-60.2 in Portal

    Hi All,
    We have configured CRM Business Package(4.0-60.2) on EP6 SP11.
    Also created the SAP_CRM system with required fields.
    But I am confused with where do I have to specify the ISA related parameters?
    Should I create new systems with the aliases specified in CRM Business Package Admin guide(i.e.according to Web Entry Point names)For e.g. ISA_B2B,ISA_B2R,SHOP_ADMIN,USER_ADMIN etc. or I have to specify this in SAP_CRM system itself?
    Your Help will be appreciated.....
    Thanks and regards,
    Amol.

    Hello James,
    Thanks for the prompt reply...
    But my question is whether I have to make these changes in SAP_CRM system itself or should i create new system namely ISA_B2B,SHOP_ADMIN,ISA_B2R etc.
    With regards,
    Amol.
    Note : If you have already configured the CRM business package, please send me the documentation or the screen-shots of the system defined in portal on my e-mail id([email protected])

  • Managed System Configuration: SSO setup failed for Solution Manager 7.1 sp11

    Hi Folks,
    While doing Managed System Configuration for Soman system i am getting error in SSO Setup
    Currently I am in
    8. Configure Automatically :Single Sign On Setup
    This is i am going for managed System (Solution Manager System Itself)
    Below is error log..
    SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
    Screen shot attached.
    Found SID for SSO ACL entry : SMP
    Found login.ticket_client for SSO ACL entry : 000
    The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
    The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
    The SSO ticket Certificate <OU=J2EE,CN=SMP> has been successfully imported into ticket Keystore
    SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
    SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
    java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    The SSO ticket Certificate <CN=SMP> has been successfully imported into ticket Keystore
    SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
    SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
    java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Exception
    java.rmi.RemoteException: Caller not authorized.; nested exception is:
    java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:160)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
    at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
    at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
    at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
    at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    at com.sap.engine.services.security.exceptions.BaseSecurityException.writeReplace(BaseSecurityException.java:349)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:331)
    at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:910)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1024)
    at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1344)
    at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1316)
    at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1260)
    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1065)
    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:282)
    at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:338)
    ... 8 more
    Regards,
    San

    Hi Sandeep,
    It seems authorization issue. Please check the below SAP Note :
    1988642 - Warning 'caller not authorized' in Step 'Single Sign On Setup'
    Hope this helps.
    Thanks & Regards,
    Nisha

  • Warnings in Managed System Configuration

    Dear all,
    We are in the process of connecting a satellite system to Solman 7.1 and to monitor its datas.
    So in Managed system configuration for system, we are facing some warnings in step 8 and step 11.
    In step 8(Configure Automatically),Generate System level metrics ended with a warning i.e "The Diagnostic Agent for Introscope Enterprise manager could not be found"
    In step 11,(Configuration),Configuration check ended with warnings.
    i.e Errors found during the last 20 run for extractor
    Kindly suggest on how to proceed further.
    Thanks,
    Regards,
    Hasan

    Hello Diego,
    Sorry for the late reply..
    Yea the Enterprise Manager is running.
    When i tried the URL which you had given, it is displaying as 404 not found.
    Also when i start the Diagnostic agent in the SOLMAN, it is getting started and it is showing green LED in MMC, but when I try to connect the Diagnostic Agent to Solman in Basic configuration step, it is turning yellow and displays as,
    ""Access denied by the Managing System
    Check username/password
    Managing System details:
    host hllsap12
    port 8103
    Last operational status 272"
    After this the Diagnostic agent turns to yellow in MMC also..
    Kindly advice,
    Thank You,
    Regards,
    Hasan

  • Managed System Configuration - PI7.1 system solman_setup

    HI all,
    In trying to execute the step "Managed System Configuration" for a PI7.1 system in Solution Manager SOLMAN_SETUP, in the first step to "maintain the connection", its failing immediately with:
    Error when opening an RFC connection
    Establish connection to System <hostname>(01) - <SID>_001
    Any ideas?
    Thanks, Neeta

    Hello Neeta,
    i face the same problem.
    Establish connection to System <hostname>(01) - <SID>_001
    / CPIC-CALL: 'ThSAPOCMINIT' : cmRc=20 thRc=726 Gateway ist not connected to the l...
    i check the following and they are all fine.
    - ping to PI from solman
    - PI IP address in SMSY
    Could you tell me which part you configured in SMSY?
    regards

  • 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

  • Managed System Configuration step Assign Diagnostics Agent

    Dear Experts,
    We've newly instaled solution manager system 7.0 Ehp1 via latest sp stack 25 on aix 6.1, we've completed initial and basic configuraiton successfully via solman_setup, and instaled wily introscpe on same host with solution manager system,
    Now i am trying to managed system configuration for solution manager system via solman_setup step Assign Diagnostics Agent as demo link below
    https://service.sap.com/~sapidb/011000358700001735062008E
    I opend http://>SOLMANHOST>:<SOLMANPORT>/smd/go/ADMIN_AGENT
    >> Agent Candidates Management
    >>  Connection Parameters
    >> Custom SLD Parameters > Aply and the selected the SMD instance then trying to attached via password SMD_ADMIN
    But agent registration is waiting, SMD_ADMIN user is creating when i execute intial configuration, after i change the intial password, password is correct, so why the agent state is waitng status, i also push sld Setting for all from SMD view tab,
    I've also try to restart SMD agent, /usr/sap/SMD/J98/SMDAgent/log/SMDSystem.0.log file after restart
    Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       Starting SMDAgent ...
    Oct 28, 2010 11:07:25 AM [Thread[main,5,main]] Info       ===> Establishing connection to server 'ms://ccisolman:8101/P4
    Oct 28, 2010 11:07:28 AM [Thread[Connector,5,main]] Info       Smd connector is disabled because no SLD association and no credentials found.
    Oct 28, 2010 11:07:32 AM [Thread[SLD-Registration,1,main]] Info       [SLDReg] Next try to push instance data in SLD is  Thu Oct 28 23:07:32 EEST 2010     
    Best Regards

    hi
    pls chk again your sld parameters and check the correct user name, password entered in agent connection management under CUSTOM SLD(in agent candidates management)
    jansi

  • 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

Maybe you are looking for

  • TS5181 iTunes radio does not appear in "Music" on my iPod Touch, Why?

    iTunes radio does not appear in "Music" on my iPod Touch. How can I fix this?

  • Problem loading swf file in flash player 9.0.47.0

    Hi all! I have a really strange problem and couldn't find any information over the internet. The problem only occurs in flash player 9.0.47.0. It works in all the others players, newer and older.. I try to load a swf file to my web application and ge

  • Com.sap.portal.prt.sapj2ee.error

    Hi, When i run "startsap" on our Portal CI, i see the following error message in: std_server0.out Mar 15, 2008 8:40:51 AM          com.sap.portal.prt.sapj2ee.error [SAPEngine_Application_Thread[impl:3]_34] Fatal: Exception during reference registrati

  • Logic 9 no longer recognising 3rd party plug ins

    Without any change to OS or software versions, Logic 9 has decided not to recognise any of the 3rd party AU plug ins that have been working perfectly in all projects ... until today. How do I fix this? I'm using: Logic Pro 9.1.1 (1697.53) in 32 bit m

  • Google calendar app error -95 when attempting to print. help!!

    So i have the HP 5510 e All in One and i am running Vista Home Basic. I have added both the Google Calendar and Daily Brief apps with a view to printing my Google Calendar. Neither will work. Google Calendar lets me log in, select which Calendar i wa