CHARM - avoid developer login to client 000 when import to QA system

Hi Gurus.
I've activated a new system to use CHARM for import. When testing the import to QA, the logon screen to QA 000 is displayed.
I already applied SAP Note 913232 which suggests that the TMSADM user (with profile S_TMW_OPERA) in QA 000 can be used as default user for import so that developer don't need to exist in QA 000, but it still didn't fix the issue.
Are there other configurations that I need to do to fix this issue.
We are currently using SOLMAN 7.0 SP25.
Thanks,
Tess

Hi Tess,
Check the TMW and trusted RFC mapped to correct client of satellite system.
SM_(system)CLNT(client)_TRUSTED
SM_(system)CLNT(client)_TMW
Rg,
Karthik

Similar Messages

Unable to login to client 000

i tired by running the SCCR_UNLOCK_CLIENT in se37
but no way
but i was able to login 800 and other as well

Hi,
You have to delete SAP* user from database and enable sap* login parameter and restart the instance.
http://sapfaq.wordpress.com/2008/02/14/hello-world/
Regards,
SBK

CTS + Error when Importing to target system (Q)

Hi all,
I have configured CTS+ for our portal landscape. I'm using Solman 7.0 as domain controller. I have released a transport from D system to Q, It creates a Q buffer properly. But when I try import in Q, I get the following error;
Internal communication error with destination CTSDEPLOY
ERROR_WEBSERVICE_RUNTIME_INIT Error when instantiating the Web service runtime (No logical port 'CTS
>>>DEPLOY' exists for the proxy c lass 'CO_TFLDEPLOY_PROXY_VI_DOCUMENT' )
I am not able to fix this issue. Can someone help in this regards?
Thanks,

Do this:
1. Call transaction RZ21.
2. Choose "Technical infrastructure -> Reorganize segment table".
3. Choose "Add missing logical ports to this client", and choose "Execute".

Client Copy Export/Import on large system. 1.5 TB

Hi,
We have a 3 tier landscape. DEV, TST, PRD.
Database size in PRD is 1.5 TB (1500 GB)
Our developers need fresh master and trans data in TST and DEV.
We are thinking about making a
PRD --> TST (1.5 TB) we do a system copy.
TST --> DEV (1.5 TB) we can't do a system copy. (Company policy says not to touch repository objects, version management what so ever in DEV....)
1. How long will a client export / import take from TST --> DEV, lets say we have "good HW" ? Will it work ?
2. I've read about TDMS but its toooo expensive.....is there maybe any 3 party tool that is good for this purpose ? Transfering 1.5 TB of data ...
Br,
Martin

Hi,
>1. How long will a client export / import take from TST --> DEV, lets say we have "good HW" ? Will it >work ?
In my opinion, a 1.5 TB database is much too big for a client copy.
It will work but may last a full week and would degrade the production system performance.
We have 1.3 TB databases and stopped using client copies since the system was 300 GB...
We only use database restores and renaming for system refresh even for the dev system.
There is procedure to keep the versionning of sources.
Regards,
Olivier

Error: The sap bw system must not be operated in client 000

Hi
I login as a client "200" and create new user "imran" and then login as a client 200 and user imran successfully but when I goto T.code RSOR it shows "the sap bw system must not be operated in client 000" when I check the status it shows client 200 and user imran.
so what is the solution??
Regards
Imran

hi
Yes I create new client "200" in a sap* then I login as a client "200" user "sap*" and password "pass" then create new user "imran" using copy DDIC then login as client 200 and user imran but result is same.
Edited by: iskhan on Nov 5, 2009 7:24 AM
Edited by: iskhan on Nov 5, 2009 11:36 AM

What's the differece between BI client 000 and 001 ?

Hello exports,
We copy the client 000 to client 100, then we done the configuration "Integration into Portal " at client 100.
But we can't success, we found that client 100 miss 7 system users( J2EE_ADMIN,SAPJSF,SLDDSUSER and so on). After we created 7 system users manually, the configuration "Integration into Portal" was sucessful .
As default, Portal connect to client 001 .
Is there any other differences bewteen BI client 000 and 001 except 7 system users ?
Thank you !
Best Regards,
Chen Jianguo

Clients are part of the defining technical structure of the SAP System. Each client contains its own master records and set of tables.
Customizing is either client-specific or cross-client, depending on which business data is configured. Cross-client Customizing is valid for all clients in an SAP System.
When you install the SAP System, the following clients are available:
Client 000 as SAP reference client
Client 001 as production preparation client
More info here:
http://help.sap.com/saphelp_nw04/helpdata/en/7e/c8189452c511d182c50000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/6c/a74a3735a37273e10000009b38f839/frameset.htm
Hope it Helps
Chetan
@CP..

Transport of modifications with ChaRM in client "000"?

Hi,
I do have a typical logical component DEV:100 -> QAS:100 -> PRD:100.
For standard customizing and workbech tansports all is working fine.
Now I have done a modification on a standard SAP object. Therfore the system wants to have a transport for client "000".
But with standard ChaRM I only user the typical logical component with the standard transport routes for client 100.
Does anyone have had a similar problem or a solution for that?
To change the system in the transport does not work, because SolMan does check the ChaRM related transports within a special table.
The only solution, which is in my mind, is the use of a second logical component for client "000" to do the modifications.
Thanks for any help.
Regards,
Alex

Agree with you Alex. For defining multiple routes in ChaRM, you need to define different logical components and assign them to the maintenance cycle.
Rajeev

Error is STMS when import client from 2 different system

I have two system in same landscape, system 1 is production with system ID : SEP, system 2 is develop with system ID : SED (is Domain Controller),
system 1 & 2 in same domain with Domain Controller : DOMAIN_SED in STMS
And then, I exported client 800 on production system (system 1) with profile SAP_EXPA
and I have 3 request : KO00189.SEP ; KT00189.SEP ; KX00189.SEP (cofiles) and RO00189.SEP ; RT00189.SEP ; RX00189.SEP (data)
I copied 3 request above into system 3 (system 3 is different landscape with 2 system above and i setup system 3 at different location, so called backup system. System 3 is setup with system ID: SED and Domain Controller DOMAIN_SED too)
Then i imported client 800 into system 3
and i have an error in system 3 : System unknown in Transport Management System
Please help me ...
Thanks all

hi Shanker !
after reset user TMSADM -> connection not change -> connection work OK
i tried it but error remaining
Information extra :
system 3 is a physical system with Domain Controller : DOMAIN_SED ****** SID : SED and extra setup a virtual system as SEP on system 3
I configured tranport route from SED to SEP, so error "System unknown in Transport Management System" no longer
but arise new error "Error occurred in SED TMS communication"
Information extra error "Error occurred in SED TMS communication" when import request :
Error occurred in SED TMS communication
Message no. XT149
Diagnosis
An error occurred in the TMS communication layer of the following SAP system:
   System: SED.DOMAIN_SED(000)
   Function: TMS_CC_READ_CCCFLOW_OF_TRKORR
   Error: SERVICE_NOT_AVAILABLE ()
System Response
The function terminates.
Procedure
Check your transport control station configuration with transaction STMS.
thanks all
I hope error to solve soon .....

Client 000, 001 and 066

Hi everyone,
Pretty new to SAP.
I am struggling to find answers to the following questions:
How do you use client 000, 001 and 066?
Apart from initial installation and support (066) can theses clients be used in development, testing and production environements?
Can 000 and 001 be used as working clients or should they only be used as template?
What should their configurations be when using SCC4 for each system inthe landscape: DEV, QA and PROD (and Solution Manager)
From a security point of view, once SAP*, DDIC have been secured should they be any other users (Dialog, System) in these clients?
Sorry quite a few questions but if anyone could give me direction as I am trying to understand if some of our current settings are correct and if not why.
Thank you

Hi Corinne,
Even though it is a very basic question, it is very essential to understand and find an answer to your questions.
Client 000, 001 and 066 are (as you know) standard clients thats pre-built when you install SAP.
"Apart from initial installation and support (066) can theses clients be used in development, testing and production environements?"
Answer: No, they cannot be used for development, testing or production environments. When I say, "they cannot", I mean they are not supposed to be used.
"Can 000 and 001 be used as working clients or should they only be used as template?"
Answer: Client 000 is basically used as working client only when you do support pack upgrade or ABAP load generations (SGEN) and implementing additional languages, etc. Otherwise, client 000 should not be used as a working client. The same applies to client 001. But the only exception with 001 is, with Solution Manager, 001 will be your working client. You will do all configurations and obtain support from SAP through this client. With other Systems like BW and CRM, this client (001) will not be a working client.
"What should their configurations be when using SCC4 for each system inthe landscape: DEV, QA and PROD (and Solution Manager)"
Answer: In the production system - "Changes and Transports for Client-Specific Objects" should be set to "No Changes allowed". "Cross Client Object Changes" should be set to "Changes to Repository and Cross-Client Customizing Allowed". "Protection: Client copier and comparison Tool" must be set to "Protection Level 1: No Overwriting". Same applies to Quality System and Development System. These are by-the-by default settings also when you install the system.
"From a security point of view, once SAP*, DDIC have been secured should they be any other users (Dialog, System) in these clients?"
Answer: Once you install the system, you must first make a copy of DDIC to any user you create in your name or any standard name. Never use DDIC when you do initial settings after the installation.
The following link might be of some help to you.
http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/c8189452c511d182c50000e829fbfe/frameset.htm
Hope this helps.
Thank you.

Use of clients 000 and 001 & their differences?

hi guys,
Any one explan me the use of predefined clients 000 and 001
The differences between them

Hi,
Clients 000, 001 and 066 are standard clients that are pre-delivered by SAP. These clients are not supposed to be used in development, quality and production environments.
Client 000 is basically used as working client only when you do support pack upgrade or ABAP load generations (SGEN) and implementing additional languages, etc. Otherwise, client 000 should not be used as a working client. The same applies to client 001. But the only exception with 001 is, with Solution Manager, 001 will be your working client. You will do all configurations and obtain support from SAP through this client. With other Systems like BW and CRM, this client (001) will not be a working client. Two standard users (SAP* and DDIC) are defined in the clients 000 and 001.The client 066 is used only for EarlyWatch functions (Monitoring and performance). The user EarlyWatch is delivered in client 066 and is protected using the password SUPPORT. This password needs to be changed for security purposes.
Rgds,
Suman

Developer helping a client with BC

I'm a developer helping a client who uses BC. I can log into their back end and have been helping them with their website. But now a question has come up about their monthly invoice from Adobe for BC. When I log in now, I see their outstanding invoice and could pay it (Submit button) if I were the one responsible for that. But I'm not, so I click the Pay Later button so I can do my work. And my client doesn't seem to be receiving the monthly invoice from Adobe for BC via email. Do I need to tell them to log into the back end of their site to pay their monthly invoice? That seems a little lame to me.
I think what has happened is that there has been some personell changes for my client. Perhaps whomever handled paying their monthly invoice no longer works there. So I'm just trying to gather information here in order to clue them in as to what to do. Is there an Adobe ID associated with Adobe BC accounts where my client could log in somewhere—other than at the back end of their site—to deal with things like monthly payments to you and having their invoices emailed to their proper address and things like that?

Hi
Your client would need to pay the due invoices , they can pay with the payment form that you are receiving while login to site admin section.
Also ask your client to submit a ticket to support team for changing invoice email address , so that invoice should be received by them.
Thanks,
Sanjit

How can one develop "view only" client applications in Lookout?This is to develop remote monitoring without control functionality.

How can one develop "view only" client applications in Lookout?This is to develop remote monitoring without control functionality.
We have 10 Client Nodes in the field and we need two "View Only" functionality in Client machines located on Supervisory Desks.

I have done this. There are many ways to approach this but I will offer what I think is the easiest. This will work ONLY if you have been assigning security levels to your objects (objects that actually control devices in the field) greater than zero AND allowing a security level of zero to view all panels. When I develop interfaces I do this just for creating a non control client.
Basically, you remove all users from the Lookout client in the user manager. You will not be able to remove the built-ins, "Guest" and "Administrator". Now when the end users tries to login using his normal login he will be denied. Consequently, he will not be able to control. But, he will still be able to view all the information since a no login can view a panel with a viewing se
curity level of zero. You must ensure any pushbuttons that are used to open panels have a security level of zero.
Now you can copy this security profile by finding the lookout.sec file and copying it to another non-control client computer. In Windows NT this file is located in the system32 directory.
There are many other ways but I find this the easiest.
Regards,
Tommy Scharmann

About the error: "The account is not authorized to login from this station" when you access NAS devices from Windows 10 Technical Preview (build 9926)

Scenario:
With the release of Windows 10 Technical Preview (build 9926), some users may encounter an error message of “The account is not authorized to login from this station” when trying to access remote files saved in NAS storage. In
addition, the following error log may also be found via Event Viewer:
Rejected an insecure guest logon.
This event indicates that the server attempted to log the user on as an unauthenticated guest but was denied by the client. Guest logons do not support standard security features such as signing and encryption. As a result,
guest logons are vulnerable to man-in-the-middle attacks that can expose sensitive data on the network. Windows disables insecure guest logons by default. Microsoft does not recommend enabling insecure guest logons.
Background:
The error message is due to a change we made in Windows 10 Technical Preview (build 9926) which is related to security and remote file access that may affect you.
Previously, remote file access includes a way of connecting to a file server without a username and password, which was termed as “guest access”.
With guest access authentication, the user does not need to send a user name or password.
The security change is intended to address a weakness when using guest access. While the server may be fine not distinguishing among clients for files (and, you can imagine in the home scenario that it doesn’t
matter to you which of your family members is looking at the shared folder of pictures from your last vacation), this can actually put you at risk elsewhere. Without an account and password, the client doesn’t end up with a secure connection to the server.
A malicious server can put itself in the middle (also known as the Man-In-The-Middle attack), and trick the client into sending files or accepting malicious data. This is not necessarily a big concern in your home, but can be an issue when you take your
laptop to your local coffee shop and someone there is lurking, ready to compromise your automatic connections to a server that you can’t verify. Or when your child goes back to the dorm at the university. The change we made removes the ability to connect
to NAS devices with guest access, but the error message which is shown in build 9926 does not clearly explain what happened. We are working on a better experience for the final product which will help people who are in this situation.
As a Windows Insider you’re seeing our work in progress; we’re sorry for any inconvenience it may have caused.
Suggestion:
You may see some workarounds (eg. making a registry change restores your ability to connect with guest access).
We do NOT recommend making that change as it leaves you vulnerable to the kinds of attacks this change was meant to protect you from.
The recommended solution is to add an explicit account and password on your NAS device, and use that for the connections. It is a one-time inconvenience,
but the long term benefits are worthwhile. If you are having trouble configuring your system, send us your feedback via the Feedback App and post your information here so we can document additional affected scenarios.
Alex Zhao
TechNet Community Support

Hi RPMM,
Homegroup works great in Windows 10 Technical Preview (9926 build), when I invited my Windows 10 Technical Preview (9926 build) joined in HomeGroup, I can access the shares smoothly:
My shares settings is like this:
Alex Zhao
TechNet Community Support

Error when importing a Transport request in CHARM???

Hi all,
when i am trying to import a transport a request( thru CHARM) , its throwing an error " No valid system specified (Q11)" and "Import error: Check TMS Alert Viewer in target system"
Note::I was able to create a Transport request , release it but facing problem while importing to quality system.development system is ECC5.0 and quality is ECC6.0
rgds,
Anand

HI abhi,
i havecreated the domain link, my ECC5.0 and ECC6.0 are in one domain of which ECC5.0 is domain controller,now i configured Solution manager as new domain controller and created a link between these two domains...
now my queries are:
1.is it enuf if i create a link between or even shud i create som transport routes between the newly added system from other domain and the existing domain
2.i am not able to see the STMS configuration in solution manager system.ie in my ECC5.0 system( domain ctrller)if i goto STMS->Overview menu-> transport routes i see the configuration, which i cannot see by logging into solution manager and wentto STMS->Overview menu-> transport routes i dont see
rgds,
Anand

Autoreaction doesn't work from client 000 but works from other clients

Autoreaction doesn't work from client 000.
More details coming.   Having trouble getting the thread to post.

We set up a new local auto-reaction.   This is not a central auto-reaction. The auto-reaction writes a
message to the UNIX system log /var/adm/messages when a "Security"
alert i.e. - Logon, RFCLogon, TransactionStart, etc. occurs.
The RZ20 alerts are being properly generated and can be seen in both
the CEN system and the local system. On the local system if I view
all alerts for the MTE using transaction RZ20 and select one of the
alerts and choose Edit -> Nodes ( MTE ) -> Start methods -> Start auto-
reaction method. The auto-reaction writes the message to the UNIX
system log. If I execute the same procedure in client 000 nothing is
written to the UNIX system log.
I've also tried triggering a new alert and running SAPMSSY8 from SE38
while the alert is still in status ACTION_REQUIRED. If I do this from
client 010, an entry is written to the unix system log. If I do this
from client 000, nothing is written to the unix system log. In both
cases, the status of the alert changes from ACTION_REQUIRED to ACTIVE.
Since the System Cyclic program ( SAPMSSY6 ) that triggers SAPMSSY8
always runs in client 000, the auto-reaction never writes the messages
to the UNIX system log.
I have been working on this issue for days. There are several posts and notes relevant to a similar situation with e-mail alerts that are not working from client 000 because SAPCONNECT is not set up in client 000.   However, this auto-reaction does not send an e-mail, so SAPCONNECT set-up should not be necessary.   I've searched Service Marketplace and could not find any notes that resolved the problem either.
I've also checked CCMS Self-Monitoring and cannot find any alerts or errors relevant to this problem.
Does anyone know why the auto-reaction only works from a client other than client 000?
Best regards,
Dave

CHARM - avoid developer login to client 000 when import to QA system

Similar Messages

Maybe you are looking for