CCMS agent is not registered at central CCMS system

Hi,
I have standalone DB (AIX) and CI (AIX) with 4 application servers. (only Abap - unicode system)
In CI sto6 and OS07 i am not getting any info regarding DB server and also in EWR in solution manager.
I came to know that ccms agent not registered.
plz help in CI which client i want to create the user csmreg and config file.( in 000 or working client)
After creating config file in which path should i copy the config file in OS level in AIX.
and how to start it.
Please suggest me.
Thanks,
Hari

Hi,
Check below link:
http://help.sap.com/saphelp_nw04/helpdata/en/48/6a76607a7c91409474ad6c7b6f5a26/content.htm
Thanks
Sunny

Similar Messages

SDM agent is not registered with SDM server of Solution Manager server

Hi,
We are in process of configuring EWA report for JAVA stack of SAP system along with ABAP stack. For ABAP stack the EWA report generation is straight forward and it is working fine. We are facing the problem while configuring EWA report for JAVA stack. Pls. find below the steps that we have followed and currently where we are stuck,
1) Installation of Willy introscope on Solman server.
2) Define JAVA component for each SAP system in SMSY
3) Installation of SDM Agent on all managed systems
4) Trying to attach SDM Agent to SDM server(solman) with the use of smdsetup.bat (managingconf & sldconf ).still we are getting error in smd agent log file as given below:
===============
Nov 24, 2011 6:16:09 PM [Thread[Connector,5,main]] Info       [p4://xxxx.xxxx.int:8103] Checking server availability...
Nov 24, 2011 6:16:39 PM [Thread[Connector,5,main]] Error      Failed to connect to SMD server - user: SMD_ADMIN
Nov 24, 2011 6:16:39 PM [Thread[Connector,5,main]] Warning    Connecting to SMD server p4://xxx.xxx..int:8103 failed - error counter: 0 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances
*     Nested exceptions are:*
*     com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: xx.xx.xx.xx and port: 8103*=================
5) The solman_setup t-code execution is successful in Solman server.
6) Trying to configure Technical system for JAVA system type through solman_setup : At this time we are getting another error as shown below:
========
The Managed System does not fulfil the Diagnostics prerequisites
Software with prerequisite are incorrect: Found SAP J2EE ENGINE 7.00 with sp level 0, minimum sp level required is 9: Please install or upgrade the required software component.========
I have gone through the SAP note: 1274287 : My solman system is already on the required patch level for LMservice and St 400 SP. Also, the managing systems Java patch level is more then sp06 which is minimum level required.
I need your help to know, why i am getting this SAP J2EE ENGINE 7.00 patch level error although my Java stack is up to date with the required patches.
Waiting for your reply friends.
Regards,

Hi,
please let us know your solman version.
check and apply the sap note
[Note 1277258 - Diagnostics prerequisite check failure|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1277258]
Thanks,
Jansi

Internal speakers not registering

i plugged my mac into a sound board to play over the speakers today,
and after i unplugged it the internal speakers are not registering
i went into system preferences, and into sound... but the internal speakers are not even an option for my sound outputs.
whats the deal?

try this (last post) worked for me
discussions.apple.com/thread.jspa?messageID=8716184&#8716184

CCMS alert monitoring data for ORACLE is not visible in Central system

Hello,
I have installed sapccm4x agents in the CI of the Satellite System and it shows in the Central System as sucessfully registered under Agents for remote System and the RFC Connection test is also successfull. When i check in RZ20 in Central System not all the predefined monitors are visible of the Satellite System in the Central System and mainly the MTE element ORACLE. The database,CI and other instances on the Satellite System are installed on separate hardware. As said the database is installed not with the CI but a standalone.
Please let us know what needs to be configured in order to get the MTE element of ORACLE to show in the Central System.
Thanks,
Vinod Meno

