No Central Monitoring server in exchange profile

Hi Experts,
I tried to configure alerts in RWB.
it shows No Central Monitoring server in exchange profile
The properties in exchange profile are as follows
hhtp port 8000
ashost FQDN has been specified..
ne idea on how to proceed with this?

Hi Ravi,
There arer some configurations needed to be done for central monitoring.Like activating reuired additional ICF services .Have you done all configurations perfect??
I think you missed activating ICF services for ALERTS..refer below link and read it..:)
http://help.sap.com/saphelp_nwpi71/helpdata/en/76/661b410210ef6fe10000000a1550b0/content.htm
Regards,
Raj

Similar Messages

Central Monitoring

I am trying to configure Central Monitoring for our environment and having problems getting the auto reactions to work on the satalite systems. I've installed the CCMS agent on the satalite but when the events occur that should trigger the auto reaction nothing is happening. The auto reactions occur fine on the central system.
My questions are, is the CCMS agent required on the central server as well as the satalite systems for the Central auto reaction to occur?
On my central monitoring server, shouldn't I be able to see all the satalite nodes in the list in RZ20? If so, how do I add them?   The only place I see the monitoring occurring centrally is in transaction DSWP under system monitoring. Why don't these systems show up in RZ20?
My auto Reactions are created on the Central Monitoring Server only. According to the documentation. When I look on the satalites they are not on those servers. Should they be?
Is there any clear documentation on setting this up?
Thanks,
Lee

Thanks for the response. I have configured my MTE's in RZ20 and I can see all the systems the environment.   I installed the CCMS agent on one of my nodes to test with. Im trying to figure out how to associate the alerts that I see in RZ20 with the autoreactions in RZ21?   I want to send alerts out for batch jobs from solution manager.
What I did was, went into RZ21,
Technical infrastructure - configure central system - assign central auto reactions
selected my system for system ID
selected R3BPServerSpecAbortedJobs for MTE Class
selected Z_CCMS_OnAlert_Emial-V2_Batch
I created the Z_CCMS_OnAlert_Emial_V2_Batch from CCMS_OnAlert_Emial_V2 and adjusted the paramters to use a distribution list which I created in client 000 and put my emial address in.   Im using Recipient -typeid C
But when jobs fail, that I think should trigger an alert, Im not seeing anything go into SCOT.
FYI.. emialing from SO01 is working fine so there is no problem with the emial just with the auto-reaction.
Any thoughts on how to test this?
Thanks
Lee

Exchange profile parameter problem after system copy of XI server

