SolMan configuration - Message type "e" is unknown

Hi all,
every time i select the step 6.6 (Connect Diagnostics Agents to Solution Manager) of the System Preparation in SolMan 7.1 SP11 i receive the following message (and related dump in ST22).
Message type "e" is unknown.
Same thing happens in two different Solution Manager (same version and SPS).
Looking for SAP Notes without help.
Any suggestions?
Regards.

Hello guys,
We have a similar issue.
Here is why we got to this error. When i setup the SLD in step 6.1 i used another system, and the Solution Manager was non existent in that SLD/LMDB.
I now configured a local SLD in 6.1 and created a local LMDB.
I am now running the synchronization again ( which as you know takes a while ).
Probably the easiest way would have been just to define the system in the first LMDB, but in our case it's a development system and i wanted to try this also.
I will let you know after the sync is finished.
Catalin

Similar Messages

JMS sender adapter : message type null is unknown, payload cannot be read

Hello,
We are building a scenario Weblogic -> PI through a JMS adapter, but we are getting the following error in the adapter :
2009-09-29 12:09:58     Information     New JMS message with JMS message ID ID:P<450046.1254218997063.0> received. The XI message ID for this message is e705a65f-3cf6-472a-3675-b04e9862ce45.
2009-09-29 12:09:58     Warning     JMS message ID:P<450046.1254218997063.0>: message type null is unknown, payload cannot be read and will be empty!
2009-09-29 12:09:58     Warning     JMS message ID:P<450046.1254218997063.0>: Payload empty or cannot be read.
2009-09-29 12:09:58     Information     JMS Message was converted to XI message succesfully.
Despite the fact that the message is not readable, PI creates a message anyway but the payload is empty. It is the same issue as described in this thread :
How to read Java Object message from JMS Queue using JMS Adapter .
But there have been no answer there.
We have read many notes but none are relevant, any ideas ????
Many thanks,
GL

Hallo,
Have you seen this note:
[Note 837501 - J2EE JMSAdapter: Empty payloads, unknown JMS message types|https://service.sap.com/sap/support/notes/837501]?
Seems it can be either message
a) does not contain any payload and/or
or
b) is not of type TextMessage or BytesMessage
/Jakub

"Message type LIP805 is unknown

hi friends,
i am facing problem with "Message type LIP805 is unknown".
i am saving the MC61 create planing Hierarchy. it is giving the message document created in status bar.
but the message "operation was terminated" getting to inbox.
appricate << removed >> solution.
YSR.
Edited by: Rob Burbank on Nov 13, 2009 1:49 PM

hi goutham,
while creating and saving it is not shwoing any error message.
but while coming out from the screen it is showing "update was terminated ".
ysr.

Message type " " is unknown

Hi Masters
When i try to cancel the subcontracting challan in T code J1IF13, it throws a run time error "Message type " " is unknown" .We discussed with the ABAPer regarding this error.He told that we have to maintain the message type in configuration. Where to maintain the message type for subcontracting challan?
Regards
Mohanraj.C

Use
The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.
The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.
Requirements
Before you continue with this activity, work through the following activities:
Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.
For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.
Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Maintain Output Types.
Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.
Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Assign Forms and Programs.
Maintain the Program, FORM routine, and the form for the output type.
Materials Management -> Inventory Management and Physical Inventory -> Output Determination -> Printer Determination -> Printer Determination by Plant / Storage Location.
Enter the output device that you use.

ALE Configuration for PEXR2002 IDoc and PAYEXT message type sending to XI

Hi all,
I need ALE Configuration for PEXR2002(Basic Type) IDoc , it's message type PAYEXT.
I don't know ALE Configuration for sending data from SAP IDS to SAP XI.????
I need ALE Configuration doc/pdf??
Please give me some guidline for this..
Regards,
Umesh

Umesh,
I was wondering if you have had any luck creating the configuration for PEXR2002 Idoc, PAYEXT message types, and sending the result set to XI.
I need to perform the same task within our R3 environment using the FTP protocol in XI to send the file to the Bank to be processed.
Any help or direction would be great.
Thanks,
Dave

Message type 1 unknown error occuring when clicked on IP workbook button

