Solution Manager Client copy

We finished client copy from 000 to 900 with profile SAP_CUST in Solution Manager.
If we copy only user accounts from 001 to 900, this will overwrite what ever we did with SAP_CUST profile ?

No. If you use SAP_USER profile only the user master will be over written.
Thanks,
Naveed

Similar Messages

Solution Manager client settings (modifiable vs. not modifiable)

Does anyone know if Solution Manager 7.1 allows changes to the following object? Everytime we want to make a change to our template we need to open our Production system. This is a tedious task due to audit compliance.
System setting does not allow changes to be made to object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Message no. TO128
Diagnosis
The system and namespace change option set for this SAP System does not allow any changes to be made to object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.
System Response
Editing is terminated, the object can only be displayed.
Procedure
If you want to edit the object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA in this SAP System, have your system administator set the SAP System to "modifiable" for this object.
This can affect the modifiability of the namespace &1 or the namespaces that correspond to the pattern &1, as well as the global setting of the system change option.
The system change option is set using the Transport Organizer tools (Transaction SE03). Expand the Administration node and execute the program Set system change option. The options are described there.

Does anyone know if Solution Manager 7.1 allows changes to the following object? Everytime we want to make a change to our template we need to open our Production system. This is a tedious task due to audit compliance.
System setting does not allow changes to be made to object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Message no. TO128
Diagnosis
The system and namespace change option set for this SAP System does not allow any changes to be made to object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA.
System Response
Editing is terminated, the object can only be displayed.
Procedure
If you want to edit the object SHI3 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA in this SAP System, have your system administator set the SAP System to "modifiable" for this object.
This can affect the modifiability of the namespace &1 or the namespaces that correspond to the pattern &1, as well as the global setting of the system change option.
The system change option is set using the Transport Organizer tools (Transaction SE03). Expand the Administration node and execute the program Set system change option. The options are described there.

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

Confiuration of ides system in to the solution manager

Hi .
   We now installed new R/3 IDES server . Now we want to configure this new server into the solution manager maintenance optimizer . Kindly give me the steps for this configuration ..
Regerds
Selvan

Hi Ragu
         We already installed the new solution manager 4.0 server and IDES . Now we want to enable maintenance optimizer in our solution manager . As per one note i have to create one request as give n below .
     Create a new transport request (transaction SE09) in the source client of your Solution Manager system. Unpack the SOLMAN40_MOPZ_TTYP_SLMO_000.zip file from the attachment to this note. Copy the contents of the SOLMAN40_MOPZ_TTYP_SLMO_000.txt file into the transport request. Use transaction SCC1 to import the transport request into your Solution Manager client.
As per the above mentioned note , iam not able to attach the SOLMAN40_MOPZ_TTYP_SLMO_000.txt file in the tcode SE09 .
KIndly give the note for do this ,
selvan

SAP EHP1 for Solution Manager 7.0 - Post Install Procedure

Hello Folks:
I completed Sol Manager 7.0 EHP1 installation on Win 2008 R2 with MS SQL in a sandbox environment. This is the first time I ever installed SAP on my own and i am in the process of performing post installation steps from Installation Guide.
In the install guide, there is no mention of creating a new client ex: 100. Could you please, provide a list of tasks that generally needed to perform after the installation is completed and before doing any configuration in Solution manager.
I have some very basic idea on the Basis but while going thru Installation Guide I am not sure if there any steps that generally need to perform to complete the installation. My goal is to complete the Sol Mgr installation first and then start preparing for ECC 6.0 Installation.
Thanks a lot in Advance.

Hi,
First - the basic post installation steps are:
1. sick t-code need to execute
2. se06 --> Perform Post-Installation Actions
3. RZ10 --> Utilities --> Import profiles --> Of active servers
4. execute sgen T-code --> This will take some time
5. setup STMS
6. create client (If custom required)
7. Take backup of the system
For the solution manager client you could use the default created '001' client.
Next you need to run the solman_setup template which 'sets up' the SolMan for usage.
Follow config guide at: https://service.sap.com/~sapidb/011000358700000308502009E.PDF
For installing the ECC system, only a install key(from SMSY) is to be generated from SolMan. But if you want to use the SolMan effectively, suggest you to run the entire solman_setup.
Regards,
Srikishan