I'm getting problem after the system copy of XI server. Following is the details. pls help to fix this one:
XQA is the system copy of XDV server. XQA is installed on rx2n1v1 server and XDV is installed on dbcixdv server. Following is weblink of XQA and XDV.
XQA: http://rx2n1v1:57400
XDV: http://dbcixdv:57000
After the system copy of XQA, i changed all xdv related parameters (hostname/port) in visual admin and configtool of XQA server.
Now when i run sxmb_ifr tcode in XQA, it should open the link of XQA server ( http://rx2n1v1:57400). But it open the link of XDV server (http://dbcixdv:57000).
The cause of this problem is the xdv parameter entires (hostname/portnumber of xdv) in exchange profile of XQA server (http://rx2n1v1:57400/exchangeProfile).
Now if i change hostname/portnumber of xdv in XQA server (http://rx2n1v1:57400/exchangeProfile), it also make the same change in XDV server (http://dbcixdv:57000/exchangeProfile).
Both XQA and XDV are in differnet hardware server. I don't understand why making changes of exchangeprofile in XQA also changed the value of exchangeprofile in XDV.
Hope it clarify.
Pls give the solution of this problem.
Thanks
Amar

Arjun,
http://<SAPHOSTNAME>50000/exchangeProfile
Yes, I can use above, but changing connection information gives me
RFC call returned an error code: 399
Use this one
http://hostname:50000/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp
This one, yes I get to the exchange give me an error: RFC call returned an error code: 399
http://hostname:50000/dir/start/index.jsp -->Administration -->login with PISUPER -->ExchangeProfile.
Internal Error
Internal error; contact your system administrator
Unable to read configuration data (ExchangeProfile/aii.properties)

Exchange Infrastructure Central Monitoring

Dear Experts,
I would like to know whether there is anyway to have central monitoring tools that can be setup in XI(i am not prefer to have CCMS monitoring),it should be more advance than the CCMS monitoring. I know there is a tool called "BMC Patrol" that can be used for monitoring purpose. But is that can be done in XI too? We want to monitor all the information that can be monitor such as the connection between R/3 system, message monitoring and so on(from Java to ABAP). If yes please send me the information and guides to setup such Monitoring tools
Thank You
Regards
Ramesh
Edited by: Ramesh Kupusamy on Aug 20, 2008 11:42 AM
Edited by: Ramesh Kupusamy on Aug 20, 2008 11:43 AM

Hi,
Refer
SAP Network Blog: How-to enrich XI monitor's output
How-to enrich XI monitor's output
Real time XI Monitoring
Thanks
Swarup

SALRT_CREATE_API with CBMA and/or Central Monitoring using Solman

Hi,
Does anyone know if function SALRT_CREATE_API can be used to raise alerts in Component Based Message Alerting (CBMA) and/or Centralised Monitoring in Solman? I understand SALRT_CREATE_API worked with the classic Alert Framework.
Che

Hi Michal,
Thank you for jumping in on this thread. Great timing with your blog
However the following thread suggests we can still use SALRT_CREATE_API:
XI Alerting and Central Monitoring : some alerts remain on PI
"Try removing the "CentralMonitoringServer-XIAlerts" RFC connection from both systems (proxy and PI). Then, ensure all com.sap.aii.rwb.server.centralmonitoring.* parameters are configured correctly on PI (restart system to apply changes on exchange profile) and try executing the scenarios again.
Check the target CCMS system the RSALERTDISP report and see if the alerts are being received there."
Perhaps the above only applies in the case of a dual stack? I am not quite ready to try some examples but when I do then perhaps options will become clearer to me. I will try to remember to update this thread with what I find.
Thanks
Che

Central Monitoring of Multiple XI Instances

Is it possible to have central monitoring (message and end-to-end) for multiple XI instances in a landscape?
We have a landscape with one Central XI instance and multiple local XI instances.
Is it possible for me to ...
1. Add the local XI integration servers to the component monitoring?
2. Monitor the messages flowing through the local XI instances in the central XI RWB (even for messages that do not flow through the central XI)?
3. Have end-to-end monitoring even for messagesthat do not flow through the central XI?

Try removing the "CentralMonitoringServer-XIAlerts" RFC connection from both systems (proxy and PI). Then, ensure all com.sap.aii.rwb.server.centralmonitoring.* parameters are configured correctly on PI (restart system to apply changes on exchange profile) and try executing the scenarios again.
Check the target CCMS system the RSALERTDISP report and see if the alerts are being received there.

No alerts from AAE after configured Solman as central Alert Server

Hi all,
i have configured a Solution Manager system to act as a central alert servcer for our PI landscape. We are using PI 7.1 ehp 1.
I changed the required nodes in the exchange profile and created the PIRWBUSER in the solution manager system. After restarting the J2EE engine of the PI system the alert rules are no created on solutiuon manager and alerts which occur in the integration engine are raised in the solution manager system. However alerts which are raised in the AAE are not forwarded.
When i check the application log in NWA I see the follwing error, whenever an alert should have been raised:
No central monitor defined in RWB.
Thrown:
com.sap.aii.rwb.exceptions.JaycoRequestFailedException: Neither messager server nor application server are defined for system SMB
at com.sap.aii.rwb.core.R3System.getITSUrl(R3System.java:1090)
at com.sap.aii.rwb.core.R3System.getITSUrl(R3System.java:1558)
In ABAP the connection CentralMonitoringServer-XIAlerts is configured correctly as alerts from the IE engine are working. I suppose I missed some configuration in the java stack. Can somebody help me on that?
Best regards and thx
Florian
Edited by: Florian Wittke on May 10, 2010 9:25 AM

Hi Caio,
thanks for your replay. Yes I know this note. But it does not solve my problem. I increased the trace level of the location where the alerts are raised in adapter engine. I get the following new entry:
Connect to message server host failed
Connect_PM TYPE=B MSHOST= FQDN GROUP=SPACE R3NAME=<SYSID> MSSERV=sapms<SYSID> PCS=1
ERROR service 'sapms<SYSID>' unknown
TIME Mon May 10 15:27:48 201
RELEASE 711
COMPONENT NI (network interface)
VERSION 39
RC -3
MODULE niuxi.c
LINE 1654
DETAIL NiPGetServByName: 'sapms<SYSID>' not found
SYSTEM CALL getaddrinfo
COUNTER 1
Issue has been resolved..the message server was not reachable due to missing entries in the services file.
Edited by: Florian Wittke on May 18, 2010 11:58 AM

PI 7.11 sp6 system copy Exchange Profile error code: 399

Experts,
We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.
I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).
I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1
I did not run into any major problems doing the steps of the copy itself.
I did the usual "post" steps, documented in the guide that really are done on any NW system.
Then I got into the specific "PI" post steps and that's where I now have a problem.
I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.
My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:
com.sap.rprof.dbprofiles.DBException: RFC call returned an error code: 399
I'm certain the user is NOT locked and the password is correct for PILDUSER. It'll give me a different error if I put the wrong password in, so I know it's hitting my system.
Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!
If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.
I see these errors in the default trace and application log:
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND:
No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",
Name="PIT.SystemHome.<traininghostname>"
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="PIT.SystemHome.<traininghostname>"
at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120)
#2.#2011 11 03 13:49:47:008#0-500#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#7E3832DEA80F002B00000000008700C6#4804850000001902##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#J2EE_GUEST#0##0AFD01D4064C11E1CB5E7E3832DEA80F#0afd01d4064c11e1cb5e7e3832dea80f#0afd01d4064c11e1cb5e7e3832dea80f#0#Application [24]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.#2011 11 03 14:51:18:096#0-500#Error#com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract#
#BC-ESI-WS-JAV#tcesiespsrv#7E3832DEA80F001100000000009A004C#4804850000001385##com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract####109F6812065511E1BF9C7E3832DEA80F#109f6812065511e1bf9c7e3832dea80f#109f6812065511e1bf9c7e3832dea80f#0#Service Runner [tcesiespsrv]#Plain##
+There is problem reading the hostname from the ClusterManager. This could lead to improper wsdl links.#
SLDCHECK shows this:
Function call returned exception code 3
Access to the XI Profile is currently disrupted.
I can't be the first person to run into this.
SO strange that I can actually plug in either my dev/QA or PROD hostname in the "ABAP connection" box and it WILL ACCEPT IT...but then, it registered my training system as a "non central adapter engine". I don't want that.
Any ideas?
Another issue is that the SLD PI information from the PIT system is missing the "Integration Directory". It has the other 5 entries...Adapter Engine, Domain, Integration Repository, Integration Server, RWB.
Thanks for reading this,
NICK

Here is the error I get when I try to change the "abap connection" to the correct hostname:
RFC call returned an error code: 399
Stack Trace class com.sap.rprof.dbprofiles.DBException: <pre>at com.sap.rprof.dbprofiles.DBProfiles.checkReturn(DBProfiles.java:184) at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:105) at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1378) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:204) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfile(RemoteProfile.java:154) at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfile(ExchangeProfile.java:46) at com.sap.rprof.remoteProfile.webui.ProfileWebTree.<init>(ProfileWebTree.java:24) at com.sap.rprof.remoteProfile.webui.Edit.getWebTree(Edit.java:322) at JEE_jsp_treeexprof_4804850_1319481176000_1319565151782._jspService(JEE_jsp_treeexprof_4804850_1319481176000_1319565151782.java:59) at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:436) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:493) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327) </pre>