Bhudev,
Thanks for the quick respose..
1.Sapccmsr agent is installed on Java standalone server and it has been sucessfully registered and running and we can grep the process to see its state as well as in the Central System i can see under ccms agents for remote systems it shows and the RFC connection test is also sucessfull.
2.Yes we are sending the data from the DB to CI first,but we also want the data visible in the Central System mainly for the MTE element Oracle.The filesystem of the Satellite Systems shows up in the Central System but i am intrested to capture the MTE element Oracle since we plan to monitor the tablespaces threhold .
I am thinking of opening an SAP message but i am trying to see if i can get some info that can give me the result.
Regards,
Vinod Menon

CCMS Agent Issue in Central Monitoring System

Dear Guru's,
We are configuring the CCMS Agent in our landscape, while registering the CCMS Agent we're facing some issue.
CEN system - Only ABAP Stack - ECC 6.0 Ehp3
Target System - Double stack (ABAP + JAVA, Netweaver 2004s)
After completing the Visual Admin settings. Service file SAPCCMSR.99 has
been generated automatically. As per the help.sap the service file should
be SAPCCMSR.<Instance No.>, our instance no. was 00 but its was generated
with 99 (SAPCCMSR.99).
Two RFC has been created in Double stack system and one RFC has been
created in ABAP system.
RFC in ABAP system :
SAPCCMSR.HOSTNAME.00 - its not working
(Error Details, ERROR:program hostname.sapccmsr.00 not registered)
RFC in Dual-stack System :
SAP.CCMS.J2EE.SID - its working
SAPCCMSR.HOSTNAME.00 - its not working
(Error Details, ERROR:program hostname.sapccmsr.00 not registered)
While testing the Remote System Topology, we're getting communication
error.
In RZ21, Topology - Agents for Remote Systems - Display Overview, Agent
for SAP System SID tab, Agents for Remote SAP Systems, selecting the
available system (Dual stack system) and give Test Connection means
its throwing Error opening an RFC connection - SAPCCMSR.HOSTNAME.00
Could you please suggest, what we're missing.
regards,
Guna

Hi,
Thanks for your reply.
What your said was rite, but I'm unable to get J2EE (Java Stack) alert information in RZ20 of the same system, coz., its dual stack system. If we don't have any issue in Java means it should be updated in RZ20 of the same system.
In Dual-stack System:
RZ20 -> CCMS monitor sets -> SAP J2EE Monitor Template -> All Systems -> SID -> J2EE Engines, J2EE Applications, J2EE Log files... these are not updating here.
Could you kindly suggest for above issue.
regards,
Guna

H.323 Gateway is not Registering in CCM 4.1.2

H.323 Gateway. I am using cisco2620
========================================
nafay#sh run
Building configuration...
Current configuration : 966 bytes
version 12.2
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
hostname nafay
ip subnet-zero
mgcp
mgcp call-agent 192.168.0.111
mgcp dtmf-relay codec all mode out-of-band
call rsvp-sync
voice class h323 1
h225 timeout tcp establish 3
ccm-manager mgcp
interface FastEthernet0/0
ip address 192.168.0.55 255.255.255.0
duplex auto
speed auto
interface Serial0/0
no ip address
shutdown
ip classless
ip http server
voice-port 1/0/0
voice-port 1/0/1
voice-port 1/1/0
voice-port 1/1/1
dial-peer cor custom
dial-peer voice 100 voip
preference 1
destination-pattern 1...
voice-class h323 1
session target ipv4:192.168.0.111
dtmf-relay h245-alphanumeric
ip precedence 5
dial-peer voice 101 voip
preference 2
destination-pattern 1...
session target ipv4:192.168.0.111
dtmf-relay h245-alphanumeric
ip precedence 5
line con 0
line aux 0
line vty 0 4
end
nafay#
=========================================

Is this config is OK. Still not registering
=====================================================
service timestamps debug uptime
service timestamps log uptime
hostname nafay
ip subnet-zero
call rsvp-sync
voice class h323 1
h225 timeout tcp establish 3
interface FastEthernet0/0
ip address 192.168.0.55 255.255.255.0
duplex auto
speed auto
interface Serial0/0
no ip address
shutdown
ip classless
ip http server
voice-port 1/0/0
voice-port 1/0/1
voice-port 1/1/0
voice-port 1/1/1
dial-peer cor custom
dial-peer voice 100 voip
preference 1
destination-pattern 1...
voice-class h323 1
session target ipv4:192.168.0.111
dtmf-relay h245-alphanumeric
ip precedence 5
dial-peer voice 101 voip
preference 2
destination-pattern 1...
session target ipv4:192.168.0.111
dtmf-relay h245-alphanumeric
ip precedence 5
line con 0
line aux 0
line vty 0 4