E-approvals in Solution Manager

Hi,
Im a Solution Manager working in a Telco Company in Sri Lanka. Currently when providing additional authorization or creating a new user in SAP, we require the user to fill out a form and attach the scanned copy to the Solman request. Is there any way we can have the form within Solution Manager (soft copy) and require them to obtain e-approvals or electornic signatures?
Please let me know the possibility of configuring the above.
Thanks & Regards,
Savindi

Hi
As David said we can attach the doc in the solutiom manager with in the ticket, but the challenge is hw it get digitally signed.
May be the below link could help you [http://help.sap.com/saphelp_nw04s/helpdata/en/23/c8b4cb4b3847a9bc32fe100f368411/frameset.htm|http://help.sap.com/saphelp_nw04s/helpdata/en/23/c8b4cb4b3847a9bc32fe100f368411/frameset.htm]
Better try to post the same query under the Forum of FORMS releated.
Thanks,
Jansi

SAP Solution Manager - authorizations

Hello!
Is there any functionality in Solution Manager for
1. Adjust user rights per project
- example:
User1 has access in Project1 but no access to Project2 in same Solution Manager client
2. Adjust user rights per part of project structure
- example:
User1 has access in Business scenario1 of Project1 but no access to Business scenario2 of Project1
3. Adjust user rights per document belonging into project
- example:
User1 has access in Document1 of Process step1 of Project1 but no access to Document2 of Process step1 of Project1

Thanks for the tip!
What I was searching for was not in Change Request Management but more like Project Administration. It was found from the Solution Manager library help in Assign Authorization for Documents:
"You can control the access rights to documents in the project by assigning authorizations for groups of documents, e.g. you can specify that only the project management can change documentation templates. The system saves Solution Manager project documents in Knowledge Warehouse folders. Access to Knowledge Warehouse folders is controlled by the authorization object S_IWB, which is in the roles SAP_SOL_KW_ALL and SAP_SOL_KW_DIS, and in the Solution Manager Composite Rolles.
You have role (transaction PFCG) and user maintenance authorization..."
So, thanks for the guidance .

Setup and Configuration for a Solution Manager instance

I am setting up a Solution Manager instance for a client in Australia.
Currently there is no reference client that I am aware of in Australia for Solution Manager. So this is extremely important to get it right. Also I am an independent contractor, so I am unable to call on any in-house experts from a consulting firm for help.
So I am looking for answers from some experts who have done this before.
Had some training on Solution Manager back in 2002.
Our client wants to setup the solution manager instance to monitor 9 SAP instances
- 3 R/3, DEV, Q/A, PROD
- 3 BI, DEV, Q/A, PROD
- 3 Enterprise Portal, DEV, Q/A, PROD
Solution Manager is running in a separate instance for all those listed above.
In addition to the above the client would also like to user the service desk function of Solution Manager for in-house support of SAP, and push to service desk request onto their support partner and/or SAP directly.
Question:
1) Is it better to use the Solution Manager client 001 or create a separate client for the customer?
2) How would you as the expert configure the service desk component to push service desk requests to the support partner (a 3rd party Service Desk Tool or another Solution Manager instance), and allow the customer to choose to send the request direct to SAP?
3) The client would also like to use the Solution Manager Instance as the CUA environment, is this advisable?
Kind Regards
David Cooper

Hello David,
Please find th answers below:
1. You should use a separate client for solution manager rather than using a standard one
2. You should configure your solution manager as the service desk for all type of support requests.Solution manager can send your requests to SAP and vice-vera.Why do you a third part tool and waste money of the client.Solution manager can do all for you very effectively
3.sure you should configure solution manager as CUA environment,there are no issues with that
Let me know of any questions
Rohit

Solution Manager 4.0 client copy

