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

Similar Messages

Essbase server is invalid. Not registered with Shared Services

Hi,
I am trying to deploy EPMA Essbase application after we upgrade to 11.1.2.2 from 11.1.2.0. I get this error.
Application server '<Server>:1423' is invalid. It is not registered with Shared Services.
URI: http://<Server>/awb/integration.verifyApplication.do
Code: com.hyperion.awb.web.common.BaseServiceException
Description: Application server '<Server>:1423' is invalid. It is not registered with Shared Services.
Actor: noneAny specific post configuration task needs to be performed?
Regards,
Ragav.

Hi,
We were able to resolve the issue. The "Invalid Deployment Information" test in the application diagnostics failed. We had to synchronize the deployment data and later we were able to validate the application.
Regards,
Ragav.

Getting "The server {85DE1C45-2C66-101B-B02E-04021C009402} did not register with DCOM within the required timeout." on WinXP machine

Hi,
I have a windows service written in .Net which access a COM component(This conponent is also written by me).
The COM component launches Acrobat and uses it for generating Thumbnail files.
I get following error is logged into event viewer when CreateDispatch("AcroExch.App", &e)) line is exicuted.
Error Message: The server {85DE1C45-2C66-101B-B02E-04021C009402} did not register with DCOM within the required timeout.
This problem occurs only when the windows service run under a specified user account say "TestUser". i.e if service runs under "Local System" account then everything works fine.
Also this problem only occurs on WinXP machine. i.e same thing on Windows2003 server works fine.
I have given all required permissions for "TestUser" on AcroExch.AVDoc and AcroExch.PDBookmark using dcomcnfg.
Any help will be appriciated.
Thanks and Regards,
Anand Mahadik.

Hello,
start by running sfc /scannow to check if there is corrupt system files.
If this does not hellp, I recommend performing an in -place upgrade of your OS.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft Certified
Professional
Microsoft Certified
Systems Administrator: Security
Microsoft Certified
Systems Engineer: Security
Microsoft Certified
Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified
Technology Specialist: Windows 7, Configuring
Microsoft Certified
IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator

The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout

Windows Server 2012 becomes slow and unresponsive, event logs show DCOM errors in event logs. After server reboot server works normally.
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          10/28/2014 9:06:32 AM
Event ID:      10010
Task Category: None
Level:         Error
Keywords:      Classic
User:          NETWORK SERVICE
Computer:      ServerName
Description:
The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10010</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-28T13:06:32.743836700Z" />
    <EventRecordID>165767</EventRecordID>
    <Correlation />
    <Execution ProcessID="760" ThreadID="5560" />
    <Channel>System</Channel>
    <Computer>ServerName</Computer>
    <Security UserID="S-1-5-20" />
</System>
<EventData>
    <Data Name="param1">{1F87137D-0E7C-44D5-8C73-4EFFB68962F2}</Data>
</EventData>
</Event>

Hi Avinash,
If this issue occurs again, please follow steps below to troubleshoot it,
Use the GUID in the error message to find what application it is.
Using Regedit, navigate to the following registry value:
HKEY_CLASSES_ROOT\CLSID\clsid value\LocalServer32. The clsid value is the information displayed in the message. Such as, {3EB3C877-1F16-487C-9050-104DBCD66683}
In the right pane, double-click
Default. The Edit String dialog box is displayed. Leave this dialog box open.
Click
Start, and then click This PC.
Using the information displayed in the
Value data box of the Edit String dialog box, navigate to the program.
Right-click the program name, and then click
Properties. The Properties dialog box for the program is displayed.
To determine who the vendor is for this program, refer to the
Version tab.
If you can’t find the file in the corresponding path, please replace with a good file.
Check if the related service have started. Stop and try to restart it.
If you have 3<sup>rd</sup> party applications, please disable it temporary, to see if this issue was caused by them.
For more details, please refer to links below, it provides more possible causes about event ID 10010.
DistributedCOM Error ID 10010
https://social.technet.microsoft.com/Forums/windowsserver/en-US/77b1db1d-f186-4515-8f7d-2241942eb9b7/distributedcom-error-id-10010?forum=winservergen
Best Regards,
Tina