Error while openning Exchange Profile

Hi All,
I am facing problem while opening Exchange Profile
http://<>:<>/exchangeProfile/index.html
and it says "Name or Password is incorrect (Repeat logon)" and after several attempt "Password logon no longer possible -too many failed attempt"
It is not taking any Username and Password, with any username i am not able to logon.
perfect solution will be aapreciated.

Hii
Their is authorization issue in the log in id ..
Pls find the links for it ..
http://help.sap.com/saphelp_nw04s/helpdata/en/89/6f1741b393f26fe10000000a1550b0/frameset.htm
Check for locked user even-
SUIM --> user --> with unsuccesful logons
According to SAP,
"Each J2EE-based component of an XI landscape has an exchange profile access client installed, where JCo RFC connection data for the central exchange profile is maintained. The connection data for the exchange profile is stored in the J2EE secure store of the component. The user specified in the connection data should have the ABAP user role SAP_BC_AI_LANDSCAPE_DB_RFC on the Integration Server."
So check the ABAP user role and see if it is SAP_BC_AI_LANDSCAPE_DB_RFC.

Exchange Profile not working in EP system

Hello All,
In our EP 6.0 system , if i try to view the exchange profile it throughs up some exceptions .
First my doubt is , wheather an exchange profile is maintained for an EP system like our XI/PI systems ?
If it is maintained then it has some problem ,Can any one clarify my doubt .
When I open up exchange profile url, below exceptions it throughs up
http://ussapdje00.corpnet2.com:50200/exchangeProfile/index.html
ABAP connection object not setup.
Stack Trace class com.sap.rprof.dbprofiles.DBException:
at com.sap.rprof.dbprofiles.AbapConnect.createJcoClientInstance(AbapConnect.java:535)
at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfile(RemoteProfile.java:141)
at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfile(ExchangeProfile.java:45)
at com.sap.rprof.remoteProfile.webui.ProfileWebTree.(ProfileWebTree.java:24)
at com.sap.rprof.remoteProfile.webui.Edit.getNewWebTree(Edit.java:327)
at jsp_treeexprof1235100618102._jspService(jsp_treeexprof1235100618102.java:32)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Best Regards
Rakesh