Hi,
I am working on authorization.
When i click on the save button in an IP workbook button, it throws the message "Message type 1 unknown" saying
that an error occured during communication with bw server, and its gets disconnected.
I have included authorization objects for the planning sequences, planning functions, process chains, also included tcodes for ADP ie rsanwb and tcodes
for ABAP programs. Still we are facing with the same problem.
Please suggest me the solution ASAP and points are awarded.
Thanks.

Hi Suresh,
I guess you have posted your question in the wrong forum.
This forum is exclusively for MDM related queries.Yours looks like a BW or ABAP related question.
Kindly repost your question under the respective forum to get immediate assistance.
Hope It Helps
Thanks & Regards
Simona Pinto

Configuration setting for Message type to take OA print out put

Hi All,
Please let us know how to configure setting for Message type for OA in SD to take print or to get print preview.
Pls let me know .
Regards,
Nagaraj S

hhv

HCM Processes & Forms - Message Type is unknown

Hi,
I have created an HCM process using HCM P&F framework. I can test the process from the ""Test Process" application on the ECC and it works fine. When I launch the process from the portal, I can see the adobe form correctly, the "Check and Send" also goes through fine, but when I click on send I get this error:
Error when processing your request
What has happened?
The URL http://xxxxxxxxxx:8000/sap/bc/webdynpro/sap/ASR_PROCESS_EXECUTE// was not called due to an error.
Note
The following error text was processed in the system SE1 : Message type is unknown.
The error occurred on the application server xxxxxxxx_SE1_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: IF_POBJ_CASE~CREATE_CASE of program CL_POBJ_CASE==================CP
Method: CREATE_LEVEL_DB of program CL_POBJ_LEVEL=================CP
Method: FLUSH_LINKED_LEVEL of program CL_POBJ_LEVEL=================CP
Method: FLUSH_COMMON of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL1================CP
Method: IF_POBJ_PROCESS_OBJECT~FLUSH of program CL_POBJ_PROCESS_OBJECT========CP
Method: SAVE of program CL_HRASR00_PROCESS_RUNTIME====CP
Has anyone else encountered this issue?
Thanks & regards,
Manish

Hi,
I have created an HCM process using HCM P&F framework. I can test the process from the ""Test Process" application on the ECC and it works fine. When I launch the process from the portal, I can see the adobe form correctly, the "Check and Send" also goes through fine, but when I click on send I get this error:
Error when processing your request
What has happened?
The URL http://xxxxxxxxxx:8000/sap/bc/webdynpro/sap/ASR_PROCESS_EXECUTE// was not called due to an error.
Note
The following error text was processed in the system SE1 : Message type is unknown.
The error occurred on the application server xxxxxxxx_SE1_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: IF_POBJ_CASE~CREATE_CASE of program CL_POBJ_CASE==================CP
Method: CREATE_LEVEL_DB of program CL_POBJ_LEVEL=================CP
Method: FLUSH_LINKED_LEVEL of program CL_POBJ_LEVEL=================CP
Method: FLUSH_COMMON of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL=================CP
Method: IF_POBJ_LEVEL_TRANS_HANDLING~FLUSH of program CL_POBJ_LEVEL1================CP
Method: IF_POBJ_PROCESS_OBJECT~FLUSH of program CL_POBJ_PROCESS_OBJECT========CP
Method: SAVE of program CL_HRASR00_PROCESS_RUNTIME====CP
Has anyone else encountered this issue?
Thanks & regards,
Manish

Configuring JMS delivery message type on B2B server

Hi,
I have configured my B2B server to use the JMS delivery channel for the host trading partner by setting the attribute 'Use JMS Queue as default' to true. Now my query is how do one configure the jms message type. Becasue by default the jms message is getting delivered as byte message. I want to change the jms message type to text. Is there a way to configure that?
Regards,
Bp

Hi Nitesh,
I am using the b2b_in_queue in my composite application. Hence i would like to know how to change the jms message type to TEXT? Is this option not possible with the "Use JMS Queue as default" property?
Regards,
Bp

Unknown message type 'Event/SkypeVideoMessage' & Bolding text Issues