"Error [10151] The LCP Port on CCM Admin for Mobile Agent is not Configured or misconfigured"

We are running into a problem which we have noticed on UCCE 8.5 and havent seen on earlier 7.5 release.
If we setup a CTI port as agent device target and if we try to login the agent using Cisco Desktop (Not CAD, just CTI OS Client) then we get following error:
"Error [10151] The LCP Port on CCM Admin for Mobile Agent is not Configured or misconfigured"
But this wasnt the issue with 7.5 and we were able to do agent login with CTI Port as device target. We dont intend to use Mobile Agent feature but just login UCCE agent to CTI port as the device.
Do we know if this is a known issue or if something has changed between 7.x and 8.x release which could be is causing this?

So you can ping and nslookup from your ms to these agents and vice versa right? I wouldn't do a manual install, I would push the agent from the management server. You can uninstall the agent manually, or use cleanmom to get rid of them. Then
do an install from the console. When you initiate the install from the console (management server), should it run into any issues it will dump out an error which will give you an idea of where the problem may be.
From Holmans post on this:
e MOM Server could not execute WMI Query "Select * from Win32_OperatingSystem" on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
The MOM Server could not execute WMI Query "(null)” on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
8004100A
800706BA
1. Ensure agent push account has local admin rights
2. Firewall is blocking NetBIOS access. If Windows 2008 firewall is enabled, ensure “Remote Administration (RPC)” rule is enabled/allowed. We need port 135 (RPC) and the DCOM port range opened for console push through a firewall.
3. Inspect WMI service, health, and rebuild repository if necessary
4. Firewall is blocking ICMP (Live OneCare)
5. DNS incorrect
http://blogs.technet.com/b/kevinholman/archive/2009/01/27/console-based-agent-deployment-troubleshooting-table.aspx
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

CSA Agent not registering with CSA MC

I have downloaded and installed my agent kit on a WinXP machine. But for some reason it is not registering with the CSA MC. Any idea why? The CSAMC is in a different subnet, but 443 is open for communication. Does the MC need other ports open to talk to the agent?
Thanks,
nate

