Error whiel activating cross system object lock

Hi ,
when I am trying to activate the cross system object lock functionality for developement system in tcode /TMWFLOW/CMSCONF from our solman system , it showing the following error
'Error RFC destination SM_SMDCLNT000_TRUSTED: You are not authorized to logon to the target system (error code 1).
Message no. /TMWFLOW/TRACK_N106'
In the above RFC connection the 'Current user' is provided.
Can anyone please let me know what I am missing in this?

Hi Farzan,
I dont have autorization in Client 000 of SMD system thats why its giving authorization error but when I am trying to activate the object locking for SMD client 321 why the system is trying to logging into the SMD : 000 can we somewhere modify the RFC conection which needs to be used.
Regards,
Amar Kamat

Similar Messages

Cross System object lock

We have implemented Charm in Solman 7.0 Ehp1. I have activated 'cross system object lock' both globally (report tmwflow/config_services) and in satellite System (tcode- /n/tmwflow/cmsconf). am able to change the same table again which i had edited earlier and stored in TR.
am i missing somewhere.
Thanks

Hello Powai,
Please, check the link below, there you can find good informations about CSOL.
/people/rajiv.jha/blog/2010/08/30/csol-managing-parallel-projects
Best Regards,
Diego Fischer

CSOL Cross System Object Lock - RFC error in satellite system

Hi
We are currently implementing Solution Manager 7.1 (ChaRM) and of the mandatory requirements is to activate Cross System Object Lock.
I have globally activated this in Solman and have gone into /TMWFLOW/CMSCONF to activate for our development client. This is now activated.
A transport has now been created in ChaRM and I login to the above mentioned development system and make a customizing change. I then choose the transport and save change. I am presented with an error:
"Error in RFC SM_DSMCLNT001_BACK to Solution Manager System" (Message No. STMWFLOW025)
I have now been looking at this for a few hours and found OSS Note 824521. However, I have already done all this. From a RFC perspective we have:
SOLMAN:
SM_DSMCLNT001_BACK - works fine in SM59. The assigned user has all the correct profiles.
In transaction SDCCN, the above RFC appears also.
In transaction SM30, table BCOS_CUST, "CHARM_DEST" and "OSS_MSG" are both set to destination NONE.
SATELLITE SYSTEM:
In transaction SDCCN, the above mentioned RFC exists
In transaction SM30, table BCOS_CUST, "CHARM_DEST" and "OSS_MSG" are both set to the above mentioned RFC
The user SMB_DSM for the RFC only exists in Solman and not in satellite system. Don't think this is needed though.
As soon as I deactivate CSOL in /TMWFLOW/CMSCONF in Solman (for development client), I can make changes and the above error (in red) does not appear. However, we needed CSOL working and this error not to appear.
Any suggestions???
Thanks
Shaun

Ok, the resolution was to ensure SMB_X82 (in Solman) has the following roles and profiles:
Roles
SAP_SOLMANTMWCOL
Z_SOLMAN_BACK
Profiles
D_SOLMAN_RFC
S_BDLSM_READ
S_CSMREG
S_CUS_CMP
S_SD_CREATE
S_TMW_ADMIN
This resolved my issue.
Thanks
Shaun

Cross system object lock after SP24 upgrade

Hi Team,
We have recently updated from Sol Man SP23 to SP24. I have set-up cross system object lock (CSOL) in SP23. It was working perfectly.
When we are in SP23, i have made following settings:
In T.code: u201C/TMWFLOW/CONFIG_SERVICESu201D , i have set he conflict analysis as "Cross-Project, Cross-Client". So i that i will always get "Warning" Messge while processing SDHF and SDMJ correction.
In t.code: /n/TMWFLOW/CMSCONF , the CSOL is active.
Recently we have upgraded to SP24. After SP24 upgrade, the CSOL is not working properly. The configurations are same as earlier.(Before SP24). Now if i process SDMJ or SDHF corrections, the CSOL always gives me "ERROR" message but i want to get "WARNING" message as earlier. I have checked the conflict analysis in t.code u201C/TMWFLOW/CONFIG_SERVICES". It is still "Cross Project, Cross-Client" only.
Any additinal SAP notes to be implemrnted to correct this behaviour.
Your valuable guidance required.
Thanks
Kumar

I dont believe this is possible at the moment. As you must be already aware, that SAP releases the locks from the objects as soon as the transport request is released from the Development System. Unless, this locking mechanism is extended to various systems first (DEV and QAS) and later to parallel landscapes (eg:- Project landscapes) it would be difficult to bring in this feature.
Rgds,
Abhijeet Bhagat

ChaRM:Cross system object lock:Ovelapping