Let me start off by saying how great Skype web is- it's much faster and easier to load in the browser. I have noticed two big issues and that is I cannot watch or receive video messages, and when someone bolds a message in Skype for Desktop it doesn't show up quite right.. Video messages come out with this error message: "Unknown message type 'Event/SkypeVideoMessage" As for the bolding issue, basic HTML, just coming out weird... probably a simple fix.

Hi and welcome to the Skype Community,
Thanks for your interest in Skyp for Web and great to hear it's a useful extension for your everyday Skype use.
Indeed the video message conversation event is currently not supported. Also rich text formatting of text is currently not rendering. Support for these features will arrive via the regular updates to Skype for Web in the future.

RFC dump : 'Message type " " is unknown.'

Hi everyone,
I am calling an RFC from one system to another and i am getting a dump with error :
Message type " " is unknown.
When i debugged the program the found that nothing is returned for " MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. "
What should i do to rectify the problems? Please do help.
Thanks In Advance.
Regards,
Heera

ABAP runtime errors    MESSAGE_TYPE_UNKNOWN
       Occurred on     03/05/2008 at 21:56:28
Message type " " is unknown.
What happened?
The current ABAP/4 program "Y_MM_C_CICS_MAT_RECON " h
because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 progra
What can you do?
Print out the error message (using the "Print" functi
and make a note of the actions and input that caused
error.
To resolve the problem, contact your
SAP system administrator.
You can print this message by choosing "Print".
Transaction ST22 allows you to display and manage sho
is especially useful if you want to keep a particular
Error analysis
Only message types A, E, I, W, S and X are allowed.
How to correct the error
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"MESSAGE_TYPE_UNKNOWN"
"Y_MM_C_CICS_MAT_RECON " bzw. "Y_MM_C_CICS_MAT_RECON "
"START-OF-SELECTION"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "46B"
Application server....... "fmsap591"
Network address.......... "10.19.196.114"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x IA64 Level 3"
Database server.......... "FMSAP591"
Database type............ "ORACLE"
Database name............ "AI0"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "46D"
Created on............... "Jul 30 2007 00:11:29"
Created in............... "NT 5.0 2195 Service Pack 2 x8
Database version......... "OCI_920_SHARE__OCI_7_API "
Patch level.............. "2335"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.0.5.., ORACLE 8.0.
8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 1
SAP database version..... "46D"
Operating system......... "Windows NT 4.0, Windows NT 5.
Windows NT 5.2, , System build information:,
                                      , LCHN : 921411"
User, transaction...
Client.............. 250
User................ "HPRAMANX"
Language key........ "E"
Transaction......... "SE38 "
Program............. "Y_MM_C_CICS_MAT_RECON "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP/4 program "Y_MM_C_CICS_MAT_RECON " in
"START-OF-SELECTION".
The main program was "Y_MM_C_CICS_MAT_RECON ".
The termination occurred in line 371
of the source code of program "Y_MM_C_CICS_MAT_RECON " (when calling the editor
3710).
Source code extract
003410       r_lgort-sign = 'I'.
003420       r_lgort-option = 'EQ'.
003430       r_lgort-low = x_storeloc_wa-ecc_st_locn.
003440       APPEND r_lgort.
003450     ENDLOOP.
003460
003470
003480   *CALL RFC TO GET MATERIAL DATA FROM F PIPE BY PASSING S_MATNR r_werks
003490   *r_lgort S_CHARG AND GETTING THE REQUIRED DATA BACK IN THE TABLE
003500   *I_MCHBF
003510
003520     CALL FUNCTION 'YCICS_MATERIALDATA'
003530     DESTINATION 'FI0250'
003540          TABLES
003550               i_matnr                        = s_matnr
003560               i_werks                        = r_werks
003570               i_lgort                        = r_lgort
003580               i_charg                        = s_charg
003590               i_mchb                         = i_mchbf
003600          EXCEPTIONS
003610               no_data_found                  = 1
003620               material_not_of_type_fert      = 2
003630               invalid_plant_entry            = 3
003640               invalid_stloc_entry            = 4
003650               invalid_plnt_matnr_combi       = 5
003660               invalid_plnt_matnr_batch_combi = 6
003670               invalid_plnt_matnr_batch_stloc = 7
003680               OTHERS                         = 8.
003690     IF sy-subrc <> 0.
003700    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
     >            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
003720     ENDIF.
003730
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 1                             SY-INDEX 0
SY-TABIX 1                             SY-DBCNT 31
SY-FDPOS 0                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+....4
VARI
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40                                          ####00000000000000
                               2222222222222222222200003333333333333322
                               0000000000000000000000000000000000000000
... + 80                          ####################################
                               2222000000000000000000000000000000000000
                               0000000000000000000000000000000000000000
... + 120                      ########################################
                               00000000
                               0000000
SY-MSGV1
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                               0000000000
SY-MSGV2
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               2222222222
                              0000000000
Y-MSGV3
                              2222222222222222222222222222222222222222
                              0000000000000000000000000000000000000000
.. + 40
                              2222222222
                              0000000000
Y-MSGV4
                              2222222222222222222222222222222222222222
                              0000000000000000000000000000000000000000
.. + 40
                              2222222222
                              0000000000
_MCHB                         #######################################
                              0000000000000000000000000000900000009000
                              0000000000000000000000004000060000001000
.. + 40                      ####0###0#######ÿÿÿÿ:###########è ####
                              1000300030000000FFFF300000000000EA280000
                              0000020001000000FFFFA000200043008D030000
.. + 80                      x> ####################################
                              7328000000000000000000000000000000000000
                              8E03000000000000000000000000000000000000
.. + 120                      ########################(#######
                              00000000
                              0000000
MCHBWA                      000000000000895405CR01CRA10001    CR01TE
                              3333333333333333334533454333332222453354
                              0000000000008954053201321100010000320145
.. + 40                      ST05####e#########
                              553300006000000000
                              3405000150C000000C
SCHARG_%_APP_%              S_CHARG S_CHARG                       to
                              5544454255444542222222222222222222222276
                              3F3812703F38127000000000000000000000004F
.. + 40
                              2222222222222222222222222222222222222222
                              0000000000000000000000000000000000000000
.. + 80                         @1FQMultiple selection@
                              2224345547676766276666766642222222222222
                              000016C1D5C490C5035C5349FE00000000000000
.. + 120
                               222
                               000
X_MCHBF_WA
                               2222222222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40                      00000000            00000000
                               3333333322222222222233333333222222222222
                               0000000000000000000000000000000000000000
... + 80                      000000 #################################
                               3333332000000000000000000000000000000000
                               0000000000000C000000C000000C000000C00000
... + 120                      ########################################
                               00000000
                               0C00000
I_MCHBF                        ################@#######################
                               0000000000000000400000000000100000000000
                               1000400040004000080050004000080000000000
... + 40                      ################ÿÿÿÿÓ###################
                               1000000000000000FFFFD0000000000000000000
                               0000000000000000FFFF30007000630000000000
... + 80                      ########################################
                               0000000000000000000000000000000000000000
                               0000000000000000000000000000000000000000
... + 120                      ########################8#######
                               00000000
                               0000000
SYST                           ########################################
                               0000000000000000000000000000000000000000
                               0000000010000000000000000000000000000000
... + 40                      ####################ã###################
                               10000000000000000000E0000000000000000000
                               F00000001000000010003000000000000000F000
... + 80                      ########################################
                               0000000000000000000000000000000000000000
                               0000000000001000800000000000000000000000
... + 120                      #######################################
                               00000000
                               0000000
X_MKPFMSEG_WA-BKTXT
                               2222222222222222222222222
                               0000000000000000000000000
%_SPACE
                               0
                               0
X_OUTPUT_WA-BTEXT
                               22222222222222222222
                               00000000000000000000
X_MCHB_WA-MATNR                000000000000895405
                               333333333333333333
                               000000000000895405
X_MKPFMSEG_WA-WERKS
                               2222
                               0000
X_MCHB_WA-WERKSF               CRA1
                               4543
                               3211
X_OUTPUT_WA-WERKS
                               2222
                               0000
X_MCHB_WA-LGORTF
                               2222
                               0000
X_MKPFMSEG_WA-LGORT
                               2222
                               0000
X_MCHB_WA-CHARG                CR01TEST05
                               4533545533
                               3201453405
Active calls / events
No.... Type........ Name..........................
       Programm
       Include                                  Line
     1 EVENT        START-OF-SELECTION
       Y_MM_C_CICS_MAT_RECON
       Y_MM_C_CICS_MAT_RECON                      371
Internal notes
The termination occurred in the function "ab_jmess" of the SAP
Basis System, specifically in line 1083 of the module
"//bas/46D/src/krn/runt/abdynpro.c#22".
The internal operation just processed is "MESS".
The internal session was started at 20080305215621.
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App       : disp+work.EXE (pid=24072)
When      : 3/5/2008 21:56:28.0
Threads   : 2
Computer Name       : FMSAP591
User Name           : ai0adm
Number of Processors: 2
Processor Type: ia64 Family 31 Model 1 Stepping 5
Windows Version     : 5.2 Current Build: 3790
Stack Dump for Thread Id 56f4
FramePtr         ReturnAd         Param#1          Function Name
00000000083a0c00 0000000076eab530 00000000000024f4 kernel32!GetDateFormatW
00000000083a0bd8 000000000215a7c0 00000000000024f4 kernel32!GetDateFormatW
00000000083a0b88 000000000067fe80 0000000000000080 disp+work!
000000001c1b0040 0000000076ea7420 0000000000212e50 MSVCRT!tanhf
000000001c1b0000 0000000000000000 000006fb7eb36e88 kernel32!GetDateFormatW

Message type " " is unknown. Transaction J1IF13

Dear all,
When i am executing transaction J1IF13 for Subcontracting i am getting this error "Message type " " is unknown."
i want to cancel the transaction
Regards
Amey

Closed

RealVNC gives unknown message type 167

I'm trying to use the RealVNC viewer from a Windows machine to talk to a Mac running OS X 10.4.3 and Apple Remote Desktop. It almost works, and in fact one time it did work, but on every subsequent attempt, I get "unknown message type 167." The message comes up after I give the VNC password, and while the screen is initially drawing. Every other VNC viewer I've tried also fails to connect.

Hey man! Here is a list of the mappings between Java and Flex classes in blazeds:
http://livedocs.adobe.com/blazeds/1/blazeds_devguide/help.html?content=serialize_data_3.ht ml
And here is a post in another forum, with a guy with your same problem:
http://www.experts-exchange.com/Web_Development/Web_Languages-Standards/Flex/Q_26185302.ht ml
I would use Object in Flex, and map it to a Map in Java.

Error after slave switch replacement - %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529

Hi guys.
We replaced a slave switch recently and error messages appear only after we connect the tenG fiber and 1 utp. Prior to the replacement there was no such errors.
I searched online and it seems like my problem is similar to Bug ID: CSCty07602 but I am using version 15.0(1)SE3 that should be a fixed version.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtt42626
------------------ show version ------------------
Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 15.0(1)SE3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Wed 30-May-12 13:41 by prod_rel_team
ROM: Bootstrap program is C3750E boot loader
BOOTLDR: C3750E Boot Loader (C3750X-HBOOT-M) Version 12.2(58r)SE, RELEASE SOFTWARE (fc1)
B1-1-ADM-R18-3750-S01 uptime is 1 year, 22 weeks, 3 days, 2 hours, 59 minutes
System returned to ROM by power-on
System restarted at 11:28:38 SGT Fri Jun 8 2012
System image file is "flash:/c3750e-universalk9-mz.150-1.SE3/c3750e-universalk9-mz.150-1.SE3.bin"
Errors
097029: 000055: Nov 11 16:22:31: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1456 (B1-1-ADM-R18-3750-S01-2)
097030: 000056: Nov 11 16:22:36: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1456 (B1-1-ADM-R18-3750-S01-2)
097031: 000057: Nov 11 16:26:10: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1444 (B1-1-ADM-R18-3750-S01-2)
097032: 000058: Nov 11 16:26:15: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1444 (B1-1-ADM-R18-3750-S01-2)
097033: 000059: Nov 11 17:06:08: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 60 (B1-1-ADM-R18-3750-S01-2)
097034: 000060: Nov 11 17:06:13: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 60 (B1-1-ADM-R18-3750-S01-2)
097035: 000061: Nov 11 18:32:19: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1458 (B1-1-ADM-R18-3750-S01-2)
097036: 000062: Nov 11 18:32:24: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1458 (B1-1-ADM-R18-3750-S01-2)
097037: 000063: Nov 11 21:36:02: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1456 (B1-1-ADM-R18-3750-S01-2)
097038: 000064: Nov 11 21:36:07: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1454 (B1-1-ADM-R18-3750-S01-2)
097039: 000065: Nov 11 21:36:13: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1454 (B1-1-ADM-R18-3750-S01-2)
097040: 000066: Nov 12 07:08:14: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1442 (B1-1-ADM-R18-3750-S01-2)
097041: 000067: Nov 12 07:08:19: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1442 (B1-1-ADM-R18-3750-S01-2)
097042: 000068: Nov 12 07:08:24: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1442 (B1-1-ADM-R18-3750-S01-2)
097043: 000069: Nov 12 07:08:34: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1442 (B1-1-ADM-R18-3750-S01-2)
097044: 000070: Nov 12 07:40:35: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 81 (B1-1-ADM-R18-3750-S01-2)
097045: 000071: Nov 12 07:40:40: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 81 (B1-1-ADM-R18-3750-S01-2)
097046: 000072: Nov 12 09:58:20: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1454 (B1-1-ADM-R18-3750-S01-2)
097047: 000073: Nov 12 09:58:23: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1457 (B1-1-ADM-R18-3750-S01-2)
097048: 000074: Nov 12 09:58:29: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1455 (B1-1-ADM-R18-3750-S01-2)
097049: 000075: Nov 12 09:58:34: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1455 (B1-1-ADM-R18-3750-S01-2)
097050: 000076: Nov 12 11:50:50: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1458 (B1-1-ADM-R18-3750-S01-2)
097051: 000077: Nov 12 11:50:55: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 60 (B1-1-ADM-R18-3750-S01-2)
097052: 000078: Nov 12 11:52:09: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1445 (B1-1-ADM-R18-3750-S01-2)
097053: 000079: Nov 12 11:52:14: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1445 (B1-1-ADM-R18-3750-S01-2)
097054: 000080: Nov 12 12:58:52: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1452 (B1-1-ADM-R18-3750-S01-2)
097055: 000081: Nov 12 12:58:57: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 1452 (B1-1-ADM-R18-3750-S01-2)
097056: 000082: Nov 12 13:53:34: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 60 (B1-1-ADM-R18-3750-S01-2)
097057: 000083: Nov 12 13:53:39: %PLATFORM_IPC-3-COMMON: Unknown IPC message type 45529 size 60 (B1-1-ADM-R18-3750-S01-2)

I am using version 15.0(1)SE3
Use 15.0(2)SE4 instead. 15.0(1)SE and higher are full of bugs.

Regarding Solman7.1 message type

Hi, Expert
We've build Solman7.1, but we will needed to change the existing message type in solman
to old message type SLFN.
If that is possible, could you kindly provide the step by step guide ?
Thank you !

Hi Takashi,
Yes instead of SIVA ..the standard delivered transaction type for VAR is SMIV in 7.1
please create a copy of SMIV to ZMIV or YMIV and then customize as per your requirement.
I would also recommend you to attend one EGI for this if possible. The EGI for this is really good and covers almost all the important queries w.r.t to this. Search SMP for EGI calendar.
In addtion, there is a new concept of business roles and sap delivered some out of box like SOLMANPRO and SOLMANREQU etc
kindly check my below blogs which might help you to customize/configure the interface as well.
Quick Tip : Customizing Business Role in Solution Manager 7.1 ITSM Part 1
Quick Tip : Customizing Business Role in Solution Manager 7.1 ITSM Part 2
hope this resolves ur doubt...All the best
Regards
Prakhar

SolMan configuration - Message type "e" is unknown

Similar Messages

Maybe you are looking for