The server {4D8E7D87-0103-42F6-BE82-598C7E90A42C} did not register with DCOM within the required tim

hello all.....
when i try to convert .indd file to PDF file in C# , i got the following error
The server {4D8E7D87-0103-42F6-BE82-598C7E90A42C} did not register with DCOM within the required timeout.
just 1 day ago i installed adobe indesign cs4 in my system.
do i need to install anything else???????
please let me know.
Thanks in advance.

Hi Avinash,
If this issue occurs again, please follow steps below to troubleshoot it,
Use the GUID in the error message to find what application it is.
Using Regedit, navigate to the following registry value:
HKEY_CLASSES_ROOT\CLSID\clsid value\LocalServer32. The clsid value is the information displayed in the message. Such as, {3EB3C877-1F16-487C-9050-104DBCD66683}
In the right pane, double-click
Default. The Edit String dialog box is displayed. Leave this dialog box open.
Click
Start, and then click This PC.
Using the information displayed in the
Value data box of the Edit String dialog box, navigate to the program.
Right-click the program name, and then click
Properties. The Properties dialog box for the program is displayed.
To determine who the vendor is for this program, refer to the
Version tab.
If you can’t find the file in the corresponding path, please replace with a good file.
Check if the related service have started. Stop and try to restart it.
If you have 3<sup>rd</sup> party applications, please disable it temporary, to see if this issue was caused by them.
For more details, please refer to links below, it provides more possible causes about event ID 10010.
DistributedCOM Error ID 10010
https://social.technet.microsoft.com/Forums/windowsserver/en-US/77b1db1d-f186-4515-8f7d-2241942eb9b7/distributedcom-error-id-10010?forum=winservergen
Best Regards,
Tina

The server did not register with DCOM within the required timeout.

Hi All,
I am using Thinkpad T43 (type 1871) with Windows XP SP3, but sometimes I find the following message in the Event Viewer:
The server {7160A13D-73DA-4CEA-95B9-37356478588A} did not register with DCOM within the required timeout.
What may be the reason for this message?
How it can be solved?
Regards,
Alper

have a look here http://www.grc.com/freeware/dcom.htm
Thinkpad R61 7733-1GU
Thinkpad X61T 7762-54U
Thinkpad X60T 6363-4GU
Did a member help you today? Thank them with a Kudo!
If a post answers your question, please mark it as an "Accepted Solution"!
Regards,
GMAC

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,

HT4623 iPhone 4s will not register with server after iOS 6 update

My iPhone 4s will not register with server after iOS 6 update. Does anyone has similar problem?

Obviously since you have iOS 7 you're a developer. As a developer, you signed a NDA with Apple not to discuss the iOS on a public forum. Please log in to the Developer Forum using your credentials and ask for help there, lest you risk having your credentials terminated.
Thanks, and best of luck to you.
GDG

Windows 2k Clients could not registered with CSAMC 5.0

hi there,
My w2k clients could not registered with CSAMC, WinXP registered o.k. I am running CSA 5.0.176.
All clients in same TESTMODE group. Any idea ?
Thanks
ade

The CSAgent-Install.log will show you if any of the shims failed to load during the install.
The csalog.txt in the same directory will log communication problems. Look for an error code like one below (cut and pasted from the Networkers 2006 CSA Troubleshooting session slides):
OKENA_STATUS_LICENSE_REACHED_LIMIT = 2030
Number of registered hosts has exceeded the license count for that host type [desktop or server]
Resolution: delete unused hosts; automatically in 30 days or use search
OKENA_STATUS_REGISTRATION_NOT_ALLOWED = 2031
Usually a certificate issue
Resolution: Set agent to debug and triage using csalog.txt
OKENA_STATUS_INVALID_LICENSE = 2035
A license has expired or file format was not valid
Resolution: Delete expired license files
OKENA_STATUS_REGISTRATION_BACKOFF =2037
A number of conditions can trigger this; all are uncommon and need attention
Resolution: Set agent to debug and triage using csalog.txt

Installed ES - Error when loading adminui: Property Editor not registered with the PropertyEditorManager