Hi Friends,
In SE38, while activating the service "/TMWFLOW/CONFIG_SERVICES", i am seeing following conflict scenarios:
Cross-Project, Client Specifi, Ovelapping
Cross-Project, Client Specifi, Partial Ovelapping
What is the meaning of overlapping? In which scenario it can be used?
Thnaks for your input
PSK

Hi
There is a feature call cross object locking in solman it is used for that
you can check below note for all the available modes
Note 981729 - Cross-system object lock: Alternative lock modes
Hope it solved ur basic doubt
Regards
Prakhar

Cross system object locking -Object editor popup does not show in dev sys

Hi ,
we want to use the cross system locking for r/3 system .
we have done all the configuration required for cross system object locking in central solution manager system and also in development r/3 system .
also we observed that object lock information is avaible in central lock monitor transcation but when ever there is object lcok it does not show us the the popup for object editing.
appreciate your valuable inputs.
Regards,
Amar Kamat

We found the problem.
The structure was being locked by a user in the QA system and overnight the M version finally activated after another transport attempt.
The second structure with this problem was only referenced as a local object (even though it had a proper tech name and package assignment) preventing its activation in the QA system. We needed to hack the query tables to make it look like a proper global structure, then re-transported and it activated.

Cross system object lock -how to build up lock entries for existing request

Hello,
we implemented ChaRM for some years and intend to activate cross system object lock (CSOL), now.
But there are a lot of existing transport requests, which have not been imported to productive system, yet.
It would be very helpful to create lock entries for objects, which are assigned to those transport requests.
Does anyone know any standard report for this purpose?
Thanks a lot for any hint.
Best regards
Horst

If anyone else needs that feature:
Report TMW_TRKORR_LOCK_UPDATE (executed in satellite system) will lock the objects of a transport request in solution manager system.

Charm without Cross system object lock

Dear All,
We have requirement for configuration of Charm without cross system object lock i.e. solution manager will be used for documentation but create, release, import request from the development system itself.
Can we make changes in the functionality and use charm for documentation only?
if anyone has the same requirement can you please let me know steps to be followed.
Thanks in advance
Regards
Sushant

Dear Prabhakar,
Thanks for the reply.
Our project has just gone live and issues immediate resolution is being carried. Charm will integrate with system and training is required for that which at this point of time not possible but at the same time without affecting the issue resolution we want to log the changes in solution manager.
We will use the CSOL feature may be some time later.
At present i have not activate CSOL, still the document doesn't flow through. Document got stuck at "In development" phase and doesn't move forward. It doesn't allow to change the status.
Regards
Sushant

Cross System Object Lock with ChaRM Retrofit

Hi-
I need to know if there is the ability to have a cross system object lock while utiliziing Retrofit within ChaRM. For example I am working with an N, N1 landscape. When I release a transport request in N I need the object to be locked in the N, and N1 (after retrofit) landscapes.
Will this be supported with both Workbench and Customizing requests?

I dont believe this is possible at the moment. As you must be already aware, that SAP releases the locks from the objects as soon as the transport request is released from the Development System. Unless, this locking mechanism is extended to various systems first (DEV and QAS) and later to parallel landscapes (eg:- Project landscapes) it would be difficult to bring in this feature.
Rgds,
Abhijeet Bhagat

ChaRM cross system object lock

Anyone have any experience with the cross system object lock in ChaRM? If so, can I get your thoughts on how well it works and your likes/dislikes?
I read the help.sap.com page. I'm looking fto hear about people's experiences.
regards,
Jason

bump.

Cross system object lock (CSOL)

Hi there,
I am trying to set up CSOL and in the SolMan-help, they talk about the CSOL monitor in SolMan.
But what report or tx do I need to start it ?
PS SolMan 4.0 SP6
"In the central SAP Solution Manager system, the cross-system object lock monitor provides an overview of all current lock entries. The entries are presented in table form, and can be selected if you need to delete them, for example"
regards
Steven

Hi Steven,
the tcode is called /tmwflow/lockmon.
Regards,
uDo

CSOL : No window Cross system object lock displayed

Hello all,
We have configured CSOL in Sol Man ChaRM. But when we test this configuration, any window is displayed to warn us or to inform us that a lock has been created whereas in /n/TMWFLOW/LOCKMON there is a long list of customizing locks entries.
Have we forgot to do something ?
Thanks for your help,
Regards.
Edited by: Changerequestmanager on Nov 22, 2011 11:29 AM

Figured out by myself : because my scenario was irrelevant.
We have chosen a Cross client/project specific scneario but create 2 transports requests in a same project, which was wrong.
Thanks for your help !

Error while activation the Datastore Object