Hello Prem,
Thanks for replying .
Ok..If that is the case , where should I edit the details relating to fully qualified name .
In portal under WebDynpro->start Assigned SLD -->
it is mentioned as only server name followed by its port number ,not the fully qualified name .
Due to this when I click on the tab it says page can not be displayed .
Where as when i execute through internet browser by mentioning fully qualified name SLD is displayed .
Instead of http://ussapdje00.corpnet2.com:50200/sld it is mentioned as http://ussapdje00:50200/sld.
Can you kindly let me know , where to edit this particular entry to fix the problem .
Best Regards
Rakesh

Importing the exchange profile in PI 7.1

Hi,
system is PI 7.1
1. System copy is done and then in post intallation process.
2. On PI System AII_PROFILES table is empty and i tried to import the the exchange profile from the link
 http://<host:port>/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp
 it showing the profile is imported successfully but it is not getting updated in database as well as the tree for exchange profile is not showing in the parameter tree.
3. after system copy there was no aii.properties file in server0 directory. i created the file manually but it is not picking the value from the aii.properties file
Please reply urgent.

Hi,
Have you followed the same procedure to import as below?
 1. On your Integration Server host, open the following URL:
http://<AS_Java_host>:AS_Java_port>/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp
The following naming convention applies for <AS_Java_Port>:
5<AS_Java_instance_number>00
50000, for example, if your AS Java instance is 00
 2. Enter the logon information:
User Name: PISUPER
Password: <pisuper_password>
The Exchange Profile page appears.
 3. Choose Connection.
The ABAP Connection page appears.
 4. Enter the required information for the PI host.
Use the logon information of user PILDUSER.
 5. Choose Set.
The Exchange Profile page appears.
 6. Choose Import.
The Import profile from database page appears.
 7. Choose Browse and select the following file:
/usr/sap/<SID>/SYS/global/xi/exchange_profile.xml
If you cannot run a Web browser on your PI host, you need to copy the file exchange_profile.xml from the PI host to a host where a Web browser runs.
 8. Choose Import Data.
The profile is imported.
Regards,
Venkata S Pagolu

Problem in importing SAP Exchange profile (BASIS settings) - Urgent

Hi,
I am currently facing problem in importing SAP Exchange profiles manually.
When i enter into http://<J2EE_host>:<J2EE_port>/exchangeProfile with username as PISUPER, the page is getting loaded but
1.it shows a error message stating, Name or password is incorrect
2. When i ignore that error and proceed with the connections tab to edit the server settings, i cannot set the password for PILDUSER. It again says, Name or Password is incorrect..
What could be the reason for these errors. Please help me... This is very urgent....
Thanks in advance,
Rose