Here is a listing of the various error codes that CSA (used to be Okena) prints when there is a communication issue between an agent and the MC.. Usually the issue is either licensing or CSAMC access restrictions, but this list has all of the causes. Please rate if this helps.
OKENA_STATUS_INVALID_SYSTEM_CONFIGURATION = 2000,
OKENA_STATUS_ICC_FAILED_GET_HANDLE = 2001,
OKENA_STATUS_ICC_FAILED_TO_WRITE = 2002,
OKENA_STATUS_ICC_FAILED_TO_READ = 2003,
OKENA_STATUS_ICC_INVALID_TOPOLOGY = 2004,
OKENA_STATUS_ICC_INVALID_INITIATOR_COMP = 2005,
OKENA_STATUS_ICC_INVALID_PAYLOAD_SIZE = 2006,
OKENA_STATUS_ICC_INVALID_VERSION = 2007,
OKENA_STATUS_ICC_INVALID_COMP_ID = 2008,
OKENA_STATUS_ICC_INVALID_PAYLOAD = 2009,
OKENA_STATUS_GROUP_DOES_NOT_EXIST = 2010,
OKENA_STATUS_INVALID_REGISTRATION_PARAMS = 2011,
OKENA_STATUS_HOST_HAS_REGISTERED_BEFORE = 2012,
OKENA_STATUS_INVALID_CONTACT_INFO = 2013,
OKENA_STATUS_HOST_NOT_REGISTERED = 2014,
OKENA_STATUS_MISSING_CONTACT_INFO_PARAMS = 2015,
OKENA_STATUS_INVALID_REGISTRATION_ID = 2016,
OKENA_STATUS_ICC_INVALID_BYTE_ORDER = 2017,
OKENA_STATUS_ICC_NOT_INITIALIZED = 2018,
OKENA_STATUS_COMP_CONFIGURED = 2019,
OKENA_STATUS_UNDEFINED_MGMT_SERVER = 2020,
OKENA_STATUS_HTTP_TRANSACTION_FAILED = 2021,
OKENA_STATUS_ICC_INVALID_HANDLE = 2022,
OKENA_STATUS_SERVER_IS_REACHABLE = 2023,
OKENA_STATUS_HTTP_TIMEOUT = 2024,
OKENA_STATUS_ICC_NO_CONNECT_MUTEX = 2025,
OKENA_STATUS_FORCE_POLLING_NOW = 2026,
OKENA_STATUS_REGISTRATION_REJECTED = 2027,
OKENA_STATUS_LOAD_CONFIG = 2028,
OKENA_STATUS_DB_ERROR = 2029,
OKENA_STATUS_LICENSE_REACHED_LIMIT = 2030,
OKENA_STATUS_REGISTRATION_NOT_ALLOWED = 2031,
OKENA_STATUS_NOT_ALLOWED_TO_STOP_AGENT = 2032,
OKENA_STATUS_CLIENT_UI_NOT_ALLOWED = 2033,
OKENA_STATUS_FAILED_TO_PRINT_AGENT_REPLY = 2034,
OKENA_STATUS_INVALID_LICENSE = 2035,
OKENA_STATUS_TIMED_OUT = 2036,
OKENA_STATUS_REGISTRATION_BACKOFF = 2037,
OKENA_STATUS_TESTMODE_ON = 2038,
OKENA_STATUS_TESTMODE_OFF = 2039,
OKENA_STATUS_INVALID_SERVER_FQDNS = 2040,
OKENA_STATUS_INVALID_SERVER_IPADDR = 2041,
OKENA_STATUS_SERVER_DNS_NOT_RESOLVABLE = 2042,
OKENA_STATUS_SERVER_IPADDR_NOT_OWN = 2043,
OKENA_STATUS_SERVER_DNS_NOT_OWN = 2044,
OKENA_STATUS_SERVER_NAME_NOT_FQDNS = 2045,
OKENA_STATUS_FAILED_OPEN_PROCESS = 2046,

Remote system monitoring entry- data not relayed to Central system

Hello Folks,
I am trying to establish a central monitoring system for our client. I am trying to test it in the DEV environment first.
The central system is a Solution manager system (Dual stack- ABAPJAVA). I am trying to bring in monitoring data from the ECC development environment (ABAPJAVA).
First of, i created to RFC connections in Solution manager system, one for data collection and the other for analysis. I have maintained the host address of the ECC system as target.
Then i have created a remote system entry in Transaction RZ21--> technical infrastructure entered the 2 RFC names and have executed the function.
At this point i am only trying to bring in ABAP stack monitoring data form the ECC system so i have not generated the CSNCONF file.
Now when i look in Solution manager RZ20-->CCMS monitoring templates, i can't see any data for the the ECC system.
I guess i am doing something wrong. Am i looking in the wrong monitor set?
As additional information: Solution manager (SMD) and ECC (ECD) use different transport domains / transport groups. I dont know if this makes a difference.
Can some one please help.
Regards,
Prashant