Hi folks,
I am in SAP BASIS, so not aware of BI very much...can u help me in this,
One user is getting error while activation the Datastore Object
below is error log,
(Green) Activation of Objects with Type DataStore Object
(Green) Checking Objects with Type DataStore Object
(Green) Checking DataStore Object DSO_TEST
(Green) DataStore object DSO_TEST is consistent
Table/view /BIC/VDSO_TEST2 (type VIEW) from DataStore object DSO_TEST saved
Change log for DataStore object "DSO_TEST" saved successfully
Writing of object catalog entries (TADIR)
(RED) The creation of the export DataSource failed
(RED) Error during the retrieval of the logon data stored in secure storage
(RED) Error when creating the export DataSource and dependent Objects
(RED) Error when activating DataStore Object DSO_TEST
Thx. in advance
Yash

Hi Yash,
Check out the below thread:
[activation of the Datastore Object.|error in ODS activation/export datasource;
Hope it helps you!
Please reward points if helpful
Manish

Error while creating a system object for R3 in portal

Hi,
I am getting error while trying to create a system object in portal.
Following are the details I used :
Under WAS...
Web AS Host Name :<XXXX>:8001
Web AS path: /sap/bc/bsp/sap/
Web AS protocol : http
Under User management:
Authentication Ticket Type : SAP Logon Ticket
Logon Method :SAPLOGONTICKET
User Mapping Type : admin,user
Under Connector:
SAP Client : <Client NO>
SAP System ID : <System ID>
SAP System No : <System No>
System Type : SAP_R3
While trying with connection test... I am getting like this:
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<FQDN server name>:8001)
5. The host name <FQDN Server Name> was resolved successfully.
6. The server sapdwh01 could not be pinged successfully.
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
It seems that the portal is not able to ping to R3 system. I tried to ping to R3 server from portal server by command prompt. I am able to ping. Also under SICF, I can see ping service as in activated state.
Kindly help.
Regards,
Niraj
Edited by: Niraj Kumar on Dec 11, 2008 10:41 AM

I created a SAP Transactional iView for transaction SE80.
Also, I tried from under System Administration -> Support -> SAP Transaction. It is not working.
Got portal Runtime error :
Portal Runtime Error
An exception occurred while processing your request
Exception id: 12:57_11/12/08_0003_2795650
See the details for the exception ID in the log file.
Regards,
Niraj

Error in Active Directory System Discovery (0x80005010)

Hi,
I've configured Active Directory System Discovery in a SCCM 2007 R2 SP2 configuration. I see several SCCM clients being populated with OU information, but others do not. I've taken a look in the adsysdis.log. There it states for a very large number of computer accounts:
INFO: discovered object with ADsPath = 'LDAP://<domain controller>/<DN computerobject>'
WARN: Could not get property (domain) for system (0x80005010)
Afterwards there is no entry that states a ddr is written for this computer object and the SCCM client object is not populated with information.
Can someone explain what exactly is the issue, and how to solve it?

I got exactly same issue - SCCM 2007 SP2 two primary sites (one central). AD sctructure got one forest and two domains.
Does anyone solved this issue ?
adsysdis.log :
Starting the data discovery. SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
INFO: Processing search path: 'LDAP://CN=COMPUTERS,DC=MY,DC=DOMAIN'. SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
INFO: Full synchronization requested SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
INFO: DC DNS name = 'dc01.my.domain' SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
INFO: search filter = '(&(objectClass=user)(objectCategory=computer))' SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
INFO: ads path = 'LDAP://dc01.my.domain/CN=COMPUTERS,DC=MY,DC=DOMAIN' SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
INFO: Bound to 'LDAP://dc01.my.domain/CN=COMPUTERS,DC=MY,DC=DOMAIN' SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
INFO: discovered object with ADsPath = 'LDAP://dc01.my.domain/CN=TEST1,CN=Computers,DC=MY,DC=DOMAIN' SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
WARN: Could not get property (domain) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
INFO: discovered object with ADsPath = 'LDAP://dc01.my.domain/CN=COMP2,CN=Computers,DC=MY,DC=DOMAIN' SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
WARN: Could not get property (domain) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
INFO: discovered object with ADsPath = 'LDAP://dc01.my.domain/CN=SRV2,CN=Computers,DC=MY,DC=DOMAIN' SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
WARN: Could not get property (domain) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
INFO: discovered object with ADsPath = 'LDAP://dc01.my.domain/CN=SRV3,CN=Computers,DC=MY,DC=DOMAIN' SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
WARN: Could not get property (operatingSystem) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
WARN: Could not get property (operatingSystemVersion) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
WARN: Could not get property (domain) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
WARN: Could not get property (dNSHostName) for system (0x80005010) SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
ERROR: System SRV3 is a unsupported operating system, unsupported version, or malformed AD entry. Reported system type is: (). SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)
WARN: CADSource::ProcessSystemInfo: Failed to get IP Address for the system. SMS_AD_SYSTEM_DISCOVERY_AGENT 19.11.2009 17:11:15 5360 (0x14F0)

Error whiel activating cross system object lock

Similar Messages

Maybe you are looking for