I just installed LiveCycle ES on a Windows 2003 virtual machine using the WebSphere application server.
Everything is finally installed, but now when I try to access the adminui url (http://xxxxx:9080/adminui/login.faces) I receive the following exception:
Error 500: com.ibm.ws.jsp.JspCoreException: Unable to convert string 'adminUIResources' to class javax.el.ValueExpression for attribute basename: java.lang.IllegalArgumentException: Property Editor not registered with the PropertyEditorManager
Am I missing something? What now?

You shouldn't have any appserver specific libraries in WEB-INF/lib (covered by the webapp's default classpath). Further on the appserver/lib (covered by the appserver's default classpath) should only contain appserver specific libraries and at highest 3rd party libraries which are going to be shared among all webapps. Finally you should NOT have added or modified anything in the jdk/lib (covered by the runtime's default classpath).
So in case of a default and unmodified environment everything should just work flawlessly. In your specific case it seems that you've unnecessarily added/copied appserver specific libraries in the WEB-INF/lib or that you have duplicated EL libraries from (another) appserver in the appserver/lib or maybe -more worse- in the jdk/lib.

Host not registering with the Management Center

Hello,
We have CSA MC v5.2. I have put a pre-defined CSA on a server (seperate from the CSA MC), which installed successfully and the MC sees the host.
However, although a pre-defined CSA is successfully installed on a host (non-server), I am unable to get the MC to see it. On the host, the CSA simply states that it's, "Not registered with the Management Center."
Please help in resolving this.
Also, is there a Windows Vista fix? Currently, I am unable to get the CSA to install on Vista.
~ Mike

If you look at the CSA log file, it will tell you an error code for why the connection is failing. Use the list below to determine what your error code means...
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,
** please rate if this helps**

Java Webconsole ELResolvers for JSR not registered with the JSP container

Trying to rebuild a LDAP server running Directory Server 6.1. Just installed Solaris 10 u9 on a SunFire V240. Loaded most recent recommended patch set dated 2011.02.02. Proceeded to load Directory Server V6.0 from native packages using JAVA ES Installer. After Directory Server installation and initialization the Java Webconsole is running but brings up a blank page login page. Note: Did not test the Webconsole prior to Directory Server installation. The errors in the /var/log/webconsole/console/console_debug_log file state:
Feb 8, 2011 10:32:32 AM com.sun.faces.lifecycle.ELResolverInitPhaseListener populateFacesELResolverForJsp
INFO: JSF1027: [console] The ELResolvers for JSF were not registered with the JSP container.
Feb 8, 2011 10:32:34 AM com.sun.faces.lifecycle.Phase doPhase
SEVERE: JSF1054: (Phase ID: RENDER_RESPONSE 6, View ID: /jsp/login/BeginLogin.jsp) Exception thrown during phase execution: javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl@13c3b45]
The JAVA version is: 1.6.0_22
The cacao version is 2.2.4.1
Kernel Patch is Generic_144488-06
Anyone have an idea what is causing this problem for the JAVA webconsole and how to fix it?

hi,
it is tomcat-6.0.20, JSF-RI 2.0.2 (Mojarra)
a whole bunch of libs and jquery4jsf (though really buggy in this manner, because all components could you rewrite for JSF2-components, etc.)
Unfortunately it is somehow a config error, because i haven't got it earlier, since i changed PhaseListener and Authentification with JAAS (sample from Ed Burns:
http://weblogs.java.net/blog/2006/03/07/repost-using-jaas-jsf, but with JDBC-based authentification)
cheers,
Istvan

IMessage on my mac says every contact is not registered with iMessage

When I type a contact to send an iMessage to from my mac, it turns red and says "message could not be sent, contact is not registered with iMessage"

Hi,
Start with the Apple ID site and the Manage ID option.
Check your Apple ID is verified and also that any Alternative email including the Recovery ID is also verified.
Check in Messages > Preferences > Accounts > iMessages account that the Apple ID is actually set to be active "Receive At" option
Same for any other email you have added.
In Contacts app check the Preferences > General section is set to the same Country/Region as the computer.
In System Preferences > Date and Time make sure the Date and Time are correct including the Time Zone and Daylight Saving if it applies.
It is worthwhile setting the Automatic Time Server function.
In the Finder > Go Menu > Go to Server enter ~/Library/Preferences into the dialogue box that appears.
In the Preferences find the com.apple.imessage.bag.plist file and (With the Messages app Quit) drag it to the Trash.
This file will hold the server the iMessages account is trying to use.
(Restart the app afterwards)
8:22 pm Thursday; September 11, 2014
 iMac 2.5Ghz i5 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