Hi Prashant,
if I understand correctly your system shows only MTEs from R/3 Stack, not from the OS side, pls check your SAPOSCOL. Are the data in OS06 in your remote system correct and do you see the current data, refredhed all 10 seconds?
To check your environment, pls do the following:
in th efirst step check in RZ21 > in the Topology part the System Overview for your system connection to your back end system. Are the Read Destination Data RFC and the Destination Analysis RFC correct and works the authority chek fine?
In the second step pls check in RZ21 > in the Agents for Remotey SAP Systems part; are there registered your remote ccms agents correctly and works the connection test.
Stop the agents and in your RZ20 monitor pls enter STAT in your command field. Are there displayed for your MTE nodes the read RFC destinations?
Start the agents and and in your RZ20 monitor pls enter STAT in your command field. Are there displayed for your MTE nodes the CCMS Agent RFC destinations?
To rebuild the Monitor in the CEN system you could try to reset the node of your remote system in the warm up status > go in the remote system to RZ1 > go to local segments > change to edit > select your segments > reset segment in "WARMUP" status.
In the CEN system you coul try to go to the edit mode for the Agents for Remot SAP Systems > select your remote system and push the button Reinitialize Agents
In the back end system you can try to delete all MTEs in RZ21 > menu Technical Infrastructure > Reorgenize Segment Table > select the options with "ALL" in the CEN and the remote system to reorgenize all data.
Could you pls post for the missing MTEs a screenshot on the one side from the CEN system and on the other side from the remote system...
and last but not least you could try the following for missing OS MTEs
delete ALALERTS, ALMTTREE and ALPERFHI in /usr/sap/ccms/<SID>_<SNR> and check in the agents folder all trace and log files for errors.

BOEDGE - SM59 Connection RFC = Program Not Registered

Hello,
I installed on a server Windows Server 2003 SP1 32bit:
               - BO Edge 3.1 (BuildVersion = 12.1.0.914)
               - Java Connector 2.1.9
               - Integration Kit for SAP 3.1 SP3 (BuildVersion = 12.3.0.601)
I see on the CCM (Central Configuration Manager) my services correctly started:
          Apache Tomcat                     --      Running
          BW Publisher Service           --      Running
          Server Intelligence Agent      --      Running
I installed on the BW server the transport order of BOBJ INTG for "BOBJ INTG for SAP XI 3.1 FixPack 3.1" (BuildVersion=12.3.1.684).
I created a RFC connection type TCP/IP and test my new connexion and I have a error message:
Connexion     Erreur connexion
Détails err.     Error when opening an RFC connection
Détails err.     ERROR: program BW_PUBLISHING not registered
Détails err.     LOCATION: SAP-Gateway on host myserver.com / sapgw10
Détails err.     DETAIL: TP BW_PUBLISHING not registered
Détails err.     COMPONENT: SAP-Gateway
Détails err.     COUNTER: 51016
Détails err.     MODULE: gwr3cpic.c
Détails err.     LINE: 1812
Détails err.     CODE RETOUR: 679
Détails err.     SUBRC: 0
Détails err.     RELEASE: 700
Détails err.     TIME: Fri Sep -
Détails err.     VERSION: 2
An idea?

Hi,
In Central Management Console ie, Admin application of BOE, you need to configure the BW system. Use the below URL,
http://<serverhostname>:<port>/CmcApp
After logging in Select the Authentication and SAP as authentication type. Regarding how to configure, follow the configuration steps mentioned in the below article:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a00ee3b2-5283-2b10-f1bf-8c6413e0898f
Once you import the roles with the above configuration, the user with which you are validating the RFC connection will be imported in the BOE.
Now, verify the RFC in the BW system.
Regards,
Noor.

ATA 186 (SIP coverted to SCCP) will not register to CM

I have a situation where SIP ATA's were ordered instead of SCCP. I downloaded and upgraded the ATA's with Version 3.2.3 software for SCCP. The ATA's pull ther configuration form the callmanager tftp server, but they will not register with callmanager. Anyone have any ideas that might help?
Thanks

you can browse to the ATA, in 3.2.3 just to the ip-address
http://ata-ip-address/
Also, can you see errors in the CCM traces where the ATA tries to register to?
Is your environment using DNS, or do you have ip-addresses for CallManager server config?

SCCM client not registering on some machines