Hi all,
We have installed solution manager 4.0 SP 12. We have also done a client copy from 001 to 100 in order to work exclusively in the client 100. I have also changed the client reference in RSADMINA table and the UME from 001 to 100. Finally, when I wanted to implement Solution Manager Diagnostics, I have run the "Setup Wizard" and it created automatically the RFC destination "WEBADMIN" but with client 001. I tried to check everywhere where the old client is still mentioned in both ABAP and Java parts, but no way. Could you tell me please if I forgot something to do after the client copy? Where can I change definitively the reference of the old client?
Thanks in advance for your action.
Regards,

Did you use client 000 as your source client (001 as the user master)? You should not client copy from source 001 as of solman 4.0.
Reference point 6 of note: 1041351
https://service.sap.com/sap/support/notes/1041351
Thanks.
Edited by: Phil May on Aug 26, 2008 7:07 PM

Client Copy for Solution Manager

Hello!
I need to know for the client copy phase , which clients do I need to copy from , for Solution manager 40 SR3.
Regards

ABAP
- SCC4: create a new client
- SCCL: copy client 000 with profile SAP_ALL to new client
- SCCL: copy client 001 with profile SAP_USER to new client
- PFCG: generate the profile for SAPJSF
JAVA
- Change the ABAP Client for UME with config tool
... reboot your server

Client Copy Solution Manager Enhacement Package 1

Hello solman experts!
I'm going to install SolMan EHP1 (SPS20). I'm preparing execution plan for installation. Now I have problem in step sequence.
Should I make client copy first and then run tamplates for initial configuration (from SOLMAN_SETUP)?
When I installed PI 7.1 I made client copy before template run (I checked note 1309239). But for SolMan I didn't find any information regarding SolMan client copy and template (and also SOLMAN_SETUP) sequence.
Do you have any ideas?

Make copy before customization

Unable to copy hidden package "Configuration Manager Client Package" to local DP