Thanks for your response guys. I checked for PISUPER and PILDSUPER in SU01 and checked for lock but it shows an error message saying User doesnot exist.
Kindly let me know how to procced on in this case.
Thanks and Regards,
Rose.

XI 3.0 System Copy - Exchange Profile incorrect

Good day,
I have copied an XI 3.0 according to the system copy guides.
I had the source system "live" as well as the "target" during post processing. During this time, I had the hostname of target populating my source SLD Exchange Profile.
As I cannot find anything documented, can anyone advise what the process should be do achieve a system copy.
Must the source be unavailable(down altogether) when doing the copy and post processing?
Any input from anyone who has been through this process will be geatly appreciated.
Thanks,
Derek

Hi,
I am facing the same problem, please help me.
We are using XI 3.0 on Windows and MSSQL platform, i have made system copy sucessfully from production system with process of DB restore for ABAP and Java Import, the new server is up and running both abap and java.
Problem : In the newserver when i execute the tcode sxmb_ifr it takes me to production server url and not the new server hostname url.
when i tried the http://newserver hostname.com:50000 it works fine. but from this url except home page every other link like exchaneprofile, SLD,IR and ID links still points to the production server host name.
Please look at the following post installation activities i have performed till now in new serverand please guide where else i have to change the host name in the new server.
Note: i did not cange the logical system assignment in scc4, beacuse i was not sure about the other problems we may face after directly assigning new logical system to the productive client in new server.
1. Run installation check: Administration u2192 System administration u2192 Administration u2192
Installation Check (transaction SM28).
2. Configure the Workbench Organizer (SE06) with the option Database Copy. This
releases all transport, repair, and customizing requests that have not been released in
the source system.
3. Configure STMS
4. In transaction RZ70, change the value for the host and the gateway service in the group box
Transport Information
5. Change the pipeline to the Integration Server by running transaction SXMB_ADM -> Configuration -> Integration Engine Configuration
6. Open Visual Administrator -> Change the new host name in the following
services -> Jcorfcprovider all the services
services -> SLD Suppiler
7. Host name Change in SLDAPICUST
Note: In the SAP system copy guide it says me to chane few parameters in exchange profile but when i go through the url http://newserver hostname.com:50000/exchangeProfile it takes me to production server, is there any option to change the exchange profile parameters ?
Please help me.
Thanks
Sonali

Install Adobe central output server 5.5 in windows XP

hi,
Anybody know how can I install Adobe central output server 5.5 in my XP profesional. and where to store all related files( JFserver,JFMerge ....)

did you get anywhere with this ?? I have built a new Windows 2012 R2 server and am having issues emailing out to external addresses. I can email to internal ones on our Exchange 2013 cluster. I have exactly the same settings in the JfEMsend.ini file as well as the same DNS.. I get invalid recipient. Not quite the same problem but could be related
thanks

SBS 2003 to Server 2008/Exchange 2007

We are in the process of moving our location and are in need of moving
from SBS to something with more CALs. I want to make this as seemless
as possible for the end-users.
We are currently on SBS 2003.
My plan:
Purchase new 64 bit server with Server 2008 and Exchange 2007.
Add new server to existing domain.
Move/migrate exchange from SBS to new server.
Make sure the user info and and Group profiles move to the new server
(not sure how to do that)
Remove the SBS, and promote the new 2008 to DC.
Possibly rename the 2008 to the same name and IP as the old SBS (so
outlook users do not have to change anything)
Would that be the correct route? If so, what am I missing? (Looks
easy on paper)
Thanks,
Mike