Hello,
I am running across a strange problem that is only affecting some machines. We are imaging via OSD task sequence, 2012 R2 and some machines do not register properly with SCCM. When I say not registering, I mean it doesn't get its Site code and
missing most of its actions. Most machines that we image work fine, but the odd one doesn't register using the same task sequence that we use on other PC's. When I watch the task sequence steps go through I noticed that right after the installing SCCM
client step it boots right into windows. Basically skipping the steps we have set afterwards, the next step is to install some software (adobe reader, SCEP, and a few others).
I also noticed it seems to happen more often with certain model machines. I have an HP Z420 and an HP Folio 9470m. These consistently fail to register everytime I image.
I've tried quite a few fixes I found online, but nothing has worked as of yet. The most recent fix I tried was to delete the hardware inventory and then rebuild it. That did not work. Entering SMSMP= in the Setup Windows and Config manager step also did
not work. I also tried entering in our DNS server into the registry under the CCM directory. It appears something is happening during the client install (or not happening). But why only certain machines? Most work fine.
Our fix is to simply re-install the client after imaging, this solution has been working for us but I want to find a more permanent solution.
Any ideas?

Jason,
We have this line in the Setup Config Manager,
PATCH=C:\_SMSTaskSequence\OSD\PNS00002\Updates\configmgr2012ac-r2-kb2970177-x64.msp
Keep in mind, that this same task sequence works fine with most other machines. It almost appears to be model specific. Certain models definitely have more issues registering than others.
I'm still fairly new to SCCM, so if you need more from the logs let me know.
==========[ ccmsetup started in process 2176 ]========== ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
Running on platform X64 ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
Launch from folder C:\_SMSTaskSequence\OSD\PNS00002\ ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
CcmSetup version: 5.0.7958.1000 ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Ccmsetup command line: "C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\PNS00002 /config:MobileClient.TCF /status:524 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Command line: "C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\PNS00002 /config:MobileClient.TCF /status:524 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Copying config file from C:\_SMSTaskSequence\OSD\PNS00002\MobileClient.TCF to folder C:\WINDOWS\ccmsetup\. Return result: 0x0 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
SslState value: 224 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPPORT:    80 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPSPORT:    443 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPSSTATE:    224 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPSCERTNAME:    ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
FSP:    ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMFIRSTCERT:    1 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Config file:      C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Retry time:       10 minute(s) ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
MSI log file:     C:\WINDOWS\ccmsetup\Logs\client.msi.log ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
MSI properties:    INSTALL="ALL" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1" ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Source List: ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
                  C:\_SMSTaskSequence\OSD\PNS00002 ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
MPs: ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
                  None ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