Content status lists it as successfully distributed to all DPs (including the local site server)
However, component status for SMS_DISTRIBUTION_MANAGER continually logs these events:
Distribution Manager failed to process package "Configuration Manager Client Package" (package ID = CDW00001).
Possible cause: Distribution manager does not have access to either the package source directory or the distribution point.
Solution: Verify that distribution manager can access the package source directory/distribution point.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
Possible cause: There is not enough disk space available on the site server computer or the distribution point.
Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
Possible cause: The package source directory contains files that might be in use by an active process.
Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
NOTE: It appears to not be any of these causes.
If I look at the smsdpmon.log on the server in question, the following is logged every half hour:
Intializing DP Monitoring Manager...    SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting monitoring thread priority SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting content library root path SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting site code SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting algorithm ID SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to find algorighm ID from registry. Use default algorithm. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting DP Cert Type SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to find DP cert type from registry. Use default type. SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Getting this DP NALPath SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to create certificate store from encoded certificate..
An error occurred during encode or decode operation. (Error: 80092002; Source: Windows) SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
Failed to initialize DP monitoring object. Error code: 0x80092002 SMS_Distribution_Point_Monitoring 1/2/2013 1:29:45 PM 2840 (0x0B18)
distmgr.log shows the following:
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANY.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.109 2013 ISTR0="CDW00001" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Retrying package CDW00001   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
No action specified for the package CDW00001.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Start validating package CDW00001 on server ["Display=\\BRICK-CONFIGMGR.corp.COMPANY.com\"]MSWNET:["SMS_SITE=CDW"]\\BRICK-CONFIGMGR.corp.COMPANYNAME.com\...   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Failed to start DP health monitoring task for package 'CDW00001'. Error code: -1   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Updating package info for package CDW00001   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Only retrying local DP update for package CDW00001, no need to replicate package definition to child sites or DP info to parent site.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
StoredPkgVersion (2) of package CDW00001. StoredPkgVersion in database is 2.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
SourceVersion (2) of package CDW00001. SourceVersion in database is 2.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BRICK-CONFIGMGR.corp.COMPANYNAME.com SITE=CDW PID=2212 TID=2124 GMTDATE=Wed Jan 02 19:29:45.213 2013 ISTR0="Configuration Manager Client Package" ISTR1="CDW00001" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CDW00001"   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Failed to process package CDW00001 after 41 retries, will retry 59 more times   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Exiting package processing thread.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:45 PM   2124 (0x084C)
Used 0 out of 3 allowed processing threads.   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:50 PM   3784 (0x0EC8)
Sleep 1825 seconds...   SMS_DISTRIBUTION_MANAGER   1/2/2013 1:29:50 PM   3784 (0x0EC8)

Both errors are certificate related. Is there anything special about your configuration such as special ACLs on the certificate store or FIPS compliance mode (see
http://support.microsoft.com/kb/811833) being enabled?
Nothing special with certificates; I've used the basic stuff for intranet management of clients.
The only related thing I can think of that may have affected this, is that I discovered earlier today that my MP installation got hosed (error 500) due to a broken client install on the site server itself. I uninstalled the client manually and the server
(as indicated by the component status views) appears to have repaired the MP install. Perhaps it didn't repair it completely? Would a site reset do me any good?

Copied Business Role in Solution Manager ITSM

Hi All
This is eunhwa.
I have a question regarindg copied business role in Solution Manager ITSM.
To copy business role, I copied technical roles Navigation profile, configuration key and PFCT Role ID. And then I copied
a business Role. And assign copied technical roles to copied business role.
And I changed Direct link group UI. For example, in copied business role ZSOLMANPRO, There were many
direct links, I only left ‘incident’ and ‘problem.
However when I selected incident’ in direct link, there was no transaction ‘zmin’ assign. I couldn’t create a incident.
Why this error happened? Is there anything which I miss?
Thanks.
Best Regards,
Eunhwa Park

Hi,
Well, there are multiple things you can check.
1. If you are using IE
You have to add the page/pop-up to the compatibility mode of your Browser.
IE -> EXTRAS -> Settings for Compatibility Mode -> Add -> Refresh the CRM WEB UI
2. Check if you had assign SM-CREATE in the ZSOLMANPRO Navigation profile. (In Assigning the direct link groups to Nav. Bar profile.
3. Check whether you had authorizations for ZMIN in PFCG profile.
4. Additionally check
1905448 - How to restrict the suggested transaction codes when creating an ITSM
Incident using CRM Web UI - Solution Manager
5. In define transaction types corresponding transaction types are active. (In SPRO under solman ->Capabilities->ITSM-> Transactions)
6. Check the copy control whether they are fine. (In SPRO under solman ->Capabilities->ITSM-> Transactions)
7. Ensure that the transaction type's channel definition in customizing is set to 'CRM Web-Client UI'
If your issue is still not resolved yet, please paste the error/screen you are getting.
Regards
Rishav

New Client in Solution Manager 4.0

Hi Gurus,
i need make a new client copy in Solution Manager 4.0 and I had made a entry also in SCC4 but after that entry when I am trying to login with sap* & pass in that new client.
It is not allowing me to login it is saying "wrong user or password repeat logon".
Please Help gurus... is there any change in solman on user name & password.
Thanks
Kamal

Hello Kamal,
Did you do this?
1. Create a client in SCC4
2. Log off from the system.
3. Logon to the new client with user SAP*, password PASS
4. Go to SCC3:
Source: Client 000
Source User: Client 001
Target: Your new client
Profile : SAP_ALL
Delete the profile parameter 'login/no_automatic_user_sapstar' when you have created the first user in the new client. Restart the system to make the changes effective.
See: SAP note 806819.
Best regards,
Dolores

Create new client in Solution Manager?

I finished installing Solution Manager 4.0 sp1 for the first time and have the default clients of 000, 001, and 066. I can log on with the SAP* user. I'm a little confused about the next step. Do I create an addtional client (For example, 100) just like a production or development system to use for users, RFC connections, etc.?
Or do I use one of the default clients?

Hi Carl,
As always... the golden rule applies to SOLMAN as well. Never touch the default clients. Have a client copy and then perfrom all the actions from and ON the Copied client. Get going with SCC4 for a new SOLMAN client :).. atleast thats what we follow here as a practice.
All thebest
Br,
Sri
Award points for helpful answers

Solution Manager Client copy

Similar Messages

Maybe you are looking for