Suddenly not registered with iMessage

So why suddenly is a guy I've been texting from my iMac "not registered" with iMessages?

Hi,
If you Mac starts doing this to every single contact you try then it because the Mac is not logging in properly at the iMessages Servers.
Each devices has it's own unique Login to the iMessages servers.
For a Mac this means using the Mac's Serial Number to create the IDS: ****-Auth Token item where the ****s are your Apple ID.
You could try deleting this and Restarting Messages to see if it will recreate again.
If it does not (The Most likely outcome) then you will have to contact Apple Support.
To Fix and Apple ID is free. Level 1 responders tend to be Script Led and try to fit everything into Software or Hardware issues.
You are most likely going to have to ask for a Level 2 and ask them to check the iMessages server for your specific Mac and it's login.
9:19 pm Sunday; April 5, 2015
 iMac 2.5Ghz i5 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

Mavericks Messages problem sending message: "not registered with iMessage"

I'm on MacBook Air(MBA) and recently installed Mavericks. I try sending a message from MBA MESSAGES to a person's cell phone number (they have an android phone). Their name appears in red and I get: "...is not registered with iMessage." So I was trying to read discussions in here and allot of them say Messages won't work unless a person has an Apple device- iphone, Mac, etc. I want to know if that is true or if there is any other way to send from the MBA a message to them? I also tried from Messages on MBA to their gmail address, which they use on their android cell phone, and get same error.
Is there anyway a non-apple person can "register with iMessage" if they have an android phone?
I know I can email them, but I wanted a fast way for emergency purposes to get a MESSAGE to them from my MBA. Sometimes they can't talk on phone at some times, but are allowed to get instant message for emergency where they work.

Hi,
You have to have otr get an AIM or AIM valid name.
AIM stands for Aol Instant Messenger.
Apple IDs issued by Apple (Those ending in @mac.com or iCloud issued @me.com and @icloud.com) are valid as AIM Screen Names if the password is kept to 16 characters or less. (this is an AIM server limit)
Apple made an Agreement with AOL over the use of names over 10 years ago.
The Original .Mac ID (@mac.com) could be paid for or could be Trial Accounts.
Trial Accounts continued to work after the trial ran out. (i.e. the email stopped but the AIM Screen Name didn't).
The same was true of lapsed accounts.
When MobileMe started people could link, email-wise, their paid for .Mac accounts to the paid for MobileMe (@me.com) accounts.
Any @mac.com still works over the AIM service.
Now also @Me.com names worked - meaning some people had two valid AIM names - they are not liked for use with AIM just that the passwords will be the same.
With the end of MobileMe all those @me.com account died as far as AIM is concerned.
However you could link it to iCloud which effectively moved it to the iCloud server.
(i.e. they are iCloud issued @me.com ID instead of MobileMe ones)
Then Apple started to issue @icloud.com IDs
This could mean that some people have three working IDs for use with AIM (but all linked to one email Account at Apple).
NOTES
From Lion onwards (iChat 6 and Above) Apple have had the app also login in to Apple before it will allow the AIM Servers to "read" the password.
This applies to any iCloud issued ID - the "newer" iCloud linked @Me.com and @iCloud.com IDs
This means you cannot use those IDs in iChat 5 or earlier as those version only do an one point login only.
With the coming of iCloud other Apple IDs could be linked to iCloud which may have given you either @me.com and later an @iCloud.com ID as well or just an @icloud one if you were later to the party as it were.
Whilst in some cases this does give you two valid AIM Screen Name the originating Apple ID does not become one.
9:04 pm Saturday; February 8, 2014
 iMac 2.5Ghz 5i 2011 (Mavericks 10.9)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
 Couple of iPhones and an iPad

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

Similar Messages

Maybe you are looking for