No version of the client is currently detected. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Updated security on object C:\WINDOWS\ccmsetup\. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Downloading file C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
Downloading C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe to C:\WINDOWS\ccmsetup\ccmsetup.exe ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 16% complete (262144 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 32% complete (524288 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 48% complete (786432 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 64% complete (1048576 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 81% complete (1310720 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 97% complete (1572864 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 100% complete (1614520 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
Download complete. ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
Running as user "SYSTEM" ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Detected 118178 MB free disk space on system drive. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Checking Write Filter Status. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Unexpected row count (0) retrieved from AD. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Failed to get site version from AD with error 0x80004005 ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
SiteCode:         PNS ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
SiteVersion:      ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
An MP does not exist on this machine. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Client (5.00.7958.1000) is installed and is the same or lower version. Initiating repair. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Repairing version 5.00.7958.1000 of the client with product code {8864FB91-94EE-4F16-A144-0D82A232049D} ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
No features were excluded and will be excluded. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
MSI PROPERTIES are REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:19:50 PM 2452 (0x0994)
C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Running installation package
Package:     C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
Log:         C:\WINDOWS\ccmsetup\Logs\client.msi.log
Properties:   REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:19:50 PM 2452 (0x0994)
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1635
Action:
ErrorMessages:
ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Next retry in 1 minute(s)... ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 7/21/2014 12:20:50 PM 2452 (0x0994)
Running installation package
Package:     C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
Log:         C:\WINDOWS\ccmsetup\Logs\client.msi.log
Properties:   REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:20:50 PM 2452 (0x0994)
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1635
Action:
ErrorMessages:
ccmsetup 7/21/2014 12:20:50 PM 2452 (0x0994)
Next retry in 1 minute(s)... ccmsetup 7/21/2014 12:20:51 PM 2452 (0x0994)
C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
Running installation package
Package:     C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
Log:         C:\WINDOWS\ccmsetup\Logs\client.msi.log
Properties:   REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:21:51 PM 2452 (0x0994)
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1635
Action:
ErrorMessages:
ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
Client installation has failed too many times. Ccmsetup will now abort. ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
A Fallback Status Point has not been specified. Message with STATEID='313' will not be sent. ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
InstallFromManifest failed 0x80070663 ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
Deleted file C:\WINDOWS\ccmsetup\ccmsetup.xml ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)

What will happen if Conference Bridge (CFB) is not registered with Call Manger?

I have a MRG consists of two CFB, it is found one is registered with CCM, the other is not. some users complain that the ad-hoc conference soft button is not working. So is that due one of the CFB is not registered? (I know all same type of resource within a MRG will be round-robin balanced).
will happen Call Manager allocate an unregistered CFB?

It will not allocate the unregistered one. Media Resource Manager will look for the available resources registered with CUCM according to the configuration and allocate the one thats available.
-Terry
Please rate all helpful posts

KABA connection issue - program not registered

I am trying to troubleshoot a connection error between SAP and KABA. I have the RFC created in SAP and when I test the connection I get a program not registered. The KABA "amsproc" service on the KABA side has been restarted, we have occasionally received a password locked message in the SAP system log after restarting the KABA service (I believe this means SAP and KABA are communicating). We have since reset the password, but we can not successfully test the RFC and when attempting to send IDOC's out we get the program not registered error. Is there something on the SAP side that needs to be done to register the program or is starting the service on the KABA side going to register the program with SAP? Any assistance would be appreciated.

Hi,
In Central Management Console ie, Admin application of BOE, you need to configure the BW system. Use the below URL,
http://<serverhostname>:<port>/CmcApp
After logging in Select the Authentication and SAP as authentication type. Regarding how to configure, follow the configuration steps mentioned in the below article:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a00ee3b2-5283-2b10-f1bf-8c6413e0898f
Once you import the roles with the above configuration, the user with which you are validating the RFC connection will be imported in the BOE.
Now, verify the RFC in the BW system.
Regards,
Noor.

Problem with RFC connection - tp program not registered

Hello everyone
recently there has appeared a problem with the RFC connection on our system - we received the following set of messages:
Trace file opened at 20101221 130738 Central European Standard Time, SAP-RE
======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Tp program is not registered.
ABAP Programm: RSRFCPIN (Transaction: SM59)
User: xxx(Client: 100)
Destination: SIDRFC_IFSAPHRCZPKCP (handle: 2, , )
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1501
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679
Program transakcji nie jest zarejestrowany
DEST =SIDRFC_IFSAPHRCZPKCP
HOST =%%RFCSERVER%%
PROG =IFCZPKCP
GWHOST =ssapprod
GWSERV =sapgw21
I tried to register program with a command:
rfcexec -aIFCZPKCP -gssapprod -xsapgw21
but with no success - the program didn't appear on the list of logged clients on the system in gateway monitor. Frankly speaking we do not know now what else we can do - please help!
We have ECC 6.0 (SAP_BASIS 700 SP18) on Windows Server 2003 R2 x64.
Thanks in advance for any help.
Regards
Peter

Hi Salim
thanks for your reply.
./rfcexec -a(PROG_ID) -gssapprod -xsapgw21 &
The syntax you're providing refers to UNIX systems, but I did similar thing on our Windows system - I tried all of the following methods (unfortunatelly without success):
rfcexec -a(PROG_ID) -gssapprod -xsapgw21
full_path_to_rfcexec.exe -a(PROG_ID) -gssapprod -xsapgw21
rfcexec -a(PROG_ID) -gssapprod.domain -xsapgw21
full_path_to_rfcexec.exe -a(PROG_ID) -gssapprod.domain -xsapgw21
Can you advise me what to do now?
Thanks
Piotr

CCMS agent is not registered at central CCMS system

Similar Messages

Maybe you are looking for