hi
here is a lead
Start by installing Windows Server 2008 on the server you’re intending on using for mail. In our example we installed all the Exchange functionality on a single server – in practice you’ll probably want to separate out the Hub and Storage
functions, and use a separate Edge server for mail traffic and user access to mail. There’s no problem with connecting to the network while you’re doing the install – Windows Server 2008 installs as a workgroup server – and you’ll
automatically be delivered the latest drivers and the most up to date OS patches. You’ll also need to give the server an appropriate fixed IP address, as it’s going to become a key component of the network infrastructure.on the role and feature-based
install model introduced with Windows Server 2003 and enhanced in Windows Server 2003 R2. Make sure you use these tools to install Internet Information Server – as Exchange 2007 will use it for Outlook Web Access and Exchange ActiveSync. Exchange 2007
requires that servers have the PowerShell management scripting environment and the
.NET framework. We’d also recommend installing Terminal Services as part of any Windows Server installation, as using Remote Desktop to access the new server and the existing SBS 2003 domain controller will let you handle much of the
migration process from the comfort of your desk.Once Windows Server 2008 has been installed, take out the install DVD and shut the server down. As you’re going to be adding a Windows Server 2008 machine to what’s really a Windows Server 2003 network,
you need to upgrade the Active Directory schema on our SBS 2003 server. This will allow you to manage the Windows Server 2008 machine from the SBS 2003 machine. You may need to update your version of Remote Desktop to one that supports the latest versions
of the RDP protocol.Put the Windows Server 2008 DVD in your SBS 2003 machine’s DVD drive (a network accessible DVD drive is suitable, especially if access to any machine room is limited, and you’re using Remote Desktop to manage
the server). Open a command line and change directory to SOURCES\ADPREP. You need to use ADPREP.EXE to update the Active Directory schema. Start by typing the following command to update the Active Directory forest.adprep.exe /forestprep.This will
begin the process of updating the schema. Be prepared to wait some time, especially if you’re working with SBS 2003 rather than SBS 2003 R2. Once the forest schema has been updated you can update the domain schema. Type the following command:adprep.exe
/domainprep.You’re now ready to bring the new Windows Server 2008 machine into your existing domain. Turn on the server, and then log in as a local administrator. Again, you can use Remote Desktop to work with the server, so you don’t need
to sit in the machine room.to the existing SBS-managed domain. Once the server is part of the domain, you will to promote it from a member server to a domain controller. Launch DCPROMO
using the Start menu search bar to find the program. Choose to add a domain controller to an existing domain. You’ll need to use the credentials of an existing domain administrator to start the process.Make the server a Global Catalog server.
If you’re going to be keeping the existing SBS 2003 system there’s no need to make the new server a DNS server. DCPROMO will then add the requisite Active Directory Domain Services to your Windows Server 2008 machine. This can take some time, especially
if you’re working with a large SBS-managed network with more than 50 users. Once the DCPROMO process is complete you’ll need to restart the server. You can now log in as a domain administrator.Now you can start the process of installing Exchange
2007 on the new server. There’s one key issue that needs to be dealt with first. Exchange 2007 needs to install on a server that’s a Schema Master.
One of the limitations of SBS 2003 is that the SBS server needs to own all five of the FSMO
roles. The Flexible Single Master Operations are key domain management tasks, and in a standard Active Directory implementation, these roles can be parcelled out across several servers. Microsoft’s restrictions on SBS can be overcome –
as the SBS licence allows FSMO roles to be temporarily transferred to other servers for the purpose of server migration and major hardware upgrades. You can continue to run SBS for up to seven days (there is an option to install an update that extends this
to 21 days) with the FSMO roles on other servers. Don’t let the migration drag on as after that point, the server will reboot every hour, until the roles are transferred back.You’ll need to be logged in to your SBS server to move the Schema Master
to the Windows Server 2008 machine. Start by registering SCHMMGMT.DLL. This allows you to use the Windows Schema Master management tools to transfer the Schema Master role to the Windows Server 2008 machine. Open a command line and type the following command.regsvr32
schmmgmt.dll
You’ll next need to open the Windows Management Console. Once you’ve done this, by typing
mmc at a command prompt or from the Run option on the start menu, you can load the Active Directory Schema management snap-in. From the File menu click Add/Remove Snap-in. This opens a dialog box where you can choose to add the appropriate
tools. Choose Active Directory Schema. This will load the schema management tools, which you can use to move the Schema Master to a new machine.In the Schema Manager console, right click on Active Directory Schema and then choose Change Domain Controller.
You’ll see a list of available servers. Choose the new Windows Server 2008 machine, and then click Change to move the Schema Master role to your new Exchange machine. Right click Active Directory Schema again, and choose Operations Master. This allows
you to make the new server the operations master for the FSMO role we’ve just transferred.
Now you can start the Exchange 2007 installation. Log on to the server, and load the Exchange 2007 DVD; using an Exchange 2007 SP1 DVD reduces the amount of time you’ll need to set aside for downloading and installing uploads. Choose the appropriate Exchange
installation for your network needs – a typical install with Hub Transport, Client Access and Mailbox roles should be sufficient for most small networks. Once Exchange has installed, restart the Windows Server 2008 machine and then open the Exchange
Management console to confirm that your install completed successfully.You will now have added your new Exchange server to the existing SBS Exchange network. On the SBS server open the Exchange System Manager.Expand the Administrative Groups tab to see the
available administrative groups. Your new server should have added itself as Exchange Administrative Group (FYDIBOHF23SPDLT). Do not move it out of this Administrative Group or the associated routing group, Exchange Routing Group (DWBGZMFD01QNBJR) –
these are required to allow Exchange 2007 to interoperate with Exchange 2003. (As a side note, there’s definitely a sense of humour in the Exchange team at Microsoft, as the default administrative group and routing group names are both Caesar Ciphers
of EXCHANGE12ROCKS).If you’re planning to run the two servers together, you can now move the Schema Master FSMO role back to the SBS server; if you’re not, you now have seven days to finish your complete server migration before the reboots start.
To move the role back use the Active Directory Schema MMC snap-in and change both Domain Controller and Operations Master to point to your SBS server.Now you can start to move mailboxes between the two servers. This is where things can start to take time,
so schedule mailbox moves for evenings and weekends – and make sure that you’ve backed up all the existing mailboxes before you start the migration.
You’ll also need to make sure that both servers have the same mailbox size limits – otherwise large mailboxes will fail to move successfully. If you’re unable to make moves at night, you can do them during working hours –
but users will be unable to connect to the Exchange server while their mailboxes are being transferred (remember to warn them in advance). Any mail that’s been delivered to the server during a mailbox transfer will be queued and delivered once the mailbox
is on the new server.
The actual process of moving mailboxes from the SBS Exchange 2003 server to Exchange 2007 is relatively simple. Log on to your Exchange 2007 server, and open the Exchange Management Console. Expand Recipient Configuration, and select the Mailbox
view. This lets you see the organisation’s mailboxes, along with where they’re currently stored. A pane on the right gives you various Actions you can perform on the mailboxes. These include the Move Mailbox wizard.
This wizard is the simplest way of moving mailboxes between servers – and, along with the underlying move – Mailbox PowerShell commandlet, is the only supported way of moving mail to an Exchange 2007 server. If you’re moving a large set of
mailboxes it’s worth writing a PowerShell script to handle the move for you.
Use the Move Mailbox wizard to move either an individual mailbox or groups of mailboxes (shift-click to select several at once). As the wizard is multi-threaded it can handle up to four mailbox moves at once. First select the target database, and then choose
the move options. You can choose to abort the move if corrupted messages exist, as well as choosing the appropriate Active Directory servers. You can also schedule the moves for out of hours – so you don’t have to be on site for a move to take
place – as well as making sure that any moves that haven’t taken place inside a set time limit are cancelled. The wizard will check mailbox quotas before making a move to make sure that the system limits allow the mailbox to transfer to a new server.
Once a move’s started you’ll see a progress bar showing the status of the move, with descriptive text for the current step in the move process. When a move completes there’s a summary screen with the results. There’s also an XML
format report you can use for further analysis.
We found that a large 4GB mailbox took about 3 hours to move, over a gigabit network. In practice, most mailboxes are a lot smaller, so expect to be able to move many more SBS mailboxes in a single overnight session. Once the mailboxes have been moved, your
Outlook users will automatically be switched to the new Exchange server. There’s no need to change anything on the desktop – the Exchange organisation will handle the changes for you. There’s one exception; if you have used a self-certified
certificate for the SBS Exchange server, you may need to delete it from all client devices (including Windows Mobile) so they can connect – especially if you’re using the same external DNS name.While Outlook handles the changes gracefully, things
aren’t so easy for users working with ActiveSync connections to mobile devices or for secure IMAP and POP3
connections. Mobile users will need to perform a manual sync on their phone (they’ll get a message in ActiveSync reminding them to do this) and accept the server policies before mail will start arriving. POP3 and IMAP connections will only continue
to work if you make sure that your new mail server has the same external CNAME as the old SBS install. If you’re not using the same DNS name, you’ll need to recreate connections for external mail clients.
Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

No Central Monitoring server in exchange profile

Similar Messages

Maybe you are looking for